Docker-aware backup & restore

Your Docker projects deserve backups that actually restore

Dockstash makes backing up any Docker project one click. It auto-detects your volumes, databases, and config, dumps each database consistently from its running container, and stores encrypted Restic snapshots off-site — with automated restore drills that prove the backup works.

Backs up:PostgreSQLMySQLMariaDBMongoDBRedisValkeySQLiteClickHouseElasticsearchRabbitMQMinIOInfluxDBNeo4j
From compose file to verified snapshot

Point it at a project. It figures out the rest.

No backup config to write. Dockstash reads your Compose stack, detects each engine, runs the correct consistent dump for it, and stores an encrypted off-site Restic snapshot — then proves it restores with an automated drill.

Most homemade Docker backups are broken

Live-file database copies

Backing up a running Postgres/MySQL data directory captures torn writes. It looks fine until the restore fails.

Silent failures

Cron jobs stop and nobody notices — until recovery day. No alert, no heartbeat, no proof.

Fragile scripts

Hand-rolled restic + cron + pg_dump breaks on a version bump and has no restore verification.

How it works

Scan, back up, verify

  1. Scan. Dockstash reads your Compose project and detects databases, volumes, and reverse-proxy config.
  2. Back up. Each database is dumped consistently from its container, then Restic snapshots the dump + files off-site, encrypted.
  3. Verify. Automated restore drills restore to a scratch location and diff against source, so you know it works.

Compared to Backrest and DIY scripts →

Why teams trust Dockstash

Verified restores, your storage, no lock-in

Docker-aware

Knows a Postgres container needs a pg_dumpall, not a file copy.

Verified restores

Automated restore-drill diffs prove your backups are real.

Your storage, no lock-in

Standard Restic repos on your own VPS. Restore without us.

Encrypted secrets

AES-256-GCM at rest; SSH host-key pinning on the backup channel.

Frequently asked questions

How does Dockstash back up a Docker database?

Dockstash runs the database’s native dump inside the running container (pg_dumpall, mysqldump --single-transaction, or mongodump --oplog), then stores the dump as an encrypted Restic snapshot. It never copies live database files off disk, because a half-written data file cannot be restored.

Where are my backups stored?

On your own storage VPS over SSH, as standard encrypted Restic repositories. Dockstash never holds your data. The Free tier runs entirely self-hosted with no paid provider.

How do I know a backup will actually restore?

Dockstash runs automated restore drills: it restores the latest snapshot to a scratch location and diffs it against the source, then surfaces per-project drill status. An untested backup is treated as no backup.

Do I need to write a backup config?

No. Dockstash scans your Docker Compose project, detects databases, volumes, and reverse-proxy config, and proposes a plan you confirm with checkboxes. One click backs everything up.

Back up your first Docker project in minutes

Free and fully self-hosted to start — no card, your storage, your keys.