Data & Storage · Integration
Supabase
Add Supabase to your product for your customers, and give your AI agents governed access to it.
Supabase wraps a Postgres database in a platform, and an embedded Supabase integration gives your product all of it: tables exposed through an auto-generated REST API, auth users, storage buckets and realtime change subscriptions, per project the customer connects. Row level security is what really shapes the integration. Whether you call as an authenticated user or with the service role changes which rows come back, and a policy the customer wrote themselves can quietly filter results your product expected, so the calling identity matters more than the query. fastn keeps each project's URL and keys per tenant, so a service role key never sits in your frontend, and follows Supabase's API as it evolves.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own project, and your product reaches their tables through the generated REST endpoints.
Call as the correct identity so each customer's row level security policies apply instead of being bypassed.
Upload and fetch files from a customer's storage buckets without your product having to hold the objects itself.
Subscribe to realtime changes so your product refreshes when a row changes in the customer's project.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent queries a table under an identity whose row level security policies bound what it can see.
An agent creates or updates a row within granted permissions, with the project and table recorded.
An agent looks up an auth user's record to confirm who a request belongs to before acting on it.
Example prompt
Show this auth user's row in the profiles table and the files they have in their storage bucket.
Set up Supabase in 4 steps
- 01Enable the Supabase connector from your fastn dashboard.
- 02Have each customer authorise their own Supabase account, so calls run under their credentials rather than a shared key.
- 03Decide which records, datasets and fields your product needs, map those fields, then enable the actions and triggers you want.
- 04Call it from your product and expose it to your agents through the same governed connection.
Why teams use the Supabase integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Supabase integration without building it. Your customers connect their own Supabase account inside your product and work their records, datasets and fields there, with no per-customer code on your side.
- Handle the part that actually costs time: schemas differ per customer and change without notice, and volumes can be large. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Supabase update is not your on-call problem.
- One integration serves your product and your agents. The same governed Supabase connection powers in-product features and gives AI agents scoped, audited access, so you read and write your customers' data where it already lives without wiring it twice.
Used by these teams
Compare with
PostgreSQL
MongoDB AtlasWorks well with
VercelOften used alongside
Tools the same teams tend to run next to Supabase, across other categories.
Anthropic Claude
OpenAI
Azure OpenAI
Hugging FaceSupabase integration FAQ
How do I add a Supabase integration to my product?
Enable the Supabase connector in your fastn dashboard, then let each customer authenticate their own Supabase account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Supabase client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Supabase account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Supabase account and only ever sees their own records, datasets and fields. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Supabase integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent queries a table under an identity whose row level security policies bound what it can see.
Who maintains the Supabase integration?
fastn does. When Supabase changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Does the Supabase integration adapt when a customer's schema changes?
Schema and field mapping is configuration per customer, so a change on their side is a mapping update rather than a code change and a release on yours.
How are large Supabase reads handled?
Pagination and throttling are handled for you, and initial backfills are rate-limited so a large import does not exhaust a customer's API allowance.
What can I build with the Supabase integration?
A common starting point: let a customer connect their own project, and your product reaches their tables through the generated REST endpoints. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Supabase integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Supabase does not change your per-connector cost. You can start free with 3 connected accounts.
Add Supabase to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.