Pricing
The shape, not an invented number.
Pricing has two halves: a package for the platform services you run, and metered usage for verification, credential and agent work. This page sets out both in full — the six packages and the six things that are counted. The figures themselves are agreed with our team once your identity mix is known, because that is the only way to quote something that still holds in six months.
The model
Two halves and a contract.
Identity platforms are usually priced badly in one of two directions: everything flat, so the expensive work is cross-subsidised until it is not; or everything metered, so your bill tracks your traffic graph. The structure below splits the difference along the line where the underlying cost actually changes.
A package for the platform
The authentication core and the capabilities your product needs are bought as a package rather than per call. Login volume is a poor proxy for what the platform is doing: a tenant with one application and strict federation requirements can be more work than a tenant with ten simple ones.
Metered trust work
Verifying a person or a company, issuing and checking credentials, and running machine and agent identities each carry a real unit of work behind them. Those are counted, because pretending they are free inside a flat package is how a bill becomes a surprise.
Enterprise terms in a contract
Advanced federation, contractual support and regional placement where it is supported are agreed in an agreement, not configured from a pricing page. If your requirements include any of those, the conversation starts there rather than ending there.
The split follows the architecture rather than the sales conversation. Read how the platform is layered and the same boundaries appear: tenancy and the authentication layer are standing capacity, while verification, credential issuance and evidence work are operations that happen a countable number of times.
Packages
Six packages, named for who they are for.
Each package names an audience and the capabilities it centres on. The audience line is usually enough to tell you which one you are in. Where two of them fit — a scaling product that also runs agent infrastructure, say — the answer is a conversation rather than a tier, because the overlap is exactly the part a fixed table gets wrong.
Build
Developers and early-stage products
- Hosted login
- Application credentials
- Sandbox tooling
- Clear usage accounting
Grow
Scaling SaaS and multi-brand products
- Organizations
- Multifactor authentication
- Federation options
- Webhooks and operations
Business
B2B and workforce customers
- Enterprise connections
- Provisioning
- Organization features
- Support
Enterprise
Complex security and compliance needs
- Advanced federation
- Contractual support
- Custom regions where supported
Trust Services
Usage-based verification and credentials
- Identity proofing
- Business checks
- Credential issuance and verification
Machine & Agent Identity
Infrastructure and agent platforms
- Machine principals
- Agent credential lifecycle
- Validation and audit exports
Two of these — Trust Services and Machine & Agent Identity — are usage-shaped rather than capability-shaped, and they sit alongside a platform package rather than replacing one. The full catalogue lists all 28 services these packages are assembled from, so you can check what a package name is actually standing in for.
Usage
What is metered, and what is not.
Six dimensions, each with a definition you can hold us to. Every one says what the unit is and what it deliberately excludes — a meter defined only by what it counts is a meter you will end up arguing about.
01
Monthly active authenticated identities
People and organization members who authenticated at least once in the month — customers, employees, contractors and partners alike.
Storage is not the meter. An identity record that sat dormant all month is not an active identity, so a long tail of old accounts does not quietly become a cost.
Customer identity and login02
Active enterprise connections and organization tenants
The customer organizations you keep live and the inbound identity-provider connections serving them, counted per connection rather than per employee behind it.
A connection is counted while it is configured and serving. One enterprise customer with thousands of staff is one connection; the people behind it are already counted in the line above, not twice.
Organizations and enterprise connections03
Verification sessions and completed proofing checks
Each attempt to verify a person or a business against evidence: document and identity proofing, and company checks against registry and ownership data.
A check that returns a negative result is still a check that was performed, so it counts. Billing you only for passes would mean pricing the outcome rather than the work, and would quietly reward a verifier for being lenient.
Identity and business verification04
Issued and verified digital credentials
Credentials your tenant issues, and presentations it verifies. Issuance and verification are separate meters because they are separate operations.
A credential issued once and presented fifty times is one issuance and fifty verifications. Revoking or expiring a credential is lifecycle, not a new unit.
Verifiable credentials05
Machine and AI agent identities
Non-human principals holding their own keys: services, workloads, containers, connected devices, and autonomous agents with an operator relationship behind them.
The meter is the principal, not its traffic. Rotating a key does not create a new identity, and a workload that authenticates every thirty seconds is one machine identity — otherwise rotation would cost more than leaving a static credential in place, which is exactly the wrong incentive.
Machine and agent identity06
Premium evidence retention, anchoring and verification exports
Evidence held beyond the retention window your tenant is configured for, ledger anchoring where you switch it on, and bulk evidence or verification exports for a review.
Anchoring is optional and is metered only when enabled. It commits a hash, never personal data — and it proves a record existed and has not changed, not that the underlying claim was true.
Event ledger and evidence
Seeing the meter
Usage accounting is a platform feature rather than an end-of-month reveal — it is listed against the Build package for that reason, and it is the same counting on every package above. If a dimension is metered, you can see your own figure for it; identity operations and the APIs are where that lives.
Plainly
Three things you will not find here.
A pricing page is where a young platform is most tempted to borrow credibility it has not earned yet. These are the three temptations, declined in writing, so you can check the rest of the site against the same standard.
No printed figures
The inputs that decide your number are yours: which packages you need, how many identities authenticate, how much verification and credential work runs through them. A figure published here would be a guess wearing the clothes of a quote, and you would discover the difference at the worst possible moment.
No advertised free tier
This page does not claim one. Sandbox and development tooling is part of the Build package; where that sits commercially is settled with the team when you start. Promising free usage that billing does not support would be the easiest sentence to write on this page and the first one to be found out.
No borrowed proof
No customer logos, no counts, no uptime figures, no certification badges. The platform is designed around published standards, which is not the same as being audited against them, and a pricing page is a strange place to blur that distinction.
There is a fourth thing no package changes: authentication establishes who or what is making a request; whether that principal may perform a particular action is decided elsewhere. No tier on this page buys a permission model, because that decision belongs to your application or to a separate authorization layer that holds the policy. The trust centre sets out how the handover is designed and what we will and will not say about it.
Questions
Questions about the commercial model.
Why are there no prices on this page?
Because the figure depends on your identity mix, and we would rather give you one that holds. The shape of the model is fully on this page — the packages, and the six things that are metered. The number is set with our team once we know which identities you need to authenticate and how much verification and credential work sits behind them.
Is there a free tier?
This page does not advertise one. Sandbox tooling and development environments are part of the Build package, and the commercial arrangement for them is agreed when you start rather than claimed here.
Do we have to buy the whole catalogue?
No. The catalogue is modular by design: start with the services your product needs now and add the next when it needs it. The packages describe shapes of use rather than a ladder you are obliged to climb.
What moves the cost as we grow?
The metered dimensions, rather than the package: active authenticated identities, live enterprise connections and organizations, verification sessions, credential issuance and verification, machine and agent identities, and premium evidence retention or anchoring. Usage accounting is part of the platform, so growth appears in your own numbers before it appears in a renewal conversation.
Does a larger package unlock permission controls?
No, and no package ever will. Authentication establishes who or what is making a request; deciding whether that principal may perform a particular action is a separate concern owned by the consuming application or by a dedicated authorization layer. That is an architectural boundary, not a packaging one, so it is not something a tier can buy.
Who do we contract with?
Agreements are with Cloud Granite Limited, the operating company behind ID Check Globe. The commercial terms for packages, metered usage and enterprise support live in that agreement rather than on this page.
Tell us the identity mix. We will tell you the figure.
Which identities you need to authenticate, how many enterprise customers sit behind them, and how much verification, credential and agent work runs through the platform. That is the whole conversation, and it is short.
Identity for everyone. Trust for everything.