Provision a production database when an agent builds an application, and create a production-like branch for every deployment preview. Scale from the first user to millions of isolated databases and branches, in your cloud and close to the applications your platform creates.
AI platforms need databases at two different moments: when an application is created, and whenever that application is previewed or changed.
When an agent builds a new application, Xata provisions an isolated Postgres database for it to use in production. The application receives a standard Postgres connection string and can start storing users, application data, agent state, and generated content immediately.
When a preview deployment is created, Xata branches the application’s production database so the preview includes the same schema and production-like data. The agent can test code, migrations, and data changes together without affecting the live application or another preview.
Every new app may need a persistent production database, and every code change may create one or more temporary branches. Xata supports this model from a few databases to millions.
Create databases and branches programmatically as users and agents start new workloads.
Give each application and preview its own schema, data, endpoint, and credentials.
Create, suspend, resume, and remove databases through your platform control plane.
Run large numbers of applications, previews, and agent workflows without relying on a limited pool of shared databases.
AI platforms can generate enormous numbers of databases and branches surprisingly quickly. Imagine a platform with:
With traditional infrastructure, millions of always-on databases and full database copies would make a free tier prohibitively expensive. Xata combines scale-to-zero compute with copy-on-write branching, so costs follow actual activity rather than the total number of databases and branches your platform has created.
Idle databases and branches stop consuming active compute while their schema and data remain available.
Preview branches share unchanged storage with production and store only the blocks that change instead of copying the full database.
Infrastructure spend is driven primarily by active compute and changed data, not by every free user, database, or preview that exists.
Give every user a real Postgres database and every deployment preview an isolated branch, without being afraid that dormant free-tier workloads will consume always-on infrastructure.
Provision millions of databases and branches while paying primarily for the workloads that are active and the data that changes.
How scale to zero worksUse Xata Cloud for simplicity, or BYOC when you need control over cloud, region, and infrastructure.
Get started quickly with a fully managed Postgres platform operated by Xata. Provision databases and branches through your platform without managing the underlying infrastructure.
Run Xata in your own cloud, close to the applications your platform creates. Keep application and database traffic in the same cloud, reduce latency and data-transfer costs, meet residency requirements, and use existing cloud agreements.
Learn about BYOCYour control plane calls the Xata API or CLI as part of its normal application lifecycle. Each application gets its own production database. Each preview, sandbox, or agent workflow gets an isolated branch, removed when the work is complete.
Application
Preview
Xata runs behind your platform. Users connect through standard Postgres drivers and connection strings, with no Xata-specific client or branding.
Create, manage, suspend, and remove databases and branches programmatically through the Xata API, CLI, or your existing control plane.
Platform pricing is based on capacity and deployment requirements rather than every branch created, so infrastructure costs stay predictable as usage grows, without limiting how many databases, previews, or agent workflows your users can create.
Align pricing with the size and activity of your platform rather than raw branch count.
Work directly with the Xata team on architecture, control-plane integration, deployment, and scaling.
Choose Xata Cloud or BYOC based on your infrastructure, regions, and customer requirements.
Use a shared Slack channel for integration support and ongoing architecture discussions.
Provision a production database for every application and an isolated branch for every preview, agent, and workflow.