Documentation  /  Modules

Reporting

One rendering engine for every document, with your branding and every figure resolving to its source.

One engine

QBRs, executive summaries, compliance evidence packs, invoices, proposals and implementation runbooks all render through the same path. Change the underlying data and every document reflects it.

Your identity, not ours

Client-facing documents carry your branding. Our attribution in the footer is off by default and is a single toggle you control.

Internal documents carry it on by default — it is your platform and you know it. Documents from us to you carry ours.

Chart honesty

  • A gap in the data is drawn as a gap, never interpolated
  • Opposing quantities are never netted into one series
  • Estimated figures are labelled on the chart itself
  • Insufficient data draws nothing rather than a confident line
  • Every point resolves to the rows behind it

SLA as a distribution

SLA attainment renders as a distribution, never a mean. A client who later finds a hidden breach stops trusting every other number on the page.

What didn't happen

The panel no other platform can produce: patches applied before the exploit was public, backups verified by restoring, machines corrected before they drifted. Evidencing an incident that did not occur needs a reconciliation engine.

← Compliance  ·  Client portal →

Not running it yet? Start a thirty-day evaluation — read-only, on your own estate, no card.

Thirty days · read-only · no card

Run it beside what you already have, against your real clients. It tells you what your tools are reporting that is not true.

Start an evaluation