In one step, branch both your database and your files. Your buckets come with your Postgres data into isolated environments, without duplicating storage.
- S3 compatible
Keep your stack
boto3, the AWS SDK, and the CLI work with Neon Object Storage out of the box. Swap the endpoint and keep your existing code.
- One credential
No separate cloud account
Authenticate with a Neon credential instead of a separate AWS account and IAM setup.
- Branchable storage
Buckets that branch with your database.
No files are duplicated up front (it's copy-on-write). The bill only grows if the branch diverges.
Test on real environments. On Neon, a branch forks Postgres and your files together, with nothing duplicated upfront.
Isolated by default
Uploads and deletes on a preview or PR branch never touch production or any sibling branch.
Copy-on-write
Creating a branch doesn’t copy your objects. You pay for what diverges, not for a second bucket.
Disposable
Delete the branch and its files go with it. Same workflow for a human, a CI job, or an agent.
Ask your agent: deploy Postgres and files via the Neon backend
import { defineConfig } from "@neon/config/v1";
export default defineConfig({
preview: {
aiGateway: true,
buckets: {
uploads: {},
},
},
});One config
Define your bucket alongside Postgres and keep your database and files together in the same
neon.tsconfiguration.One deploy
Run
neon deployto provision the bucket and automatically pull the required S3 variables into your.env.local.Agent tools
Agents are a first-class interface through Neon’s API, CLI, and MCP server.
Your questions,
answered.
S3-compatible blob storage for your files, built into the Neon backend. This is different from the object store Lakebase Postgres uses internally for database pages. You upload objects into buckets, point a standard S3 client at your branch endpoint, and authenticate with a Neon credential.
Your files branch with everything else. Create a branch and your whole backend forks with it — database, storage, auth, and a gateway endpoint of its own.
Built for agents and
the developers behind them.
Every service is designed with the same API and operational model, whether it's used by a developer or called directly by an AI agent. Build once, then let both humans and agents use the same platform without additional integration work.
Branchable
Spin up isolated environments to test model changes safely, without touching production. Merge changes only when they're ready.
Serverless
Usage-based infrastructure that scales automatically with your traffic, so you only pay for what you use and nothing while idle.
Agent-ready
Provision and operate every service through APIs that AI agents can call directly, using the same interfaces as developers.
Trusted at scale. Neon has been part of the Databricks Platform since May 2025.
20M+
Databases started daily - built for scale and reliability.
3M+
Developers building on Neon worldwide
Neon's serverless philosophy is aligned with our vision: no infrastructure to manage, no servers to provision, no database cluster to maintain.
Talk to us.
Fill out a short form and we’ll get back to you within a few business days.
