At a glance
| DumpCat | Ottomatik | |
|---|---|---|
| Price and license | Free and open source (Apache-2.0). No account, no license key. | Lite $14/month (3 jobs, daily, 5 GB), Professional $79 (50 jobs, every 5 minutes, 100 GB, API), Agency $199 (250 jobs, every minute, 200 GB). Your own storage on every plan; 14-day trial. |
| How it runs | Self-hosted: one binary with a web UI, running as a systemd or Windows service next to your database. | Hosted SaaS. Its servers connect to yours over SSH and install Python, pip and the AWS CLI there. |
| Platforms | Linux (amd64, arm64) and Windows (64-bit). | Linux servers. |
| Databases | MySQL 5.7, 8.0, 8.4, Percona Server, MariaDB 10.x and 11.x. | MySQL, PostgreSQL and MongoDB. MariaDB support is not stated on the pages we checked. |
| Backup methods | Logical with mysqldump / mariadb-dump or parallel mydumper; hot physical backups with XtraBackup / MariaBackup, including incrementals. No locks on InnoDB. | mysqldump, with options for a single transaction or skipping locks, routines and events. |
| Point-in-time recovery | Yes. Continuous binlog archiving; restore to a timestamp, a binlog position or just before a GTID. | Partial: binlogs can be uploaded to S3 or copied by a file backup job; replaying them is manual. |
| Storage | Local disk / NFS, S3 and compatibles, Google Drive, OneDrive, SFTP, FTP / FTPS, WebDAV, Backblaze B2, Azure Blob, Dropbox and every rclone backend; several per job. | Ottomatik's storage, Amazon S3 and S3-compatible, Google Drive, Dropbox, Backblaze. |
| Encryption | age encryption on your server before anything is uploaded; zstd compression; SHA-256 for every file. | Credentials are stored encrypted; encryption of the backup files is not described on the pages we checked. |
| Scheduling and retention | Cron-style schedules; retention per storage by count, age or GFS (daily / weekly / monthly). | From daily (Lite) to every minute (Agency); jobs and storage capped per plan. |
| Restore | From the web UI: restore under a new database name, test-decrypt every file before dropping anything, integrity checks after each run. | One-click restore to the same or another server, on some plans. |
| Where your data goes | Straight from your server to the storage you choose. Nothing passes through a third party. | The backup goes from your server straight to your storage, but Ottomatik keeps SSH, database and storage credentials (encrypted) on its side. |
| Notifications | Email, Telegram, Slack, Discord and HMAC-signed webhooks. | Webhooks; team roles for the dashboard. |
Choose Ottomatik if
- You want scheduling and monitoring that run outside your server, with nothing to keep updated yourself.
- You back up PostgreSQL and MongoDB too and want one dashboard for all of them.
- You want backups as often as every minute and one-click restores to another server.
Choose DumpCat if
- You would rather not give a third party SSH access to your database server.
- You want point-in-time recovery from the UI instead of replaying binlogs by hand.
- You run Windows servers, or need hot physical backups for large databases.
- You want it free, with no limits on jobs or storage.
Switching from Ottomatik
- Install DumpCat on the database server.
- Add your S3, Google Drive or Dropbox storage to DumpCat, in a new folder.
- Recreate each job with its schedule and retention, turn on binlog archiving, and run it once.
- Once DumpCat's retention covers what you need, remove Ottomatik's SSH key from the server.
Sources
Facts about Ottomatik 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.
- Ottomatik pricing
- Ottomatik: MySQL backup and restore
- Ottomatik help: how sensitive data is encrypted
- Ottomatik help: MySQL binlog backups
- Ottomatik help: automated MySQL dump restore
Ottomatik is a trademark of its owner. DumpCat is an independent open-source project and is not affiliated with it.