Dockstash vs Backrest

Backrest is a free, open-source web UI and scheduler wrapped around restic. It is the closest tool to Dockstash and an excellent generic restic frontend. The gap: Backrest is not Docker-aware — it backs up paths, so a live Postgres data directory gets copied instead of dumped, and there is no restore-drill verification.

Head to head

At a glance

CapabilityDockstashBackrest
Docker-aware database dumpsAuto-detects Postgres/MySQL/MariaDB/Mongo and dumps from the running containerNone — backs up whatever host paths you point it at, including live DB files
Compose + reverse-proxy detectionScans docker-compose.yml, .env, volumes, and Traefik/nginx config automaticallyManual — you list every path yourself
Automated restore-drill verificationScheduled restore-to-scratch + diff vs source proves the backup restoresrestic check verifies repo integrity only, not restorability
Failure alertingResend email alerts plus a dead-man’s-switch heartbeat catch silent stallsBasic notification hooks; no heartbeat / dead-man’s-switch
Per-project billing for agenciesPer-project metering and multi-VPS fleet viewNone (not a product goal)
Underlying backup engineRestic (encrypted, deduplicated, incremental) — standard reposRestic (same engine) — standard repos
PriceFree self-host tier; paid Pro/Business for scale + supportFree and open-source, no paid tier
Lock-inStandard restic repos on your storage VPS — restore without DockstashStandard restic repos — restore without Backrest

Who each is for

Choose Dockstash if…

You run databases in Docker and want them dumped correctly (pg_dumpall, mysqldump --single-transaction, mongodump --oplog) and drill-verified — not copied live.

Choose Backrest if…

Self-hosters who back up plain files and directories and are comfortable adding their own pre-backup database dump hooks.

Migrating to Dockstash

Both tools write standard restic repositories, so migration is low-risk: point Dockstash at your existing restic repo and it reads your snapshots directly. The one change worth making is to stop backing up live database data directories and let Dockstash’s adapters dump them from the container instead. Your retention and prune policies map across one-to-one.

Start free The Backrest alternative in depth

Last updated: July 2026

Frequently asked questions

Is Dockstash a fork of Backrest?

No. Both use restic as the engine, but Dockstash is a separate MERN application built around Docker-project awareness: adapter-based database dumps, Compose/reverse-proxy detection, and automated restore drills. Backrest is a generic restic UI.

Backrest is free — why pay for Dockstash?

Dockstash has a free self-host tier too. You pay only when you want scheduling at scale, email alerts, more projects, or per-project billing for many client servers. The database-adapter and restore-drill correctness features are the reason to switch, not the price.

Can Backrest back up my Postgres container correctly?

Only if you add your own pre-backup hook that runs pg_dumpall and writes the dump to a path Backrest then backs up. Out of the box it copies the live data directory, which is not a consistent, restorable dump. Dockstash does the dump for you.

Will my existing restic repo work with Dockstash?

Yes. Dockstash reads standard restic repositories. Point it at the same repo and password and your Backrest-created snapshots are visible immediately.

Does Backrest verify that backups restore?

Backrest can run restic check, which validates repository integrity. It does not restore the data to a scratch location and diff it against the source. Dockstash runs that restore drill on a schedule so you know recovery works before you need it.