Xata - Postgres at Scale

A coding agent wants its own database for every task, created when the work starts and removed when it ends. A shared staging database doesn't survive that for long. Our CEO Monica Sarbu on what to do instead, today 2:50pm PT, Stage 2, WeAreDevelopers San José: "Databases in the Agent Era."

Need production data to debug a slow query? Normally, you'd have to isolate & validate data & deploy the fix. With the Xata MCP server and Codex, you just talk to an agent. Branch your Postgres database in seconds regardless of the size and let AI do the debugging. Watch 👇

Coding agents write and run SQL now. The same connection that lets one fix a query lets it drop a table. The Xata MCP server gives it a branch instead: the agent creates it, works in it against real data, deletes it when the run ends. xata.io/blog/introdu...

Finding a slow query on a Postgres branch, without leaving the terminal. xata branch query-insights ranks that branch's statements by cost, flags the slow ones, and prints the command to inspect any of them. Logs and instance metrics are one command away.

xata branch query-insights active reads pg_stat_activity, so it shows what is executing right now, with each query's state and wait event. Currently running queries are the one part of this with no console page.

2TB+ Postgres. Branch it in seconds, query it, delete it. xata scratch (new Xata CLI cmd) forks a disposable branch off your real DB, drops you into psql or runs SQL inline, tears it down on exit. Demo 👇

Introducing the Xata GitHub App. Connect a repo to your Xata project and every pull request gets its own isolated Postgres branch off main, with production-like data, ready in seconds when the PR opens and gone when it closes.

Branch-per-PR is the starting point. The same mechanism works for every developer, every QA environment, and every agent that opens a PR. And agents open a lot of PRs.

Introducing the Xata GitHub App. Connect a repo to your Xata project and every pull request gets its own isolated Postgres branch off main, with production-like data, ready in seconds when the PR opens and gone when it closes.

The app watches your PRs. When one opens, it creates a copy-on-write branch off main, mirroring production. Same branch name in GitHub and Xata, so your GitHub Action runs against it and reports back on real data, not an empty seed.

Introducing the Xata GitHub App. Connect a repo to your Xata project and every pull request gets its own isolated Postgres branch off main, with production-like data, ready in seconds when the PR opens and gone when it closes.

Xata is now on Google Cloud. Spin up an isolated Postgres branch from your production data in 3 seconds, in-region in us-central1 (Iowa). Every coding agent, PR, and CI run gets its own production-like database. No shared staging, no migration.

Built for instant Postgres branching: - branch in 3s from your full database, copy-on-write - branch from production with sensitive fields masked - scale-to-zero: idle branches stop, wake on demand - live in us-central1 (Iowa), more regions coming

Xata is now on Google Cloud. Spin up an isolated Postgres branch from your production data in 3 seconds, in-region in us-central1 (Iowa). Every coding agent, PR, and CI run gets its own production-like database. No shared staging, no migration.

Deployment previews & CI Create a fresh Postgres branch in 3 seconds for every pull request and test run. Review every change against production-like data.

Xata is now on Google Cloud. Spin up an isolated Postgres branch from your production data in 3 seconds, in-region in us-central1 (Iowa). Every coding agent, PR, and CI run gets its own production-like database. No shared staging, no migration.

We run 100% vanilla Postgres. No fork, no modifications. A deliberate decision from day one to build a platform around Postgres, with branching at the storage layer instead of inside the database. This means the whole Postgres ecosystem just works with Xata.

And we give back in code, not just funding. Keycloak is our authentication layer. We contributed full management for organization invitations to it, our upstream contribution shipped in Keycloak 26.5.0.

We run 100% vanilla Postgres. No fork, no modifications. A deliberate decision from day one to build a platform around Postgres, with branching at the storage layer instead of inside the database. This means the whole Postgres ecosystem just works with Xata.

pgBackRest nearly went unmaintained, and now runs on a coalition of sponsors. Thanks to David Steele for keeping it going.

We run 100% vanilla Postgres. No fork, no modifications. A deliberate decision from day one to build a platform around Postgres, with branching at the storage layer instead of inside the database. This means the whole Postgres ecosystem just works with Xata.

Branching gives every engineer and every agent their own Postgres. Now every branch has its own logs. Read, filter, and search them in the console, or match a pattern in one click. Same logs in your terminal with xata branch logs.

DeltaX, our open-source timeseries and columnar extension for Postgres, just shipped v0.2.1, mostly analytics performance work. A few engineering bits worth sharing:

Planner statistics for compressed partitions: DeltaX now builds histograms, MCV lists, and distinct-value estimates for its columnar segments, so the planner picks the right plan for joins and multi-table queries on compressed data.