Branded PDF reports for monitoring, security, uptime, and updates - on demand or on a schedule.
Reports are generated as A4 landscape PDFs with your organization branding, a dark executive-friendly theme, and proper typography. They include real charts (not screenshots): performance graphs, security score trends, uptime history, update timelines, and alert summaries. A single PDF can cover one server, a group of servers, or an entire project, and is assembled on demand from the data already stored in your account.
Every report has a type and a time range. Monthly reports summarize the previous calendar month; Weekly reports cover the previous week; Custom reports let you pick any start and end date - useful for post-incident retrospectives or audit evidence for a specific window. The same report template works for all three so the structure is predictable whether you are reading last week's or last quarter's.
Inside each report you choose which sections to include: Monitoring (CPU, memory, disk, network, load), Security (CVE and audit findings), Site Uptime (availability and response time), Updates (what was patched and what is still pending), Alerts (what fired and how long it took to resolve), or the Full report with all of the above. The data is cached as JSON, so regenerating the PDF with a different layout is instant.
On the first of every month Optimux automatically generates the previous month's report for every project so you always have a paper trail without having to remember. The PDF appears in Reports > All Reports ready to download, forward to a customer, or attach to a compliance ticket. Automatic generation is always on - there is no cron job to babysit.
In Reports > Schedules you can set up recurring report schedules that generate and optionally email the PDF to a specific address on the chosen cadence. Typical uses: a weekly ops summary to the engineering channel, a monthly compliance package to the customer, or a daily uptime digest to a stakeholder who does not log into the dashboard. Schedules run on the same reliable queue that powers the rest of the platform.
