Turso
localhost:8081Paste the URL and the token. dbplex pulls your Supabase, Turso or Postgres database and starts a local copy with its own URL. You never write a dump script or open a compose file.
See how it worksComing soon for Mac
Pick your database and paste what it needs to connect. Credentials go straight into your Mac's Keychain.
Table structure always comes. Data, auth users, storage, edge functions and auth settings are on by default, and you can turn any of them off.
dbplex starts the copy and shows its local URL. Copy it, or copy everything as a .env, and run your code against real data.
Each copy runs on your Mac and answers on its own local URL.
| Database | What you paste | What runs on your Mac |
|---|---|---|
| Project URL, database password, service role key, access token | The official Supabase stack: database, auth users and settings, storage, edge functions, realtime and Studio, plus a mailbox that catches auth email. Needs Docker Desktop, and you never touch a container. | |
| Database URL, auth token | A local libSQL server with an http://localhost URL, so the same client code keeps working. No containers. | |
| Any connection string, including Railway, Neon, Render and AWS RDS | Postgres matched to the major version of your source. No containers. | |
| A .db or .sqlite file | A local libSQL server that gives the file its own URL. No containers. | |
| A .sql or .dump file, or a dbplex backup | Restored into a new local database of the right type. |
See what is running, start and stop with one click, and look inside any database without opening a terminal.
Databases
Running3
Supabase
localhost:543222Turso
localhost:8081PostgreSQL
localhost:5433Pulling1
Turso
Copying the database
Stopped1
SQLite
The code that talks to your source can read and dump, and that is all. The app has no push, sync or copy back, and credentials stay in the Mac Keychain.
A copy keeps everything the original has, including scheduled jobs and webhooks that can still call outside services. dbplex scans each pull and lists what it finds on that database, so you know what can still reach out.
Still active: these came with the copy and can still call outside services, including production.
nightly-invoicesScheduled joborder_createdWebhookdbplex comes with an MCP server. Claude Code and other local agents can create and refresh copies, run any SQL and migrations, and read logs, with the window closed.
Agents act on local copies only and never see your source credentials. Query results do go to your agent's AI provider, and copies hold real data, so choose what you import with that in mind.
claude mcp add dbplex -- "/Applications/dbplex.app/Contents/MacOS/dbplex-mcp"Tools include create_database, refresh_database, run_sql, run_migration, get_schema_graph, read_logs and read_mailbox.
dbplex only reads from production. The code that talks to your source can read and dump, and the app has no push, sync or copy back. Keep in mind that a copy behaves like the original, so scheduled jobs and webhooks that came with it can still call outside services. dbplex scans each pull and warns you about them.
Your project URL, database password, service role key and access token. The access token is only needed for edge functions and auth settings, so you can leave it out if you turn those off.
For Turso, SQLite and PostgreSQL, no. Supabase runs the official stack in containers, so it needs Docker Desktop. dbplex starts and manages the containers, and you never see a compose file.
Supabase, Turso, SQLite, and any PostgreSQL database you can reach with a connection string, including Railway, Neon, Render and AWS RDS. You can also restore a dump file. MySQL, MariaDB, MongoDB and Redis are not supported yet.
Press Refresh from Production. It replaces the local copy with a fresh pull using the credentials and choices you already saved. If you changed the copy since the last pull, it warns you first.
Values like edge function secrets and OAuth client secrets can't be read from Supabase. dbplex lists what is missing and gives you a place to enter it.
Copies stay on your Mac and listen on your own machine only. Credentials are kept in the Mac Keychain and are only sent to the database they belong to.
Not yet. The first version is for Mac.
Coming soon for Mac