Beta Systems Garancy Suite

Beta Systems Garancy Suite is an identity-governance platform for controlling digital identities and access rights from onboarding through departure. It suits mid-sized and large organizations that need structured approvals, recertification, and governance for both applications and files. The strongest case is a compliance-oriented team that wants deployment flexibility and automated provisioning; organizations seeking transparent, self-serve pricing should look elsewhere.

Overview

Garancy centralizes identities, roles, groups, and permissions, then applies rules and approval workflows to access decisions. Joiner, mover, and leaver processes can be automated, while recurring access recertification gives managers a formal way to confirm or remove rights. Approved permissions can flow to connected systems through standard connectors or the uConnect connector, reducing manual account administration.

Its scope extends beyond application accounts. Garancy Data Access Governance controls unstructured-data access down to folder and file level in SharePoint, file servers, and shared mailboxes. That makes the suite more relevant to organizations whose compliance exposure includes documents and shared storage, not only SaaS applications.

Key features

Lifecycle, requests, and certification

Self-service authorization requests and flexible workflows let employees request access while designated approvers retain control. Rule-based permissions and centralized role management provide a structure for repeatable decisions. Access certifications support periodic review, and segregation-of-duties (SoD) controls help identify or prevent conflicting access combinations. Together, these capabilities fit audit-driven programs better than ad-hoc ticket handling, though they require a well-defined role and approval model to deliver value.

Provisioning and integrations

Garancy provisions approved access into target systems through standard connectors, uConnect, and, in release 26.1, SMART SCIM Connect for SCIM 2.0 applications. The stated examples include AWS, Salesforce, Atlassian, OpenAI, and Anthropic. A ServiceNow integration combines a Garancy connector, web services, and workflows so requests can provision access in target systems. This breadth is useful for mixed estates, while systems outside the connector coverage will need integration work.

Reporting and governance

Multidimensional reports and analyses expose roles, permissions, and risks for compliance work. The combination of reporting with file-level data governance gives security and audit teams a broader view than an identity directory alone.

Pricing

Garancy uses custom pricing. Customers can choose either a subscription or a one-time purchase, but neither option has a published price, seat allowance, quota, trial period, or renewal term.

Custom pricing is normal for an enterprise identity-governance deployment, but it makes direct comparison difficult. Budget owners should ask specifically about connector coverage, implementation, support service-level agreements, and any costs tied to deployment or scale.

Platforms

Garancy is offered through an API and web interface and can be self-hosted. The product can run on-premises or in the cloud, and customers can switch deployment models without losing functionality. That flexibility favors organizations with data-residency, infrastructure, or transition requirements, while teams wanting only a lightweight hosted service may find the suite more than they need.

Who it's for

Garancy targets mid-sized and large companies across financial services, manufacturing, retail, and IT services. It is a strong fit where lifecycle automation, access certifications, SoD controls, and unstructured-data governance must operate together. Its stated relevance to NIS-2, DORA, ISO 27001, the IT Security Act (KRITIS), BSI IT-Grundschutz, and TISAX also suits compliance programs shaped by those requirements. A five-step implementation process is presented as ready to launch in 10 weeks; organizations should validate that timetable against their systems and approval structures.

Pros and cons

• Pro: Covers joiner, mover, and leaver automation plus recurring certifications, addressing the full employee access lifecycle.
• Pro: Governs SharePoint, file servers, and shared mailboxes down to folder and file level, not just application accounts.
• Pro: On-premises, cloud, API, and self-hosted options accommodate varied architecture and migration plans.
• Pro: Standard connectors, uConnect, SCIM 2.0 support, and ServiceNow workflows can reduce manual provisioning across heterogeneous systems.
• Con: Subscription and one-time-purchase prices are both custom, so buyers cannot estimate cost from the product page.
• Con: Connector-dependent provisioning means less-common target systems may require additional integration effort.
• Con: The enterprise implementation and governance scope may be excessive for small organizations with simple access needs.

Alternatives

Browse the Identity Governance Software category for more options. Choose Evolveum midPoint if a free, open-source, self-hosted platform is the priority; clustering and selected features require a support subscription. Soffid Identity Governance Administration is worth considering for free binary downloads and a free trial. Pick Corma when a freemium model and a 10-app allowance meet your needs. Oracle Cloud Infrastructure Secret Management is a free API/web option focused on secrets rather than full lifecycle governance. Stitchflow offers a free first workflow and a paid ongoing plan. SailPoint IdentityIQ, Saviynt Enterprise Identity Cloud, and Torii are paid alternatives with enterprise identity-governance offerings and custom pricing.

Verdict

Choose Garancy Suite when your organization needs lifecycle identity management, formal access reviews, SoD controls, and file-level data governance in one platform, with the option to run on-premises or in the cloud. Its main drawback is commercial opacity: pricing and key terms require a sales process, and connector and implementation requirements should be examined before commitment.