Where do my backups live and how much space will they occupy?

Archives can be saved to local volumes, S3-compatible buckets, Google Drive, Dropbox and other cloud targets. Databasus implements balanced compression, which typically shrinks dump size by 4-8x with incremental only about 20% of runtime overhead, so you have storage and bandwidth savings.

How will I know a backup succeeded — or worse, failed?

Databasus can notify with real-time emails, Slack, Telegram, webhooks, Mattermost, Discord and more. You have the choice of what channels to ping so that your DevOps team hears about successes and failures in real time, making recovery routines and compliance audits easier.

Databasus

PostgreSQL backup tool with MySQL and MongoDB support

Databasus is a free, open source and self-hosted tool to backup PostgreSQL. Make backups with different storages (S3, Google Drive, FTP, etc.) and notifications about progress (Slack, Discord, Telegram, etc.). MySQL, MariaDB and MongoDB are supported too

Configure in 2 minutes GitHub

Overview

Features

Databasus provides everything you need for reliable production backup management. From automated scheduling to backups encryption. Suitable well for both individual developers with personal projects, DevOps teams and enterprises

Scheduled backups

Backup is a thing that should be done in specified time on regular basis. So we provide many options: from hourly to monthly

Configurable health checks

Each minute (or any another amount of time) the system will ping your database and show you the history of attempts

The database can be considered as down after 3 failed attempts or so. Once DB is healthy again - you receive notification too

Many destinations to store

Files are kept on VPS, cloud storages and other places. You can choose any storage you. Files are always owned by you. View all →

Notifications

You can receive notifications about success or fail of the process. This is useful for developers or DevOps teams. View all →

Self hosted via Docker

Databasus runs on your PC or VPS. Therefore, all your data is owned by you and secured. Deploy takes about 2 minutes via script, Docker or k8s

Open source and free

The project is fully open source, free and have Apache 2.0 license. You can copy and fork the code on your own. Open for enterprise as well

Many PostgreSQL versions

PostgreSQL 12, 13, 14, 15, 16, 17 and 18 are supported by the project. You can backup any version from 2019

Security

Enterprise-grade encryption protects sensitive data and backups. Read-only database access prevents data corruption. Everything this does not require any knowledge and ready out of the box from the start automatically. Read more →

Access management

for teams

Provide access for users to view or manage DBs. Separate teams and projects. Suitable for DevOps teams and developers. Read more →

Audit logs

for teams

Track all system activities with comprehensive audit logs. You can view access and changes history for each user (backup downloads, schedule changes, config updates, etc.). Read more →

Security

Suitable both for self-hosted and cloud databases

Databasus works seamlessly with cloud-hosted databases including AWS RDS, Google Cloud SQL, Azure Database. This is why Databasus does not support incremental backups: clouds already have them, but usually you cannot restore external PITR backup back to the cloud. Hourly and daily granularity are enough for 99% of even large enterprise projects

4-minutes overview

How to use Databasus?

Watch in this video how to connect your database, how to configure backups schedule, how to download and restore backups, how to add team members and what is users' audit logs

Rostislav Dugin

Developer of Databasus

Databases

Supported databases

Databasus supports PostgreSQL, MySQL, MariaDB and MongoDB. You can backup and restore all of them with the same tool. Primary focus is on PostgreSQL, but MySQL, MariaDB and MongoDB are supported too

PostgreSQL

PostgreSQL is the primary database supported by Databasus. All versions from 12 to 18 are supported

MySQL

MySQL is the second most popular database in the world. You can backup and restore your MySQL databases with the same simplicity

MariaDB

MariaDB is supported with the same features as MySQL. You can backup and restore your MariaDB databases seamlessly

MongoDB

MongoDB is the most popular NoSQL database. You can backup and restore your MongoDB databases with the same easy-to-use interface

Process

How to make backups?

The main priority for Databasus is simplicity, right now this is the easiest tool to backup PostgreSQL in the world. To make backups, you need to follow 4 steps. After that, you will be able to restore in one click

Step 1

Select required schedule

You can choose any time you need: daily, weekly, monthly, particular time (like 4 AM) and cron cycles

For week interval you need to specify particular day, for month you need to specify particular day

If your database is large, we recommend you choosing the time when there are decrease in traffic

Step 2

Enter your database info

Enter credentials of your PostgreSQL database, select version and target DB. Also choose whether SSL is required

