Databasus

Databasus is a self-hosted database backup tool for PostgreSQL, MySQL, MariaDB, and MongoDB. It is best suited to developers and operations teams that want to manage backups in their own environment. PostgreSQL is its strongest use case, particularly for teams that need point-in-time recovery and can run PostgreSQL 17 or newer.

Overview

Databasus is free, open-source software under the Apache 2.0 license. It combines scheduled backups with continuous PostgreSQL WAL streaming, access controls, audit logs, encryption, and restore verification. That breadth makes it more than a basic scheduler, but self-hosting puts responsibility for the service and backup storage on the operator.

Installation options include an automated Linux script, Docker, Docker Compose, and Helm for Kubernetes. The minimum documented setup is one CPU core, 500 MB of RAM, 5 GB of installation storage plus separate backup storage, Docker Engine 20.10 or later, and Docker Compose 2.0 or later. Those requirements are modest, though they do not remove the need to plan storage capacity for backups.

Key features

PostgreSQL recovery

For PostgreSQL, Databasus supports logical, physical full, and incremental backups, along with WAL streaming for point-in-time recovery. The recovery options are a strong reason to consider it for PostgreSQL operations; physical, incremental, and WAL backups require PostgreSQL 17 or newer, so older installations cannot use that full set of capabilities.

Backup schedules can run hourly, daily, weekly, monthly, or at cron intervals. Storage destinations include local storage, S3-compatible storage, Cloudflare R2, Google Drive, Azure Blob Storage, NAS, FTP, SFTP, and rclone. This range lets teams choose among local, cloud, and transfer-based destinations, but they still need to operate the deployment and arrange the storage themselves.

Verification, security, and team controls

Databasus periodically downloads the latest backup, restores it into a throwaway database container, and reports the result. That gives operators a recurring check that a backup can be restored, rather than treating successful backup creation as proof of recoverability.

It provides user access management for databases, separate teams and projects, and audit logs of access and changes. Databasus says it encrypts credentials and backup files with AES-256-GCM, and uses read-only database access requiring SELECT permissions. These controls can help teams limit what the backup service can do and track how it is used.

Notifications can go to Slack, Discord, Telegram, Microsoft Teams, email, or custom webhooks. Databasus supports PostgreSQL, MySQL, MariaDB, and MongoDB, but its physical, incremental, and WAL recovery options are specifically described for PostgreSQL.

Pricing

The Free, open-source software plan costs nothing and includes all described product features under the Apache 2.0 license. There is no free trial, but there is also no paid entry tier or feature-gated cheaper plan to graduate from. The trade-off is that the plan is self-hosted: operators must provide the host, backup storage, and ongoing maintenance.

Platforms

Databasus is available for Linux, self-hosted deployment, and the web. Supported installation paths include the Linux script, Docker, Docker Compose, and Helm for Kubernetes. Its documented minimums include Docker Engine 20.10 or later and Docker Compose 2.0 or later.

Who it's for

Databasus fits individual developers, DevOps teams, and enterprises that want a free backup system they can run and administer themselves. PostgreSQL users who need continuous WAL streaming and periodic restore checks have the clearest reason to choose it. It is a weaker fit for teams unable to maintain a self-hosted service, or PostgreSQL installations below version 17 that need physical, incremental, or WAL backups.

Pros and cons

• Pros: All described features are included in a free Apache 2.0 plan, with no trial period to manage.
• Pros: PostgreSQL backup options include logical, full physical, incremental, and WAL-based point-in-time recovery, subject to the PostgreSQL 17 requirement for the latter three.
• Pros: Periodic restore verification checks backups by restoring them in a throwaway container.
• Pros: Destination and notification integrations span common cloud, file-transfer, and team-alert channels.
• Cons: Self-hosting means the operator must maintain the service and provision backup storage beyond the 5 GB installation minimum.
• Cons: Physical, incremental, and WAL backups require PostgreSQL 17 or newer.

Alternatives

Compare database backup software if you want to consider other tools in the category. DBAegis is another free option, with a Community plan capped at one admin, three connections, and three schedules, plus local logical PostgreSQL backups. SqlBak may suit teams that need a Windows option or a defined backup-history cap: its free plan covers one server, two databases, one month of history, and server-down alerts every 60 minutes, while Standard costs $6 a month.

pgBackRest is a free, open-source Linux and self-hosted option under the MIT license for personal or commercial use. pg_probackup is a free backup and recovery utility for PostgreSQL clusters, with Linux, self-hosted, and Windows platforms. Barman is another free, open-source PostgreSQL disaster recovery tool for Linux and self-hosted use.

Zmanda Recovery Manager for MySQL is worth considering for MySQL and MariaDB backup and recovery, with optional snapshot and plugin licenses. Databasement is another free option. SQLBackupAndFTP is a freemium option for Windows.

Verdict

Choose Databasus if you want a free, self-hosted backup system with broad storage choices and PostgreSQL point-in-time recovery, and can meet the PostgreSQL 17 requirement for its deepest recovery features. Look elsewhere if you want a managed service or cannot take responsibility for running the deployment and its backup storage.