# Portabase/portabase

Portabase - Database backup & restore tool for PostgreSQL, MySQL, MsSQL, MariaDB, Firebird SQL, SQLite, MongoDB, Redis and Docker Volume

Repository: https://github.com/Portabase/portabase
Canonical: https://ross.abutalabs.com/products/portabase
Homepage: https://portabase.io
Language: TypeScript
License: Apache-2.0
License Family: permissive
Topics: backup, postgresql, selfhosted, docker, nextjs, backup-tool, devops, mysql, mariadb, database, mongodb, sqlite-database, redis, valkey, firebirdsql, mssql-database, docker-backup, docker-volumes
Last push: 2026-08-24T11:09:55+00:00

## Health v2 (maintenance only)
Score: 85/100 (v2, computed 2026-09-03T02:39:23.370411+00:00)
- activity 99, release rhythm 87, longevity 48
- inputs: {"age_days": 683, "days_push": 9, "days_rel": 9, "gap_med": 1.0, "n_releases_24m": 129}
- flags: none
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 1666, forks 103 (observed 2026-08-28T04:05:19.596979+00:00)

## What it is
Portabase is an open-source, self-hosted dashboard and agent system for automating database backups and restores across PostgreSQL, MySQL, MariaDB, MongoDB, Redis/Valkey, SQLite, Firebird, MSSQL, and Docker volumes. A central Next.js control plane manages agents deployed near the databases, with multi-backend storage (including S3), notifications, scheduling, and RBAC/OIDC authentication.

## Use cases
- automate nightly backups of postgres and mysql databases
- restore a corrupted mongodb database from a backup
- centralize database backups across multiple self-hosted servers
- back up docker volumes on a homelab server
- replace hand-written bash backup scripts with a dashboard
- send alerts when a database backup fails
- store database backups in my own S3-compatible storage
- manage team access to backup configuration with RBAC

## When to choose
- you want a self-hosted, open-source control plane for multi-database backups
- you need agents that pull-based connect to a central server without opening inbound ports
- you want unified backup/restore across relational, document, and key-value databases
- you prefer your own storage backends and full data sovereignty

## When to avoid
- you only need a simple single-database cron dump without a dashboard
- you need managed cloud backup with vendor support
- you require restore support for Redis/Valkey, which is not yet available
- you need a lightweight CLI-only tool with no web interface

## Facets
- artifact type: application
- maturity: active
- function: backup, scheduling, monitoring, alerting, auth, authorization, self-hosted, developer-tools
- domain: databases, self-hosted
- platform: windows, self-hosted
- tags: database-backup, restore, agent-based, s3-storage, rbac, oidc, nextjs, helm-chart, docker-volumes, devops, backup, automation, linux, macos, docker, kubernetes, web-server

## Member repositories
- Portabase/portabase (main) score 85

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:05:19.596979+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-30T03:42:57.202931+00:00, confidence not recorded.
  - readme: https://github.com/Portabase/portabase (fetched 2026-08-28T04:05:19.596979+00:00, sha a9921b185adc)
  - homepage: https://portabase.io (fetched 2026-08-29T11:16:45.040263+00:00, sha fd29a46bd4f9)
  - site_page: https://portabase.io/docs/dashboard/installation/setup (fetched 2026-08-29T11:16:45.046823+00:00, sha 021f1318e548)
  - site_page: https://portabase.io/docs (fetched 2026-08-29T11:16:45.044230+00:00, sha e7852f3afd26)
- Data as of 2026-08-30T08:39:29.467469+00:00.