Databasus, by default, compress backups at balance level to not slow down backup process (~20% slower) and save x4-x8 of the space (that decreasing network traffic)

Step 3

Choose storage for backups

You can keep files with backups locally, in S3, in Google Drive, NAS, Dropbox and other services

Please keep in mind that you need to have enough space on the storage

Step 4

Choose where you want to receive notifications (optional)

When backup succeed or failed, Databasus is able to send you notification. It can be chat with DevOps, your emails or even webhook of your team

We are going to support the most of popular messangers and platforms

Get started

How to install?

Databasus support many ways of installation. Both local and cloud are supported. Both ways are extremely simple and easy to use even for those who has no experience in administration or DevOps

Automated script (recommended)

The installation script will install Docker with Docker Compose (if not already installed), set up Databasus and configure automatic startup on system reboot.

sudo apt-get install -y curl && \
sudo curl -sSL https://raw.githubusercontent.com/databasus/databasus/refs/heads/main/install-databasus.sh | sudo bash

Frequent questions

The goal of Databasus — make backing up as simple as possible for single developers (as well as DevOps) and teams. UI makes it easy to create backups and visualizes the progress and restores anything in couple of clicks

What is Databasus and why should I use it instead of hand-rolled scripts?

Databasus is an Apache 2.0 licensed, self-hosted service backing up databases. It differs from shell scripts in that it has a frontend for scheduling tasks, compressing and storing archives on multiple targets (local disk, S3, Google Drive, NAS, Dropbox, SFTP, rclone, etc.) and notifying your team when tasks finish or fail — all without hand-rolled code

How do I install Databasus in the quickest manner?

Databasus supports multiple installation methods: automated script, Docker, Docker Compose and Kubernetes with Helm. The quickest route is to run the one-line cURL installer, which fetches the current Docker image, creates a docker-compose.yml and boots up the service so it will automatically restart on reboots. For Kubernetes environments, use the official Helm chart for production-ready deployments. Overall time is usually less than two minutes on a typical VPS.

What backup schedules can I schedule?

