Borgmatic vs Vorta: Which BorgBackup Frontend?

BorgBackup started as a fork of Attic in 2015 and quickly became one of the most trusted deduplication-based backup tools in the Linux ecosystem. But Borg’s CLI is powerful, not friendly — which spawned two frontends with completely different philosophies: Borgmatic for server automation and Vorta for desktop convenience.

Quick Verdict

If you’re backing up servers or Docker hosts, Borgmatic is the right tool — it runs headlessly via cron or systemd, handles database dumps natively, and integrates with monitoring services. If you’re backing up a Linux or macOS desktop and want to click through configuration instead of writing YAML, Vorta provides a visual interface for the same BorgBackup engine underneath.

Overview

Borgmatic is a server-side automation wrapper for BorgBackup. You define your backup configuration in YAML — source directories, repositories, retention policies, database dumps, monitoring hooks — and Borgmatic handles the orchestration. It runs via cron, systemd timers, or Docker, and requires zero interaction after initial setup. Version 2.1.2 is the current release (February 2026).

Vorta is a desktop GUI application for BorgBackup. It provides a graphical interface for creating backup profiles, browsing archives, restoring files, and scheduling backups — all through a native desktop application on Linux and macOS. Version 0.11.3 is the current release (January 2026).

Feature Comparison

Feature	Borgmatic	Vorta
Interface	YAML config + CLI	Desktop GUI (Qt)
Deployment	Server (Docker, systemd, cron)	Desktop app (Linux, macOS)
Scheduling	Cron/systemd timers	Built-in scheduler (GUI)
Database backups	PostgreSQL, MySQL, MariaDB, MongoDB, SQLite	No (filesystem only)
Multiple repositories	Yes (in YAML config)	Yes (profile-based)
Archive browsing	CLI (borgmatic list, borgmatic info)	Visual archive browser
File restore	CLI (borgmatic extract)	GUI point-and-click restore
Monitoring hooks	Healthchecks, PagerDuty, Uptime Kuma, ntfy, Cronitor	None
Filesystem snapshots	Btrfs, LVM, ZFS integration	No
Pre/post scripts	Yes (preparation and cleanup hooks)	Limited
Docker support	Official community image	No (desktop-only)
Headless operation	Yes (designed for it)	No (requires display)
Configuration format	YAML	GUI preferences
License	GPL v3	GPL v3

Installation

Borgmatic runs in Docker or installs via pip/package manager on any Linux server:

# Borgmatic in Docker
services:
  borgmatic:
    image: ghcr.io/borgmatic-collective/borgmatic:2.1.2
    volumes:
      - /etc/borgmatic:/etc/borgmatic:ro    # YAML config
      - /root/.ssh:/root/.ssh:ro            # SSH keys for remote repos
      - borg-cache:/root/.cache/borg        # Dedup cache
      - /srv:/srv:ro                        # Data to back up
      - /var/lib/docker/volumes:/docker-volumes:ro  # Docker volumes
    environment:
      - TZ=UTC
      - CRON_SCHEDULE=0 3 * * *             # Run at 3 AM daily
    restart: unless-stopped

volumes:
  borg-cache:

Vorta installs as a desktop application:

# Ubuntu/Debian
sudo apt install vorta

# macOS (Homebrew)
brew install vorta

# Flatpak
flatpak install flathub com.borgbase.Vorta

Setup Step	Borgmatic	Vorta
Install	Docker pull or pip install	apt/brew/flatpak
Configure sources	Edit YAML file	Click through GUI
Set schedule	Cron expression or systemd timer	GUI toggle
First backup	Runs at next scheduled time	Click “Start Backup”
Time to first backup	10–15 min (YAML setup)	5 min (GUI walkthrough)

Performance and Resource Usage

Both tools are thin wrappers — actual backup performance depends entirely on BorgBackup itself. Neither adds meaningful overhead to the deduplication, compression, or encryption operations.

Resource	Borgmatic	Vorta
RAM (idle)	0 MB (runs on schedule, exits)	~80–120 MB (Qt GUI resident)
RAM (during backup)	200–800 MB (BorgBackup, scales with dataset)	200–800 MB (same BorgBackup engine)
CPU	Same as Borg	Same as Borg
Disk (application)	~10 MB	~50 MB
Runs without display	Yes	No (requires X11/Wayland or macOS)

Community and Support

Borgmatic has an active community centered around its documentation site (torsion.org/borgmatic) and GitHub. The project is the de facto standard for automated Borg backups on servers, frequently recommended in r/selfhosted and r/homelab.

Vorta is developed by the BorgBase team (a commercial Borg hosting provider) and has a growing community of desktop users. It’s the most polished GUI for BorgBackup on any platform, though its user base is smaller than Borgmatic’s server-focused audience.

Use Cases

Choose Borgmatic If…

• You’re backing up servers, NAS devices, or Docker hosts
• You need database-aware backups (PostgreSQL, MySQL, MongoDB dumps included automatically)
• You want headless, unattended operation via cron or systemd
• You need monitoring integration (Healthchecks.io, Uptime Kuma, ntfy alerts on failure)
• You want to run backups in a Docker container alongside your other services
• You manage multiple servers with similar backup configurations (reuse YAML templates)

Choose Vorta If…

• You’re backing up a Linux or macOS desktop/laptop
• You prefer GUI configuration over editing YAML files
• You want to visually browse and restore files from backup archives
• You’re new to BorgBackup and want a guided setup experience
• You back up to BorgBase (Vorta integrates natively with BorgBase’s commercial hosting)

Final Verdict

If you’re backing up a server or any headless system, Borgmatic is the right tool. Its YAML configuration, database dump integration, monitoring hooks, and Docker support make it purpose-built for server infrastructure. Once configured, it runs silently and alerts you only when something fails.

If you’re backing up a desktop machine and prefer clicking over YAML editing, Vorta wraps the same BorgBackup engine in a clean Qt interface. It’s particularly well-suited for users new to Borg who want to understand what’s happening before automating everything.

They’re not competitors — they’re the same backup engine with different interfaces for different deployment contexts.

Frequently Asked Questions

Can I use both Borgmatic and Vorta?

Yes. Use Borgmatic on your servers and Vorta on your desktops. Both write to standard BorgBackup repositories, so you can even back up to the same remote repository (separate paths) and manage everything from one place.

Does Borgmatic have a web UI?

No. Borgmatic is CLI/YAML only. For a web-based backup management UI, look at Kopia or Duplicati.

Can Vorta back up Docker volumes?

Technically yes — you can add any directory as a source — but Vorta runs as a desktop app with user-level permissions. Server-side backups of Docker volumes are better handled by Borgmatic running as root in its own container.

Related

• How to Self-Host BorgBackup with Borgmatic
• Best Self-Hosted Backup Solutions
• Duplicacy vs Kopia
• Duplicacy vs Restic
• Backup Strategy: The 3-2-1 Rule
• Docker Compose Basics