Name: Zluri
Brand: Zluri
Rating: 4.6 (252 reviews)

Published Oct 15, 2026

01Common complaints

- Company sizes or stages where this product is overkill or insufficient - Early-stage startups (fewer than ~100 employees) with limited SaaS sprawl may find the implementation overhead and sales-led procurement model disproportionate to needs. - Industries or use cases where competitors are clearly superior - If procurement and spend optimization workflows are the primary requirement, specialized SMPs or procurement-focused tools may provide faster ROI. - If deep, traditional IGA functionality (fine-grained entitlement governance across complex on-prem systems) is required, established IGA suites may be more appropriate. - Technical requirements that this product cannot meet - If the environment requires exhaustive connector coverage for niche or legacy applications and partial coverage is unacceptable, proceed with caution and validate connector roadmaps. - Budget constraints that make alternatives more appropriate - Organizations that require transparent, low-cost self-serve pricing may prefer alternatives with published pricing. - Specific workflows or integrations where the product falls short - If a governance program relies heavily on endpoint or browser agents, note independent review commentary on agent limitations and validate whether this affects the environment. - Red flags in the buying process - No public free-trial terms were identified in this research run; buyers should clarify contract length, renewal terms, and price-protection clauses. - Current limitations acknowledged by the vendor - Documentation indicates that certain features (for example, Approver Insights) are available to a subset of organizations or are feature-gated. - Features on the roadmap (not yet available) - No roadmap items with public dates were identified in the accessible sources. - Scale limitations - No public scale ceilings were identified in the available documentation. - Security or compliance gaps - Certification claims exist, but public proof for scope, dates, and auditors is not fully disclosed in the sources accessed; buyers should verify under NDA. - Technical debt or architectural limitations mentioned in reviews - Community comments raise concerns about release discipline (anecdotes of emergency fixes during sales interactions), suggesting potential process immaturity in some cases. - API limitations or integration constraints - Community and independent review sources imply connector and browser-agent constraints; validate API access, rate limits, and connector maintenance commitments.

Why some customers left for competitors (churn reasons)

Direct churn narratives were not strongly represented in accessible review snippets.
Based on complaints and product comparisons, plausible churn drivers include:
- Organizations requiring very mature IGA depth (complex entitlement modeling) may prefer established IGA vendors.
- Organizations prioritizing procurement and finance-grade spend workflows may choose SMPs with deeper spend functionality.

02Why they buy

- Competitive advantages observed in customer feedback (separate from vendor marketing) - Usability: some reviewers describe the interface as intuitive and relatively easy to learn. - Support: select reviewers reported proactive, hands-on troubleshooting during integration efforts. - Features and capabilities that may differentiate the product - The vendor emphasizes a combined approach to identity governance and SaaS management; buyers should validate the depth of access automation actions, entitlement modeling, and certification workflows against specific requirements. - Differentiation from competitors based on reviews - Reviewer themes suggest a combined visibility and automation approach (discovery + governance + optimization), though competitors make similar convergence claims and may differ in maturity and specialization. - Value propositions with evidence from case studies - This research did not find independently verified ROI case studies; treat savings and ROI claims as directional unless supported by customer-authored evidence. - Areas where competitors have advantages - More mature documentation and enablement ecosystems - Clearer public security attestations and trust centers - Stronger specialization in either deep IGA or procurement/spend workflows

Why customers chose this product over alternatives

Review sentiment indicates perceived value in:
- Discovery and visibility across SaaS
- Workflow automation for onboarding/offboarding and access governance
- Cost optimization and licensing insights

03Field reports

Direct quotes from Gartner Peer Insights, Reddit, TrustRadius, G2, HackerNews

- Gartner Peer Insights (positive) - "Working with [named vendor contacts] and the Zluri team has been a genuinely positive experience… provide detailed walkthroughs, help troubleshoot integration challenges…" (Reviewer, Gartner Peer Insights). - "Zluri is very intuitive to understand, the UI can be picked up quite quickly…" (Reviewer, Gartner Peer Insights). - Reddit (mixed/negative) - Community thread: "They pushed code to production during a sales call (to fix a bug), which means they clearly do NOT have proper review and testing in place." (community forum post). - Same thread noted both positive and negative points: Zluri demonstrated substantial discovery capabilities but felt early-stage in some areas; support responses were inconsistent, and some integrations did not always synchronize reliably. - Pricing anecdote: community posts referenced an anecdotal per-user price for a standard plan (anecdotal). - TrustRadius - Listing showed a relatively high score on the platform with a small sample size, suggesting limited representation on that site relative to larger review ecosystems. - G2 - Public snapshots available during research showed a moderate review footprint and an accessible average rating; some reviews were identified as vendor-invited or incentivized, which can bias sentiment. - HackerNews - Targeted searches during the research window did not surface prominent discussions in accessible results.

