Export a Postgres database schema
Paste a Supabase, Neon, or any Postgres connection string. You get back a zip with the schema as plain SQL, plus a docker-compose and Kubernetes stack that boots a Supabase-compatible backend from it. Schema only, never your data, nothing stored here, no account needed.
Want the data too, with backups and branching?
Scribase runs this same Supabase-compatible stack hosted, $25 a month flat per project, with daily backups, point-in-time recovery and instant branching built in — and the full authenticated export (data included) is one command away any time.
Questions people ask
Is my data exported too?
No. This tool runs pg_dump --schema-only against your connection string: tables, indexes, constraints, views, functions and extensions, with zero rows. A public, no-signup page cannot safely read or transmit an unknown amount of row data, so data export is intentionally out of scope here.
Is my connection string stored anywhere?
No. It is sent once over HTTPS to this page's own API route, used to run one pg_dump, and never written to a database, log, or file. The schema it reads is streamed back into your download and then discarded on the server.
What is in the downloaded bundle?
schema.sql (the DDL), deploy/docker-compose.yml, a deploy/kustomize/base/ for Kubernetes, a .env.example with every variable named (no real secret is ever included), and a README with exact boot commands.
Why would I want this if I am happy with Supabase or Neon?
You might not — this is also just a fast way to stand up a local or self-hosted copy of your schema for testing. If you do want the data too, hosted, with branching and backups from day one, that is what a Scribase project does with scribase import.