Topic starter
12/06/2026 1:23 am
TL;DR: The underlying issue is not adoption alone but the governance burden that comes with sprawling SaaS access and usage, as Zluri says it raised $10 million in Series A funding led by MassMutual Ventures to expand SaaS discovery, manage integrations, and automate control of increasingly complex application estates, with more than 100 customers added in 2021 and 300-plus direct integrations reported.
Editorial analysis by NHI Mgmt Group, based on content published by Zluri: “SaaS Management Platform Zluri raises $10M led by MassMutual Ventures”.
By the numbers:
- The company says it added over 100 new customers from North American and Asian markets in the past year.
Key questions
Q: How can IT and IAM teams reduce SaaS sprawl without slowing the business?
A: They should standardise app ownership, review duplicate tools by function, and retire software that no longer has clear demand.
Q: Why do delegated SaaS integrations complicate identity governance?
A: They complicate governance because the access is often granted by business users or vendor workflows, yet the blast radius reaches production data and privileged APIs.
Q: What signals show that SaaS governance is not working?
A: Look for delayed offboarding, repeated manual exports, inconsistent access review responses, and inactive accounts that still carry paid licenses.
Practitioner guidance
- Define a SaaS control inventory Build a single inventory of all sanctioned applications, admin owners, and delegated integrations so governance starts from a complete estate view.
- Treat integrations as access relationships Review OAuth connections, connectors, and automation links as privileged access paths that require ownership, purpose, and revocation criteria.
- Bind automation to authoritative identity data Use source-of-truth identity and application ownership records before automating provisioning, deprovisioning, or access optimisation workflows.
Bottom line: SaaS growth becomes a governance problem when discovery, ownership, and integration oversight cannot keep pace with adoption.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
12/06/2026 11:17 am
SaaS sprawl is now an identity governance problem, not a procurement by-product. The funding story only makes sense because enterprises have reached a point where application growth outpaces control visibility. Once SaaS acquisition becomes frictionless, governance shifts from license management to identity and access orchestration across hundreds of connected services. The practitioner conclusion is that SaaS oversight belongs inside IAM and IGA operating models, not as a side process.
A few things that frame the scale:
- The average enterprise SaaS platform connects to 42 or more third-party applications through OAuth tokens, API keys, webhooks and automation platforms.
A question worth separating out:
Q: Should organisations prioritise SaaS discovery or access review first?
A: Discovery should come first when the app estate is poorly understood, because you cannot govern what you cannot see. But access review must follow quickly, otherwise discovery becomes a static inventory exercise. The right sequence is discover, assign ownership, then recertify or remove access.
👉 Read our full editorial: Zluri's $10m funding spotlights SaaS governance pressure