Why should you care?

PostgresVerse MVP uses Supabase so frontend gets API and postgres without custom backend for first sprint.

See it live — copy this example

Run in pgAdmin or psql.

-- Supabase SQL editor / psql to project
ALTER TABLE orders ENABLE ROW LEVEL SECURITY;

CREATE POLICY "users see own orders" ON orders
  FOR SELECT
  USING (auth.uid() = user_id);

GRANT SELECT ON orders TO authenticated;

What happened?

• auth.uid() is Supabase JWT helper in policies.
• authenticated role maps to logged-in API users.
• RLS enforces row access for PostgREST automatically.

Practice next

1. Create Supabase project; note connection string and anon key.
2. Create orders with user_id uuid column in Table Editor.
3. Add RLS policy in SQL editor.
4. Add realtime publication on orders for live dashboard lesson.
5. Link storage bucket policy to postgres metadata table.

Remember

Supabase is postgres + auth + PostgREST. RLS policies are mandatory for public API safety. Direct postgres connection still available for migrations.

PostgresVerse hackathon MVP

Team ships order tracker in 48h using Supabase RLS and hosted postgres.

Outcome: Migrates to self-hosted RDS later with same SQL schema.