• 3 posts
  • 2 comments
Joined 8 months ago
Cake day: March 17th, 2026

Hi everyone,

It’s been a while since I last posted here! I’m happy to announce that we’ve released Portabase 1.34!

Repository: https://github.com/Portabase/portabase (on the road to 2k stars)

For those unfamiliar with Portabase, it’s an open-source, self-hostable backup and restore platform designed for data retention, disaster recovery, and homogeneous migrations.

Until now, Portabase supported 10 data sources (including PostgreSQL, MySQL, MariaDB, MongoDB and Docker volumes).

With v1.34, we’re introducing our 11th data source: files and directories!

There are 3 ways to back up your files:

  • Archive (logical backup): creates a full .tar.gz of the selected directory.
  • Snapshot (incremental): uses Restic under the hood to provide incremental backups with deduplication, reducing storage usage.
  • Sync: synchronize files and directories to a destination. This is a direct copy, not a restorable backup.

What’s new in 1.34?

  • Support for file and directory backup/restore (obviously)
  • UX improvements and UI fixes
  • Multiple security fixes, thanks to users who reported vulnerabilities
  • DACPAC support for Microsoft SQL Server (in addition to BACPAC, and native BACKUP DATABASE support is also on the way)
  • Helm chart improvements

Important: If you’re upgrading and want to use the new file and directory backup features, make sure to update your agents as well.

As always, if you encounter a bug, please open an issue on GitHub. And if you like the project, consider giving us a star! It means a lot to us and helps the project gain visibility.

Thanks to everyone using, testing, contributing to, and supporting Portabase!

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!

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.