Supabase Postgres Schema Visualization Tool

See What PostgREST Exposes From Your Supabase Schema

Supabase is PostgreSQL at heart: PostgREST turns your tables into a REST API, while Auth and Storage keep their own schemas beside yours. DbSchema connects to that Postgres directly and shows the whole data model your app is built on.

Standard Postgres connection — select PostgreSQL, no dedicated driver

Diagram the public schema beside auth.users and storage.objects

Full SQL editor for EXPLAIN ANALYZE, CTEs, window functions, DO blocks

Documentation you can attach to design docs and security audits

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

Every Migration You Ship
Reshapes Your Public API

On Supabase the schema is the contract: PostgREST exposes tables and views as REST endpoints, and Row Level Security policies decide row by row what each authenticated user sees. A column added in Studio is an API change your frontend meets immediately.

DbSchema gives that schema a visual home — the tables, views, and foreign keys behind your endpoints, laid out as diagrams your backend and frontend teams read together.

Reverse engineer a Supabase PostgreSQL schema into an ER diagram

Reverse Engineer the Project Schema

Connect once and get the public schema with its foreign keys as an interactive diagram — the exact data model PostgREST serves to your frontend, in plain sight.

Organize Supabase system schemas into focused diagrams

System Schemas, Organized

Lay out auth, storage, and public on separate focused diagrams — handy when tracing how user IDs in auth.users relate to rows in your application tables.

Generate schema documentation for a Supabase project

Docs for Audits and Handoffs

Generate offline schema documentation to include in technical design documents and security audits — readable in a browser, with no project access granted.

Supabase Moves Fast
Your Schema History Shouldn't Blur

Keep the design model in Git beside your application code. Each schema change becomes a diff your team reviews in a pull request before any SQL runs — and because Supabase is standard PostgreSQL under the hood, the generated scripts are plain Postgres SQL you read first.

Supabase Connection Facts — Direct, Pooler, SSL

Select PostgreSQL as the database type — Supabase needs no dedicated driver. Copy the connection string from the Supabase dashboard under Settings → Database: the direct endpoint uses port 5432, forming a URL like jdbc:postgresql://db.xxxxx.supabase.co:5432/postgres?sslmode=require, where xxxxx is unique to your project. Keep the sslmode=require parameter in place — Supabase enforces SSL on this endpoint.

A connection pooler (PgBouncer) endpoint — its hostname contains pooler.supabase.com — suits free-tier projects with a limited connection count, or sessions that hit connection timeouts during intensive query work. The database password is the one set in the Supabase dashboard and is separate from any API keys used by the PostgREST layer. Projects using the pgvector extension can inspect embedding columns like any other data in DbSchema's editors. Setup details are on the Supabase JDBC driver page.

Frequently asked questions

Yes — Supabase exposes a standard PostgreSQL connection, so you select PostgreSQL as the database type in DbSchema and connect using the connection string from the Supabase dashboard under Settings → Database.

Supabase's direct connection uses port 5432 with SSL enforced, forming a URL like jdbc:postgresql://db.xxxxx.supabase.co:5432/postgres?sslmode=require. A separate pooler (PgBouncer) endpoint is available for apps that open many short-lived connections.

RLS policy definitions stay managed in Supabase, in the dashboard or in SQL. DbSchema focuses on the schema itself — tables, columns, and relationships — and does not import the policies into the diagram.

See What PostgREST Exposes From Your Supabase Schema

Every Migration You Ship
Reshapes Your Public API