portabase

Open source alternative to SimpleBackups, Veeam Backup & Replication, Druva Data Security Cloud, Rubrik Security Cloud and Cohesity DataProtect

1.9K stars
Apache-2.0
Active this week
Last commit 1 day ago

Last verified Oct 20, 2026

Automate database backups and restores for PostgreSQL, MySQL, MongoDB, SQLite, Redis, and Docker volumes, with scheduling and S3-compatible storage.

Visit website GitHub1.9K Deploy on Hostinger

Read the full breakdownWho it is for, how it works, trade-offs, the quick start and the FAQ

who it's for

Who portabase is for#

DevOps engineers managing multiple database engines

Portabase replaces per-engine backup scripts with a single dashboard covering PostgreSQL, MySQL, MongoDB, SQLite, and Docker volumes. You define schedules and retention policies once per database, connect your S3-compatible storage backend, and receive notifications when a job fails. The unified interface removes the context-switching cost of maintaining separate backup tooling for each engine.

Skip if:

If you run a single PostgreSQL instance and already use pg_dump with a tested cron job and restore runbook, the added complexity of a dedicated backup system may not be worth it. Portabase earns its setup cost when you are managing three or more engines simultaneously.

Homelab operators running self-hosted services

The Unraid Community Apps listing and single-command Docker install make Portabase practical for homelab environments. GFS retention policies and notifications are available without writing custom retention logic, and the non-profit governance model means the tool is not going to be acquired or moved behind a paywall.

Skip if:

If you only back up one or two simple databases and your storage is already handled by a NAS snapshot policy at the volume level, a lighter-weight cron plus rclone setup may be simpler to maintain long-term.

Platform teams adding database backups to deployment pipelines

The REST API and MCP server let platform teams trigger pre-deployment database snapshots programmatically. The RBAC model supports a separation between who can configure backup schedules and who can trigger on-demand restores, which matters in teams with dedicated DBA and platform engineering roles working in the same Portabase instance.

Skip if:

If your deployment pipeline already relies on cloud provider managed snapshots (RDS automated backups, Velero for Kubernetes PVCs) and those cover your recovery objectives, Portabase adds an application-layer backup on top, which may be redundant depending on your RTO and RPO targets.

Teams replacing SaaS database backup tools like SimpleBackups

Teams paying monthly subscription fees for SaaS database backup tools get the same scheduling, retention, and restore capabilities from Portabase at no licensing cost. Self-hosting moves backup data off a third-party system, addressing data residency concerns for regulated industries and teams with strict data sovereignty requirements.

Skip if:

If you prefer paying for managed infrastructure and have no data residency requirements, a SaaS tool remains the more convenient choice. Portabase requires a server to run on and ongoing maintenance as the project evolves.

the problem

The problem it solves#

Ad-hoc database backup workflows break under pressure. Bash scripts written for pg_dump get passed between team members, never tested for restore, and forgotten when the engineer who wrote them leaves. When corruption or accidental deletion hits, the team discovers the backup was either incomplete, stale, or unrestorable.

The cost of commercial database backup tools adds up fast for teams running multiple engines. Enterprise-grade products like Veeam or Cohesity are priced for large organizations with dedicated storage administrators, not for a DevOps team managing several database instances across a Kubernetes cluster. Simpler SaaS tools remove the infrastructure burden but introduce data access and vendor dependency concerns. Teams end up either overpaying for features they do not need or maintaining fragile custom tooling.

how portabase solves it

How it solves it#

Nine-Engine Database Coverage

Backs up and restores PostgreSQL (versions 12-18), MySQL (5.7, 8, 9), MariaDB (10 and 11), MongoDB (4-8), SQLite 3.x, Firebird (3.0-5.0), and MSSQL Server (2017, 2019, 2022, and Azure SQL). Redis and Valkey are supported for backup, though restore is not available for those two engines. Docker volume backups include full restore support with Docker Engine 20.10 or later.

GFS Retention Policies

Define retention rules per database using Grandfather-Father-Son (GFS) tiers: hourly, daily, weekly, monthly, and yearly snapshots. Also supports keep-last-N and keep-for-X-days strategies. Rules run automatically and prune old backups without manual intervention, keeping storage costs predictable across long-running instances.

