Do I need a domain to use Databasus?

No. Databasus publishes its interface on the VPS loopback: open an SSH tunnel (`ssh -L 4005:127.0.0.1:4005 root@ `) then http://localhost:4005. If you prefer permanent HTTPS access, attach a domain or the VPS's free sub-domain from the client area.

How do I log in the first time?

On first access, Databasus offers to create an account: the first account created is the administrator. Later sign-ups stay open by default with a plain member role, so turn off external registrations in the settings once your account exists.

Where are the backups stored?

Wherever you choose: on the VPS disk, or off-site — S3, Cloudflare R2, Google Drive, SFTP, Rclone. For real protection, send at least one copy off the VPS: a backup kept on the same machine disappears with it.

How do I know a backup can be restored?

Turn on restore verification: after each backup or on a schedule, Databasus actually restores the backup into a temporary database, compares the resulting size and lists every table with its row count. The report can be sent to you as a notification.

Spin up a data platform quickly.

Databasus

Databasus — scheduled, encrypted PostgreSQL, MySQL and MongoDB backups, verified by a real restore.

1 GB minimum RAM 1 vCPU Port 4005 In validation

In validation

Automatic installation for this solution is ready and currently going through our tests on a real server. Ordering will open as soon as validation is complete.

Tech stack

DockerGoPostgreSQL

Minimum RAM1 GB minimum

Minimum CPU1 vCPU

Default port4005

Compatible OSChoice of Linux distributions

Databasus is an open-source (Apache-2.0) database backup tool focused on PostgreSQL. You declare a database, a schedule and a destination — the VPS disk, S3, Cloudflare R2, Google Drive, SFTP… — and Databasus takes the backups, applies retention and alerts you on failure by email, Telegram, Slack or webhook.

For PostgreSQL it goes beyond a dump: full and incremental physical backups, plus WAL streaming for point-in-time recovery (PITR). MySQL, MariaDB and MongoDB are covered with logical backups. Above all, Databasus checks its own backups by actually restoring them and comparing the result: you know a backup restores before you need it.

Key features

Full PostgreSQL coverage — full and incremental physical backups, WAL streaming and point-in-time recovery (PITR).

MySQL, MariaDB and MongoDB — compressed logical backups from the same interface.

Verified restores — Databasus actually restores the backup and produces a table-by-table report.

Many destinations — local disk, S3, Cloudflare R2, Google Drive, SFTP, Rclone and more.

AES-256-GCM encryption — backup files stay unreadable even on shared storage.

Retention and alerts — duration, count, GFS, size caps; email, Telegram, Slack or webhook notifications.

When to use this solution?

1

Protect your application's production database

Schedule a daily backup of your SaaS's PostgreSQL database to an S3 bucket, with WAL streaming so you can roll back to the minute before a bad migration.

2

Centralise backups across several servers

Declare the databases of your various VPS and clients in separate workspaces, each with its own destinations, alerts and access rights.

3

Prove that restores work

Schedule a weekly verification: Databasus restores the latest backup, counts the rows of every table and sends you the report — enough to answer an audit without a manual drill.

Deploy Databasus on your VPS

Guide optimized for ServOrbit Cloud VPS.

01

Create the VPS

Order an Ubuntu 24.04 VPS with at least 1 GB of RAM, and plan disk space if you keep backups locally. No domain name is needed: Databasus opens through an SSH tunnel, and you can attach a domain later from the client area.

02

Install Databasus from the Marketplace

In your client area, select Databasus and click Install. The script deploys the container, which initialises its internal database on first start; the port is published on the VPS loopback only.

03

Log in for the first time

Open an SSH tunnel from your machine — ssh -L 4005:127.0.0.1:4005 root@<vps-ip> (replace 4005 with the port shown in the client area if it differs) — then go to http://localhost:4005. Create your account: the first account created becomes the administrator. Then turn off external registrations in the settings.

04

Add a database and its destination

Declare the database to back up (host, port, read-only user, password), then a storage destination. For a database installed on the same VPS, use host.docker.internal as the host and make sure the database server accepts connections from the Docker network.

05

Schedule, then verify

Pick the frequency and retention, run a first backup by hand, then enable restore verification and a failure notification. A backup that has never been restored is only an assumption.

Frequently asked questions

PostgreSQL with physical backups (full, incremental, WAL streaming for point-in-time recovery) and logical backups; MySQL, MariaDB and MongoDB with logical backups. One instance handles several databases across several servers.

No. Databasus publishes its interface on the VPS loopback: open an SSH tunnel (ssh -L 4005:127.0.0.1:4005 root@<vps-ip>) then http://localhost:4005. If you prefer permanent HTTPS access, attach a domain or the VPS's free sub-domain from the client area.

Complementary solutions

Databases

Databasus isn't orderable yet.