Portabase/portabase

Portabase - Database backup & restore tool for PostgreSQL, MySQL/MariaDB, MongoDB, SQLite (more engines coming soon 🚀)

Summary

Portabase is a self-hosted, Apache-2.0 licensed tool for backing up and restoring a wide range of database engines, packaged as a web dashboard paired with a separate Rust-based agent. Written primarily in TypeScript on Next.js, it consolidates backup workflows for PostgreSQL, MySQL, MariaDB, MongoDB, SQLite, Redis, Valkey, Firebird, MSSQL, and Docker volumes behind one interface. The repository is not archived and is actively maintained.

What it is useful for

Most database engines ship their own backup utilities, which makes consistent scheduling, retention, and off-host storage hard to standardize across a mixed stack. Portabase addresses this by providing one dashboard that talks to agents deployed near the data. The README's compatibility table lists stable support for PostgreSQL 12 through 18, MySQL 5.7 through 9, MariaDB 10 and 11, MongoDB 4 through 8, SQLite 3.x, Redis 2.8+, Valkey 7.2+, Firebird 3.0 through 5.0, MSSQL 2017/2019/2022 plus Azure SQL, and Docker Engine 20.10+ volumes. Restore is supported for every engine except Redis and Valkey, so engineers depending on those two should plan a separate recovery path. Practical scenarios include nightly snapshots of a homelab or small production cluster, scheduled protection of Docker volumes attached to application containers, and one-off restores after migrations or accidental drops.

How engineers can use it

The README requires Docker as a prerequisite, then lists five install paths: an automated CLI (recommended), docker run, Docker Compose, Unraid Community Apps, and a Helm chart for Kubernetes, plus a development setup. The exact commands and YAML snippets are not included in the README itself; each path is documented on the project's documentation site. A typical flow is to run the Portabase dashboard container, deploy a Portabase agent on each host that owns a target database, register the agent through the UI, then add database or volume sources and configure schedules. Authentication uses BetterAuth, persistence is handled with Drizzle, and the UI is built with shadcn/ui on Next.js, so engineers extending the dashboard can work in a familiar TypeScript stack. For concrete install commands, Helm values, and agent registration steps, follow the setup page referenced in the README.