Portabase: A self-hosted tool for database backup & restore

Published: (February 24, 2026 at 08:43 AM EST)
4 min read
Source: Dev.to

Source: Dev.to

Cover image for Portabase: A self‑hosted tool for database backup & restore

Portabase profile image Portabase author avatar

Backups are one of those things everyone knows they should have, but few enjoy setting up. Between security concerns, network complexity, and tools that assume way too much expertise, database backups often end up ignored until something breaks.

Portabase is a backup‑and‑restore tool for databases, currently supporting PostgreSQL, MySQL, MariaDB and MongoDB (Redis coming soon).

Portabase features a secure‑by‑design architecture, using a central server and lightweight agents that enable deployment at the edge and operation across multiple networks. Don’t worry—you never need to expose your database to the internet!

These agents handle everything: they back up your data, encrypt it, and send it to your preferred storage locations—all without requiring any technical skills. You can manage everything from the web interface.

In a hurry? Use the CLI or the ready‑to‑go Docker Compose setup provided in the documentation.

How does Portabase work?

Portabase’s ecosystem is built around three primary components:

Central server (management plane)

  • Provides a user‑friendly interface that serves as the central control plane for all backup and restoration operations.
  • Users can register and manage agents, configure backup policies, and review historical backups.
  • The dashboard shows storage usage, retention compliance, and lets teams manage multiple databases and agents from a single location.

Agents (execution plane)

  • Lightweight connectors deployed on database hosts that perform the actual backup and restore operations.
  • Operate in outbound pull mode, eliminating the need to open inbound ports on protected infrastructure while maintaining secure communication with the central server.

CLI (assistant)

  • A command‑line utility that streamlines installation and configuration of both the dashboard and agents.
  • Automates environment setup, configuration generation, and operational commands.

Core Features & Capabilities

Portabase is cron‑based and supports three retention strategies that work well for logical backups:

  1. Fixed number of backups retained
  2. Time‑based retention (n days)
  3. GFS rotation (Grandfather‑Father‑Son)

Retention policies

These policies apply to logical backup artifacts and help enforce organizational data‑retention standards.

For organizational usage, Portabase implements workspace structures that let you manage access and segmentation of resources (databases, storage locations, and notifiers). This enforces permission boundaries for teams and projects within the same instance.

Highly modular with many integrations

The platform supports multiple storage backends, including:

  • Local file systems
  • Any S3‑compatible storage (AWS S3, CloudFlare R2, MinIO, RustFS, etc.)
  • Google Drive

Add storage channel

Portabase is designed for flexibility and scalability. You can link each database to multiple storage targets, enabling redundancy and resilience—backups stay safe even if one storage location fails.

Notification & alerting integrations

Portabase integrates with popular notification platforms such as Slack, Discord, and Telegram, allowing teams to stay informed about backup status in real time. Alerts can notify you of successful backups or failures, enabling proactive monitoring and faster response times.

Add notification channel

These integrations help ensure that critical backup operations are never overlooked and make it easy to embed Portabase into existing team workflows and communication channels.

Under the Hood

The central server is built with Next.js 16, leveraging server‑side rendering (SSR) and optimized client‑side hydration to deliver low‑latency interfaces. The backend uses PostgreSQL for reliable data storage, with Drizzle ORM managing database interactions, ensuring type‑safe queries, transactional integrity, and efficient schema migrations.

The agent, originally written in Python, has been fully refactored in Rust 🦀, taking advantage of Tokio’s asynchronous runtime for high‑throughput, non‑blocking operations. This rewrite:

  • Reduces the Docker image size by
  • Minimizes runtime errors
  • Guarantees reliable, concurrent backup and restore operations across multiple databases

Rust’s memory safety and performance guarantees make the agent well‑suited for production environments with high I/O demands.

If you find Portabase useful, don’t forget to give it a star on GitHub!

0 views
Back to Blog

Related posts

Read more »

DevOps and Vibe Coding: A Journey

Things to Do Map Your Application - Map your application on paper, in a spreadsheet, or using graphics/flowcharts. This is the first step. - Understanding the...

OpenAI just raised $110 billion. Wow

Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink. Hide child comments as we...