Multi-Backend S3-Compatible Storage

Connect multiple storage backends simultaneously and choose where each database's backups are stored. Supports any S3-compatible provider, giving you flexibility to store sensitive backups on-premises while keeping archival snapshots in cloud object storage. Storage configuration is per-database, not a single global setting.

Secure-by-Design Agent Architecture

The central dashboard never initiates inbound connections to agents. Agents run alongside your databases on your infrastructure and push data outbound to storage. No ports need to be opened on your database servers, reducing the attack surface compared to centralized backup systems that pull data from a management plane.

Scheduling via Cron Syntax or Fixed Intervals

Schedule backups using standard cron syntax or fixed time intervals, configurable from the web interface without editing config files. Each database can have its own schedule, making it straightforward to run hourly PostgreSQL backups alongside daily MongoDB snapshots within the same Portabase instance.

REST API, MCP Server, and CLI

Portabase exposes a REST API and an MCP server for integration with CI/CD pipelines, infrastructure automation tools, and AI agents. The CLI lets you install agents, manage configurations, and trigger operations from the terminal. The CLI auto-updates when a new version is released, so your tooling stays current without manual maintenance.

strengths · trade-offs

Strengths and trade-offs#

Strengths

Apache-2.0 License with Non-Profit GovernancePortabase is Apache-2.0 licensed, permitting commercial use, modification, and distribution without licensing fees. The project is led by a non-profit organization and supported by the IONOS Cloud Partner Program. For teams concerned about vendor capture or pricing changes, the governance model provides stronger guarantees than VC-backed open core products where monetization pressure can shift the licensing terms.
Restore Is a First-Class OperationMost backup tools focus on the backup side and treat restore as an afterthought. Portabase supports on-demand restore for all supported engines except Redis and Valkey. The dashboard surfaces restore alongside backup scheduling, which matters when an incident requires fast rollback and the team cannot afford to piece together a manual restore procedure under pressure.
Quick Setup Across Multiple Deployment OptionsThe Portabase CLI installs the agent and dashboard via a single shell command, with the project reporting a setup time under two minutes. Deployment options include Docker Run, Docker Compose, Unraid Community Apps, and Kubernetes with Helm, covering the full range from a single-server homelab to a production Kubernetes cluster without requiring a different toolchain for each environment.
Notifications and Alerting by SeverityPortabase sends notifications when backup jobs fail or incidents occur, with configurable channels based on severity level. Teams can route critical failures to a paging channel and routine warnings to a lower-priority queue. This removes the need to manually monitor the backup dashboard and makes it practical to run Portabase as unattended infrastructure.

Trade-offs

-Redis and Valkey: Backup Only, No RestoreRedis and Valkey are supported for backup but not for restore through Portabase. If your disaster recovery plan requires rolling back a Redis or Valkey instance from a Portabase snapshot, you will need a separate restore path for those engines. This limitation is documented in the compatibility table in the official docs and should be factored into your backup strategy before adopting Portabase for those engines.
-Relatively New ProjectPortabase was created in October 2024 and has accumulated 1,668 GitHub stars with 35 open issues as of mid-2026. Development is active (last push August 2026) and the community is growing, but it has not been through the years of production hardening that older backup tools have. Teams with strict reliability requirements should evaluate the open issue backlog and test the restore path thoroughly before relying on it for critical workloads.
-Docker Required for All Standard Install PathsAll documented install paths (CLI, Docker Run, Docker Compose, Kubernetes with Helm) depend on Docker being available on the host. Portabase does not document a bare-metal install path without a container runtime. Teams running infrastructure without Docker support will need to work outside the documented setup paths.

versus alternatives

portabase vs alternatives#

Portabase vs Veeam Backup & Replication

Veeam Backup & Replication is the dominant enterprise backup tool for virtualized and physical infrastructure, covering full-system images and virtual machine snapshots. Portabase targets a narrower problem: backing up database instances and Docker volumes at the application layer.

Feature	Portabase	Veeam Backup & Replication
License	Apache-2.0 (free)	Proprietary
Self-hosting	Yes (Docker-based)	Yes (Windows-based server)
Database-native backup	9 engines with per-engine scheduling	Application-aware via agents
On-demand restore from UI	Yes	Yes
Pricing	Free	Per-socket or per-workload licensing

