Use cases
Start from your sector.
9 short reads, one for each industry whose identity problems differ enough to be worth stating on their own. Each sets out the outcomes that matter in that sector, the services behind them, and where the full detail lives.
How to read this
A sector page is a routing page.
If you arrived with an industry in mind, there is usually a specific question behind it — how a customer organization brings its own identity provider, how a credential gets checked by someone outside your company, how a workload authenticates without a shared key. These pages answer that quickly and then hand you on.
Shorter on purpose
Each sector page names the outcomes that matter in that industry and then points at the solution and the services that go into detail. It does not restate the catalogue.
The sectors overlap
A marketplace has customers, suppliers and partner integrations. Where your product sits across several of these, read more than one page — the services underneath are the same catalogue either way.
Authentication, not authorization
Every outcome listed is an authentication outcome: establishing who or what is making a request. Whether that principal may perform a particular action is decided by your application or by a separate authorization layer.
What is not on these pages
No logo wall, no case studies, no sector statistics.
We have not printed customer names, deployment counts or testimonials, and no page here claims a certification, an audit result or a response-time commitment. A sector page is the easiest place on a website to imply experience it has not earned, and a reader in a regulated industry can tell the difference.
What these pages do contain is checkable: the outcomes the platform is designed to produce, the services that produce them, and the standards each flow is built on. The trust centre sets out how the platform is built, and the developer portal carries the protocol detail behind them.
By sector
9 industries, one identity question.
Who or what is making this request? The answer looks different in a hospital, a marketplace and a deployment pipeline, and these are the differences that matter.
SaaS and B2B platforms
Give every customer organization its own identity boundary.
Organization-aware sign-in, enterprise SSO per customer, membership lifecycle and trustworthy API identities.
Read the sector viewE-commerce and retail
Fewer abandoned sign-ins, fewer reset tickets.
Unify customer login, passkeys, account recovery and step-up authentication for the actions that carry real risk.
Read the sector viewFinancial services
High-assurance identity, documented end to end.
Identity proofing, business verification, strong client authentication and an auditable record of the identity lifecycle.
Read the sector viewHealthcare and sensitive data
Clinician, patient, partner and machine access on one record.
Privacy-aware identity with clear audit trails and strict data minimization.
Read the sector viewEducation and credentialing
Issue qualifications people can carry and others can check.
Verifiable credentials for students, graduates, members and professional qualifications.
Read the sector viewPlatforms and marketplaces
Know who is on both sides of the transaction.
Verify buyer and seller identities, organizations, partner integrations and delegated software participants.
Read the sector viewAI and autonomous systems
Identities for software agents and the organizations behind them.
Agent credentials, operator binding and verifiable delegation for safer cross-platform interaction.
Read the sector viewCloud and DevOps
Workload identity instead of shared secrets.
Authenticate workloads, services, deployment automation and API integrations with short-lived credentials.
Read the sector viewMulti-brand organizations
Share identity infrastructure, not customer experience.
Core identity across product brands with dedicated domains, tenant separation and distinct user journeys.
Read the sector viewDeeper reads
Your sector is not the only way in.
If none of these sectors fits, or your product sits across several of them, the other two routes into the platform are organized by problem and by service rather than by industry.
Every sector asks the same question first.
Who or what is making this request? Start with a development tenant and one application, or talk the architecture through first — tenancy, proofing, credential lifecycle and the boundaries you want to keep in your own stack.