Iden vs Lumos
A detailed guide to Iden vs Lumos: coverage, control, cost, and when each solution fits your stack.
10 min read · Last updated April 2026
Lumos started as a SaaS management platform and added IGA on top. That history shapes what it’s strong at: self-service access requests, license optimization, and coverage for your top-50 SaaS apps. Where it runs into trouble is the long tail - niche apps, internal tools, on-prem systems, and anything that requires a connector your team has to build and maintain.
That’s the gap Iden fills. This guide covers what each does well, where each falls short, and how to pick.
When to choose Lumos
Lumos is a serious platform. If your situation fits the profile below, it deserves a real look.
- —
Your stack is primarily modern SaaS - Okta or Google Workspace as IdP, popular apps like Salesforce, Slack, GitHub. Lumos covers these well.
- —
AppStore UX is a genuine priority. Users requesting access via Slack or web is consistently the most praised thing about Lumos.
- —
SaaS spend management matters as much as governance. Lumos unifies license optimization, shadow IT discovery and IGA in one.
- —
Your access review stays under 1,000 users per campaign. Lumos's Albus AI agent meaningfully reduces reviewer burden.
- —
You have internal dev capacity to build and maintain custom connectors using Lumos's SDK when you hit the wall.
When to choose Iden
Lumos is built for cloud-native SaaS stack. Once you step outside that - on-prem or custom apps, NHI at scale, contractors - the gaps compound.
- —
Your stack has apps that lock SCIM behind enterprise tiers. Lumos relies on SCIM and force upgrades as any enterprise IGA. Iden doesn't.
- —
Your stack has on-prem, legacy apps or internal tools. Lumos's on-prem coverage is explicitly limited - Iden governs them natively.
- —
You need custom connectors but don't have dev resources to build them with Lumos SDK. Iden builds and ships connectors in under 48 hrs.
- —
You need to govern non-human identities - service accounts, API keys, OAuth grants, AI agents - now, not later this year. NHI is on their roadmap.
- —
Access review campaigns run across more than 1,000 users. Lumos has reported timeout issues at this scale. Iden has no ceiling.
- —
You need transparent pricing without buying full suite upfront. Lumos requires all modules live for a stable UX. Iden starts at $7.50/user/mo, flat.
- —
You run multiple IdPs or a non-standard IdP setup. Iden works with any combination - no migration required.
- —
Contractor and partner lifecycle needs to be governed the same way FTEs are. Iden has native non-FTE lifecycle management.
Already using Lumos AppStore? Iden can run alongside or replace it. Most teams run parallel for 30-60 days and cut over when ready. Your existing IdP setup stays untouched.
Where they differ
The shared ground ends there. Coverage, control, and cost are the three areas where Lumos’s limits start to show.
1. Iden covers your entire stack. SCIM or not.
Lumos claims 300+ integrations. The catalog is solid for popular SaaS - Salesforce, AWS, Slack, GitHub, Zendesk, Google Workspace. Lumos doesn’t specify which of those integrations are SCIM-based vs API-based. For most SaaS apps, there is no provisioning API to speak of. Only developer-workflow tools tend to expose one. So it’s safe to assume that these are mostly SCIM-based that need forced tier upgrades.
Coverage drops fast once you move off the top-50 list. Gartner Peer Insights reviewers are direct about it - read more below.
For apps outside the catalog, Lumos provides a Connector SDK - but your team builds and maintains those connectors.
Iden offers 180+ connectors: SCIM, API or custom when neither is available - all by Iden, not your team. Anything outside the catalog, we build a connector in 48 hours.
Coverage gets you connected. Control is where the real governance work happens - and where Lumos’s limits start to compound.
2. Controls that go deeper than Lumos’s.
Lumos governs at the entitlement and role level for connected apps - which is better than Okta IGA’s group-only ceiling. But the depth of what it can govern depends entirely on what each connector exposes. For apps built on the SDK by your team, that’s a moving target.
Access review campaigns above 1,000 users have reported timeouts. Large enterprise campaigns require careful scoping and batching. Lumos’s Albus AI agent meaningfully helps at smaller scales; the scale ceiling is the limitation.
NHI governance is a real gap today. Discovery and ownership mapping are live. Anomaly detection, context-aware policies, and bot-vs-human logic in access reviews are “Coming in 2026.” If you need NHI governance now, that roadmap doesn’t help.
Lumos also requires full suite implementation before the platform experience stabilizes. Practitioners are consistent: you can’t piece-meal it. That means Access Requests, UARs, Lifecycle Management, and Entitlement Audit Management all live before things work as marketed.
Iden has no hard caps. No access review ceiling. NHI governance native today. Contractor and partner lifecycle built in. Engineering dependency: none.
The capability gaps are one thing. Cost is where they show up on your renewal invoice.
3. Transparent pricing. No module bundling.
Lumos doesn’t publish pricing. No tiers, no per-user list price on the website. Demo required for a quote. Third-party estimates from 2023-2025 put the range at $5-10/user/mo depending on company size - but that’s before module stacking.
The module problem is where it gets real. IGA, SaaS Management, and AppStore are separate modules. Practitioners consistently report that you need to buy and implement all of them to get a stable experience. “You can’t really piece meal this platform” is a direct quote from a Gartner Peer Insights reviewer. That changes the budget conversation significantly.
Module bundling: the hidden cost of Lumos
Lumos sells IGA, SaaS Management, and AppStore as separate modules. All three need to be live before the platform experience stabilizes - that’s the consistent practitioner report.
Iden has everything rolled into one. Starts at $7.50/user/mo. All connectors included.
Then there’s the SCIM tax. Lumos doesn’t publicly say which of its 300+ connectors are SCIM-based vs API-based. It matters because most SaaS apps don’t expose a user provisioning API at all - only developer-workflow tools tend to. For the rest, SCIM is the only path. Which means the forced upgrade is real for most of your stack. Iden provisions on standard plans. No forced upgrades.
SCIM Tax: applies to Lumos too
Lumos uses SCIM where apps expose it. That means the same forced upgrades: ~70% of your stack locks SCIM behind enterprise tiers.
On a 300-person team, the Figma upgrade alone is +$22,200/year. Just for automated provisioning.
Iden works on standard plans. No upgrades required.
Iden starts at $7.50/user/mo. Vol discounts at 500+ users. All connectors included. No custom connector development required. Spend reclaim built in.
For teams that need a custom connector, Iden builds it in 48 hours at no extra charge. With Lumos, that’s an internal dev project - packaging, compiling, deploying, and maintaining the connector on your team’s time.
What practitioners say about Lumos
“The main areas of improvement are the integration challenges for niche and legacy systems. The available out of the box connectors support only the most popular SaaS applications while older/legacy/on-prem systems connectivity is very limited.”
“The product can do a lot, and most of the platform needs to be implemented before you have a stable experience and good working product (Access Requests, UAR's, LCM, Entitlement Audit Mgmt, etc). You can't really piece meal this platform.”
“Integration challenges including limited and complicated integrations, especially with custom applications, and inconsistent responsiveness from the Lumos Support team.”
“Missing features particularly the lack of security information for various SaaS apps, and limited integrations with popular SaaS apps hinder overall experience.”
What Iden customers say
“We govern Notion, Figma, Linear, and our internal tools. All in one place. Our previous platform couldn't touch half of them.”
“We finally have deeper access reviews. Not just 'is this person in the group' but what they can actually do inside the app.”
“We ran the numbers. Between the SCIM tax and wasted licenses, Iden paid for itself in the first quarter.”
“First 12 apps connected in under an hour. We were live before our previous vendor's POC was even scoped.”
How to choose between Iden and Lumos
Depends on your stack and your team. Lumos fits cloud-native SaaS-heavy orgs that want AppStore UX and SaaS spend consolidation. Iden fits everything with a longer tail.
Want the full breakdown?
The complete feature-by-feature comparison - Coverage, Control, and Cost - in one reference document. Every Lumos hard limit, every Iden capability, side by side. Useful for vendor evaluations, internal presentations, and budget conversations.
Download the comparison PDFNo form. Direct download.
A few things worth saying directly
Lumos has a great AppStore UX. Does Iden match it?
Iden has AppStore-style self-service via Slack, web, and API. Lumos's AppStore is a genuine strength - it was the original product before IGA was added. Both are worth demoing with your actual apps before deciding.
Lumos claims 300+ integrations. Does Iden have that?
Iden's 180+ connectors work without SCIM. Lumos doesn't disclose which of its 300+ are SCIM vs API - and for most SaaS apps, there's no provisioning API anyway. So most of that catalog is SCIM-based: forced tier upgrades apply. Not with Iden.
Can I buy just the IGA module from Lumos?
Practitioners consistently report that you need to buy and implement the full suite - IGA, SaaS Management, and AppStore - before the experience stabilizes. 'You can't really piece meal this platform' is a direct quote from a Gartner Peer Insights reviewer. Iden is modular: start with what you need, add more when it makes sense.
We're already using Lumos. How does switching work?
Most teams run parallel for 30-60 days. Iden connects to everything Lumos isn't covering and you cut over when you're ready. Your existing IdP, SSO, and MFA stay untouched. Iden's onboarding team mirrors your existing setup.
Lumos does SaaS spend management too. Is that part of Iden?
Yes - shadow IT discovery and SaaS spend optimization are built into Iden. Lumos's SaaS management is more mature and was the original core product. If spend management is the primary driver, run a side-by-side demo. If IGA is the primary driver and spend management is a bonus, both cover it.
We have a SOC 2 audit in 3 months. Is that enough time?
Yes. Most Iden customers are audit-ready within 2 weeks of go-live. Audit evidence for access reviews, task logs, and certification campaigns available in real-time.