PAIRING · MEASURED SIDE BY SIDE
Lumos vs Veza: reach beyond the IdP and IGA
The short answer
On our default weights Veza scores higher overall, 6.37 against 6.13 out of 10. Lumos scores higher on Unmanaged app discovery and Executes changes itself; Veza scores higher on Accounts inside the app, Reach into apps without APIs or SCIM, Orchestrates through the existing stack and Machine, service and agent accounts. They tie on Audit evidence and Pricing transparency. They sit in different layers (Identity governance (IGA) platform and Access graph and governance), so many teams run both.
By The Credential Desk · IAM Compared · Published 2026-10-08
Desk research from public vendor pages and documentation read in September 2026, updated 2026-10-13. Editorial assessment; we did not test the products.
How do they score on each criterion?
| Criterion | Weight | Lumos | Veza | Higher |
|---|---|---|---|---|
| Unmanaged app discovery | 18% | 6.0 Identity Analytics surfaces shadow IT alongside dormant and over-privileged accounts. | 3.5 Finds accounts outside identity platforms within the systems it integrates with; discovery of applications nobody connected is not described. | Lumos |
| Accounts inside the app | 16% | 6.2 Surfaces dormant accounts and revokes local accounts; app-native role mapping is not detailed. | 8.0 Reveals local, machine and service accounts and dormant accounts, with effective permissions from the Access Graph. | Veza |
| Reach into apps without APIs or SCIM | 14% | 5.0 Revocation described across custom and on-prem apps; handling of apps with no API is not detailed. | 7.0 The Open Authorization API imports authorization metadata from any system, including custom or on-premise apps, through a JSON schema and REST API; someone has to build the feed. | Veza |
| Orchestrates through the existing stack | 14% | 7.0 Works across the IdP, HRIS, SaaS and cloud stack already in place, with 300+ integrations. | 7.5 Adds visibility beside existing IdP and HR sources and writes changes back through OAA Write; now part of ServiceNow. | Veza |
| Executes changes itself | 12% | 8.0 HRIS-triggered joiner, mover and leaver workflows; leavers offboarded with licenses reclaimed. | 7.2 Birthright access, role-change and offboarding automation, including local accounts, with Dry Run and Safety Limits. | Lumos |
| Machine, service and agent accounts | 10% | 6.0 MCP Governance records agent tool calls with the human identity and policy decision; service account coverage is not detailed. | 7.5 Reveals machine and service accounts; the acquisition post frames the combined offer as an agent identity control plane. | Veza |
| Audit evidence | 10% | 7.0 Full audit trail of every grant and revocation. | 7.0 Audit logging for lifecycle actions; a framework-mapped evidence export is not described on the pages reviewed. | Tie |
| Pricing transparency | 6% | 2.0 No published prices. | 2.0 No public pricing. | Tie |
| Total | 100% | 6.13 | 6.37 | Veza |
What shape is each tool's reach?
- DISC
- Unmanaged app discovery
- 6.0
- INAPP
- Accounts inside the app
- 6.2
- NOAPI
- Reach into apps without APIs or SCIM
- 5.0
- ORCH
- Orchestrates through the existing stack
- 7.0
- EXEC
- Executes changes itself
- 8.0
- NHI
- Machine, service and agent accounts
- 6.0
- EVID
- Audit evidence
- 7.0
- PRICE
- Pricing transparency
- 2.0
Each sector is one criterion. The longer the engraved sector, the higher the editorial score. Sectors are equal width, so the picture shows the shape of a tool's reach, not its weighted total.
- DISC
- Unmanaged app discovery
- 3.5
- INAPP
- Accounts inside the app
- 8.0
- NOAPI
- Reach into apps without APIs or SCIM
- 7.0
- ORCH
- Orchestrates through the existing stack
- 7.5
- EXEC
- Executes changes itself
- 7.2
- NHI
- Machine, service and agent accounts
- 7.5
- EVID
- Audit evidence
- 7.0
- PRICE
- Pricing transparency
- 2.0
Each sector is one criterion. The longer the engraved sector, the higher the editorial score. Sectors are equal width, so the picture shows the shape of a tool's reach, not its weighted total.
Which parts of the estate does each document?
| Zone | Lumos | Veza |
|---|---|---|
| Unsanctioned SaaS | Partial Shadow IT surfaced in Identity Analytics | Not documented Discovery of unconnected SaaS not described |
| On-prem and legacy apps | Partial Revocation across on-prem systems | Documented The Open Authorization API imports authorization metadata from custom or on-premise apps |
| Custom-built apps | Partial Revocation across custom apps | Documented Custom systems connect through OAA |
| Local accounts in apps | Partial Revocation across local accounts; dormant accounts surfaced | Documented Reveals local accounts outside identity platforms |
| Service accounts and hardcoded credentials | Not documented Not described on the pages reviewed | Partial Reveals machine and service accounts; hardcoded credentials not described |
| AI agents | Partial MCP Governance for agent tool calls | Partial Acquisition post frames the combined offer as an agent identity control plane |
Which should you choose?
Frequently asked questions
Which scores higher overall, Lumos or Veza?
On our default weights Veza scores higher overall, 6.37 against 6.13 out of 10.
Where does Lumos score higher than Veza?
Lumos scores higher on Unmanaged app discovery (6.0 against 3.5) and Executes changes itself (8.0 against 7.2).
Can Lumos and Veza be used together?
Often, yes. They sit in different layers (Identity governance (IGA) platform; Access graph and governance), and each one's pages describe working with existing identity tools.