From connection string to tested backup

Paste a connection string for Postgres, MySQL, MongoDB or Convex. backupd backs it up on your schedule, locks it to a key you hold, and restores it in a sandbox to prove it comes back.

14 days free on Starter. Nothing to install.

Connection stringpostgres://backupd:••••••@pg.acme.dev:5432/app
Schedule
Every hour
Keeps
90 days
Tested backupapp-prod.pgdump.zst.age
  1. ConnectTLS, read-only user
  2. Dumppg_dump, 2.1 GB
  3. Compresszstd, 412 MB
  4. Encryptage, 2 keys
  5. Storebackupd Storage
  6. Restore test48 tables, every row back

Works where your database already lives

  • PostgreSQL
  • MySQL
  • MongoDB
  • MariaDB
  • Convex
  • Supabase
  • Neon
  • PlanetScale
  • Cloud SQL
  • DigitalOcean
  • Railway
  • Render

Any host, as long as the database is reachable over TLS.
Names and logos belong to their owners.

See every database at a glance

Click through the app as it ships: your databases, their uptime, every backup file, alerts, keys and your team. Every screen here is in the product today.

AcmeTeam

Good morning

Acme · 4 databases, backed up on schedule.

Databases
4
3 active, 1 paused
Backups
2,317
711 this month
Storage
66.5 GB
Compressed size
Verified
98%
Restore tests passed

Recent backups

  • app-prod612 MBVerified12 min ago
  • billing88 MBSucceeded2 h ago
  • billingLost connection to serverFailed3 h ago
  • events1.4 GBVerified9 h ago

Needs attention

  • marketing-site is pausedNo backups for 3 days
  • billing failed onceThe next run succeeded

OverviewKnow in one look that last night’s backups ran, and what needs you.

Every backup, proven to restore

Most teams learn their backups are broken on the day they need them. backupd restores yours into a temporary database, checks that every table came back whole, then cleans up. If one is short, you get an alert, and the backup’s page names the table.

Restore test

app-prod-2026-10-15-0300.pgdump.zst.age
Restorable
Tables
5 of 5
Rows
1,766,383
Took
41s
Sandbox
postgres 16
  1. Fetch the backup612 MB from storage6s
  2. DecryptUnlocked and checksum matched3s
  3. RestoreInto a temporary Postgres 16 database27s
  4. Count rowsEvery table matches the backup4s
  5. Clean upTemporary database deleted1s
Counts per table, backed up against restored
TableBacked upRestoredResult
public.sessions1,402,3771,402,377match
public.order_items241,880241,880match
public.orders96,51296,512match
public.users18,20418,204match
public.invoices7,4107,410match
Starter
The latest backup, every day
Pro
Every backup, up to 10 GB

Locked before it is stored

Every backup is encrypted the moment it is made. Without one of its keys it is noise, to your cloud provider and to anyone who finds the file.

  • Create a key in your browser, or bring one you already have
  • Your secret key never reaches us
  • backupd keeps its own key so it can test and restore for you

app-prod-2026-10-15-0300.pgdump.zst.age

Locked to 3 keys. Any one of them opens it.

  • backupdRuns restore tests and restoresage1qyqs…3290gq
  • Your keyKept on your laptopage1m8tz…k4v7xp
  • Team keyKept in your password managerage1d3hn…q0s5re

When something breaks, you hear first

A failed backup, an unreachable database or a short restore test reaches your channel straight away, with the real error and never your password. Pick one and see what lands.

What broke
Where your team hears it

#ops-alerts

backupd APP 03:04

Backup failed · billing

The backup of billing in Acme failed.

Database
billing
Error
mysqldump: Lost connection to server during query
Open backupd

Big databases, no spare disk

Backups stream to storage while they are being made. A 100 GB database never needs 100 GB of free space, and nothing sits on a disk waiting to upload.

A backup is compressed and encrypted piece by piece and packed into upload parts in memory. Each full part goes to storage while the next one fills. Nothing is written to disk.

Part 4 is 5 of 8 pieces full. 3 parts uploaded, 0 B on disk.
0 B
Written to disk while a backup runs.
64 MiB
Parts upload while the dump continues.
2 checksums
Checked before and after encryption.
5 min
A stalled run is stopped and retried.

Convex exports are staged on our side first, then compressed and encrypted the same way.

Everything a backup needs

On every plan. How many databases and how often is on the pricing below.

Four databases, one place

Paste a connection string and pick a schedule. There is no agent to install and nothing to run on your servers.

On your schedule

Every hour to once a week, or right now with Back up now.

History you choose

Keep a week to a year. The newest good backup is never pruned.

A copy in your own bucket

On Pro, every backup is also copied to storage you own, still encrypted.

Made for teams

Invite your team, sign in with a passkey or two-factor, and see every change in the audit log.

Alerts and uptime checks

Each database is checked every 5 minutes. A failed backup or an outage reaches your team where it already works.

Pay for what we store

Starter is free for 14 days. Storage is counted after compression and encryption, so it is usually a fraction of your database’s size.

Starter

$10

a month after 14 days free. For a product with real users.

  • 5 databases
  • Every 12 hours, kept 30 days
  • 50 GB, then $0.10 per GB
  • Restore test every day
  • 2 backups at once
Start 14-day trial

Pro

$25

a month. For teams that cannot lose a day.

  • 20 databases
  • Hourly, kept 90 days
  • 150 GB, then $0.08 per GB
  • Every backup restore-tested, up to 10 GB
  • 4 backups at once
  • 48 manual backups a day
  • Copies to your own bucket
Choose Pro

Custom

Let’s talk

For many databases, long history or a lot of data.

  • More databases than Pro
  • Retention longer than 90 days
  • Larger backups, more at once
  • Restore tests on every backup, any size
  • Storage priced for your volume
  • Help moving your first databases in
Contact sales

Or write to [email protected]

Questions worth asking first

Yes. Add your own key in Settings and every new backup is locked to it as well as to ours. Download the file and open it on your own machine with free, open-source tools. The docs walk you through it.

Your database has to be reachable from the internet over TLS, either public or allowing our IP addresses. Databases inside a private network, behind an SSH tunnel or an agent, are not supported yet.

Every backup is locked to backupd’s key for your workspace, so we can run restore tests and restores for you, and to every key you add. There is no mode where only you can open it.

We restore your latest backup into a temporary database on a sandbox server running the same engine, count the rows in every table against what we backed up, then delete it. Convex has no temporary database, so its backups get an integrity check and per-table counts instead.

Storage is counted after compression and encryption, never at the size of your database. Starter and Pro carry on at $0.10 and $0.08 per GB, up to a spending cap you set, so a busy month never turns into a surprise bill.

Starter is free for 14 days. Cancel before then and you pay nothing. If a workspace has no plan, backups stop, but every backup already taken stays there to download and restore.

Not yet. Each backup is a full copy, as often as every hour on Pro. Point-in-time recovery and incremental backups are not available yet.

Keep a key of your own

Try Starter free for 14 days. Add your own key, and every backup after that is yours to open, with or without us.