Self-hosting Databasus the easy way
Yulei ChenDatabasus is a free, open-source tool for backing up PostgreSQL, MySQL, and MongoDB databases. Instead of juggling cron jobs, shell scripts, and cloud CLI tools, you get a clean web UI to schedule and manage all your database backups in one place.
Sliplane is a managed container platform that makes self-hosting painless. With one-click deployment, you can get Databasus up and running in minutes - no server setup, no reverse proxy config, no infrastructure to maintain.
Prerequisites
Before deploying, ensure you have a Sliplane account (free trial available).
Quick start
Sliplane provides one-click deployment with presets.
Deploy Databasus >- Click the deploy button above
- Select a project
- Select a server (If you just signed up you get a 48-hour free trial server)
- Click Deploy!
About the preset
The one-click deploy above uses Sliplane's Databasus preset. Here is what it includes:
- Official
databasus/databasusDocker image - Specific version tag for stability
- Persistent storage mounted to
/databasus-dataso your backup configs and history survive restarts - Health check configured at
/api/v1/system/healthfor automatic restart on failure - Port 4005 exposed for the web UI
Next steps
Once Databasus is running on Sliplane, access it using the domain Sliplane provided (e.g. databasus-xxxx.sliplane.app).
Adding database connections
After opening the UI, you can add your first database connection. Databasus supports PostgreSQL, MySQL, and MongoDB. If your database runs on the same Sliplane server, use the internal service name as the host (e.g. postgres.internal). For external databases, use the public connection string.
Backup storage
By default, backups are stored in the /databasus-data volume. This volume is persistent, so your backups survive container restarts and redeployments. For offsite storage, you can configure S3-compatible destinations directly in the Databasus UI.
Environment variables
You can customize Databasus behavior through environment variables in Sliplane's service settings:
| Variable | Description |
|---|---|
PORT | Port the web UI listens on (default: 4005) |
HOST | Bind address (default: 0.0.0.0) |
Logging
Databasus logs to STDOUT by default, which integrates directly with Sliplane's built-in log viewer. For general Docker logging tips, check out our post on how to use Docker logs.
Cost comparison
You can also self-host Databasus with other cloud providers. Here is a pricing comparison for the most common ones:
| Provider | vCPU | RAM | Disk | Monthly Cost | Note |
|---|---|---|---|---|---|
| Sliplane | 2 | 2 GB | 40 GB | €9 (~$10.65) | Flat rate, 1 TB bandwidth, SSL included |
| Fly.io | 2 | 2 GB | 40 GB | ~$18 | Disk and bandwidth billed separately |
| Render | 1 | 2 GB | 40 GB | ~$35 | 100 GB bandwidth, Disk billed separately |
| Railway | 2 | 2 GB | 40 GB | ~$67 + $20 plan | Pro plan floor, usage-based, bandwidth billed separately |
Click here to see how these numbers were calculated.
(Assuming an always-on instance running 730 hrs/month)
- Sliplane: flat €9/month for the Base server. Unlimited services on the same server, 1 TB egress and SSL included.
- Fly.io:
shared-cpu-2x2 GB = $11.83/mo + 40 GB volume × $0.15/GB = $6 -> ~$17.83/mo. Egress billed separately ($0.02/GB in EU). - Render: closest match is Standard ($25, 1 vCPU / 2 GB) plus 40 GB disk × $0.25/GB = $10 -> ~$35/mo. Stepping up to Pro (2 vCPU / 4 GB) costs $85/mo + disk.
- Railway (Pro plan): CPU 2 × $0.00000772/s × 2,628,000 s = $40.57; RAM 2 × $0.00000386/s × 2,628,000 s = $20.29; volume 40 × $0.00000006/s × 2,628,000 s = $6.31 -> ~$67/mo compute, plus the $20/mo Pro plan floor and $0.05/GB egress.
Bandwidth costs can add up fast on usage-based providers. Use our bandwidth cost comparison tool to see what your egress would cost on each platform.
FAQ
What databases does Databasus support?
Databasus supports PostgreSQL, MySQL, and MongoDB. You can connect to any instance that is reachable from your Sliplane server, whether it runs on the same server, a different provider, or a managed database service.
Can I store backups in S3?
Yes. Databasus supports S3-compatible storage destinations. You can configure your S3 bucket, endpoint, and credentials directly in the web UI. This works with AWS S3, Hetzner Object Storage, MinIO, and other S3-compatible providers. If you are looking for affordable options, check out our 5 cheap object storage providers comparison.
How do I update Databasus?
Change the image tag in your Sliplane service settings to the newer version and redeploy. Check Docker Hub for the latest stable version.
Are there alternatives to Databasus?
Yes. Duplicati is a popular general-purpose backup tool that supports scheduled, encrypted backups. For database-specific needs, you can also use native dump tools like pg_dump, mysqldump, or mongodump combined with cron jobs. Check out our guides on backing up Postgres, MySQL, and MongoDB via SSH tunnel.
Can I back up databases running on other servers?
Yes. As long as your database accepts remote connections, Databasus can connect to it. Use the public hostname or IP of your database server along with the correct port and credentials. For databases behind a firewall, you can set up an SSH tunnel to establish a secure connection.
