🥟 For Postgres and MySQL on Supabase, Railway, Neon, Render, Fly and anywhere else
Your hosted database has no off-platform backup. Fix that tonight, into a bucket you own.
Dumpling runs pg_dump / mysqldump on a schedule and streams the result straight into your S3, Cloudflare R2 or Backblaze B2 bucket. We store nothing, we need only a read-only user and one allow-listed IP, and you get an email the moment a backup does not happen.
No credit card. One database with daily, encrypted backups is free, forever. Setup takes one sitting: a database user, a bucket key, and allow-listing one IP.
$ dumpling run "production-db" [02:17:01] Connected: PostgreSQL 16.4, size 640 MB [02:17:01] Running pg_dump --format=custom ... [02:18:44] Uploaded 138 MB to backups/production-db/2026-09-10T02-17-01Z.dump.enc [02:18:45] Retention: deleted 1 old backup(s), keeping 14 [02:18:45] ✅ done in 1m 44s — next run in 24h
Nothing to lose if we disappear
Backups stream from your database straight into storage you own, in native pg_dump and mysqldump formats. We never keep a copy. If Dumpling vanished tomorrow, every backup you have would still restore with the standard tools.
The cron job that tells you when it stops
Failure emails and webhooks, an alert when a run is overdue, size guards before every run, and a log you can read. The point of a backup is the day it is missing; you will hear about that day.
Nothing to take on trust
Credentials encrypted at rest and decrypted only for the run, one fixed IP to allow-list, a read-only user is all we need, and the security page says exactly what is stored. Run by one person who answers the support address.
Works wherever your database lives
Any publicly reachable PostgreSQL or MySQL, and any S3-compatible bucket.
Three steps, no agent to install
- 01
Connect your database
Paste host, port, user and password. We test the connection and check the size right away. Use a read-only user if you like.
- 02
Point at your bucket
Add S3 / R2 / B2 credentials scoped to a single bucket. We write a tiny test object and delete it to confirm access.
- 03
Pick a schedule
Hourly, daily, weekly or cron. Set how many backups to keep. Optionally encrypt files so they decrypt with plain openssl anywhere.
Simple pricing
One database is free forever. Pay when you have several to protect, and only for the scheduling, monitoring and alerts: the storage is yours.
Free
For a side project that deserves a backup.
- ✓ 1 backup job
- ✓ Daily backups
- ✓ Databases up to 1 GB
- ✓ 7 days of run history
- ✓ Email alerts on failure
- ✓ Encrypted backups (openssl-compatible)
Pro
For indie hackers and small SaaS products.
- ✓ 10 backup jobs
- ✓ Hourly backups
- ✓ Databases up to 25 GB
- ✓ 90 days of run history
- ✓ Email + webhook alerts
- ✓ Encrypted backups (openssl-compatible)
Team
Pro with more room: more jobs, faster schedules, a year of history.
- ✓ 50 backup jobs
- ✓ Backups every 15 minutes
- ✓ Databases up to 100 GB
- ✓ 1 year of run history
- ✓ Email + webhook alerts
- ✓ Encrypted backups (openssl-compatible)
Questions
- Do you store my backups?
- No. The dump is streamed from your database through our worker's memory into your bucket using multipart upload. Nothing is written to disk on our side, and we keep no copy.
- How are my credentials stored?
- Database passwords and bucket secrets are encrypted at rest with AES-256-GCM and decrypted in memory only for the connection test and the backup run. The security page lists exactly what is stored and what never is.
- What if a backup fails?
- You get an email (and a webhook if configured) with the error and the log. Every run's log is available in the dashboard.
- How do I restore?
- Postgres backups are pg_dump custom format: `pg_restore -d yourdb file.dump`. MySQL backups are gzipped SQL: `gunzip < file.sql.gz | mysql yourdb`. Encrypted files decrypt with plain openssl. The restore command is shown on every run.
- Is my database exposed?
- Your database has to be reachable from our worker's single fixed IP. Most managed providers let you allow-list one IP; we show you which one. A read-only database user is all we need.
- Who is behind this?
- One independent developer, named on the about page, who answers the support address. Dumpling is deliberately small: one server, no investors, and a design where your data never passes through storage we control.