HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
Permify
permify
Go2022–2026
Permify / permify

permify

An open-source authorization as a service inspired by Google Zanzibar, designed to build and manage fine-grained and scalable authorization systems for any application. — Permify is now part of FusionAuth 🎉

9Distinct people
11Mentions
0Explicit recommenders
6KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

An open-source authorization as a service inspired by Google Zanzibar, designed to build and manage fine-grained and scalable authorization systems for any application. — Permify is now part of FusionAuth 🎉

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 1:49:46 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year11 dated mentions

Observed mentions: 2022-07-14 14:38:14 UTC to 2026-05-02 12:12:41 UTC.

0123452022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 5 mentions; 1 submissions, 4 comments20222023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 3 mentions; 2 submissions, 1 comments20242025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC514
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC110
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC321
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC101
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC101

What Hacker News says

11 sources
We've had community members bring this up[0]. While there are a variety of approaches, currently our recommended solution is to use the Watch API[1] to create Leopard-style (matrix) indexes in the client’s database to enable efficient permission filtering using schema and YAML-based index definitions. We started down the path of building an example watch consumer[2] but both the team and the interested community members were pulled off it for reasons, but not for technical ones. This FAQ may be helpful to learn more about leopard indexes[3]. 0: https://github.com/Permify/permify/issues/2681 1: https://fusionauth.io/permify-docs/api-reference/watch/watch... 2: https://github.com/Permify/indexer 3: http://nil.csail.mit.edu/6.5840/2023/papers/zanzibar-faq.txt
In We Built an Authorization Engine That the Fortune 100 Bet On
ucatbas·Aug 21, 2024Submission

Show HN: Permify 1.0 – Open-source fine-grained authorization service

Permify was born out of our repeated struggles with authorization. Like any other piece of software, authorization starts small but as things grow scaling it becomes a real pain and begins to hinder product development processes. Ad-hoc authorization systems scattered throughout your app’s codebase are hard to manage, reason about, and iterate on as the company grows. Also you will need to have more specific access controls as things grow. Traditional approaches like RBAC is inefficient for defining granular permissions such as resource-specific, hierarchical, or context-aware permissions. Architecture is another problem, in a distributed system you’re going to need a solid plan to manage permissions between your services — all while ensuring high availability and providing low latency in access checks for sure. We’ve created an open-sour
Read the rest
ce project to eliminate the authorization burden for devs. It’s Permify, an Authorization-as-a-Service to help developers build and manage their authorization in a scalable, secure, and extendable manner. And last week, we released the first major version (v1.0.0) of it! Here is how Permify helps you handle authorization. - Centralize & Standardize Your Authorization: Abstract your authorization logic from your codebase and application logic to easily reason, test, and debug your authorization. Treat your authorization as a sole entity and move faster within your core development. - Build Granular Permissions For Any Case You Have: You can create granular (resource-specific, hierarchical, context aware, etc) permissions and policies using Permify’s domain specific language that is compatible with RBAC, ReBAC and ABAC. - Set Custom Authorization For Your Tenants: Set up isolated authorization logic and custom permissions for your vendors/organizations (tenants) and manage them in a single place. - Scale Your Authorization As You Wish: Achieve lightning-fast response times down to 10ms for access checks with a proven infrastructure inspired by Google Zanzibar, Google’s Consistent, Global Authorization System. Try it out and send any feedback our way!
154 points · Open discussion

Show HN: AI assistant powered by Groq to generate authorization models

Hi I'm Karan, one of the maintainers of Permify (https://github.com/Permify/permify), an open source authorization service to build scalable authorization systems. I want to share with you that we've built an AI assistant to help modeling your desired authorization logic! You can basically describe your authorization logic in Permify AI and it will generate the respective model and semantics accordingly. Think of it like ChatGPT for authorization modeling/policy generation. Here's the project if you would like to play with it: https://ai.permify.co/. Brief backstory: Since authorization is generally a domain specific issue use cases vary widely - roles, relationships, attributes, hierarchies between business units, contextual permissions, etc. To address this, we're offering a domain specific language that we built purely using golang to
Read the rest
help model authorization logic programmatically. You can see what it looks like with sample examples in our playground: https://play.permify.co/ Although our domain specific language helps our users significantly, the general idea of policy generation is hard challenging if you have complex authorization logic and versatile permission requirements. Additionally, the flexibility of our modeling language allows for achieving the same policy/permissions through various approaches. But creating the best possible policy is crucial for several reasons including the performance of access checks, the readability of the authorization logic, visibility, and achieving least privilege, etc. When we tallied up all those reasons, it hit us: using AI could really smooth out the policy generation process. It could not only reduce the engineering effort but also yield the best possible results. That's why we integrated Groq to make to create Permify AI! Would love to get your feedback on this!
12 points · Open discussion
egea·Nov 22, 2023Submission

