Backups that restore, with the service running.
MM BackItUp detects the services on your servers and backs up each one with everything it needs to start again: data with a consistent dump, configuration, volumes, container image and versions. Encrypted at the source and stored on your own storage.
# 1. Check the installer signature
minisign -V -P <key> -m SHA256SUMS
sha256sum -c --ignore-missing SHA256SUMS
# 2. Dashboard, storage and agent on this machine
sudo sh install.sh --completa \
--carpeta /srv/data
# 3. Open the dashboard
https://<host>:18443
What it does
Three parts. Backups travel encrypted from the agent to storage; the dashboard only sees metadata.
Agent
Static binary for Linux amd64 and arm64. Detects services (Docker Compose, systemd, databases) and folders, takes consistent dumps and encrypts with Restic before sending.
Storage
Restic REST repositories over HTTPS, isolated per agent and with quotas. It receives data already encrypted: without the agent's key it cannot read it.
Dashboard
Scheduling, inventory, alerts and restores. It stores metadata (what was backed up, when and how it went) and never carries or decrypts backups.
Editions
The same product, depending on where you want each part.
Complete
Dashboard, storage and agent on a single machine with a single command. For one server or to get started.
Ubuntu 24.04, amd64. How to install it
Self-hosted
For several servers. You install the Complete edition on the main server (dashboard and storage) and add the others from the dashboard with Add server: a one-line command with a single-use token that downloads the agent for its architecture, checks its signature and enrols it.
Agents on amd64 and arm64. How to add servers
SaaS
For MercaMoney users: we run the dashboard and the storage. You only paste the agent line. Backups are still encrypted on your server before they leave.
Not available yet.
Restore levels
Every detected service shows one of these three levels in the dashboard. None is promised beyond what has been tested.
Certified restore
An automatic end-to-end test backs it up, restores it onto an empty server and checks that it works with identical data, on amd64 and arm64. Only these can be restored as a service.
Files and configuration
Its data and configuration are backed up and restored as files. Starting the service is up to you.
Detected only
Listed in the inventory, but not backed up.
Services with certified restore
This list comes from the tests; it is never written by hand. Another variant of the same engine (a replica, a cluster or a replica set with authentication) is “Files and configuration” until it has its own test.
| Service | Certified variant | Test passed |
|---|---|---|
| Caddy on Docker Compose | not applicable | amd64: 2026-11-21 arm64: 2026-11-22 |
| MySQL on Docker Compose | primary | amd64: 2026-11-21 arm64: 2026-11-22 |
| Nginx on Docker Compose | not applicable | amd64: 2026-11-21 arm64: 2026-11-22 |
| PostgreSQL on Docker Compose | primary | amd64: 2026-11-21 arm64: 2026-11-22 |
| Redis on Docker Compose | primary | amd64: 2026-11-21 arm64: 2026-11-22 |
The monitor cannot always see the variant of PostgreSQL, MySQL or Redis. Until the first backup the dashboard shows “Certified restore (confirmed on the first backup)”; if that backup finds a replica, the service becomes “Files and configuration”.
Verifiable end to end
Encrypted at the source
Backups leave the server encrypted. Each agent's master key is kept in an envelope encrypted with your custody key: the dashboard stores it but cannot open it.
Signed packages
Every release is published with SHA-256 sums and a minisign signature. The installer and the “Add server” line stop if a signature does not match.
New target
Restores go to a new target and install what is missing (Docker and Compose in the backup's version). The original is never overwritten unless you confirm it.