KillianLarcher

DISCLAIMER: All the code was written by humans until December 2025. Since then, we have started using AI as an assistant, mainly to speed up debugging and for low-value-added tasks (UI and some simple logic). However, all code is reviewed by a human, and the architecture is designed exclusively by humans.

Hi everyone,

We’ve just released Portabase 1.29, with another round of improvements focused on configuration, reliability and reducing the amount of manual setup required.

Repo: https://github.com/Portabase/portabase

Quick recap if you’re new to Portabase

Portabase is an open-source, self-hosted backup and restore platform designed for data retention, disaster recovery and homogeneous database migrations. It uses a central dashboard with lightweight agents deployed close to your databases and workloads.

We currently support 9 database engines (PostgreSQL, MySQL, MariaDB, MongoDB, SQLite, Redis, Valkey, Firebird SQL and Microsoft SQL Server) as well as Docker volume backups.

What’s new

You can now add new databases directly from the dashboard! Until now, databases were only declared through the agent's configuration file (databases.json). Both approaches can be used depending on how you prefer to manage your infrastructure.

Portabase now checks whether backup files are actually still available in the configured storage. If a file has been deleted, moved, or is otherwise unavailable, it is now marked as unavailable instead of being presented as a valid restore candidate.

The new version of the agent (v1.19) adds support for MongoDB SRV connections, making it easier to connect to MongoDB deployments using mongodb+srv://, including managed/cloud MongoDB environments.

What’s next

We’re now working on several areas:

• Deploying a public Portabase demo
• Improving and restructuring the documentation
• Enhancing the agent retry and resilience system
• Additional dashboard UX/UI improvements
• A database-specific options system, allowing advanced parameters to be configured for each supported engine
• Audit logs across the ecosystem for better traceability

As usual, feedback is welcome. If you find bugs, have trouble with the new dashboard-based configuration, or need database-specific options we don’t support yet, feel free to open an issue on GitHub.

Thanks!

Hi everyone,

I'm happy to share that Portabase now supports Docker volume backup and restore!

Portabase is an open-source, self-hosted backup and restore platform, currently supporting 9 databases including PostgreSQL, MariaDB, MongoDB, Redis, and more.

We’re now expanding it to cover Docker volumes too, because many self-hosted apps do not store critical data only in databases.

Typical use cases include WordPress uploads, Nextcloud user files, media libraries, app configuration data, and more generally any self-hosted service where critical data lives in Docker volumes.

The goal is still the same: make backup and restore simple, reliable, and easy to operate. Portabase uses a central server with lightweight agents running close to your workloads.

If you find bugs, please open an issue on GitHub, we’re actively looking for feedback.

Thanks!

Hi everyone,

I’m one of the maintainers of Portabase. I already shared the project here recently, but we have a major update: REST API is now available!

Repository: https://github.com/Portabase/portabase

This is still a first version and it will be extended over the coming weeks.

Since this was requested by the community, the goal is to make Portabase easier to integrate into automation workflows, CI pipelines, n8n scenarios, and other external tools.

Swagger with OpenAPI documentation is also available: https://portabase.io/docs/dashboard/api/introduction

This should make it easier to explore the available endpoints and start testing.

Quick recap for those who do not know the project yet: Portabase is an open-source platform for database backup and restore, built on an agent-based architecture with one central server and lightweight agents deployed next to your databases.

We now support 9 databases:

• PostgreSQL
• MariaDB and MySQL
• SQLite
• MongoDB
• Redis and Valkey
• Firebird SQL
• Microsoft SQL Server

As always, feedback is very welcome. Feel free to open an issue if you find a bug or have suggestions.

Hello all!

I’m one of the maintainers of Portabase, I share about it on Lemmy one month ago (https://lemmy.world/post/45042565) and I have some updates!

Repository: https://github.com/Portabase/portabase

Database homogenous migration is now built-in!

Previously, migrating meant:

• Download backup from the source DB
• Upload & restore it into the target DB

Now: no download, no upload, everything happens directly through the GUI.

It works with all supported databases, and migrations can be done within the same organization.

We also added support for Microsoft SQL Server! It still needs broader community testing to help identify bugs or edge cases we may have missed.

Quick recap : Portabase is an open-source platform for database backup and restore.

We now support 9 databases:

• PostgreSQL
• MariaDB and MySQL
• SQLite
• MongoDB
• Redis and Valkey
• Firebird SQL
• Microsoft SQL Server

What’s new since version 1.10:

• Healthchecks for both the database and the agent (with optional notifications)
• Homogeneous database migration
• Support for Microsoft SQL Server

If you’re using Microsoft SQL Server (or any other supported database), we’d really appreciate your feedback. Feel free to open issues if you find any bugs.

Hi community,

I’m one of the maintainers of Portabase, I shared it here for the first time two weeks ago and I have now some updates!

After an initial request from a community user in mid-January, and a few more along the way, we’ve finally added support for Firebird SQL. It seems to have a solid community behind it even though I hadn’t heard of it before.

Quick recap : Portabase is an open-source platform for database backup and restore.

Repository: https://github.com/Portabase/portabase

So it now we support 8 databases: PostgreSQL, MariaDB, MySQL, SQLite, MongoDB, Redis, Valkey and Firebird SQL

What’s new in version 1.10:

• Support for Firebird SQL (obviously)
• Healthchecks for both the database and the agent (with optional notifications)
• End-to-end tests to prevent regressions (coverage is still light, but we’re working on it)

What’s coming next:

• Support for Microsoft SQL Server

If you’re using Firebird SQL (or any other supported database), we’d really appreciate your feedback. Feel free to open issues if you find any bugs.

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?