Connectors / Supabase
Database
Supabase
Connect your app to a Supabase project you already have: its database, sign-in and file storage.
Included on every plan. An admin approves it once.
What your app can do with it
- ✓Your data stays in your own Supabase account
- ✓Bring an app built elsewhere without moving the data
- ✓Move away later and the app keeps running against the same project
For your IT admin
Setting it up
Done once, in your company's own account with Supabase.
1
Create or open the project in the customer’s own Supabase account, never one owned by an individual consultant.
2
Copy the project URL and the anon (publishable) key from the project’s API settings.
3
Copy the service_role (secret) key. It bypasses Row Level Security, so it belongs only in the platform and the customer’s password manager, never in a repository or a browser.
4
Enable Row Level Security on every table the application exposes. The anon key is only as safe as the policies behind it.
For developers
What your app receives
Connects an application to a Supabase project the customer owns: the Postgres database, its auto-generated REST API, auth and storage. Three variables: the project URL, the anon key the browser may hold, and the service_role key that bypasses Row Level Security and must only ever be read server-side. The project stays the customer’s, on their own Supabase account and billing, so leaving the platform costs nothing, since the same three variables set anywhere else keep the app running. This is also the natural landing place for an app built elsewhere against Supabase: point it at the same project and the data never moves.
Supabase's own documentation →SUPABASE_URLSUPABASE_ANON_KEYSUPABASE_SERVICE_ROLE_KEYMore connectors
All 12 connectors →Get your spot in the beta.
We open spots from the waitlist, oldest first. When yours opens, the free tier is a real environment with a real URL. No card.
We use cookies
We use essential cookies to run the site and optional ones to understand usage. See our Privacy Policy.