Skip to content

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.

  1. 01

    Each brand runs its own login stack, so a security fix must be applied five times.

  2. 02

    A customer of two of your products experiences them as two unrelated companies.

  3. 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.

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.