Strata Identity

Name: Strata Identity
Brand: Strata Identity

Modern identity for any application. No coding required. Integrate decades of enterprise identity architecture. Now.

Est 2019|Valuation $171.4M|Raised $40.6M|11 Ref Customers

LinkedIn 7K|Web traffic 25K|FTEs 53|HQ Boulder, Colorado, US

MarketsIdentity Provider (IdP) & Single Sign-On (SSO)

01Competitive Landscape

| Aspect | Strata Identity (Maverics) | PingOne DaVinci (Ping Identity) | Okta (Workforce + Workflows) | |---|---|---|---| | Starting Price | Public list price not fully disclosed; vendor materials show per-app/per-IDP examples; marketplace listings include published per-app and per-IDP examples. | Pricing not fully public on the DaVinci product page; Ping has broader platform pricing pages. | Often published per-user starting prices for baseline SKUs; Workflows is an add-on and pricing varies by package/volume. | | Best For | Hybrid/multi-cloud enterprises needing to orchestrate multiple IDPs and modernize legacy app auth without rewriting apps; migration/coexistence and continuity scenarios. | No-code customer/employee identity journey orchestration across tools; strong focus on flow design templates and UX orchestration. | Organizations wanting a broad IAM suite (SSO/MFA/UD) plus workflow automation; strong SaaS ecosystem and admin experience. | | Key Strength | Vendor-agnostic “identity fabric” positioning; per-app/per-IDP (not per-user) pricing can be attractive at scale; explicit focus on legacy app modernization and IDP coexistence. | No-code orchestration and templates; marketed for integrating identity tech stack regardless of vendor; strong in CIAM/journey orchestration narratives. | Large ecosystem, mature IAM suite, strong admin workflows, many integrations/connectors; widely adopted and easier to hire for. | | Key Weakness | Limited independent public reviews; orchestration layer adds architectural complexity and a runtime dependency; ROI claims largely vendor-sponsored. | May still be tied to Ping platform strategy; pricing transparency can be limited; may overlap with existing CIAM/IDP tooling. | User-based pricing can become costly at very large scale; some orgs find overlap with Microsoft Entra in Microsoft-centric shops. | Narrative analysis - Direct competitors and key differentiators - Strata positions itself as a runtime identity orchestration fabric for hybrid/multi-cloud identity fragmentation, with a strong emphasis on avoiding app rewrites and enabling multi-IDP coexistence. - PingOne DaVinci is positioned more as a no-code orchestration engine for identity journeys and integrations (often used heavily in CIAM contexts), with broad vendor-integration messaging. - Okta’s “orchestration” framing often overlaps with workflow automation and IT service delivery orchestration; it is typically an IAM suite-first approach, not a pure “orchestrate other IDPs at runtime” layer. - Pricing comparison: value proposition vs alternatives - Strata’s per-app/per-IDP pricing can be attractive for scenarios with very large user bases (or future “agent” identity counts) but relatively bounded app/IDP counts. - Conversely, organizations with very large numbers of apps (or where each environment/instance counts as an app) should model costs carefully. - Market share and adoption trends (evidence constraints) - Okta, Microsoft, and Ping have broader category visibility and substantially more public reviews and analyst coverage. - Strata has credible venture funding and coverage in mainstream tech press, but a limited public review footprint.

01Competitive Landscape

