Pricing
How pricing works
We are not going to put a number on this page and pretend it applies to you. What we can do is tell you exactly how the number is built, so nothing in the proposal is a surprise.
Priced per identity
Not per module, not per administrator, not per connection. You are charged for the people and agents you govern — which is the thing you can actually count.
Start with one capability
You do not pay for seven capabilities to use one. Land on recertification, and add the next only when it has earned it.
Same price, either deployment
Running it yourself does not cost more, and it does not cost less. The product is the product wherever it runs.
How we model the savings
Conservatively, and only against the vendors you actually retire. If you keep Okta, we do not put Okta’s licence in the savings column — a lot of consolidation business cases do exactly that, and it is why so many of them collapse under scrutiny at renewal.
We also count the parts nobody invoices you for: the people maintaining the connections between products, and the quarter your team loses to every access review. Those are usually the larger number.
What is included
No pricing traps
The things vendors normally charge extra for, once you have signed and moving is expensive.
Your data, on the way out
Export is a contractual right, not a professional services engagement. Leaving should be cheap, or the rest of what we say about lock-in is theatre.
The audit record
Evidence is the product. We do not sell it back to you as a compliance add-on.
Standards at every edge
Connecting us to what you already own is not a premium tier.
What does cost more
Isolated and air-gapped deployments carry real engineering cost, and we charge for it rather than hiding it in the licence. So does bespoke onboarding, if you want it.