Free developer tool
Free Supabase RLS policy generator
Source on GitHubConfigure the policies
Access preset
Signed-in users can create, read, update and delete only their own rows.
Your SQL
5 statements-- Row-level security for "public"."posts" — preset: owner only.
-- Generated by the free supastack RLS tool: supastack.dev/tools/supabase-rls-generator
-- Postgres ORs policies together: drop any existing policies on this table before re-applying.
-- Assumes "public"."posts"."user_id" references auth.users(id).
alter table "public"."posts" enable row level security;
-- Select: signed-in users can only read rows they own.
create policy "posts_select_owner"
on "public"."posts"
for select to authenticated
using (auth.uid() = "posts"."user_id");
-- Insert: new rows must set "posts"."user_id" to the caller.
create policy "posts_insert_owner"
on "public"."posts"
for insert to authenticated
with check (auth.uid() = "posts"."user_id");
-- Update: only the owner can change a row — ownership can't be moved.
create policy "posts_update_owner"
on "public"."posts"
for update to authenticated
using (auth.uid() = "posts"."user_id")
with check (auth.uid() = "posts"."user_id");
-- Delete: only the owner can remove a row.
create policy "posts_delete_owner"
on "public"."posts"
for delete to authenticated
using (auth.uid() = "posts"."user_id");
Loved byfounders worldwide.
What early builders have shared about using the kit.
bynikojuliusI'm a marketer, not a full-time developer. Supastack brings auth, workspaces, billing, BYOK AI, email and themes together in one codebase. The AGENTS.md and prompts help me start building with Claude Code without learning every corner of the repo. It's a solid base for an AI SaaS.
Universepnpm verify:local, the theme packs and the block library helped me restyle my whole marketing site quickly. The kit is easy to work with.
Ka-Chun-MaWhile building Skin Profile, I could see how auth, billing, jobs and the AI router are configured. It feels complete.Maybe you?
Start building
PengGangjieI'm building Lixing, a local-first reflection app, so I didn't move it onto Supastack. I ran the monorepo on Windows and borrowed four patterns for my app: config, secure license storage, entitlements and a paywall. Those changes passed 26 tests behind a feature flag. I don't need auth or billing today, but I know where to look when Lixing needs a backend.
OpenMargin24I'm using Supastack for my app's backend now. I wish I'd had it from the start; it would have saved me even more work.
Raven S.I went through the repo in depth and ran the Rust tests. Few boilerplates ship a desktop option, so Supastack feels like a dream come true. The boundaries are written down and the code honors them — the desktop app never forks the web app's UI or auth.Your next product starts here.
Pay once. Keep building profitable products.