Aspect	Strata Identity (Maverics)	PingOne DaVinci (Ping Identity)	Okta (Workforce + Workflows)
Starting Price	Public list price not fully disclosed; vendor materials show per-app/per-IDP examples; marketplace listings include published per-app and per-IDP examples.	Pricing not fully public on the DaVinci product page; Ping has broader platform pricing pages.	Often published per-user starting prices for baseline SKUs; Workflows is an add-on and pricing varies by package/volume.
Best For	Hybrid/multi-cloud enterprises needing to orchestrate multiple IDPs and modernize legacy app auth without rewriting apps; migration/coexistence and continuity scenarios.	No-code customer/employee identity journey orchestration across tools; strong focus on flow design templates and UX orchestration.	Organizations wanting a broad IAM suite (SSO/MFA/UD) plus workflow automation; strong SaaS ecosystem and admin experience.
Key Strength	Vendor-agnostic “identity fabric” positioning; per-app/per-IDP (not per-user) pricing can be attractive at scale; explicit focus on legacy app modernization and IDP coexistence.	No-code orchestration and templates; marketed for integrating identity tech stack regardless of vendor; strong in CIAM/journey orchestration narratives.	Large ecosystem, mature IAM suite, strong admin workflows, many integrations/connectors; widely adopted and easier to hire for.
Key Weakness	Limited independent public reviews; orchestration layer adds architectural complexity and a runtime dependency; ROI claims largely vendor-sponsored.	May still be tied to Ping platform strategy; pricing transparency can be limited; may overlap with existing CIAM/IDP tooling.	User-based pricing can become costly at very large scale; some orgs find overlap with Microsoft Entra in Microsoft-centric shops.

Narrative analysis

Direct competitors and key differentiators
- Strata positions itself as a runtime identity orchestration fabric for hybrid/multi-cloud identity fragmentation, with a strong emphasis on avoiding app rewrites and enabling multi-IDP coexistence.
- PingOne DaVinci is positioned more as a no-code orchestration engine for identity journeys and integrations (often used heavily in CIAM contexts), with broad vendor-integration messaging.
- Okta’s “orchestration” framing often overlaps with workflow automation and IT service delivery orchestration; it is typically an IAM suite-first approach, not a pure “orchestrate other IDPs at runtime” layer.
Pricing comparison: value proposition vs alternatives
- Strata’s per-app/per-IDP pricing can be attractive for scenarios with very large user bases (or future “agent” identity counts) but relatively bounded app/IDP counts.
- Conversely, organizations with very large numbers of apps (or where each environment/instance counts as an app) should model costs carefully.
Market share and adoption trends (evidence constraints)
- Okta, Microsoft, and Ping have broader category visibility and substantially more public reviews and analyst coverage.
- Strata has credible venture funding and coverage in mainstream tech press, but a limited public review footprint.

Aspect

Strata Identity (Maverics)

PingOne DaVinci (Ping Identity)

Okta (Workforce + Workflows)

Starting Price

Public list price not fully disclosed; vendor materials show per-app/per-IDP examples; marketplace listings include published per-app and per-IDP examples.

Pricing not fully public on the DaVinci product page; Ping has broader platform pricing pages.

Often published per-user starting prices for baseline SKUs; Workflows is an add-on and pricing varies by package/volume.

Best For

Hybrid/multi-cloud enterprises needing to orchestrate multiple IDPs and modernize legacy app auth without rewriting apps; migration/coexistence and continuity scenarios.

No-code customer/employee identity journey orchestration across tools; strong focus on flow design templates and UX orchestration.

Organizations wanting a broad IAM suite (SSO/MFA/UD) plus workflow automation; strong SaaS ecosystem and admin experience.

Key Strength

Vendor-agnostic “identity fabric” positioning; per-app/per-IDP (not per-user) pricing can be attractive at scale; explicit focus on legacy app modernization and IDP coexistence.

No-code orchestration and templates; marketed for integrating identity tech stack regardless of vendor; strong in CIAM/journey orchestration narratives.

Large ecosystem, mature IAM suite, strong admin workflows, many integrations/connectors; widely adopted and easier to hire for.

Key Weakness

Limited independent public reviews; orchestration layer adds architectural complexity and a runtime dependency; ROI claims largely vendor-sponsored.

May still be tied to Ping platform strategy; pricing transparency can be limited; may overlap with existing CIAM/IDP tooling.

User-based pricing can become costly at very large scale; some orgs find overlap with Microsoft Entra in Microsoft-centric shops.