Syntica
Get started
OverviewConnectorsAgentsConsultancies and agenciesInternal teamsPricingDocsGuidesBlogSecurityAbout
← All connectors
Database

Supabase

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.

Before you connect it

01
Create or open the project in the customer’s own Supabase account, never one owned by an individual consultant.
02
Copy the project URL and the anon (publishable) key from the project’s API settings.
03
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.
04
Enable Row Level Security on every table the application exposes. The anon key is only as safe as the policies behind it.

What your application receives

An admin enters these once, and the platform injects them as environment variables at deploy time. Your code reads them. It never sees a login screen or an SDK for this.

SUPABASE_URLSUPABASE_ANON_KEYSUPABASE_SERVICE_ROLE_KEY
Supabase’s own docs, from the vendor →
Syntica
Real environments for client work. Your code. Your repo. No lock-in.
Product
PricingRelease notes
Who it's for
Consultancies and agenciesInternal teamsMigration
Developers
DocsStatus
Company
AboutSecurity and governanceBlogContact
© 2026 Syntica. All rights reserved.
Privacy PolicyTerms of Service
We use cookies
We use essential cookies to run the site and optional ones to understand usage. See our Privacy Policy.