A Schema Diagram for Every Xata Branch

Xata is a serverless data platform on PostgreSQL where every branch is its own isolated schema environment. DbSchema connects to any branch's PostgreSQL-compatible endpoint and reverse-engineers it into a diagram you can query, inspect, and share.

One saved connection profile per branch — main, preview, development
Standard SQL against the branch: joins, aggregations, window functions, CTEs
File-attachment metadata readable as formatted JSON in the explorer
Confirm the app writes the structure you expect before merging

available for

ISO-27001 certified

Free Community Edition No signup required 15-day Architect trial included

Free Download

DbSchema diagramming the schema of a Xata branch

Trusted by teams at

Branches Fork in Seconds
Schema States Multiply Just as Fast

Xata's workflow forks a branch per feature, gives it an isolated PostgreSQL environment, and merges schema changes back like code. Convenient — until review time, when "what exactly does this branch's schema look like now?" has no visual answer.

Point DbSchema at the branch endpoint and the answer is a diagram: tables, columns, and relationships as that branch defines them.

Connect, Query & Review
Xata Branches as Real Databases

Because under the serverless surface, that is exactly what they are.

Reverse engineer a Xata branch schema into an ER diagram

A Diagram per Branch Endpoint

Each Xata branch exposes its own PostgreSQL-compatible URL; DbSchema reverse-engineers whichever one you connect to, using the bundled PostgreSQL driver.

Write PostgreSQL SQL against Xata branch endpoints

PostgreSQL SQL, Serverless Backend

The endpoint accepts standard SQL — joins, aggregations, window functions, CTEs — so testing a query against a feature branch works like on any PostgreSQL database.

Build queries against Xata tables visually

Queries Assembled by Click

Select tables, columns, filters, and joins visually and read the resulting SQL — handy when exploring a branch someone else created.

Xata Branches the Database,
Git Versions the Design

Pair the two workflows: keep the DbSchema model file in the same repository as the feature branch, diff schema changes in the pull request, and compare branch schemas against the model to see exactly what a merge will bring to main.

Comparing a Git-versioned model with Xata branch schemas

Read Git Workflow Docs

Xata Connection Mechanics

Copy the branch's direct PostgreSQL connection string from the Xata dashboard under Settings > Connection strings — it looks like jdbc:postgresql://us-east-1.sql.xata.sh/mydb:main?sslmode=require, with database and branch joined by a colon in the path. Choose PostgreSQL as the database type; the org.postgresql.Driver is bundled with DbSchema.

SSL is mandatory, so keep sslmode=require. Authenticate with an API key from the dashboard as the password, and the username the connection string names. Since every branch has a distinct endpoint, save one profile per branch you work on. More on the Xata JDBC driver page.