Hi community,
I’m one of the maintainers of Portabase, and this is my first time sharing about it on Lemmy.
Portabase is an open-source platform for database backup and restore.
It’s designed to be simple, reliable, and lightweight, without exposing your databases to public networks. It works via a central server and edge agents (like Portainer), making it perfect for self-hosted or edge environments.
It currently supports 7 databases:
PostgreSQL, MariaDB, MySQL, SQLite, MongoDB, Redis and Valkey
Repository: https://github.com/Portabase/portabase
(we hit 500 stars recently!)
Key features:
- Logical backups for PostgreSQL, MySQL, MariaDB, MongoDB, SQLite, Redis, Valkey
- Multiple storage backends: local filesystem, S3, Cloudflare R2, Google Drive
- Notifications via Discord, Telegram, Slack, webhooks, etc.
- Cron-based scheduling with flexible retention strategies
- Agent-based architecture for secure, edge-friendly deployments
- Ready-to-use Docker Compose setup and Helm Chart
What’s coming next:
- Increasing test coverage
- Extending database support
I’d love to hear from you: which database would you like to see supported next in Portabase?
Hi,
The agent need to be on the same network as your database. You can either include the agent in the same Docker Compose setup or create a Docker network to link them. I’m not sure what you mean by ‘persist across restarts.’ Can you clarify? However, it works perfectly fine with databases running in Docker.
For Redis and Valkey, hot restores are unfortunately not supported. You need to stop the services and perform some manual operations. This limitation is why backups are mainly useful for disaster recovery rather than live rollback.
Feel free to ask any other questions or clarification if needed.