Pull requests
Create a production-like database branch when a pull request opens. Run migrations and tests against it, then delete it after merge.
PR #842
PR #842: Pull request opened, branch created, Tests passed.
Give every agent an isolated Postgres branch with production-like data for each task, pull request, and preview deployment, ready in seconds.
A production Postgres database branches into four active isolated environments while capacity lanes represent hundreds more production-like branches.
PR #842
Add billing
PR #843
Update schema
PR #844
Checkout redesign
PR #845
New permissions




Coding agents multiply the number of changes happening at once. A single shared database cannot safely support all those migrations, tests, and experiments.
Shared staging puts four workflows in one database, causing migration conflicts, failed tests, overwritten data, and waiting. Xata creates four isolated Postgres branches with production-like data so every workflow can run independently without conflicts.
Run migrations and test schema changes without affecting production or anyone else’s work.
Catch issues that empty databases, fixtures, and mocks cannot reveal before changes ship.
Give every developer, agent, and preview an isolated database without waiting on shared staging.
Create isolated branches from production without copying the full database. Each branch gets its own schema, compute, and production-like data.
Using copy-on-write storage, each branch shares data with its parent and stores only changes instead of creating full copies.
Run branches only when needed. When idle, they hibernate and use no compute.
Branches wake on first query and respond instantly: no connection timeouts, no spin-up delays.
Branching happens in the storage layer, not through a custom Postgres fork, so you keep standard PostgreSQL, extensions, drivers, and tooling.
Connect Xata to GitHub, CI, or your coding agents. A Postgres branch is created automatically for every task, pull request, or preview and removed when the work is complete.
Create a production-like database branch when a pull request opens. Run migrations and tests against it, then delete it after merge.
PR #842
PR #842: Pull request opened, branch created, Tests passed.
Let agents create isolated branches through the API or MCP, safely modify schemas and data, and clean up when the task finishes.
Claude task
Claude task: Coding session started, branch created, Migration applied.
Connect every preview to its own Postgres branch so the complete application, code, schema, and data, can be validated before publishing.
Preview #319
Preview #319: Preview deployment, branch created, Preview live.
Keep production where it is, or move it to Xata. Either way, every pull request and deployment preview gets its own isolated Postgres branch.
Create a clone of your production database in Xata, keep it in sync with production, and have it ready for instant branching.
Run your production database on Xata with native branching, built-in high availability, read replicas, and automatic scale-to-zero.
Xata runs vanilla PostgreSQL with high-performance storage, isolation, and instant branching built in.
Xata includes built-in production observability for your database — uptime, query latency, throughput, and active connections.
No forks, no proprietary APIs. Just PostgreSQL.
Scale reads independently from writes.
Restore your database to any point in time.
NVMe-backed storage for low latency and high throughput.
Consider a company creating 100 pull requests per day against a 100 GB production database. With traditional database infrastructure, giving every pull request its own isolated database quickly becomes unsustainable.
Give every user, workspace, preview, or coding agent an isolated Postgres branch, created through one API and managed by Xata.
Create a new Postgres database in a second through a simple API.
Create a production-like branch in seconds, regardless of database size. Scale to zero when idle and wake in about a second.
Support large numbers of short-lived databases without duplicating storage or paying for idle compute.
Use Xata Cloud or run in your own cloud with BYOC, private networking, and regional control.
See what engineers, builders and leaders are saying about Xata.

Xata is currently the best way to run the pg_duckdb extension in the cloud. The platform’s flexibility and API access make Xata the perfect PostgreSQL partner for us.
CEO, MotherDuck

Xata was an easy choice for our team because of how straightforward the entire platform is, while simultaneously providing a suite of adequate features that we need. The Xata team has also been super responsive and more importantly quick to resolve the hiccups that we brought upon ourselves.
Lead Software Engineer, Safestreets

By adopting Xata, we cut database costs vs. our RDS setup and got better help from Postgres experts.
Co-founder, CallKarma.ai

Xata was a no-brainer for our team. We get a lot of value out of the copy-on-write database branching and scale-to-zero features.
Software Engineer, SaaSgrid
Branch production in seconds for coding agents, pull requests, previews, tests, and experiments.