DumpCat
ENVI

DumpCat vs Databasus

Databasus, formerly Postgresus, is a popular open-source backup web app that grew from PostgreSQL to MySQL, MariaDB and other engines. DumpCat focuses on MySQL and MariaDB only. Both are Apache-2.0 and self-hosted; here is where they differ.

Download DumpCat Source on GitHub

At a glance

DumpCatDatabasus
Price and licenseFree and open source (Apache-2.0). No account, no license key.Free and open source (Apache-2.0).
How it runsSelf-hosted: one binary with a web UI, running as a systemd or Windows service next to your database.Self-hosted web app, deployed with an install script, Docker, Docker Compose or Helm.
PlatformsLinux (amd64, arm64) and Windows (64-bit).Wherever Docker or Kubernetes runs.
DatabasesMySQL 5.7, 8.0, 8.4, Percona Server, MariaDB 10.x and 11.x.MySQL 5.7, 8.0, 8.4 and later, MariaDB from 5.5; also PostgreSQL and other engines.
Backup methodsLogical with mysqldump / mariadb-dump or parallel mydumper; hot physical backups with XtraBackup / MariaBackup, including incrementals. No locks on InnoDB.Logical only for MySQL and MariaDB: mysqldump / mariadb-dump with --single-transaction. Physical and incremental backups are for PostgreSQL only.
Point-in-time recoveryYes. Continuous binlog archiving; restore to a timestamp, a binlog position or just before a GTID.Not for MySQL or MariaDB; point-in-time recovery (WAL) is PostgreSQL only.
StorageLocal disk / NFS, S3 and compatibles, Google Drive, OneDrive, SFTP, FTP / FTPS, WebDAV, Backblaze B2, Azure Blob, Dropbox and every rclone backend; several per job.Local, S3, Cloudflare R2, Google Drive, Azure Blob, NAS, FTP, SFTP and rclone.
Encryptionage encryption on your server before anything is uploaded; zstd compression; SHA-256 for every file.AES-256-GCM; compression on by default.
Scheduling and retentionCron-style schedules; retention per storage by count, age or GFS (daily / weekly / monthly).Retention by time, count, GFS tiers or total size.
RestoreFrom the web UI: restore under a new database name, test-decrypt every file before dropping anything, integrity checks after each run.Restores from the UI, and restore verification in throwaway containers that reports row counts.
Where your data goesStraight from your server to the storage you choose. Nothing passes through a third party.Your own infrastructure: from the Databasus instance you run to your storage.
NotificationsEmail, Telegram, Slack, Discord and HMAC-signed webhooks.Email, Telegram, Slack, Discord, Teams, Mattermost and webhooks; workspaces, roles, audit logs, two-factor login, Google and GitHub sign-in.

Choose Databasus if

  • You back up PostgreSQL as well, where Databasus also offers physical backups and point-in-time recovery.
  • You run on Kubernetes or Docker and want a Helm chart.
  • You want automatic restore verification in throwaway containers, or team workspaces with Google / GitHub sign-in.

Choose DumpCat if

  • You need point-in-time recovery for MySQL or MariaDB: DumpCat archives binlogs and restores to a second or just before a GTID.
  • Your MySQL databases are large: parallel mydumper and hot physical backups with XtraBackup / MariaBackup, including incrementals.
  • You do not want Docker: DumpCat is one binary, installed as a systemd or native Windows service.
  • You want a tool built only around MySQL and MariaDB, with restores into a new database name and checks before anything is dropped.

Sources

Facts about Databasus were checked on October 18, 2026 against the sources below. Products change: if something here is out of date, please open an issue on GitHub.

  1. Databasus on GitHub
  2. Databasus: MySQL backup
  3. Databasus: restore verification

Databasus is a trademark of its owner. DumpCat is an independent open-source project and is not affiliated with it.

Other comparisons