Lutril vs Lumos
Lumos is an autonomous identity platform for mid-market and enterprise companies of 200 employees and up, with agentic access reviews and Slack requests. Lutril is access governance for employees and AI agents, in Slack, Teams and the app UI, hosted in the EU, with an MCP proxy. Where each fits, and the Lumos alternatives question answered.
Cette page n’est pas encore traduite. Voici la version anglaise.
Réponse courte
Lumos and Lutril overlap on the core: SaaS discovery from Google Workspace and Microsoft 365, access reviews whose rejections auto-revoke, Slack requests with time-boxed grants, HRIS-driven lifecycle and an owner on every non-human identity. They differ on three things. Lumos targets companies of 200 employees and up and says a small team may find it more than it needs; Lutril is built for teams without an IAM function. Lumos governs agent tool calls with MCP Governance, a tool-use hook in Claude Code and Codex that allows or denies and logs each call, which Lumos says is not a gateway; Lutril's MCP proxy sits in front of every connected SaaS tool as one endpoint and enforces policy on each agent call, with prompt DLP and a kill switch. And Lumos documents no EU hosting region or French UI, where Lutril is hosted in France and available in French.
D'où part chaque produit
Lumos
Identity management for the agentic era: the autonomous identity platform, with agents that continuously govern access for every human, machine and AI, an AI layer called Albus, an Identity Agent Force of out-of-the-box agents, and MCP Governance for agent tool calls since September 2026. San Francisco, $85M+ raised, Series B led by Scale in 2024, a Strong Performer in Gartner's 2026 Voice of the Customer for IGA. Requests in Slack, the IT system or through MCP; 300+ integrations.
Lutril
Access governance for employees and AI agents in one policy layer: discovery the day you connect Google Workspace or Microsoft 365, requests in Slack, Teams and the app UI with automatic expiry, reviews that revoke, HRIS-driven lifecycle, and an MCP proxy that checks every agent tool call with prompt DLP and a global kill switch. Built by a practising CISO, hosted in France, in French and English.
Capacité par capacité
| Capacité | Lumos | Lutril |
|---|---|---|
| SaaS discovery from IdP sign-in and OAuth grants (Google Workspace, Microsoft 365) | OuiGoogle scope to discover apps employees signed into with Google; Microsoft 365 report and audit scopesSource 3 | OuiGoogle Workspace and Microsoft 365 sign-in signals and OAuth grants, from the day you connect |
| Browser extension for shadow IT and shadow AI discovery | PartielBrowser sessions cited as a signal; no extension documented in the help centreSource 4 | OuiChrome extension for the SaaS and AI tools that skip SSO |
| Access reviews whose keep-or-remove decisions execute the revocation | OuiAuto-revoke rejected access through downstream integrationsSource 5 | OuiDecisions execute in the connected tool; proof in the campaign export |
| Access requests and approvals in Slack | OuiSlack app for requests, approver notifications and remindersSource 6 | OuiRequests, approvals and expiry warnings in Slack |
| Access requests and approvals in Microsoft Teams | PartielRequests flow into Teams; approval inside Teams not explicitly documentedSource 7 | OuiSame flow in Microsoft Teams, and in the app UI |
| Just-in-time, time-boxed access that expires on its own | OuiDurations from 2 hours to 90 days, or unlimited, with automatic revocationSource 8 | OuiOne hour to seven days; an approver can shorten, never extend; auto-revoked |
| Onboarding triggered by the HRIS | OuiWorkday, BambooHR, Rippling, ADP Workforce Now, Oracle HCMSource 9 | OuiLucca, PayFit and Eurécia native; other HRIS through the MCP endpoint |
| Offboarding that deprovisions across SaaS, including apps outside SSO | OuiOne-click offboarding for SSO and non-SSO appsSource 10 | OuiNative connectors plus a universal MCP endpoint for any tool with an API |
| Shadow AI discovery: AI tools and agents in use | PartielShadow IT and AI discovered and monitored; method not documentedSource 11 | OuiSign-in logs, mailbox scanning, Chrome extension and code scanning |
| AI agent registry with an accountable owner | OuiEvery NHI mapped to a human owner; Agent Ownership FinderSource 12 | OuiOwner, model and scopes on every agent; offboarded like an employee |
| MCP proxy or gateway enforcing policy on agent tool calls | PartielMCP Governance: tool-use hook in Claude Code and Codex allows or denies and logs each call; vendor says it is not a gatewaySource 18 | OuiLutril MCP proxy: policy on every call, append-only audit log, global kill switch |
| Prompt-level DLP and redaction for LLM traffic | Non documenté | OuiDetect and redact PII and secrets in prompts, per-model policy |
| EU hosting and a French-language product | Non documentéPrivacy policy mentions transfers outside the EEA; no region or language option found | OuiOVHcloud, France; product and documentation in French |
| Compliance evidence exports for SOC 2 and ISO 27001 | OuiEvidence-backed reports formatted for SOC 2, SOX and ISO 27001Source 5 | OuiCampaign export with decisions and revocation proof, one link |
| Native integrations | Oui300+ integrationsSource 15 | OuiMore than 55 native connectors plus the universal MCP endpoint |
| Published pricing | Non proposéPricing page without figuresSource 2 | Non proposéOn request |
Choisissez Lumos si
- You have 200 employees or more, an IT or IAM team to run it, and want AI-assisted reviews and an agent workforce inside the identity platform.
- Your HRIS is Workday, ADP or Oracle HCM and your integrations are already in Lumos's catalogue.
- US hosting is acceptable and an English-only product is fine.
Choisissez Lutril si
- You are a mid-market company without an IAM team and need discovery, reviews and offboarding running in weeks.
- AI agents call your SaaS tools and you want one proxy in front of every connected tool that enforces policy on each MCP call, with prompt DLP and a kill switch, rather than a hook in each agent client.
- Requests and approvals must run in Microsoft Teams as well as Slack.
- Your data has to stay in the EU, or your team works in French.
Les questions que se posent les acheteurs
What are the best alternatives to Lumos for access reviews?
Look for a tool whose review decisions execute the removal, that covers apps outside SSO, and that exports evidence an auditor accepts. Lutril, C1 (formerly ConductorOne), Zluri, Torii and Okta Identity Governance all run campaigns; they differ on automatic remediation, Teams support, EU hosting and AI agent coverage. Lutril's campaigns include registered AI agents alongside employees, execute removals in the connected tool, and export one link with the decisions and the revocation proof.
Does Lumos govern AI agents through MCP?
Yes. Lumos maps each non-human identity to a human owner and ships MCP servers so assistants can request access or administer Lumos itself. Since September 2026 its MCP Governance product shows the MCP servers and tool calls agents use and enforces policy at runtime through a tool-use hook, starting with Claude Code and Codex; each call is allowed or denied and logged with its inputs, the human identity and the decision. Lumos states it is not an MCP gateway and does not route tool calls through a single chokepoint. Lutril takes the proxy approach: one endpoint in front of every connected tool, role-based policy per call, an append-only audit log, prompt DLP and a global kill switch.
Is Lumos suitable for a company of 80 people?
Lumos's own comparison content says it targets mid-market and enterprise, generally 200 or more employees, and that a small team may find it more capability than it needs. Lutril is designed for teams with no dedicated IAM function, with discovery starting the day you connect your workspace.
Where is each product hosted?
Lumos's privacy policy refers to transfers outside the EEA with safeguards; we found no documented EU region or French-language option. Lutril is hosted at OVHcloud in France, with Cloudflare at the edge, and the product and documentation exist in French and English.
Sources
- 1Lumos homepageconsulté le 26 septembre 2026
- 2Lumos pricingconsulté le 2 septembre 2026
- 3Lumos help, connecting Google Workspaceconsulté le 2 septembre 2026
- 4Lumos, Zluri alternatives and competitorsconsulté le 2 septembre 2026
- 5Lumos, access reviewsconsulté le 2 septembre 2026
- 6Lumos help, connecting Slackconsulté le 2 septembre 2026
- 7Lumos, Microsoft Teams integrationconsulté le 2 septembre 2026
- 8Lumos help, AppStore quick startconsulté le 2 septembre 2026
- 9Lumos, lifecycle managementconsulté le 2 septembre 2026
- 10Lumos, JML workflow orchestrationconsulté le 2 septembre 2026
- 11Lumos, identity security postureconsulté le 2 septembre 2026
- 12Lumos, non-human identitiesconsulté le 2 septembre 2026
- 13Lumos developers, MCPconsulté le 2 septembre 2026
- 14Lumos privacy policyconsulté le 2 septembre 2026
- 15Lumos integrationsconsulté le 2 septembre 2026
- 16Lumos, ConductorOne competitors and alternativesconsulté le 2 septembre 2026
- 17Lumos, aboutconsulté le 2 septembre 2026
- 18Lumos blog, introducing MCP Governanceconsulté le 26 septembre 2026
Cette page a été rédigée par Lutril. Les faits concernant Lumos proviennent de leur documentation publique au 26 septembre 2026 ; la mention « Non documenté » signifie que nous n'avons trouvé aucune source publique qui confirme ou infirme la capacité. Une erreur ? Écrivez à hello@lutril.com et nous corrigerons.