Made for your console. Written for your client's QBR.
Three views from the MSP console: the fleet, the simulator, and the record. Everything below runs on sample data and says so, because we don't fake traction and we don't fake posture.
Accounting · 17 seats91Secure
Real estate · 22 seats74Needs work
Dental · 31 seats62Needs work
Legal · 29 seats48At risk
The heaviest single control on the catalog
It walks straight past MFA. Still a top attack vector.
Standing privilege is standing risk
Two administrators had never registered for MFA, and the Conditional Access policy meant to enforce it was sitting in report-only mode, which looks configured on a screenshot and enforces nothing at all.
Both admins registered, and the policy moved from report-only to enforced. The MFA knockout clears. Privileged access still scores partial, because eleven standing Global Admins is more than the control allows.
Created during an onboarding four days earlier, and nobody would have looked until the next quarterly review. Comparing the signed records surfaced it that week. Because MFA is a knockout control, one unprotected admin puts the whole tenant back at risk regardless of the other twelve.
The account was brought under policy and standing admins were cut to four. Every step above stays in the chain, which is what turns a year of quiet maintenance into something a client can actually read.
Everything the report
stands on.
Fleet posture
Your whole book on one screen. Every tenant scored, ranked by risk, and tracked against the controls that actually decide whether they get breached.
Remediation simulator
Toggle a fix and watch posture and status move in real time. You walk into the QBR knowing which change to sell and what it's worth.
White-label reports
Your logo, your colors, your domain. Your client sees a professional security assessment with your name on it, and never sees ours.
Chained attestations
Every scan anchors to the one before it. Anyone can verify the trail. Nobody can alter it, and that includes us.
Drift detection
Posture changes between scans are caught by comparing signed results. A new admin without MFA surfaces that week, long before it turns into an incident.
Ephemeral engine
The core promise is engineered rather than promised: collection, evaluation, and destruction happen in one breath. You can't leak what you don't keep.
Delegated access
Runs on the delegated admin relationship you already hold. There's nothing to install in your client's tenant, and they can revoke it any time without asking us.
Verified or labeled
A control is pass, partial, fail, or plainly "not verified by this scan." There is no fifth option, and no code path that invents a status the scanner didn't check.
Client-ready output
Every scan exports as the leave-behind your client actually keeps: the monthly document that makes your security line item defend itself at renewal.
All thirteen controls,
weight by weight.
Published in full, including the eleven we cannot verify yet. A knockout control caps the tenant's grade on its own rather than merely costing it points, and a control the scan couldn't reach is recorded as a coverage gap instead of a failure. The version above is stamped onto every attestation, so a result from this catalog stays interpretable after the catalog moves on.
Verification, source by source.
Coverage grows one integration at a time. Until a source is wired up, the controls it would verify are labeled "not verified" rather than estimated.
See it on your own book.
We're working with a small group of MSPs ahead of wider release. Tell us who you are. A founder reads every note.
Request early access