Self-Hosted Borg Backup Web Dashboards: BorgWeb vs Vorta Server vs BorgWare Guide 2026

BorgBackup is the gold standard for deduplicating backup in the self-hosted community. Its compression and deduplication efficiency are unmatched. But Borg’s native interface is command-line only — you run borg create, borg list, borg check in a terminal. For teams, monitoring backup health, or just preferring a visual interface, web dashboards transform Borg from a sysadmin tool into a managed backup platform.

Why Use a Web Dashboard for Borg?

Borg’s CLI is powerful but presents real operational challenges. There’s no at-a-glance view of backup status across multiple repositories. Non-technical team members can’t verify backups or trigger restores. There’s no built-in notification when a backup fails or repository needs maintenance. And tracking backups across multiple machines requires custom scripting.

A web dashboard solves all of these. You get visual backup status, email and Slack notifications, user-friendly restore interfaces, and centralized management — all while Borg does the heavy lifting underneath.

Comparison: BorgWeb vs Vorta Server vs BorgWare

BorgWeb: The Lightweight Repository Browser

BorgWeb is the official read-only web interface from the BorgBackup project itself. It provides a clean, fast interface for browsing backup archives and checking repository health — nothing more, nothing less.

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14

version: "3.8"
services:
  borgweb:
    image: borgbackup/borgweb:latest
    container_name: borgweb
    volumes:
      - ./repos:/backups:ro
    environment:
      - BORGWEB_REPO_DIR=/backups
      - BORGWEB_BIND=0.0.0.0:5000
    ports:
      - "5000:5000"
    restart: unless-stopped
    read_only: true

 1
 2
 3
 4
 5
 6
 7
 8
 9
10

# Reverse proxy config for BorgWeb with auth
server {
    listen 443 ssl;
    server_name backups.example.com;
    location / {
        auth_basic "Borg Backup Dashboard";
        auth_basic_user_file /etc/nginx/.htpasswd;
        proxy_pass http://borgweb:5000;
    }
}

BorgWeb’s philosophy is “do one thing well.” It won’t schedule backups or send notifications, but it excels at letting you quickly verify that last night’s backup ran successfully and browse file trees in any archive. For teams that already have backup scheduling via cron or systemd timers, BorgWeb adds the missing visual layer.

Vorta Server: The Full Management Platform

Vorta is best known as a desktop GUI for Borg, but it also has a server component that provides web-based backup management. Vorta Server combines backup scheduling, repository management, and a restore interface into one package.

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23

version: "3.8"
services:
  vorta-server:
    image: borgbase/vorta-server:latest
    container_name: vorta-server
    volumes:
      - ./repos:/backups
      - ./vorta-data:/data
      - ./ssh:/root/.ssh:ro
    environment:
      - SECRET_KEY=generate-a-random-secret-key-here
      - DATABASE_URL=sqlite:////data/vorta.db
      - BACKUP_DIR=/backups
      - NOTIFICATION_EMAIL=admin@example.com
      - SMTP_HOST=smtp.example.com
    ports:
      - "8000:8000"
    restart: unless-stopped

  redis:
    image: redis:alpine
    container_name: vorta-redis
    restart: unless-stopped

Vorta Server is the most feature-complete option. It handles everything from scheduling nightly backups to email notifications on failure, to a point-and-click restore interface. It’s the closest thing to a “Borg-as-a-Service” experience you can self-host.

BorgWare: The Minimalist Web Frontend

BorgWare takes a middle-ground approach — more capable than BorgWeb but lighter than Vorta Server. It’s written in Go for fast startup and minimal resource usage, making it ideal for resource-constrained environments.

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11

version: "3.8"
services:
  borgware:
    image: ravimda/borgware:latest
    container_name: borgware
    volumes:
      - ./repos:/backups:ro
      - ./borgware-config.yaml:/etc/borgware/config.yaml:ro
    ports:
      - "3000:3000"
    restart: unless-stopped

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15

# borgware-config.yaml
repositories:
  - name: "Production DB Backups"
    path: "/backups/db"
    schedule: "0 2 * * *"
  - name: "Config Backups"
    path: "/backups/config"
    schedule: "0 3 * * sun"

notifications:
  email:
    smtp_host: "smtp.example.com"
    to: "admin@example.com"
  on_failure: true
  on_success: false

BorgWare’s strongest feature is its configuration-as-code approach. Rather than clicking through a UI to set up backup schedules, you define everything in a YAML file — perfect for infrastructure-as-code workflows and GitOps.

Deployment Architecture

