Pricing
Priced by module, not by the seat
Your bill should track what you use, not how many people you hired. A compliance team that grows from two to six should not cost three times as much for the same portal — so there is no per-seat charge anywhere in this product, and nothing counts your colleagues.
Every new account starts with all of it switched on, including the parts you would otherwise have to buy to evaluate. Deciding what to keep is easier once you have seen the whole thing, and a portal with no register and no documents is not a demonstration of anything.
Included in every account
Core Controls
Core Controls — never sold separately
Your control register: what you operate, and your written answer for each control. Every other module maps back to this.
It is always entitled and cannot be switched off, because every other module maps back to it. A tenant that could disable its own register could empty its own portal by accident.
Modules you add
Add them when the work shows up
Each is a separate module with its own price. Entitlement and publication are separate things: holding a module does not put anything on your portal until you decide to publish it.
Evidence
The artefacts behind your answers: attestations, reports, policies, exports. Linked to the controls they support, with a review date.
What it publishes: Documents you have published, at the classification you set. Anything not public stays in the tenant.
Compliance
Framework coverage, derived from your register. Answer a control once and see which requirements it satisfies across the frameworks you report against.
What it publishes: A coverage figure per framework, computed from mapped controls. The figure is derived, so it cannot drift from the register the way a hand-maintained number would.
Audits
The audits and certifications you hold: framework, report type, auditor, period, expiry, and the report itself.
What it publishes: Attestations you have marked public. A public attestation must name its auditor and its period — the database refuses one that does not.
FAQ
Published answers to the questions customers keep asking — written once, readable by everyone, so the next prospect does not have to ask you by email.
What it publishes: Answers you have published. A published entry must carry a written answer and the moment you published it — the database refuses one that does not, so an unanswered question cannot appear here however it was asked.
In every plan
The things we did not put behind a tier
Some capabilities are not upgrades here. Gating them would mean selling a trust portal that cannot be trusted as far as it claims.
How to buy
There is no checkout button yet
We are onboarding the first customers by hand, which means no price list and no card details anywhere on this site. Create a portal, use all of it, and talk to us about price once you have decided it is useful — we would rather earn that decision than bill ahead of it.