Review PlanetScale Branch Schemas Before They Deploy

PlanetScale is serverless MySQL built on Vitess, and its branching workflow gives every schema change an isolated branch with its own credentials. DbSchema connects to any branch with the MySQL driver and that branch's connection string, and shows its schema as a diagram worth reviewing.

Diagram exactly what is on a branch — tables, indexes, column types
Standard MySQL SQL in the editor, EXPLAIN included
Foreign keys drawn as logical relationships, even where runtime enforcement is off
Browse branch data to verify seeds and migrations

available for

ISO-27001 certified

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

Free Download

DbSchema visualizing a PlanetScale branch schema as an ER diagram

Trusted by teams at

The Branch Workflow Moves Fast
Reviews Deserve More Than a Diff File

On PlanetScale, schema changes travel as branches and ship through deploy requests — the platform's pull request for DDL. The request shows the migration text; what it cannot show is the shape of the schema around it.

DbSchema adds that shape: connect to the branch, see its tables, relationships, and index coverage as a diagram, and judge the change in context before the deploy request ships.

Visualize, Query & Check
Any Branch in the Keyspace

MySQL-compatible tooling for a Vitess-backed workflow.

Review PlanetScale branch relationships and index coverage in diagrams

Index Coverage at a Glance

Lay the branch schema out in focused diagrams, check relationships and index coverage visually, and export the layout for the review thread.

Run MySQL-compatible SQL against a PlanetScale branch

MySQL Semantics, Branch Scope

Run standard MySQL statements against any branch, and use EXPLAIN to confirm the plan hits your indexes before the change goes further.

Browse PlanetScale branch data in the DbSchema data explorer

Verify the Seed Data

Page and filter branch tables to confirm fixtures and data migrations produced what you expected — then export a CSV snapshot to share.

The Model Lives in Git
The Deploy Request Lives in PlanetScale

Keep the schema as a DbSchema model file in your repository: design and review it alongside the application code, then carry the approved change into the PlanetScale deploy request that ships it. Two reviews, no surprises.

PlanetScale branch schema compared against a Git-versioned DbSchema model

Read Git Workflow Docs

PlanetScale Connection Facts

Select MySQL in DbSchema — the Connector/J driver (com.mysql.cj.jdbc.Driver) is bundled — and copy the branch's username and password from the "Connect" panel in the PlanetScale dashboard; every branch has its own credential set. With host aws.connect.psdb.cloud and the default MySQL port 3306, the URL reads jdbc:mysql://aws.connect.psdb.cloud/mydb.

SSL is required on every PlanetScale connection: add ?sslMode=VERIFY_IDENTITY (older drivers: ?useSSL=true&requireSSL=true) if it is not enabled automatically. Name connection profiles after their branches — "main", "feature/add-payments" — to tell them apart. PlanetScale keeps foreign keys as documentation rather than enforcing them at runtime; DbSchema still draws them as logical relationships. Driver details: PlanetScale JDBC driver page.