Every connection starts at the endpoint, never at the server, so Borg Backup Server can back up Linux, Mac, and Windows machines behind NAT and firewalls without opening a single inbound port. A lightweight agent on each machine polls for tasks over HTTPS, pushes deduplicated archives over SSH, and reports live progress. Append-only SSH access means an endpoint can add and restore archives but never prune or delete them. The dashboard shows backup charts, server stats, and active jobs at a glance. Plans run from hourly to monthly, several per client, built from reusable directory templates for common server roles, with per-plan retention from hourly to yearly. Lost a file? Browse the archive tree in your browser, tick what you need, and restore it to the client or download a .tar.gz. MySQL and PostgreSQL dumps run before each backup and restore as a copy or a replacement. Repositories can live on the server, on BorgBase, Hetzner, or rsync.net, and mirror to S3-compatible storage such as AWS, Wasabi, or Backblaze B2. Apprise alerts reach more than 100 services, and a nightly report lands in your inbox. Two-factor login and role-based access guard the console. Upgrades roll out to the server and every agent together, and the server backs itself up daily. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

Encrypted, incremental, compressed backups on storage you already have - Amazon S3, Backblaze B2, Google Drive, Azure, OneDrive, Dropbox, MEGA, Storj, WebDAV, SFTP, FTP, SMB, or a plain local disk - is what the MIT-licensed Duplicati has quietly done for years. Its security model is Trust No One: every block is encrypted with AES-256 (or a local GPG instance) before leaving the machine, and the passphrase never travels, so the storage provider holds only ciphertext. The block-based storage engine gives the best of both backup worlds: after one initial full backup, only changed data blocks upload - modify a tiny part of a huge file and only that part transfers - yet every backup version restores like a full backup in a single operation, with no incremental chains to replay. Deduplication and compression keep remote storage growth slow even across years of versions. A web interface manages everything: the built-in scheduler keeps backups current automatically, flexible filters select folders, file types, or custom patterns, retention policies prune old versions, and an integrated updater flags new releases. On compatible object-lock backends, immutable (WORM) storage protects backup data from ransomware that reaches the credentials. Runs on Windows, macOS, and Linux, free even for commercial use.

Borg UI is a self-hosted web management interface for BorgBackup that eliminates complex command-line syntax by organizing deduplicated backups, automated pruning schedules, and interactive file restorations into an intuitive graphical control center. System administrators connect local drives, remote SSH hosts, and SFTP endpoints to establish resilient storage repositories guarded by client-side encryption and cryptographic authentication. The centralized dashboard visualizes storage capacity, compression ratios, deduplication savings, and the health status of active backup jobs in real time. Configurable backup plans schedule automated cron jobs with granular retention rules, executing pre-backup database dumps and filesystem snapshots before running incremental syncs and background integrity checks. Users browse multi-version archive filesystems directly from the web browser, searching file trees and extracting individual files or entire folders without manual command line extraction. The platform orchestrates remote fleet backups by deploying SSH keys across client machines, tracking connection health, and executing non-disruptive background operations. Comprehensive alert routing dispatches real-time job status notifications, failure warnings, and storage alerts across Discord, Telegram, Slack, and email using integrated multi-channel messaging services. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. GNU AGPLv3 licensed.

Engineers who have outgrown Duplicati or rsync scripts tend to appreciate Kopia's design: encrypted, compressed, content-deduplicated snapshots in Go, stored in a repository on any storage you control - S3, Google Cloud Storage, Azure Blob, Backblaze B2, SFTP, WebDAV, or a plain filesystem. Encryption is mandatory and end-to-end: every block is encrypted client-side with AES-256-GCM or ChaCha20-Poly1305 using keys derived from your repository password, and even file names never leave the machine in plaintext. Blocks are packed into 20-40 MB blobs with random names, so the storage provider learns nothing about content or structure. Deduplication is automatic and content-based - identical data across files, snapshots, and even multiple machines backing up to the same repository is stored once. Policies govern everything per-directory: compression choice, retention (hourly through annual), scheduling, and ignore rules. Incremental snapshots are point-in-time records you can mount and browse like a filesystem. This deployment runs the Kopia repository server with its web UI, centralizing backups from multiple client machines over an authenticated API - each client connects with the server URL and certificate fingerprint, and users only see their own snapshots. Error correction, high-latency-tolerant caching, and both CLI and GUI round it out.

Backrest turns the command-line restic backup engine into a visual, browser-managed disaster recovery platform that schedules encrypted snapshots, orchestrates repository maintenance, and restores individual files from a unified web dashboard. Import existing restic repositories or initialize new encrypted backup stores across Amazon S3, Backblaze B2, Google Cloud Storage, Azure Blob Storage, SFTP servers, local directories, and any storage provider supported by rclone. Define granular backup plans with directory inclusion lists, glob exclusion rules, and flexible schedules driven by cron expressions, hourly intervals, or last-run-time clocks that prevent missed backups after server downtime. Automated retention policies handle snapshot forgetting, repository pruning, and cryptographic integrity checks in the background without manual intervention. When a file is accidentally deleted or corrupted, open the interactive snapshot tree browser to inspect historical directory structures and download or restore specific files directly to disk. Pre-backup and post-backup shell command hooks let administrators dump databases or pause containers before snapshots start, while configurable alerts dispatch status reports to Discord, Slack, Gotify, Healthchecks, and Shoutrrr endpoints whenever an operation succeeds or fails. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. GPL-3.0 licensed.

On a schedule you choose, Pluton backs up your folders to cloud storage and other disks, then lets you verify and restore every snapshot and see exactly what happened in a clean, self-hosted web dashboard. Three copies: every plan writes to a primary storage and can replicate to up to two more, so the 3-2-1 rule is a toggle in the plan wizard rather than a weekend project. Two kinds of media: pair a local disk or mounted drive with Backblaze B2, Cloudflare R2, Google Drive, Dropbox, pCloud, SFTP, S3-compatible buckets, or any of 70+ connectors, and press Verify to test a connection before trusting it. One place to look: the plan page charts file counts and sizes over a selectable range, a health strip colors recent runs, and a live panel counts files, bytes, and time remaining while each mirror initializes and replicates. Zero mysteries: every backup keeps a timestamped event timeline from dry run to pruning, and plan logs filter by level and task, search messages, and download as a file. Schedules run from every few minutes to monthly, including chosen weekdays; retention keeps daily, weekly, and monthly snapshots; and scripts can run before or after a job. Alerts reach you by email, Slack, Discord, or ntfy, and optional two-factor sign-in guards the dashboard. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache-2.0 licensed.