dbplex is a Mac app that copies your Supabase, Firebase, PostgreSQL, MySQL, MongoDB or any of 12 databases to localhost, real data included. Run your tests, try the migration and let your AI agent loose on it. Production is never written to.
For Apple Silicon Macs. 7 days free with every feature. No card and no account.
Agent
Running your new migration on the copy.
DROP DATABASE production;
BRO
HAVE YOU DELETED MY DATABASE
Read
Agent
Relax, that was the copy on your Mac.
The real one never noticed.
Spoiler: 0042 is not safe to run.
Production untouched. dbplex only reads it.
Supabase
Firebase
PostgreSQL
MySQL
MongoDB
Turso
SQLite
Redis
MariaDB
DynamoDB
SQL Server
Oracle
Neon
Railway
Render
PlanetScale
AWS RDS
Google Cloud SQLAzure Database
DigitalOceanMongoDB Atlas
UpstashAiven
Dump filesYour Supabase, Firebase, PostgreSQL, MongoDB and Redis copies sit side by side in one window, so you always know what's running and can stop what isn't. Each one is a real database server on your Mac, with its own localhost URL.
A Supabase copy also brings the auth users, the storage files and the edge functions, and a local mailbox catches every email your app sends. Nothing is ever written back to production, so you can run the migration, delete rows or try the risky idea without a single customer noticing.
Try it. This is the real app.
It connects to nothing and the rows are made up, so click the fields instead of pasting real credentials.dbplex is a Mac app. Open this page on your Mac to try it live.
Those tools give you a database, but it starts empty and lives in a terminal you have to remember. So most people skip them and change production directly.
| The CLI or Docker | dbplex | |
|---|---|---|
| Your data | Starts empty. You write seed scripts or restore a dump by hand. | Starts with your real tables and rows, masked where you choose. |
| Back to production | You write the migration by hand and hope it matches what you changed. | The Changes tab writes it from the difference, in the order it must run. |
| Supabase | Tables only, unless you script auth users and storage yourself. | Auth users, storage files, edge functions and settings come too. |
| Where it runs | A terminal or a Docker container per project, easy to leave running and forget. | One window lists every copy, running or stopped. |
| Fresh data | Dump and restore again. | One Refresh button. |
| AI agents | You hand them production, or they refuse to touch it. | A copy of their own over MCP, without your production credentials. |
| Production | One wrong migration away from an outage. | Only ever read. |
Claude Code, Cursor and other coding agents often refuse to touch production, and they're right to. dbplex gives them a copy they can break. Its built-in MCP server lets an agent run SQL, rehearse and run migrations, and branch its own copy. Agents never see your production credentials, and personal columns can be masked before an agent reads a single row.
Add it to Claude Code, Cursor, Codex or Windsurf from Settings.
When the work on your copy is done, the Changes tab compares its schema with production, table by table, like a pull request: what production has now in red, what your copy brings in green. dbplex reads only the schema, and only when you ask.
Then it writes the migration script in the order it must run: tables, triggers, backfills, indexes, then drops. A drop stays off until you turn it on, a rename is asked rather than guessed, and a column someone added to production since your pull is left alone. Rehearse the script on a throwaway copy of your data, then run it yourself. dbplex never runs it on production.
Your AI agent gets the same script over MCP. Works with Supabase, PostgreSQL, MySQL, MariaDB and Turso, and rehearsing with all of them but Supabase. The migration script is in beta.
Twelve databases, and the hosts they run on. Paste the address your provider gives you.
Each backup is one zip, pulled read-only and kept in a folder you choose, out of your provider's reach.
The database URL, the API URL and the keys are on one screen, or copy them all as a .env file.
The schema graph draws every table and how it links to the others, right from your copy.
No. It only reads.
UPDATE production SET data = NULL;
ERROR: dbplex only reads production. 0 rows changed.
dbplex reads production to make your copy. It cannot push, sync or write anything back.
PostgreSQLpostgresql://app:••••••@db.example.com/apppostgresql://postgres@localhost:5433/appSELECT * FROM cron.job;
Cron jobs and webhooks come with a copy and can still email real users, so dbplex lists every one that can reach outside after each pull.
Try it free. Then pick a plan. 7 days with every feature. No card and no account.
For a short project.
Need it past 6 months? From month 7, a license costs less, and the app keeps working after you stop.
For everyday use. The app is yours.
Renew with no gap and the price falls. The lower prices are for renewing before your updates end. If your license runs out, the next year is $79.99 again.
99of 100 left.
When the 100th sells, lifetime is gone.
Two years of a license cost $139.98. Eight months of monthly cost $103.92.
Buying for your company? Tell us how many people and we reply with a price.
Email usUse everything for 7 days, then enter a key if you want to keep it.
Download for MacAll payments are final, so try it first. An old version can stop pulling when a provider changes something, and fixing that takes an update. For Apple Silicon Macs. Read the terms and the privacy policy.
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.
Only for Supabase, SQL Server and Oracle. Supabase runs the official stack in containers, and SQL Server and Oracle run in Docker too, so those need Docker Desktop. dbplex starts and manages the containers, and you never see a compose file. Every other database runs without Docker.
Supabase, Firebase (Firestore), PostgreSQL, MySQL, MongoDB, Turso, SQLite, Redis, MariaDB, DynamoDB, SQL Server and Oracle. PostgreSQL works with any connection string you can reach, including Neon, Railway, Render, AWS RDS, Google Cloud SQL, Azure Database, DigitalOcean, Aiven and PlanetScale. MongoDB includes MongoDB Atlas, and Redis includes Upstash. You can also restore a dump file. For Firebase, Auth users, Storage files and other named databases are not copied.
Yes, for Supabase, PostgreSQL, MySQL, MariaDB and Turso. The Changes tab compares your copy's schema with production and writes the script in the order it must run, with drops left off until you turn them on. On PostgreSQL, MySQL, MariaDB and Turso you can rehearse it on a throwaway copy of your data first. Your AI agent can get the same script over MCP. dbplex never runs it on production, and the script is in beta.
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.
Yes. dbplex comes with an MCP server, which you add to Claude Code, Cursor, Codex or Windsurf from Settings. An agent can run SQL, rehearse and run migrations, make a branch of its own, save and restore states, read logs and refresh from production. Agents act on local copies only and never see your source credentials. Query results do go to your agent's AI provider, so choose what you import with that in mind.
Yes. Query results an agent reads go to its AI provider, so you can mask emails, names and other personal columns as the copy is pulled. dbplex suggests which columns to mask, and you confirm each one.
Not yet. dbplex runs on Macs with Apple Silicon.
Yes. 7 days with every feature, and no card or account. Download the app and start. Each Mac gets one trial.
Monthly is for a short project: updates are included, and the app locks when you stop paying. A license is yours: it comes with 1 year of updates, and if you stop renewing, the app keeps working and only the updates end.
Year 2 is $59.99, then $39.99 a year, as long as you renew with no gap. Once your updates have ended, the next year is $79.99 again. We email you before your updates end, and you can renew at /account. To renew automatically, tick the box when you buy or turn it on at /account, and we email you before each charge.
On a license or lifetime, nothing stops. You keep the version you have, though an old version can stop pulling when a provider changes something, and fixing that takes an update. On monthly, the app locks and its copies stop when the paid month ends. Nothing is deleted, and paying again brings it back.
Yes. Email s.castellitti.dev@gmail.com and tell us how many people. We reply with a price, and you get one key for the whole team.
Up to 3, and they can be changed at /account.
Go to /account.
No, all payments are final, so try it during the 7-day trial first.