Show HN: Underrated Postgres: Build Multi-Tenancy with Row-Level Security

#1

Post by noctarius » Thu, Sep 18, 2025, 9:46 AM UTC

Utilizing Postgres' RLS feature to isolate user data instead of easy-to-forget where-clauses, is such an underrated use case, I really wonder why not more people use it.

If you prefer code over the blog post, I've put the full application example on GitHub. Would love to hear your thoughts.

https://github.com/simplyblock/example-rls-invoicing

Show HN: Underrated Postgres: Build Multi-Tenancy with Row-Level Security
simplyblock.io

Re: Show HN: Underrated Postgres: Build Multi-Tenancy with Row-Level Security

#2

Post by _jsmh » Thu, Sep 18, 2025, 9:58 AM UTC

From Postgres docs https://www.postgresql.org/docs/current/ddl-rowsecurity.html

I built multi-tenant services and never used RLS because it's complicated.

Re: Show HN: Underrated Postgres: Build Multi-Tenancy with Row-Level Security

#3

Post by MohanYC » Thu, Sep 18, 2025, 10:01 AM UTC

Great share!

Re: Show HN: Underrated Postgres: Build Multi-Tenancy with Row-Level Security

#4

Post by noctarius » Thu, Sep 18, 2025, 10:03 AM UTC

_jsmh wrote: post #2

From Postgres docs https://www.postgresql.org/docs/current/ddl-rowsecurity.html I built multi-tenant services and never used RLS because it's complicated.

It is complicated to initially wrap your head around, I agree. That's why I thought a demo application is the best way to show that it doesn't have to be super complicated once understood.

Like many things in PG, they aren't always easy to get right away I remember my first time with it years and years ago.

Re: Show HN: Underrated Postgres: Build Multi-Tenancy with Row-Level Security

#5

Post by noctarius » Thu, Sep 18, 2025, 10:04 AM UTC

MohanYC wrote: post #3

Great share!

Thank you very much :)

Happy to get any idea on how to make it even better!