Hey Supabase community 👋
I’m currently building Permetra, a nonprofit, open-source project inspired by BloodHound’s graph-based approach to understanding relationships and access.
The idea started with a simple question:
Who can access what in a Supabase project and why?
Permetra aims to visualize users, roles, grants, tables, RLS policies, and the relationships between them as an interactive access graph.
It’s still in development and hasn’t been publicly released yet. Before I get too far, I’d really like to hear from people actually building with Supabase.
What would make something like this useful for you?
Are there parts of RLS, permissions, roles, or access relationships that become difficult to understand as your project grows?
I’m building Permetra in the open and will share the repository once it’s ready for early testing.
For now, I’m sharing development updates here: Permetra
Feedback, ideas, and criticism are very welcome. 🙌
https://github.com/user-attachments/assets/c055d4a2-b2f0-4c13-8bc7-c810641783b3
Oussama Larhnimi introduces Permetra, a nonprofit, open-source project designed to visualize access relationships in Supabase projects. The tool aims to help users understand who can access what and why, by mapping users, roles, grants, tables, and RLS policies into an interactive graph. Oussama seeks feedback from the Supabase community to refine the project before its public release.