Is ConductorOne being acquired?

Yes, pending. ConductorOne rebranded to C1 in April 2026, and on 13 October 2026 Workday signed a definitive agreement to acquire C1, terms undisclosed. Workday expects the deal to close in its fiscal fourth quarter, which ends 31 January 2027, subject to customary conditions. Workday's announcement says nothing about whether C1 continues as a standalone product for customers whose HR system is not Workday.

Which scores higher, C1 or Lumos?

C1, narrowly, at 4.1 overall against 4.0. The two tie on governance and audit at 4.5, on authorization and lifecycle provisioning at 4.0, and on support and ecosystem at 3.5. C1 leads on developer experience, 4.0 to 3.5, and on pricing transparency, 3.5 to 3.0. Neither covers authentication or MFA in any depth.

Do C1 and Lumos publish prices?

No. As of 5 November 2026, C1's pricing page describes SKU-based platform pricing by managed identities, in Pro and Advanced tiers with product modules on top, and a usage-based Flex option billed monthly in C1 Tokens, but lists no rates. Lumos's pricing page lists no plans or prices and routes buyers to a demo or a free identity assessment.

Which handles legacy on-premises apps better?

Neither is built for a legacy-heavy estate, and both profiles list deep on-prem connectors as a reason to look elsewhere. C1's Advanced tier explicitly adds on-prem integrations and connectivity, which is the clearest published on-prem path of the two. If most of your entitlements live in mainframe, ERP, or directory-bound apps, shortlist SailPoint or Saviynt instead.

ConductorOne vs Lumos

CapabilityC1 (formerly ConductorOne)Lumos

Overall

4.1

4.0

Authentication: 3.0; 3.0
SSO & Federation: 3.0; 3.0
Authorization: 4.0; 4.0
Lifecycle & Provisioning: 4.0; 4.0
MFA & Passwordless: 2.5; 2.5
Governance & Audit: 4.5; 4.5
Developer Experience: 4.0; 3.5
Deployment Flexibility: 3.5; 3.5
Pricing Transparency: 3.5; 3.0
Support & Ecosystem: 3.5; 3.5

Scored 0–5 against a published rubric. Bold marks the higher score. Independent analysis, no vendor sponsorship.

At a glance

C1 (formerly ConductorOne) and Lumos are both SaaS-only, modern identity governance platforms for cloud-first companies, and the capability matrix shows how close they are: 4.1 against 4.0, tied at 4.5 on governance and audit. C1 is the stronger pick when access reviews, just-in-time access, and developer-friendly integration are the project. Lumos is the stronger pick when the goal is cutting IT access tickets through a self-serve app store. The bigger variable in late 2026 is ownership: Workday has agreed to buy C1, and that should shape any multi-year commitment.

Where each wins

Decision factor	C1	Lumos
Overall score	4.1	4.0
Governance and audit	4.5 (tie)	4.5 (tie)
Developer experience	4.0, wins	3.5
Pricing transparency	3.5, wins (models published)	3.0 (no models published)
Self-serve access requests	C1 Access module	Core of the product (AppStore in Slack, service desk, MCP)
Published on-prem connectivity	Advanced tier adds on-prem integrations	Not stated on pricing page
Ownership stability	Pending sale to Workday	Independent, private

Pricing reality

Neither vendor publishes a rate. C1's pricing page is the more informative of the two (checked 2026-11-05). It offers SKU-based platform pricing scoped by managed identities, with a Pro tier (integrations, visibility, identity security, shadow detection) and an Advanced tier that adds on-prem integrations and connectivity. Modules sit on top: C1 Identity Governance (Lifecycle, Access, Comply), C1 AI Gateway, C1 Vault, and C1 Agents. A usage-based Flex option bills monthly in C1 Tokens consumed by billable events. Lumos's pricing page lists no plans, units, or prices (checked 2026-11-05) and routes buyers to a demo or a free identity assessment. Model both in the TCO calculator, and for C1 ask whether module bundling or Flex is cheaper at your identity count.

