Analytics cookies only (Google Analytics, PostHog). No ad networks, no cross-site tracking. See our privacy policy.
A configuration-driven wrapper around BorgBackup: one YAML file lists the source directories, the Borg repositories (local or over SSH), the retention policy, consistency checks, database dumps and hooks, and borgmatic runs create, prune, compact and check in order. The docker-borgmatic image adds Borg, Apprise notifications, an s6 supervisor and a cron schedule (daily at 01:00 by default), so the container itself is the scheduler. There is no web interface; you drive it from the config file and `docker exec`.
Runs on a VPS from $4/mo (Kamatera 1GB, 1 GB RAM) · prices checked Nov 2026
Fits home hardware (5 MB measured idle, RAM only): Raspberry Pi 4 (4 GB) (arm64 install tested), Raspberry Pi 5 (8 GB) (arm64 install tested), Repurposed laptop (8 GB), Intel N100 mini PC (16 GB), AMD Ryzen mini PC (32 GB).
Pick borgmatic when you want backups defined in a text file rather than clicked together: one YAML config lists the source directories, the BorgBackup repositories, the retention policy, consistency checks, database dumps and hooks, and borgmatic runs create, prune, compact and check in the right order. The docker-borgmatic image (GPL-3.0; BorgBackup itself is BSD-licensed) bundles Borg, borgmatic, Apprise notifications and a cron scheduler that runs daily at 01:00 unless you set `CRON`. Our snippet pins `ghcr.io/borgmatic-collective/borgmatic:2.2.0`, released 2026-10-30 with borgmatic 2.2.0 and Borg 1.4.5, generates the repository passphrase into `.env`, creates a local encrypted repository with `borgmatic repo-create`, and runs one backup of a sample directory. The README publishes no RAM minimum, so our 256 MB floor is an estimate. It has no web interface at all, which separates it from the catalog's Backrest, Zerobyte, Duplicati and UrBackup; against restic and Kopia, it uses Borg's repository format, which backs up over SSH to a Borg server and cannot talk to S3-style buckets directly.
Paid link — we earn a commission if you shop through it.
Run these commands on your server:
# borgmatic (docker-borgmatic) — scheduled Borg backups, no web UI — pinned to 2.2.0 (borgmatic 2.2.0 + Borg 1.4.5); adapted from the README quick start with a local repository
mkdir -p sample-data borgmatic.d borg-repository
echo 'hello from SelfHost Atlas' > sample-data/hello.txt
echo "BORG_PASSPHRASE=$(openssl rand -hex 24)" > .env
cat > borgmatic.d/config.yaml <<'EOF'
source_directories:
- /mnt/source
repositories:
- path: /mnt/borg-repository
label: local
archive_name_format: 'atlas-{now:%Y-%m-%d-%H%M%S}'
keep_daily: 7
keep_weekly: 4
EOF
cat > docker-compose.yml <<'EOF'
services:
borgmatic:
image: ghcr.io/borgmatic-collective/borgmatic:2.2.0
container_name: borgmatic
hostname: borgmatic
restart: unless-stopped
stop_grace_period: 10m
environment:
- TZ=UTC
- BORG_PASSPHRASE=${BORG_PASSPHRASE}
volumes:
- ./sample-data:/mnt/source:ro
- ./borg-repository:/mnt/borg-repository
- ./borgmatic.d:/etc/borgmatic.d
- ./state/borg-config:/root/.config/borg
- ./state/borg-cache:/root/.cache/borg
- ./state/borgmatic:/root/.local/state/borgmatic
EOF
docker compose up -d
timeout 300 bash -c 'until docker compose exec -T borgmatic borgmatic --version; do sleep 3; done'
docker compose exec -T borgmatic borg --version
docker compose exec -T borgmatic borgmatic repo-create --encryption repokey-blake2
docker compose exec -T borgmatic borgmatic create --stats
docker compose exec -T borgmatic borgmatic list
# → no web UI: the container now runs this backup daily at 01:00. Keep .env (the repository passphrase) somewhere safe and export the key with `borgmatic key export`; swap /mnt/source for the directories you want to protectThe docker-borgmatic README flags these before you rely on it:
borgmatic used 5 MB of RAM at idle on GCP e2-standard-2 · Ubuntu 26.04 LTS · Docker 29.9.3 (first boot, measured Nov 2026). We list a minimum of 256 MB.
The borgmatic install snippet is marked verified on Ubuntu 26.04 (Nov 2026).