Comparison

How does Borg Backup Server
compare to alternatives?

There are several open-source tools built around BorgBackup. Each takes a different approach — here's how Borg Backup Server compares to Vorta, BorgWarehouse, and Borg-UI.

At a glance

Four tools, four different approaches to BorgBackup management.

Borg Backup Server Borg Backup Server

Agent-based web platform for managing BorgBackup across unlimited servers. Agents pull work over HTTPS, push backups over append-only SSH. Supports Linux, macOS, and Windows clients.

Multi-Server Agent-Based Web UI Cross-Platform
Vorta

Desktop GUI for BorgBackup on macOS, Linux, and Windows. Manages backups for a single machine with a native system tray application.

Single Machine Desktop App
BorgWarehouse

Web UI for managing Borg repositories on a single server. Focuses on repo provisioning and monitoring — not scheduling or restoring.

Repo Management Web UI
Borg-UI

Web interface for running BorgBackup against SSH hosts. The server SSHs into each machine to execute borg commands remotely.

SSH Push Web UI

Feature-by-feature comparison

How each tool handles the key requirements of backup infrastructure management.

Feature
BBS
Vorta
BorgWarehouse
Borg-UI
Architecture
Multi-server management
Repos only
Architecture model
Agent pull
Local only
Server-side
SSH push
Works behind NAT/firewall
No SSH to managed machines
N/A
Client platforms
Linux, Mac, Win
Mac, Linux
Linux
Linux
Backup Features
Scheduled backups
Database backup plugins
MySQL, PostgreSQL
Pre/post backup hooks
Retention policies
File-level restore via web UI
Desktop
S3 offsite sync
AWS, Wasabi, etc.
Remote storage hosts (SSH)
BorgBase, Hetzner, rsync.net, any SSH host
Security
Append-only SSH
Auto-configured
Manual
RBAC (role-based access)
N/A
Two-factor authentication
TOTP
N/A
Credential encryption
AES-256-GCM
OS keychain
No client credentials on server
N/A
Stores SSH keys
Operations
Centralized dashboard
Email & webhook notifications
Desktop only
Remote agent updates
N/A
Borg binary management
Technical
Built with
PHP + Python
Python (Qt)
Next.js
Python (Flask)
License
MIT
GPL-3.0
MIT
MIT

Borg Backup Server vs. Vorta

Vorta is a great desktop GUI for managing BorgBackup on a single machine. It's ideal for personal laptops and workstations, with a clean native interface and system tray integration.

Single machine vs. fleet management

Vorta runs on one computer and manages backups for that computer only. BBS manages backups across all your servers from a single dashboard.

No database backups

Vorta backs up files and directories. BBS has native plugins for MySQL and PostgreSQL that handle dump, backup, and cleanup automatically.

Different use cases

Vorta is the right choice for personal desktop backups. BBS is built for managing backup infrastructure across servers, VMs, and containers.

Borg Backup Server vs. BorgWarehouse

BorgWarehouse is a web interface for managing Borg repositories on a single server. It handles repo provisioning and SSH key management, but doesn't schedule backups or perform restores.

Repo management vs. full backup platform

BorgWarehouse manages repositories (create, delete, monitor disk usage). BBS does that plus scheduling, executing backups, retention, file restore, database plugins, S3 sync, and more.

No scheduling or restore

BorgWarehouse doesn't schedule or run backups — clients must set up their own cron jobs. There's no file browsing or restore capability. BBS handles all of this from the web UI.

No RBAC or 2FA

BorgWarehouse has a single admin login with no multi-user support, no role-based permissions, and no two-factor authentication.

Borg Backup Server vs. Borg-UI

Borg-UI is a web-based tool that SSHs into your machines to run borg commands remotely. It's the closest alternative to BBS in terms of scope, but uses a fundamentally different — and riskier — architecture.

Server stores SSH keys to all managed machines

Borg-UI requires SSH access to every managed server and stores the private keys in its database. Compromising the Borg-UI server gives an attacker SSH access to your entire infrastructure.

SSH host key verification disabled

Borg-UI uses StrictHostKeyChecking=no for SSH connections, making it vulnerable to man-in-the-middle attacks. BBS never SSHs into client machines at all.

Doesn't work behind NAT or firewalls

Borg-UI needs direct SSH access to each machine, which means opening inbound ports or setting up tunnels. BBS agents initiate outbound HTTPS connections, working naturally behind any NAT or firewall.

No database backups, S3 sync, or restore

Borg-UI handles file backups but has no database plugins, no S3 offsite replication, and no file-level restore from the web UI. BBS provides all of these out of the box.

Why choose Borg Backup Server?

Zero-trust architecture

The server never SSHs into your machines and holds no client credentials. Agents pull work over HTTPS and push backups over append-only SSH.

Complete backup platform

Scheduling, execution, retention, file restore, database plugins, S3 sync, email alerts, and remote storage — all managed from one web interface.

Works everywhere

Agents work behind NAT, firewalls, and across cloud providers. No inbound ports, no tunnels, no VPN required.

Enterprise-grade security

Multi-user RBAC with 2FA, AES-256-GCM credential encryption, append-only repos, rate limiting, and OWASP-compliant web security.

See it for yourself

Spin up a live demo to explore every feature. Full access, no credit card, no install required.

Try Live Demo View on GitHub