Data & Storage · Integration
PostgreSQL
Add PostgreSQL to your product for your customers, and give your AI agents governed access to it.
Embedding a PostgreSQL integration lets a customer keep their database exactly where it is and still have your product read and write it. Tables, views and schemas are addressed per tenant, and multi-statement writes run inside a transaction so a partial failure rolls back instead of leaving half a change behind. Two things bite here. Postgres allows a bounded number of concurrent connections, so an integration that opens one per request starves the customer's own application long before it meets any API limit, which makes pooling a design decision. And change notification runs through LISTEN and NOTIFY or logical replication rather than webhooks, so reacting to a row change happens at the database level. fastn manages the pooled connections, the credentials and the upkeep.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Have a customer attach their own database, so your product queries the tables and views they already run instead of a nightly extract.
Group a set of writes into one transaction so your product never leaves a customer's data half updated.
Subscribe to row-level change notifications so your product responds when the customer's application writes something.
Share a pooled connection across requests so a busy feature does not exhaust a customer's connection limit.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent runs a read-only query against one tenant's database, with the statement it executed retained.
An agent performs an approved update inside a transaction, so a failed step leaves nothing behind.
An agent reads the schema catalogue to see which tables and columns it is allowed to touch.
Example prompt
Query the subscriptions table for accounts renewing next month and group them by plan.
Set up PostgreSQL in 4 steps
- 01Enable the PostgreSQL connector from your fastn dashboard.
- 02Have each customer authorise their own PostgreSQL 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 PostgreSQL integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a PostgreSQL integration without building it. Your customers connect their own PostgreSQL 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 PostgreSQL update is not your on-call problem.
- One integration serves your product and your agents. The same governed PostgreSQL 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
MySQL
Microsoft SQL Server
SupabaseOften used alongside
Tools the same teams tend to run next to PostgreSQL, across other categories.
Anthropic Claude
OpenAI
Hugging FacePostgreSQL integration FAQ
How do I add a PostgreSQL integration to my product?
Enable the PostgreSQL connector in your fastn dashboard, then let each customer authenticate their own PostgreSQL account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no PostgreSQL client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own PostgreSQL account?
Yes. Every connection is scoped to the individual customer, so each authorises their own PostgreSQL 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 PostgreSQL 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 runs a read-only query against one tenant's database, with the statement it executed retained.
Who maintains the PostgreSQL integration?
fastn does. When PostgreSQL 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 PostgreSQL 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 PostgreSQL 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 PostgreSQL integration?
A common starting point: have a customer attach their own database, so your product queries the tables and views they already run instead of a nightly extract. 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 PostgreSQL integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding PostgreSQL does not change your per-connector cost. You can start free with 3 connected accounts.
Add PostgreSQL to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.