Show HN: Blending Go and WebAssembly to Build Authorization Playground

Hi folks, I’m one of the maintainers and co-founder of the Go OSS project Permify (https://github.com/Permify/permify), an open-source authorization infrastructure inspired by Google Zanzibar. I would like to share a post where we aimed to provide a brief overview of how we integrated WASM with Golang to provide a richer user experience in our open-source playground. You can use the playground to create and test any authorization logic in a browser. The playground has three main sections: Schema: to model your authorization logic through our domanin specific language we built. Data: to create sample authorization data according to the model for use in tests. Enforcement: to test your authorization structure bt access check scenarios. Here's the post if you're interested: https://www.permify.co/post/wasm-go/ And here's the playground: http
Read the rest
s://play.permify.co/ Appreciate your time!
5 points · Open discussion
Love the growing number of OSS Zanzibar implementations, and congrats to the Aserto team for launching Topaz! Ory Keto's intro video @ SV IAM User Group [0] is worth a watch. Other OSS Zanzibar implementations: - https://github.com/authzed/spicedb - https://github.com/Permify/permify - https://github.com/openfga/openfga [0]: https://www.youtube.com/watch?v=3vtTFLB_jDo [Disclaimer: On the OpenFGA team]
In Show HN: Topaz: open-source authorization combining the best of OPA and Zanzibar
We are super excited to announce that we launched Permify Playground to create and test your authorization in a browser. First of all, we build our playground based on our open-source authorization service by compiling with Web Assembly [1]. This helps us to give you browser compatible test environment that you can test Permify[2] fast and easily within your browser. Our playground consists 3 sections; - Authorization Model: You can model & test your authorization logic through our DSL. - Visualizer: Visualize your relationships and model to make it easier to reason about them. - Authorization Data: Create sample authorization data according to the model. - Access Checks: To test your authorization structure by sending access checks. [1] https://webassembly.org/ [2] https://github.com/permify/permify
In Permify launches Playground: Test your authorization in browser
Congrats on the launch! One of the founders of Permify is here. We love this approach and Google Zanzibar paper, as we're a taking pretty similar approach with Permify but as an Open-source product.[1] As some mentioned there are legacy tools like AWS Cognito, which mostly focuses on authentication and simpler authorization use cases. But it's evident for us, that in order to solve these problems you have mentioned[2] we need a product which can cover more complex use cases and easier to start with. [1] https://github.com/Permify/permify [2]https://www.permify.co/post/why-decouple-authorizations
In Launch HN: Warrant (YC S21) – Authorization and access control as a service
Interesting to see another project open sourced around Google Zanzibar. On a timeline for context: - Ory came out first with Ory Keto ( https://github.com/ory/keto ) which is trying to be a close adaptation of the paper. Initially, many concepts were missing but they are making a lot of progress with the DSL and it interfaces with the rest of Ory (OAuth2, User Mangement) - Authzed came out as a SaaS only, open sorucing the code base later on at https://github.com/authzed/spicedb - Auth0 has been playing around with Zanzibar concepts in various forms and published a beta service at https://dashboard.fga.dev - apparently now also open source parts of it similar to what Authzed did: https://github.com/openfga - Permify - who on a side note spammed me quite a lot with outreach because I was active in these communities - joins as well https://
Read the rest
github.com/Permify/permify It's exciting to see so much movement, yet also sad that so many companies are brewing their own beer instead of working collaborative on the more succesful projects. Feels like we'll just end up with one or two successful projects (looking at Ory / Auth0 here) with the rest perishing. I'm wondering if there truly is a business model for just this permission system as a saas service (looks like this is what everyone is going with). Here I'm giving Auth0 probably the biggest plus as they have an established identity service. Then again, Okta (parent of Auth0) and Auth0 themselves are not particularly known for good business practices that we usually expect from developer tooling. What's refreshing though with Permify is that they are trying a bit of a different approach to Zanzibar!
In Show HN: Permify – Open-source authorization service based on Google Zanzibar

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.