warrant

Warrant is a highly scalable, centralized authorization service based on Google Zanzibar, used for defining, querying, and auditing application authorization models and access control rules. (by warrant-dev)
Add to my DEV experience access-control Authorization Golang Rbac Acl fine-grained-access-control fine-grained-authorization Permissions Abac Authz role-based-access-control ciam rebac zanzibar Iam entitlements pricing-tiers zero-trust relationship-based-access-control fgac
Source Code
warrant.dev
warrant Reviews
Suggest alternative
Edit details
The modern identity platform for B2B SaaS
The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
workos.com
Sponsored

Warrant Alternatives

Similar projects and alternatives to warrant

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better warrant alternative or higher similarity.
Suggest an alternative to warrant

warrant reviews and mentions

Posts with mentions or reviews of warrant. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2024-02-05.
  • A list of SaaS, PaaS and IaaS offerings that have free tiers of interest to devops and infradev
    47 projects | dev.to | 5 Feb 2024
    Warrant — Hosted enterprise-grade authorization and access control service for your apps. The free tier includes 1 million monthly API requests and 1,000 authz rules.
  • How Open ID Connect Works
    1 project | news.ycombinator.com | 4 Jan 2024
    The specific challenge with authz in the app layer is that different apps can have different access models with varying complexity, especially the more granular you get (e.g. implementing fine grained access to specific objects/resources - like Google Docs).

    Personally, I think a rebac (relationship/graph based) approach works best for apps because permissions in applications are mostly relational and/or hierarchical (levels of groups). There are authz systems out there such as Warrant https://warrant.dev/ (I'm a founder) in which you can define a custom access model as a schema and enforce it in your app.

  • How to Do Authorization - A Decision Framework: Part 1
    7 projects | dev.to | 14 Dec 2023
    Let's use warrant.dev as an example. The system provides a set of REST APIs for you to define object types and access policies (called warrants). The general process is first to create object types using HTTP POST:
  • Warrant – open-source Access Control Service
    1 project | news.ycombinator.com | 15 Nov 2023
  • A guide to Auth & Access Control in web apps 🔐
    8 projects | dev.to | 7 Nov 2023
    https://warrant.dev/ (Provider) Relatively new authZ provider, they have a dashboard where you can manage your rules in a central location and then use them from multiple languages via their SDKs, even on the client to perform UI checks. Rules can also be managed programmatically via SDK.
  • Warrant v1.0 - Highly scalable, centralized authorization service based on Google Zanzibar, now v1.0 and production-ready
    1 project | /r/golang | 5 Nov 2023
  • warrant VS openfga - a user suggested alternative
    2 projects | 15 Aug 2023
  • Policy as Code vs. Policy as Graph Comparison
    2 projects | news.ycombinator.com | 30 Jun 2023
    I would describe this debate more as Policy-as-Data (Zanzibar) vs Policy-as-Code (OPA et al).

    In Zanzibar, all of the information required to make an authorization decision (namespaces, relationship tuples, etc.) is stored in Zanzibar, and the decision engine resolves access checks based on this data. This data can be scaled horizontally (and consistently) as needed for an application’s needs. This makes Zanzibar a centralized, unified solution for all of an application’s authorization needs. I’ve found this approach more purpose built / well suited for application authorization.

    With OPA and other policy engines, the data required for performing access checks lives somewhere else (maybe the application’s database) and must be separately queried and included as part of the authorization check because OPA et al. are stateless decision engines. This makes it such that you need to piece together data from different sources in order to get your final decision, which IMO is something most developers don’t want to deal with.

    On the flip side, Zanzibar’s “namespaces” are a very simple policy layer not well suited to querying against data outside of Zanzibar’s scope (e.g. geolocation, time, etc). For scenarios like this, a full fledged policy-as-code solution is great. However, it should be noted that some open source Zanzibar implementations like Warrant[1] and SpiceDB[2] (mentioned in the article) also offer a policy-as-code layer on top of Zanzibar’s graph-based/ReBAC approach to tackle these scenarios.

    Disclaimer, I’m one of the founders of Warrant.

    [1] https://github.com/warrant-dev/warrant

    [2] https://github.com/authzed/spicedb

  • Show HN: Open-Source, Google Zanzibar Inspired Authorization Service
    2 projects | news.ycombinator.com | 29 Jun 2023
    Hey HN, I recently shared my thoughts on why Google Zanzibar is a great solution for implementing authorization[1] and why we decided to build Warrant’s core authz service using key concepts from the Zanzibar paper. As I mentioned in the post, we recently open sourced the authz service powering our managed cloud service, Warrant Cloud[2], so I thought I’d share it with everyone here. Cheers!

    [1] https://news.ycombinator.com/item?id=36470943

    [2] https://warrant.dev/

  • Why Google Zanzibar Shines at Building Authorization
    2 projects | dev.to | 28 Jun 2023
    More than two years after choosing to build Warrant atop Zanzibar’s core principles, we’re extremely happy with our decision. Doing so gave us a solid technical foundation on which to tackle the various complex authorization challenges companies face today. As we continue to encounter new scenarios and use cases, we’ll keep iterating on Warrant to ensure it’s the most capable authorization service. To share what we learn and what we build with the developer community, we recently open-sourced the core authorization engine that powers our fully managed authorization platform, Warrant Cloud. If you’re interested in authorization (or Zanzibar), check it out and give it a star!
  • A note from our sponsor - InfluxDB
    www.influxdata.com | 27 Apr 2024
    Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality. Learn more →

Stats

Basic warrant repo stats
39
979
8.9
5 days ago

warrant-dev/warrant is an open source project licensed under Apache License 2.0 which is an OSI approved license.

The primary programming language of warrant is Go.

Popular Comparisons

  1. warrant VS cerbos
  2. warrant VS OPAL
  3. warrant VS sablier
  4. warrant VS yai
  5. warrant VS whisper
  6. warrant VS Ory Hydra
  7. warrant VS jolt
  8. warrant VS tfautomv
  9. warrant VS schemahero
  10. warrant VS Caddy

Sponsored
SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives
www.saashub.com