Portabase is the better fit for teams running Linux-based Docker environments with multiple database engines who need a purpose-built backup interface without Veeam licensing costs. Veeam remains the stronger choice for organizations that need full-system backup, VM-level recovery, or deep integration with VMware and Hyper-V: capabilities Portabase does not offer.

Portabase vs SimpleBackups

SimpleBackups is a SaaS database backup service that removes the need to manage a backup server, targeting developers and small teams. Portabase provides the same core workflow (scheduled backups to S3-compatible storage with retention policies) as a self-hosted tool under an open source license.

Feature	Portabase	SimpleBackups
License	Apache-2.0	Proprietary SaaS
Self-hosting	Yes	No
Data residency	Your own storage	SimpleBackups infrastructure
Pricing	Free (self-hosted)	Monthly subscription
Restore from dashboard	Yes	Yes

For teams with data residency requirements or who prefer not to pay a recurring subscription, Portabase is the direct open source alternative. SimpleBackups is the better choice when you want zero server maintenance and are comfortable with backup data transiting a third-party service.

Portabase vs Druva Data Security Cloud

Druva is an enterprise cloud data protection platform covering endpoints, SaaS applications, and cloud workloads, with compliance and legal hold capabilities. The two products serve different markets: Druva targets large organizations with audit, governance, and legal hold requirements, while Portabase targets DevOps and DBA teams managing database instances on self-hosted infrastructure.

Portabase is not a replacement for Druva in enterprise compliance contexts where cross-cloud data governance and legal hold are required. For self-hosted database backup and restore specifically, Portabase covers the use case without the enterprise contract and implementation overhead that Druva carries.

install · quick start

Quick start#

bash

Self-hosting installs the Portabase dashboard and agent using the CLI, which sets up a Docker-based instance in under two minutes.
```bash
curl -sL portabase.io/install | bash
portabase dashboard .
portabase agent .
```

tech stack · detected from GitHub

What it's built on#

Languages: JavaScriptTypeScript
Frameworks: Next.jsReact
Databases: MariaDBMongoDBMySQLPostgreSQL
Infrastructure: Docker
Cache: Redis

frequently asked

FAQ#

Which databases does Portabase support?

Portabase supports PostgreSQL (versions 12-18), MySQL (5.7, 8, 9), MariaDB (10 and 11), MongoDB (4-8), SQLite 3.x, Redis 2.8+, Valkey 7.2+, Firebird (3.0, 4.0, 5.0), MSSQL Server (2017, 2019, 2022, and Azure SQL), and Docker volumes (Docker Engine 20.10+). Redis and Valkey support backup operations only; restore is not available for those two engines. All other engines support both backup and restore.

Is Portabase free to use?

Yes. Portabase is Apache-2.0 licensed and free to run on your own infrastructure with no usage-based or seat-based fees. The project is led by a non-profit organization. There is no managed cloud version with paid tiers; you provide the server and storage backend. The only costs are the infrastructure you run it on and the storage you use for backups.

Do my databases need to be publicly accessible for Portabase to back them up?

No. Portabase uses a secure-by-design architecture where agents run alongside your databases on your infrastructure and initiate outbound connections to storage. The central dashboard never opens inbound connections to agents, so you do not need to expose your databases to the internet or open additional inbound ports on your infrastructure.

How do I install Portabase?

The fastest path is the CLI: run curl -sL portabase.io/install | bash to install it, then use portabase dashboard . and portabase agent . to start a local instance. Docker Run, Docker Compose, Unraid Community Apps, and a Kubernetes Helm chart install are also documented. Docker must be installed on your machine before starting any of these paths. The project reports a setup time under two minutes.

Can Portabase notify my team when a backup fails?

Yes. Portabase includes notifications and alerting with configurable channels based on severity levels. When a backup job fails or an incident occurs, the configured channels receive an alert. This removes the need to manually check the dashboard to confirm that scheduled backups completed, making it practical to run Portabase as unattended infrastructure.

also worth a look

Similar open-source tools#

Homeio

Alternative toUnraid

Browser desktop for your self-hosted home server

90 GitHub stars
Licence AGPL-3.0

