Warrant (now WorkOS FGA)
Capability scores
Methodology →- Authentication
- 2.5
- SSO & Federation
- 2.5
- Authorization
- 4.5
- Lifecycle & Provisioning
- 2.5
- MFA & Passwordless
- 2.0
- Governance & Audit
- 3.5
- Developer Experience
- 4.5
- Deployment Flexibility
- 3.5
- Pricing Transparency
- 3.5
- Support & Ecosystem
- 4.0
Scored 0–5 against a published rubric. Independent analysis, no vendor sponsorship.
Overview
Warrant was a Zanzibar-inspired fine-grained authorization (FGA) service with an Apache-2.0 open-source core. WorkOS acquired it in 2024 (announced 2024-04-23), and Warrant no longer exists as a standalone product: warrant.dev now carries one line, "Warrant -> Now WorkOS FGA." What WorkOS sells today under the FGA name is a re-architected product, not hosted Warrant. The open-source Warrant repository is still public, not archived, and links to WorkOS, but its last tagged release is v1.15.1 from 2024-06-10, and its README says that version handles only "low-to-moderate throughput."
What WorkOS FGA is good at
Resource-scoped roles for B2B SaaS without a new modeling language. In WorkOS's December 2025 post, FGA "extends the straightforward RBAC model to support nested, resource-scoped permissions," with up to five layers of hierarchical resource types. The FGA docs describe the mechanics: you define resource types (for example workspace, project, app) in the dashboard, register resources with a parent, and assign a user or group a role on a specific resource. Permissions flow to child resources automatically. Access checks answer three questions (can this user do X on Y, which resources can this user reach, who can reach this resource), at a documented sub-50 ms p95 with strong consistency. Organization-scoped roles are embedded in AuthKit access tokens, so org-wide checks need no API call, and IdP group mapping works for org-level roles. Existing RBAC customers need no migration.
Where it falls short
It is no longer relationship-based access control (ReBAC) in the Zanzibar sense. WorkOS explicitly argues against syncing high-cardinality resources into an external system; instead, applications keep fine-grained data locally and register only stable parent resources. That is pragmatic, but it means sharing models such as per-document grants to arbitrary users are your application's job. Several pieces were still listed as coming soon when we checked: IdP role mapping to resource-scoped roles, per-user permission grants or exclusions, edge caches, and non-user subject types. The product only makes sense inside WorkOS, and the open-source engine has had no tagged release since June 2024, so do not plan production use on it.
Pricing
Not published separately. As of 2026-11-05 the WorkOS pricing page lists AuthKit, SSO, Directory Sync, Audit Logs, and other products but no FGA or RBAC line item; ask WorkOS sales.
Best for, and who should look elsewhere
Choose WorkOS FGA if you already use WorkOS for SSO and SCIM and your permission model is a hierarchy of tenant resources. If you need Zanzibar-style relationship tuples, use OpenFGA or AuthZed (see OpenFGA vs AuthZed vs Cerbos). For policy-as-code, compare Cerbos, Permit.io, or Styra OPA. The RBAC to ReBAC guide and best authorization tools help frame the choice.
Bottom line
Warrant is gone as a product. Its successor, WorkOS FGA, is a clean hierarchical RBAC extension for WorkOS customers, not a general-purpose ReBAC engine.
Warrant (now WorkOS FGA): frequently asked questions
- Is Warrant still available as a standalone product?
- No. WorkOS announced its acquisition of Warrant on 2024-04-23, and warrant.dev now shows a single line, 'Warrant -> Now WorkOS FGA.' The hosted Warrant service is no longer sold on its own. The open-source Warrant engine remains on GitHub under Apache-2.0, but its last tagged release was v1.15.1 on 2024-06-10.
- Is WorkOS FGA the same as Warrant?
- Not in design. WorkOS's December 2025 FGA post describes FGA as an extension of WorkOS RBAC with up to five layers of hierarchical resource types and no new schema language, and it criticizes traditional Zanzibar-inspired systems for requiring high-cardinality resources to be synced. Warrant was a Zanzibar-inspired relationship engine. Treat current WorkOS FGA as a new product built by the combined team.
- What should Warrant users migrate to?
- If you are a WorkOS customer whose model is a resource hierarchy (organization, workspace, project), WorkOS FGA is the native path. If you depend on arbitrary relationship tuples and a schema language, look at OpenFGA or AuthZed SpiceDB, both Zanzibar-style; for policy-as-code, Cerbos or OPA.
More Authorization vendors
All Authorization →- AuthZed4.3/5
- Styra / Open Policy Agent4.3/5
- OpenFGA4.2/5
- AWS Verified Permissions4.1/5
- Cerbos4/5
Related on Start with Identity
- CVESMB Server Kerberos reflection via Ghost SPNs
October 2025 follow-on to CVE-2025-33073. SMB Server elevation of privilege by combining Kerberos reflection with Ghost SPNs and DNS self-registration.
- CVEWindows SMB Client improper authentication (tampering)
Windows SMB Client improper authentication (CWE-287) that allows tampering. Not an Entra token bug, but it sits in the same Microsoft identity-adjacent patch tr
- CVEWindows SMB Kerberos reflection elevation of privilege
Kerberos authentication reflection on SMB, still abusable via Ghost SPNs after the first fix. High-severity elevation of privilege on Windows.
- VendorAserto
strong
- Comparisonauthzed-vs-openfga
Both are Apache 2.0 Zanzibar-style ReBAC engines. SpiceDB (AuthZed) has token-based point-in-time consistency and capacity-priced managed tiers; OpenFGA is a CN
- VendorAWS Verified Permissions
strong_contender
By SWI Community Team · Last evaluated 2026-11-05
Independent, community-driven analysis. No vendor sponsorship. Compiled from public research and community input and verified on a best-effort basis, so details may be incomplete or out of date. Scores are opinions, not advice. Trademarks belong to their owners; mention does not imply affiliation or endorsement. See the full disclaimer, or send corrections to community@startwithidentity.com.