Balance: include both high-rated and low-rated reviews with equal weight

Reviews accessed on major platforms (G2, Gartner, TrustRadius) were dominated by higher ratings in accessible snippets; lower-rated narratives tended to appear more in independent community forums such as Reddit.
Buyer caution: when public review distributions show few low-star reviews, confirm whether reviews are vendor-invited and cross-check with independent community forums.

Common criticisms and complaints (support issues, bugs, missing features)

Setup and integration effort and time-to-value
Documentation gaps
Endpoint/browser agent limitations
Questions about release and quality processes (community anecdotes of emergency fixes)
Integration synchronization reliability concerns

Specific outcomes customers achieved (with metrics when available)

Vendor and third-party sources emphasize cost savings and faster discovery, but this research did not identify independently verified ROI metrics.

Customer pain points and frustrations mentioned in reviews

Integration hurdles and reliability issues
Support inconsistency
Documentation limitations

Deal-breakers and reasons customers didn't purchase

Sales-led pricing with limited public tiers can be a blocker for SMBs or teams seeking self-serve options.
Organizations with strict software development lifecycle or change-management expectations may be cautious due to community quality-control anecdotes.

Case Studies

- Detailed customer success stories with metrics - This research did not locate detailed, metric-heavy, independently validated customer case studies from Zluri in the publicly accessible sources reviewed. - Specific results and quantified business impact - Vendor materials frequently imply cost savings and governance automation benefits, but independent validation and methodological detail were not found in the sources accessed. - Implementation details and time to value - Indirect evidence suggests implementation can be non-trivial, with setup and integration troubleshooting cited in user reviews and community discussions. - Challenges faced during adoption and how they were resolved - Reviewer comments indicate troubleshooting integration challenges was a common adoption activity; specific remediation details are generally limited to vendor or customer-owned case notes. - Critical: Note when metrics are vendor-published without independent verification - Any ROI or cost‑savings claims should be treated as vendor-published unless supported by customer-authored materials that include detailed methodology. - Include mixed results - projects that struggled or failed when available - Industry community threads and forums surface negative operational signals (process quality concerns; synchronization issues), but accessible sources do not document fully failed enterprise deployments.

04Best fit

- Company sizes - Likely best fit - Mid-market to enterprise organizations - Companies with significant SaaS sprawl and multiple identity providers or directories - Evidence signals - Reviewer profiles and vendor positioning are consistent with a mid-market to enterprise focus. - Industries and verticals where adoption is strongest - Installation and review data indicate usage across sectors such as information technology, real estate, and finance/insurance. Public named customer examples were not captured in this research run. - Roles and personas: decision makers AND end users - Decision makers - Head of IT / IT Director - IAM / Security leadership - Procurement / Finance stakeholders for spend governance - End users - IT administrators managing connectors and workflows - Application owners and approvers managing access approvals and reviews - Pain points and challenges the product addresses - Shadow IT and shadow AI discovery - Manual joiner-mover-leaver processes - Access reviews to support audit readiness (e.g., SOX/SOC 2) - License sprawl and underutilization - Qualification criteria: what makes a good fit - Organizations with multiple SaaS applications and inconsistent provisioning - Organizations that need auditable access governance across many applications - Organizations that can assign an implementation owner and allocate time to integrations - Deal disqualifiers: circumstances where the product is a poor fit - Very small teams that require transparent self-serve pricing and minimal setup - Organizations that require exhaustive public documentation and formalized enablement programs - Environments in which critical applications lack stable connectors and cannot accept manual workarounds - Real customer examples with company names when available - Not captured from accessible sources in this research run.

05The pitch

What the product does (core value proposition in objective terms)

- Zluri is an Identity Governance & Administration (IGA) and SaaS management platform that centralizes discovery of applications and identities, access requests, joiner-mover-leaver (JML) workflows, access reviews/recertifications, and SaaS spend/license optimization. - Primary capability areas identified in materials: - Visibility: discover SaaS applications (including "shadow IT/AI") and identities. - Governance: access requests, access reviews/recertification, policy-based workflows. - Optimization: usage analytics, identification of underutilized licenses, and spend controls.

Target market and market positioning

- Primary buyers/users appear to be: - IT Operations / IT Management teams responsible for SaaS portfolio governance - Security / IAM / GRC teams needing access reviews and audit readiness - Finance / Procurement stakeholders for spend and renewal management - Market positioning spans two adjacent categories: - SaaS Management Platform (SMP) - IGA / identity governance features (access requests + access reviews) - The convergence of SMP and IGA functionality is also presented by some competitors (notably Torii).

Get a comprehensive analysis of Zluri including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →