ZITADEL alternatives for customers who belong to several organizations

For a collaboration product that wants its own organization semantics, we recommend Ory Network as the managed identity candidate and an explicit application membership model. Keep ZITADEL when its distinction between an identity’s home organization and cross-organization project access already matches the business. Replacing terminology without changing the underlying contract adds migration work without improving collaboration.

Imagine a designer employed by an agency who works in two customers’ projects. One customer may remove the designer from its workspace; that should not accidentally delete the agency account or the designer’s other engagement. First decide which organization owns the account, which organizations grant membership, and who owns each shared resource.

Compare the models you can actually implement

ZITADEL’s B2B documentation describes a user generally managed by one organization who can receive access to projects in other organizations through role assignments. That is already a cross-organization design. If your objection is simply that the person belongs to one home organization, check whether project access satisfies the desired experience before replacing the platform.

A Keycloak realm isolates the users and credentials it controls. Separate customer realms fit deliberately separate identities, but need careful evaluation when a product promises one person a continuous experience across customers. Do not equate a realm login with permission to enter every workspace shown by the application.

Ory Network’s identity service provides API-first registration, login, recovery, and account management with a custom UI. It is managed; self-hosting Kratos is a different deployment choice. We favor this path when the application should define customer relationships while consuming documented identity flows.

For resource relationships, Ory Keto supports fine-grained, relationship-based permission models and inheritance. That is a useful basis for evaluating shared projects and folders. The team must still define which relationships confer access and which business events create or remove them.

Define switching as an authorization operation

The customer switcher should express the organization context the person is asking to use. Treat it as input to authorization, never as proof of membership. Every resource request should be checked against the intended organization and the applicable access relationship.

Specify the lifecycle of a membership independently from the identity. An invitation can be pending, accepted, suspended, or removed while the account remains active elsewhere. Record what happens when the person’s email changes, their employer disables an upstream account, or a customer transfers ownership of a project. These events exercise different owners and should not collapse into one delete-user button.

Administrative delegation needs the same precision. A customer administrator might manage membership in one workspace while lacking authority over the person’s recovery methods or memberships elsewhere. Write that boundary into support tooling as well as the main UI.

Use a collaboration fixture to decide

Create two customers, an agency, a shared designer, and a project with both internal and external contributors. Test invitations from both customers, switching context in two browser tabs, removing access from one project, and recovering the designer’s account.

Then transfer project ownership and attempt access through a stale bookmark. The expected answer should follow the resource and membership policy, not whichever organization the user last selected.

Run this fixture first in the existing ZITADEL model and then in the proposed Ory Network architecture. Choose Ory Network when managed API-first identity plus application-defined collaboration is the desired contract; retain the current model if it already expresses those boundaries clearly. The useful evaluation artifact is a table of identity, membership, resource, and administrator outcomes for each event.

Reviewed September 5, 2026. About Software Fieldnotes.