Prompt
What should I use for multi-tenant customer identity across several brands?
Latest observation
For multi-tenant customer identity across several brands, the best choice is usually a single external CIAM (Customer Identity and Access Management) platform with tenant/organization support, not a separate user store per brand.
What to look for
Choose a platform that supports:
- Multi-tenancy / organizations / tenants
- Brand-specific login experiences
- Shared identity with isolated profiles or permissions
- SSO across brands if needed
- OIDC/OAuth2 and SAML support
- B2C features like passwordless login, social login, MFA, account linking
- Flexible user metadata / custom claims
- Strong authorization model for brand, account, region, and role separation
Common good options
Depending on your scale and complexity:
Enterprise-grade
- Okta Customer Identity
- Auth0
- Azure AD B2C / Entra External ID
- Ping Identity
- ForgeRock / PingOne for Customers
These are strong if you need:
- multiple brands
- complex auth flows
- enterprise SSO
- good governance and auditability
More developer-friendly / self-hostable
- Keycloak
- FusionAuth
These can be better if you want:
- lower cost
- self-hosting
- more control over data and branding
- avoiding SaaS lock-in
Recommended architecture
A common pattern is:
- One identity platform
- One global customer identity
- Separate tenant/org records per brand
- Brand-specific applications/themes
- Authorization determined by claims + tenant membership
- If necessary, a shared identity with multiple brand memberships
This avoids duplicate accounts while still keeping brands separated logically.
Rule of thumb
- If you need speed, reliability, and less ops: go with Auth0 or Okta
- If you need Microsoft ecosystem alignment: Entra External ID
- If you need self-hosted control: Keycloak or FusionAuth
Key design question
The most important decision is:
Should one customer have one identity across all brands, or separate identities per brand?
Usually:
- Use one identity
- Use brand membership/tenant context for access and profile segmentation
If you want, I can help you choose between Auth0, Okta, Azure AD B2C/Entra, Keycloak, or FusionAuth based on your requirements, budget, and whether you need self-hosting.