Show HN: Supakey – let users bring their own Supabase to your app

Supakey lets users bring their own Supabase project to your app. You add “Sign in with Supakey” (OAuth). On first consent, Supakey deploys your app’s schema into the user’s Supabase (least-privilege, RLS on). From then on, your app talks directly to their database using app-scoped credentials—no central multi-tenant DB to run.

Why

Users keep control and portability of their data.

Developers ship simple apps without hosting and babysitting per-user data.

How it works

User signs up on Supakey and connects their Supabase project.

Your app uses “Sign in with Supakey” (standard OAuth).

On first consent, Supakey deploys your app’s schema into the user’s Supabase with RLS enabled and minimal privileges.

Your backend/frontend uses app-scoped credentials to read/write their DB directly.

Users can revoke access anytime; data remains in their project.

For users

Keep all your application data in your own Supabase.

Use any compatible app as long as you like; no vendor lock-in.

For developers

Don’t host or retain user data; reduce ops and compliance surface.

Perfect for simple CRUD apps, notes/todos, personal trackers, prototypes.

Security & privacy

Per-app schema with RLS by default.

Least-privilege grants; credentials scoped to the app’s schema.

OAuth consent + easy revocation; no central data copy.