You can choose from hourly, daily, weekly, monthly or cron cycles and even choose an exact run time (such as 04:00 when it's late night). Weekly schedules enable you to choose a particular weekday, while monthly schedules enable you to choose a particular calendar day, giving you very fine-grained control of maintenance windows.

How does Databasus ensure security?

Databasus enforces security on three levels: (1) Sensitive data encryption — all passwords, tokens and credentials are encrypted with AES-256-GCM and stored separately from the database; (2) Backup encryption — each backup file is encrypted with a unique key derived from a master key, backup ID and random salt, making backups useless without your encryption key even if someone gains storage access; (3) Read-only database access — Databasus only requires SELECT permissions and performs comprehensive checks to ensure no write privileges exist, preventing data corruption even if the tool is compromised.

How do I set up and run my first backup job in Databasus?

To start your very first Databasus backup, simply log in to the dashboard, click on New Backup, select an interval — hourly, daily, weekly, monthly or cron. Then specify the exact run time (e.g., 02:30 for off-peak hours).

Then input your PostgreSQL host, port number, database name, credentials and SSL preference. Choose where the archive should be sent (local path, S3 bucket, Google Drive folder, Dropbox, etc.).

If you need, add notification channels such as email, Slack, Telegram or a webhook and click Save. Databasus instantly validates the info, starts the schedule, runs the initial job and sends live status. So you may restore with one touch when the backup is complete.

How does PostgreSQL monitoring work?

Databasus monitors your databases instantly. This optional feature helps avoid extra costs for edge DBs. Health checks are performed once a specific period (minute, 5 minutes, etc.). To enable the feature, choose your DB and select 'enable' monitoring. Then configure health checks period and number of failed attempts to consider the DB as unavailable.

Who is Databasus suitable for?

Databasus is designed for single developers, DevOps teams, organizations, startups, system administrators and IT departments who need reliable databases backups. Whether you're managing personal projects or production databases, Databasus provides enterprise-grade backup capabilities with a simple, intuitive interface.

How is Databasus different from PgBackRest, Barman or pg_dump? Where can I read comparisons?

Unlike other tools, Databasus provides a way to manage many databases for teams in a modern, user-friendly web interface (instead of complex configuration files and command-line tools). While PgBackRest and Barman just backups single database, require extensive configuration and command-line expertise — Databasus offers way to setup full backup management for many databases. Unlike raw pg_dump scripts, it includes built-in scheduling, compression, multiple storage destinations, health monitoring and real-time notifications — all managed through a simple web UI.

We have detailed comparison pages for popular backup tools: Databasus vs pg_dump, Databasus vs pgBackRest, Databasus vs Barman, Databasus vs WAL-G and Databasus vs pgBackWeb. Each comparison explains the key differences, pros and cons, and helps you choose the right tool for your needs.

Can I use Databasus as an individual and as a team?

Yes, Databasus works perfectly for both individual developers and teams. For individuals, you can manage all your databases with a simple, secure interface. For teams, Databasus offers access management features that let you create multiple users with different permission levels (viewer, editor, admin).

You can control who can view or manage specific databases, making it ideal for DevOps teams and development organizations. Additionally, audit logs track all system activities, showing who accessed what and when, which is essential for security compliance and team accountability.

Is Databasus an alternative to pg_dump?

Yes, Databasus is a modern alternative to pg_dump. Under the hood, Databasus extends pg_dump features, adds user-friendly web interface, automated scheduling, multiple storage destinations, real-time notifications, health monitoring and backup encryption. Think of Databasus as pg_dump with superpowers — you get all the reliability of pg_dump plus optimizations and enterprise features without writing shell scripts.

Which databases does Databasus support?

Databasus supports PostgreSQL, MySQL, MariaDB and MongoDB. However, Databasus was originally created specifically for PostgreSQL and maintains its primary focus on it — providing 100% excellent support and maximum efficiency for PostgreSQL backups. While MySQL, MariaDB and MongoDB are fully supported, PostgreSQL remains the core priority with the most optimized features and ongoing development.

Why doesn't Databasus support PITR (Point-in-Time Recovery)?

Databasus intentionally focuses on logical backups rather than PITR for several practical reasons:

Complex setup requirements — PITR tools typically need to be installed on the same server as your database, requiring direct filesystem access and careful configuration. You can backup only single database (Databasus allows many)
Restoration limitations — incremental backups cannot be restored without direct access to the database storage drive
Cloud incompatibility — managed cloud databases (AWS RDS, Google Cloud SQL, Azure, Supabase) don't allow restoring external PITR backups, making them useless for cloud-hosted PostgreSQL
Built-in cloud PITR — cloud providers already offer native PITR capabilities, and even they typically default to hourly or daily granularity
Practical sufficiency — for 99% of projects, hourly or daily logical backups provide adequate recovery points without the operational complexity of WAL archiving

So instead of second-by-second restoration complexity, Databasus prioritizes an intuitive UX for individuals and teams, making it the most reliable tool for managing multiple databases and day to day use

Why was Postgresus renamed to Databasus?

Databasus has been developed since 2023. It was internal tool to backup production and home projects databases. In start of 2025 it was released as open source project on GitHub. By the end of 2025 it became popular and the time for renaming has come in December 2025.
The renaming from Postgresus to Databasus was an important step for the project's growth. There are several reasons:

Project evolution — Postgresus is no longer a small tool that just adds UI for pg_dump. It became a reliable backup management system for individual users, DevOps, DBAs, teams and enterprises. Tens of thousands of users use it daily. The initial positioning is no longer suitable — it's not just a UI wrapper, it's a solid backup management system now
Multiple databases support — while the primary focus remains PostgreSQL (with 100% support in the most efficient way), the project now supports MySQL, MariaDB and MongoDB. More databases will be supported in the future
Trademark compliance — "postgres" is a trademark of PostgreSQL Inc. and cannot be used in project names. For legal safety and compliance, renaming was necessary

If you're currently using Postgresus, you can continue using it or migrate to Databasus following the installation steps. Note that simply renaming the image isn't enough, as they use different data folders and internal database naming.

How is AI used in Databasus development?

There have been questions about AI usage in project development. As the project focuses on security, reliability and production usage, we want to be transparent about how AI is used in the development process.

AI is used as a helper for code quality verification, documentation improvement and assistance during development. AI is NOT used for writing entire code or code without tests. The project has solid test coverage, CI/CD automation and verification by experienced developers.

For detailed information about AI usage, development process and security measures, please visit our dedicated FAQ page.

How can I join the Databasus community?

You can join our large community of developers, DBAs and DevOps engineers at t.me/databasus_community. The community is a great place to ask questions, share experiences, get help with configuration and stay updated with the latest features and releases.