Identity for groups of products
Many brands, one identity foundation.
Share core identity infrastructure across product brands while preserving dedicated domains, tenant separation and distinct user experience.
The situation
What this usually looks like
Three things we are describing, not three things we are offering. If two of them match the system you have, you are reading the right page.
01
Each brand runs its own login stack, so a security fix must be applied five times.
02
A customer of two of your products experiences them as two unrelated companies.
03
Nobody can produce a single inventory of who has access to what.
The approach
How this is addressed.
What the platform does about the situation above, layer by layer, before any service names are involved.
- Separate where it matters, shared where it helps
- Give each brand its own login domain, theme and tenant boundary on top of one authentication engine, one key lifecycle and one event stream.
- One operational picture
- Keep a central inventory of tenants, applications and credentials across the whole group without flattening the boundaries between them.
The services involved
What this is built from.
A solution is a reading path through the catalogue, not a separate product. These are the services it draws on — each one with its own page, scope and integration detail.
Multi-Tenant Identity Platform
One foundation for many products and organizations.
Tenant, brand and environment isolation with shared authentication primitives.
Service detailsHosted Authentication and UI Components
Great authentication without starting from scratch.
Flexible interfaces and flows for sign-in, signup, MFA, account recovery and organization entry.
Service detailsEnterprise Identity Operations
Operate digital identity with confidence.
Administration, lifecycle analytics, governance and operational controls for identity teams.
Service detailsFederation Broker and Identity Routing
One connection point for many identity providers.
A federation layer connecting organizations, identity providers and applications across protocols.
Service detailsEvery service above establishes who or what is making a request. Deciding whether that authenticated principal may perform a particular action is authorization, and it stays with the consuming application or a separate authorization layer. Each service page states where it stops.
Identity for groups of products
Where this starts.
Create a development tenant and connect one application, or talk the architecture through first — tenancy, evidence, credential lifecycle, and which parts stay in your own stack.
Reading first is fine too: the developer portal covers APIs, SDKs and the standards each flow follows, and pricing sets out the packages and what is metered — the figures themselves are agreed with our team.