A complete self-hosted Borg backup system with a web dashboard typically runs backup clients that create Borg archives into a repository on local storage, NFS, or S3-compatible object storage. The web dashboard reads the repository and presents a user-friendly interface through a reverse proxy like Nginx, Caddy, or HAProxy. Team members access the dashboard through their browsers with proper authentication.

The Borg repository can be on local storage, NFS, or S3-compatible object storage. The web dashboard reads the repository in read-only mode (or read-write for Vorta Server) and presents an interface through a reverse proxy.

Why Self-Host Your Backup Monitoring?

Self-hosted backup monitoring keeps your data sovereignty intact. Unlike cloud backup services where you pay per GB and have limited visibility into backup health, self-hosted Borg with a dashboard gives you full control over your backup data. No third party has access to your encryption keys. You get unlimited retention without per-GB-per-month charges. Borg’s deduplication can reduce storage by 90 percent or more for similar datasets, making self-hosted backup dramatically cheaper at scale than cloud alternatives.

For comparing Borg with other backup tools, see our Borg vs Restic vs Kopia guide. For backup integrity verification strategies, check our backup testing guide. And for backup repository server deployment patterns, see our backup server comparison.

Beyond basic backup operations, web dashboards transform Borg into a team-friendly platform. Non-technical stakeholders can verify backup status, initiate restores, and review backup history without touching a terminal. Automated notifications via email or webhooks ensure you know about backup failures immediately — not when you discover them during an outage. For organizations with compliance requirements, dashboards provide audit trails showing who accessed what data and when, satisfying regulatory requirements for data recoverability verification.

Security Best Practices for Backup Dashboards

Backup dashboards expose sensitive information about your infrastructure — file structures, backup schedules, and potentially database names and server hostnames. Treat them as production-critical services with appropriate security measures.

Always place your Borg dashboard behind a reverse proxy with TLS termination. Never expose it directly on the internet without HTTPS. Configure HTTP Strict Transport Security (HSTS) headers to prevent downgrade attacks. Use strong authentication — HTTP basic auth at minimum, preferably OAuth2 or SAML integration via Authelia or Authentik for team environments.

Restrict read-only access where possible. BorgWeb operates in read-only mode by default, which is the safest configuration for team members who only need to verify backup status. Reserve write access to Vorta Server or BorgWare for administrators who need to trigger restores or modify backup schedules.

Implement network-level restrictions using firewall rules or VPN requirements. Your backup dashboard should only be accessible from your internal network or through a VPN like WireGuard. If remote access is required, use a bastion host or Cloudflare Access to add an authentication layer before traffic reaches your dashboard.

Regularly audit dashboard access logs to detect unauthorized access attempts. Configure your reverse proxy to log all access and integrate with your centralized logging system. Set up alerts for unusual access patterns — multiple failed authentication attempts, access from unexpected IP ranges, or high-frequency browsing that could indicate data exfiltration attempts.

FAQ

Do I need to run Borg itself separately from the web dashboard?

Yes. All three tools act as frontends to an existing Borg repository. You still need Borg via borg create or borgmatic to actually perform backups. The dashboard provides visibility and management, not the backup engine itself.

Can I use these dashboards with remote Borg repositories?

Yes. BorgWeb and BorgWare can access repositories over SSH by mounting the remote filesystem. Vorta Server has built-in SSH support for connecting to remote Borg servers. Ensure the dashboard container has SSH access to the repository host.

Which dashboard should I choose for a small team?

BorgWeb if you just want to browse archives and verify backup health. Vorta Server if you need scheduling, notifications, and a restore interface. BorgWare if you prefer configuration-as-code and a lightweight Go binary.

Are these dashboards safe to expose to the internet?

Only with proper authentication. Always put your Borg dashboard behind a reverse proxy with authentication using HTTP basic auth, OAuth2, or Authelia and Authentik. Never expose it directly — even read-only access to backup metadata can reveal sensitive information about your infrastructure.

How do I monitor backup completion status?

Vorta Server has built-in email and webhook notifications. For BorgWeb and BorgWare, set up external monitoring — a simple cron job that runs borg check and sends the result to your monitoring system via Prometheus, Grafana, or a simple email alert.

Can BorgWeb handle encrypted repositories?

Yes, BorgWeb supports password-protected repositories. Provide the repository passphrase via environment variable BORG_PASSPHRASE so the web interface can decrypt archive metadata for browsing.

💰 想测试你的市场判断力？我用 Polymarket 做预测市场交易——这是全球最大的预测市场平台，从大选结果到加密货币监管，什么都可以押注。和赌博不同，这是真正的信息市场：你懂的信息越多，胜率越高。我靠预测科技事件的走向已经赚了不少。用我的邀请链接注册：Polymarket.com