<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: oussama larhnimi</title>
    <description>The latest articles on DEV Community by oussama larhnimi (@echosso).</description>
    <link>https://dev.to/echosso</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4123155%2F916de7b1-fc57-406d-b83b-b7d575fb744c.jpeg</url>
      <title>DEV Community: oussama larhnimi</title>
      <link>https://dev.to/echosso</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/echosso"/>
    <language>en</language>
    <item>
      <title>I’m building Permetra an open-source access graph for Supabase</title>
      <dc:creator>oussama larhnimi</dc:creator>
      <pubDate>Sun, 20 Sep 2026 01:20:43 +0000</pubDate>
      <link>https://dev.to/echosso/im-building-permetra-an-open-source-access-graph-for-supabase-4i4</link>
      <guid>https://dev.to/echosso/im-building-permetra-an-open-source-access-graph-for-supabase-4i4</guid>
      <description>&lt;p&gt;Hey everyone 👋&lt;/p&gt;

&lt;p&gt;I’m building &lt;strong&gt;&lt;a href="https://www.linkedin.com/company/permetra" rel="noopener noreferrer"&gt;Permetra&lt;/a&gt;&lt;/strong&gt;, an open-source security tool for Supabase.&lt;/p&gt;

&lt;p&gt;The idea is simple:&lt;br&gt;
**&lt;br&gt;
Who can access what in your Supabase application  and why?**&lt;/p&gt;

&lt;p&gt;As an app grows, access control gets distributed across users, roles, tenants, database grants, tables, functions, and RLS policies. It can become difficult to understand the complete access picture.&lt;/p&gt;

&lt;p&gt;Permetra turns this into an interactive, BloodHound-inspired graph so you can explore relationships and access paths visually.&lt;/p&gt;

&lt;p&gt;The goal is to help developers:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Visualize users, roles, tenants, tables, policies, and permissions&lt;/li&gt;
&lt;li&gt;Understand why a user can access a resource&lt;/li&gt;
&lt;li&gt;Discover unexpected access paths&lt;/li&gt;
&lt;li&gt;Review tenant isolation and authorization&lt;/li&gt;
&lt;li&gt;Make Supabase security easier to understand&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;I’m still building the first version and would love feedback from Supabase developers, security engineers, and open-source contributors.&lt;/p&gt;

&lt;p&gt;If you use Supabase: Would something like this be useful for you? What would you want it to detect first?&lt;/p&gt;

&lt;p&gt;Early testers and contributors are very welcome 🚀&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fer7wue9m5v093qdtnyta.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fer7wue9m5v093qdtnyta.png" alt="MVP" width="800" height="401"&gt;&lt;/a&gt;&lt;/p&gt;

</description>
      <category>database</category>
      <category>opensource</category>
      <category>security</category>
      <category>showdev</category>
    </item>
  </channel>
</rss>
