Lumos vs Veza
ILM Reference editors · Editorial assessment · Published 2026-09-28
Veza scores higher overall on our weights: 69/100 against 62/100 for Lumos. Lumos wins one of the seven criteria (JML automation) and Veza wins four (disconnected-app coverage, orphan and local account discovery, certification campaign depth and works alongside existing IdP and IGA); they tie on audit evidence and pricing transparency. On disconnected-app coverage, the heaviest-weighted criterion, Veza leads 65 to 50.
Scores are an editorial assessment of public vendor material. See Editorial method.
How do Lumos and Veza score on each criterion?
| Criterion (weight) | Lumos | Veza | Winner |
|---|---|---|---|
| Disconnected-app coverage (22) | 50 | 65 | Veza |
| Orphan and local account discovery (18) | 62 | 80 | Veza |
| JML automation (15) | 80 | 72 | Lumos |
| Certification campaign depth (12) | 72 | 78 | Veza |
| Audit evidence (13) | 70 | 70 | Tie |
| Works alongside existing IdP and IGA (12) | 70 | 75 | Veza |
| Pricing transparency (8) | 20 | 20 | Tie |
| Lifecycle coverage score | 62 | 69 | Veza |
Read the reasons for each score
- Disconnected-app coverage
- Lumos: Revocation described across local accounts, custom and on-prem apps; handling of apps with no API not detailed.
- Veza: Reveals accounts that exist outside identity platforms; custom systems connect through the Open Authorization API.
- Orphan and local account discovery
- Lumos: Identity analytics surfaces dormant accounts and shadow IT.
- Veza: Detects dormant accounts and reveals local, machine and service accounts.
- JML automation
- Lumos: HRIS-triggered joiner, mover and leaver workflows; leavers offboarded with licenses reclaimed.
- Veza: Birthright access, role-change and offboarding automation, including local accounts, with Dry Run and Safety Limits.
- Certification campaign depth
- Lumos: Agents scope reviews, certify straightforward items and prepare audit-ready documentation.
- Veza: Access certification campaigns prioritized by risk, with effective permissions in plain terms.
- Audit evidence
- Lumos: Full audit trail of every grant and revocation.
- Veza: Audit logging for lifecycle actions; no framework-specific evidence export described on the pages reviewed.
- Works alongside existing IdP and IGA
- Lumos: Works across the IdP, HRIS, SaaS and cloud stack already in place.
- Veza: Integrates with Okta and HR sources and adds visibility beside existing IdP tooling.
- Pricing transparency
- Lumos: No public prices.
- Veza: No public pricing.
What does each tool do?
Agent-driven identity governance with HRIS-triggered lifecycle, access reviews and identity analytics across 300+ integrations.
Category Identity governance and administration (IGA)
Builds an Access Graph of effective permissions across 325+ integrations and runs reviews and lifecycle actions on top of it.
Category Access graph and governance
How do Lumos and Veza compare on pricing and deployment?
How do they handle disconnected applications?
| Tool | Discovery of the app | Account data collection | Leaver action on the app | Method described | Source |
|---|---|---|---|---|---|
| Veza | Not documented | Documented accounts outside identity platforms, custom systems via OAA | Documented offboarding including local accounts | Access Graph integrations and OAA | Source: veza.com lifecycle and access reviews pages · Reviewed Sep 2026 |
| Lumos | Partial shadow IT in identity analytics | Not documented | Partial revocation across local accounts, custom and on-prem apps | Integrations; no-API handling not detailed | Source: lumos.com lifecycle page · Reviewed Sep 2026 |
Source: veza.com lifecycle and access reviews pages · Reviewed Sep 2026
Source: lumos.com lifecycle page · Reviewed Sep 2026
Which should you choose?
Choose Lumos if HR-driven joiner, mover and leaver automation is the priority.
Agent-driven identity governance with HRIS-triggered lifecycle, access reviews and identity analytics across 300+ integrations.
Choose Veza if you need coverage for applications with no connector, no SCIM endpoint and no SSO integration, or if finding orphan, dormant and local accounts is the priority.
Builds an Access Graph of effective permissions across 325+ integrations and runs reviews and lifecycle actions on top of it.
Weights change the answer. Try your own in the calculator.
FAQ
Which is better for identity lifecycle management, Lumos or Veza?
On our rubric Veza scores 69/100 and Lumos 62/100. Veza is ahead mainly on disconnected-app coverage and orphan and local account discovery. Buyers who weight JML automation more heavily may prefer Lumos; the calculator shows how the order changes.
Which handles disconnected applications better, Lumos or Veza?
Veza scores 65 to 50 on disconnected-app coverage. Lumos: Revocation described across local accounts, custom and on-prem apps; handling of apps with no API not detailed. Veza: Reveals accounts that exist outside identity platforms; custom systems connect through the Open Authorization API.
Do Lumos and Veza publish pricing?
Lumos: Not published. Contact sales. Veza: Not published. Contact sales.
Keep reading
Sources
- lumos.com
- lumos.com lifecycle management
- lumos.com identity analytics
- lumos.com pricing
- veza.com lifecycle management
- veza.com access reviews
- veza.com
Reviewed Sep 2026