Arrmada

Alternative toPlex

Movies, TV, books and requests in one app, arr stack included

396 GitHub stars
Licence MIT

Keda

Alternative toKedify

Event-driven Kubernetes autoscaling with 70+ scalers and scale to zero

10,646 GitHub stars
Licence Apache-2.0

Duckle

Alternative toFivetran

Self-hosted ETL on DuckDB with 385 connectors and no per-row billing.

1,517 GitHub stars
Licence Apache-2.0

rustfs

Alternative toAmazon S3

S3-compatible object storage built in Rust, Apache 2.0 licensed

35,244 GitHub stars
Licence Apache-2.0

seaweedfs

Alternative toAmazon S3

One cluster: S3 store, POSIX files, and Iceberg tables

35,636 GitHub stars
Licence Apache-2.0

by category

Run portabase on your own server

Self-host portabase on a Hostinger VPS.

Deploy on Hostinger

Featured

rakazo

Alternative toGrok Bot

AI teammates you own: your keys, your model, your machine.

4,904 GitHub stars
Licence Apache-2.0
#AI Agents

Inbox Zero

Alternative toSuperhuman

AI email assistant that drafts replies and clears your inbox

12,712 GitHub stars
Licence AGPL-3.0
#Email

Omnara

Alternative toClaude Managed Agents

Open-source agent deployment API. Self-host or use Omnara Cloud.

2,957 GitHub stars
Licence Apache-2.0
#AI Agents

Feature your project

The projects we add and every new guide. Free, unsubscribe any time.

Find open source alternatives to paid software

Portabase vs Veeam Backup & Replication

Feature	Portabase	Veeam Backup & Replication
License	Apache-2.0 (free)	Proprietary
Self-hosting	Yes (Docker-based)	Yes (Windows-based server)
Database-native backup	9 engines with per-engine scheduling	Application-aware via agents
On-demand restore from UI	Yes	Yes
Pricing	Free	Per-socket or per-workload licensing

Portabase vs SimpleBackups

Feature	Portabase	SimpleBackups
License	Apache-2.0	Proprietary SaaS
Self-hosting	Yes	No
Data residency	Your own storage	SimpleBackups infrastructure
Pricing	Free (self-hosted)	Monthly subscription
Restore from dashboard	Yes	Yes

Who portabase is for#

DevOps engineers managing multiple database engines

Skip if:

Homelab operators running self-hosted services

Skip if:

Platform teams adding database backups to deployment pipelines

Skip if:

Teams replacing SaaS database backup tools like SimpleBackups

Skip if:

The problem it solves#

How it solves it#

Nine-Engine Database Coverage

GFS Retention Policies

Multi-Backend S3-Compatible Storage

Secure-by-Design Agent Architecture

Scheduling via Cron Syntax or Fixed Intervals

REST API, MCP Server, and CLI

Strengths and trade-offs#

Strengths

Trade-offs

portabase vs alternatives#

Portabase vs Veeam Backup & Replication

Portabase vs SimpleBackups

Portabase vs Druva Data Security Cloud

Quick start#

What it's built on#

FAQ#

Similar open-source tools#

Open source tools in these categories#

Databases & Storage

DevOps & CI/CD

IT Management

Find open source alternatives to paid software

Who portabase is for#

DevOps engineers managing multiple database engines

Skip if:

Homelab operators running self-hosted services

Skip if:

Platform teams adding database backups to deployment pipelines

Skip if:

Teams replacing SaaS database backup tools like SimpleBackups

Skip if:

The problem it solves#

How it solves it#

Nine-Engine Database Coverage

GFS Retention Policies

Multi-Backend S3-Compatible Storage

Secure-by-Design Agent Architecture

Scheduling via Cron Syntax or Fixed Intervals

REST API, MCP Server, and CLI

Strengths and trade-offs#

Strengths

Trade-offs

portabase vs alternatives#

Portabase vs Veeam Backup & Replication

Portabase vs SimpleBackups

Portabase vs Druva Data Security Cloud

Quick start#

What it's built on#

FAQ#

Similar open-source tools#

Open source tools in these categories#

Databases & Storage

DevOps & CI/CD

IT Management

Find open source alternatives to paid software