Skip to content
Start with Identity
Concept

Identity Orchestration

Identity orchestration is the practice of running login, registration, verification and access journeys as configurable flows that call several identity services (identity providers, MFA, fraud signals, identity proofing) from one layer outside the application, so the journey can change without a code release. An identity orchestration platform is the product that runs those flows.

The mechanics are simple: a flow is a sequence of steps, each step calls a connector to a service, and decision logic between steps picks the next path. Ping's documentation describes PingOne DaVinci as "an orchestration platform that lets you create flows to guide users through IAM activities," and lets one application split traffic between flows for A/B testing. The same pattern drives IdP migrations: the orchestration layer routes each user to the old or new provider until cutover, and Rubrik now uses Strata's orchestration, acquired in June 2026, to fail authentication over to a secondary IdP during an outage.

It matters because most organizations run more than one identity system. The trade-off is a new tier-zero dependency in the login path: if the orchestration layer is down or misconfigured, every flow behind it is too.

See also: identity orchestration tools compared, CIAM journey orchestration, what is identity fabric, identity provider, identity fabric

Last reviewed By SWI Community TeamSuggest a correctionHow we research