Alternatives
Products that do what Enforce Access Policies on Postgres does
- 1SF
2015 · github.com
- 2AN
2017 · cossacklabs.com
- 3PE
2018 · bluejekyll.github.io
- 4RP
2020 · github.com
- 5PN
2020 · ongres.com
- 6SF
2020 · github.com
- 7PS
2019 · github.com
- 8PA
2015 · pgcli.com
- 9AE
2016 · github.com
- 10PC
2016 · github.com
- 11FS
2020 · github.com
- 12DL
2014 · databaselabs.io
- 13
- 14AS
2020 · github.com
- 15IS
2022 · github.com
- 16OO
2020 · osohq.com
- 17MP
2020 · dev.to
- 18AS
2023 · github.com
- 19AU
2019 · pgmustard.com
- 20TS
2018 · github.com
- 21PA
2019 · subzero.cloud
- 22ZA
Hi HN, I'm Jiasheng, co-creator of ZenStack. Access control usually ends up scattered across app code instead of living with the data model — and that's riskier when the code is written by an agent, since it's easy to ship a query with a missing or incomplete authorization check. ZenStack enforces policy (RBAC/ABAC/relation-based) directly at the ORM layer, on top of Kysely, so every query gets checked the same way regardless of who wrote it and who is calling it. Postgres RLS is an option too, but it's hard to maintain and scale, and it's Postgres-only — ZenStack's approach is…
Jul 2026 · zenstack.framer.website
- 23PI
2019 · github.com
- 24AO
2020 · github.com
Ranked by how close each launch is in meaning, then by votes. Refine with a description →