Scheduled database backups
Create hourly, daily, weekly, monthly, or cron-based backup jobs from a browser UI instead of hand-rolled scripts.
Self-Hosted Databasus
Your own database backup control panel, running on your server.
Databasus is an open-source, self-hosted backup tool focused on PostgreSQL, with support for schedules, storage destinations, notifications, and restore verification. On Kumo2 you can deploy Databasus in one click with the official Docker image, persistent storage, and direct access on port 4005.
7-day money-back guarantee
Features
Restore verification
Check that backups can actually be restored, so your recovery plan is tested before an incident.
Storage and notifications
Send backups to local or cloud storage and notify your team when jobs succeed, fail, or need attention.
Official Docker deployment
Kumo starts databasus/databasus:latest with Docker Compose, exposes port 4005, and keeps Databasus data in a persistent databasus-data directory.
What you can do with it
- Give side projects and production apps a visible backup schedule instead of scattered shell scripts.
- Centralize backup jobs for PostgreSQL-focused stacks while keeping the control plane on your VM.
- Pair local backup storage with S3-compatible destinations, alerts, and restore verification.
System requirements
CPU
1 vCPU
Memory
1 GB
Storage
20 GB
Runtime
Docker Compose
Port
4005
Recommended sizes
Starter Backups
1 vCPU / 1 GB RAM / 20 GB SSD
Personal projects, homelab databases, and light scheduled backups with Databasus on one server.
Databasus Recommended
Default2 vCPU / 2 GB RAM / 40 GB SSD
A stronger default for regular backups, restore checks, notifications, and modest local backup storage.
Team Backups
2 vCPU / 4 GB RAM / 60 GB SSD
More memory and disk headroom for several databases, cloud storage sync, and longer retention.
Recovery Workspace
4 vCPU / 8 GB RAM / 120 GB SSD
For heavier backup schedules, restore verification work, larger archives, and busy teams.
Resources & documentation
How deployment works
- 1
Pick a plan and a region close to you.
- 2
Choose how you'll sign in and confirm your order.
- 3
Kumo provisions a Linux server and starts the app with Docker — ready in minutes.
Frequently asked questions
What is self-hosted Databasus?
It is Databasus running on a cloud server in your Kumo account. You control the VM, Docker Compose stack, network endpoint, backup configuration, and stored data.
How do I access it after deployment?
Open http://SERVER_IP:4005 in your browser, then create your first backup job. The deployment output shows the exact endpoint.
What does Kumo deploy?
Kumo starts the official databasus/databasus:latest Docker image with Docker Compose, publishes port 4005, and persists Databasus data in ./databasus-data mounted at /databasus-data.
What size should I choose?
Start with Databasus Recommended for regular use. Choose Team Backups or Recovery Workspace when you expect larger backup archives, more databases, or frequent restore verification.
Can I use my own domain and HTTPS?
Yes. Point your domain to the server IP and place Databasus behind your own reverse proxy. The upstream docs also show a Caddy setup for automatic HTTPS.
Ready to deploy your own Databasus?
Spin it up on a server you control. We handle provisioning and Docker — you keep the keys.
Deploy Databasus7-day money-back guarantee
Not happy within 7 days of deploying? Get a full refund — just ask.