All the governance. None of the rollout.
Lumos is a full identity-governance and provisioning platform, powerful, and a project to stand up. Driply gives a growing team the governance and evidence that matter, without write-access connectors to build, own, or repair.
Lumos is a capable identity-governance and access platform: it automates provisioning and deprovisioning, runs access requests and reviews, and integrates deeply into the apps you run. That power comes with a footprint, write-access connectors to configure and maintain, and a rollout sized for larger organizations.
Driply is the lighter alternative for a 20-to-200-person team: it documents and proves access, who has it, who approved it, with an audit trail, using only read-only Google Workspace sync and Slack, so there’s no connector surface to break and nothing to stand up for a quarter.
- Core modelDriply:A system of record, documents and proves access.Lumos:A provisioning + governance platform that writes into your tools.
- IntegrationsDriply:Read-only Workspace + Slack. Nothing wired in that can break.Lumos:Deep write-access connectors across many apps to configure.
- Automated provisioningDriply:No, by design. Driply records the decision; your team makes the change in the tool, and Driply never writes to it.Lumos:Yes, provisions and deprovisions accounts automatically.
- Time to valueDriply:Set up in an afternoon, self-serve.Lumos:An implementation and rollout, often with onboarding support.
- Requests & approvalsDriply:Slack-native /driply with full web parity.Lumos:Self-service catalog and approval workflows.
- Audit evidenceDriply:Append-only log, exportable PDF/CSV for SOC 2 & ISO.Lumos:Governance reporting and access certifications.
- Security surfaceDriply:Holds no privileged write-access to your tools.Lumos:Holds the credentials needed to provision across systems.
- Right-sized forDriply:Startups and small companies (≈10–200 people).Lumos:Mid-market and enterprise IT/security teams.
- PricingDriply:Transparent self-serve tiers; free for 10 people / 20 tools.Lumos:Sales-led, priced for larger rollouts.
Driply documents and proves access. It doesn’t provision or revoke inside your tools, and by design never writes to them. You stay in control of the actual access.
The connectors are the cost
Deep write-access integrations are where provisioning platforms drift, break on an API change, and need an owner. Driply skips them entirely, read-only sync and a catalog instead, so there’s nothing to maintain and far less for a security review to worry about.
The part auditors actually ask for
Who has access to what, approved by whom, with an expiry and a trail. Driply delivers that core without a platform team, exactly what most teams under a few hundred people need from governance.
Cost and permission are different questions
Driply records what a tool charges, seat by seat, apart from what a person may do with it. A permission change never quietly moves what you pay, and a tool that sells three seat tiers is costed as three tiers. The register you keep for governance answers the money question too.
Adoption you don’t have to drive
Requests and approvals live in Slack, not a new portal, so people use the control instead of routing around it, and the record stays accurate without a rollout to push.
When Lumos is the right call
If you need to automate provisioning and deprovisioning across dozens of applications at scale, and you have the team to own those integrations, a full identity-governance platform like Lumos is built for exactly that, and Driply isn’t trying to be it. Driply documents and proves access; it doesn’t flip switches inside your tools.
Driply is the better fit when you want the governance and the evidence, who has access, who approved it, kept current and exportable, without taking on a write-access integration project to get there. Many growing teams find that’s all they actually need, and that a heavy platform can complement it later if they ever do.
The result, Enterprise-grade accountability at a startup’s weight, and no integration project.
Questions, answered.
- Is Driply a Lumos alternative?
- For teams that want access governance and audit evidence without an automated-provisioning platform, yes. Driply covers requests, approvals, reviews, and audit trails as a lightweight system of record, without the write-access connectors and rollout a full IGA platform involves.
- Does Driply provision and deprovision like Lumos?
- No, and by design it never will. Driply records access decisions and proves them; your administrator or the tool’s owner performs the actual change in each tool. Driply never holds write-access to your tools, which keeps its integration surface small and its security review short.
- Will Driply scale as we grow?
- It covers the governance fundamentals from roughly 10 to a few hundred people. If you later need automated provisioning across many systems, a heavier platform can complement it, many teams find they never need to.
- What does Driply integrate with?
- Read-only Google Workspace directory sync to build your roster, and Slack for requests and approvals. Every other tool is cataloged, not wired in, so there’s nothing brittle to maintain.