Ownership changes

ConductorOne rebranded to C1 on 6 April 2026. On 13 October 2026 Workday announced a definitive agreement to acquire C1, terms undisclosed, expected to close in Workday's fiscal fourth quarter ending 31 January 2027. Workday plans to make C1 the governance layer for people and AI agents tied to its HR lifecycle and Agent System of Record. The release makes no commitment either way on customers who run a different HRIS. If yours is not Workday, get roadmap, connector support, and price-protection terms in writing before signing. See our news coverage. Lumos remains private and independent.

Deployment and architecture

Both are multi-tenant SaaS that connect to your IdP, HRIS, and SaaS and cloud APIs. C1's pricing page lists commercial, regional, and federal hosting paths. C1 leans on its connector and API model and treats AI agents as first-class identities, including an MCP gateway and support for enterprise-managed authorization of MCP servers. Lumos centers its architecture on the AppStore, where humans and AI agents request access in Slack, the IT service desk, or through MCP, with its Albus agent layer scoping reviews, proposing roles, and discovering non-human identities. Both now offer just-in-time grants with scheduled revocation, so zero standing privileges for SaaS is achievable with either.

Migration notes

Most buyers come from spreadsheet certifications or a legacy suite. Export prior review decisions and evidence before cutover, because auditors will ask for continuity across the review period. Start with the IdP and HRIS connectors so joiner, mover, and leaver events are authoritative, then add high-risk apps for reviews, then turn on just-in-time requests. Switching between C1 and Lumos later is a connector and policy rebuild, not a data migration, so the main cost is re-creating approval workflows and role definitions.

Who should pick which

Pick C1 if your team wants engineer-friendly governance, cares most about reviews and least privilege, and either runs Workday or is comfortable with the pending owner. Pick Lumos if reducing access tickets with a self-serve catalog is the headline outcome and vendor independence matters through 2027. If legacy on-prem coverage dominates, neither fits: see SailPoint vs Saviynt, Veza vs SailPoint, our IGA buyer guide, and best IGA tools.

Frequently asked questions

Is ConductorOne being acquired?: Yes, pending. ConductorOne rebranded to C1 in April 2026, and on 13 October 2026 Workday signed a definitive agreement to acquire C1, terms undisclosed. Workday expects the deal to close in its fiscal fourth quarter, which ends 31 January 2027, subject to customary conditions. Workday's announcement says nothing about whether C1 continues as a standalone product for customers whose HR system is not Workday.
Which scores higher, C1 or Lumos?: C1, narrowly, at 4.1 overall against 4.0. The two tie on governance and audit at 4.5, on authorization and lifecycle provisioning at 4.0, and on support and ecosystem at 3.5. C1 leads on developer experience, 4.0 to 3.5, and on pricing transparency, 3.5 to 3.0. Neither covers authentication or MFA in any depth.
Do C1 and Lumos publish prices?: No. As of 5 November 2026, C1's pricing page describes SKU-based platform pricing by managed identities, in Pro and Advanced tiers with product modules on top, and a usage-based Flex option billed monthly in C1 Tokens, but lists no rates. Lumos's pricing page lists no plans or prices and routes buyers to a demo or a free identity assessment.
Which handles legacy on-premises apps better?: Neither is built for a legacy-heavy estate, and both profiles list deep on-prem connectors as a reason to look elsewhere. C1's Advanced tier explicitly adds on-prem integrations and connectivity, which is the clearest published on-prem path of the two. If most of your entitlements live in mainframe, ERP, or directory-bound apps, shortlist SailPoint or Saviynt instead.

Last updated 2026-11-05

Independent, community-driven analysis. No vendor sponsorship. Compiled from public research and community input and verified on a best-effort basis, so details may be incomplete or out of date. Scores are opinions, not advice. Trademarks belong to their owners; mention does not imply affiliation or endorsement. See the full disclaimer, or send corrections to community@startwithidentity.com.