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.

Five servers, five cron jobs, five restic scripts nobody quite remembers writing: Arkeep replaces that archaeology with one dashboard where every backup in your infrastructure reports for duty. A small agent on each machine dials out to the central server and waits for work, so nothing listens on an agent port and machines behind NAT or a home firewall enroll just as easily as cloud VPSes. From the web interface you define destinations, which can be local disk, any S3-compatible storage, SFTP, a restic REST server, or more than forty Rclone backends, then build policies that send one backup job to several destinations at once for a genuine 3-2-1 layout. Docker volumes are discovered automatically, and databases stream straight into the backup with pg_dump and mysqldump instead of fragile file copies. Retention and repository integrity checks run per destination on their own schedules. When recovery day comes, you open any snapshot in the browser, browse its files, and restore a single folder in place or somewhere new. Failures announce themselves by email, Slack, Discord, or webhook, or stay silent in Healthchecks.io. Sign-in is yours to choose: local accounts with TOTP two-factor, or single sign-on through any OIDC provider. 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.

Replace fragile cron scripts and complex terminal commands with Zerobyte, a self-hosted web control center that schedules, monitors, and restores encrypted backups across any cloud or local storage infrastructure. System administrators can connect local drives, NFS shares, SMB exports, WebDAV mounts, and SFTP endpoints as backup sources with custom inclusion and exclusion rules. The visual interface lets you dispatch incremental, client-side encrypted snapshots to local directories, Amazon S3, Google Cloud Storage, Azure Blob, and forty cloud storage providers supported via rclone. You can schedule automated jobs using cron expressions, configure custom retention windows to automatically prune obsolete archives, and run repository health checks directly from the browser. Interactive file trees allow operators to inspect historical snapshot contents, download specific documents, or restore entire directory structures to their original locations in a single click. Configurable pre-backup and post-backup HTTP webhooks help pause databases before snapshots, execute dump commands, and alert teams through Discord, Slack, Telegram, or ntfy notifications. Multi-repository mirroring duplicates critical backups to secondary cloud providers for disaster recovery. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. AGPL-3.0 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.

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.

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.

Centralizing BorgBackup usually means hand-creating Unix users, wiring SSH keys, and remembering which machine stopped backing up three weeks ago; BorgWarehouse replaces that terminal work with a dashboard built for exactly this job. Add a repository and it provisions the dedicated user, authorized key, and storage quota for you, then hands back ready-to-paste client commands so a new machine is backing up in minutes. Every repository carries a freshness threshold: when no modification lands within the window you set, its status dot turns red and an alert goes out by SMTP email, through Apprise to Discord, Telegram, Slack, Gotify, or ntfy, or as a signed webhook POST to tools like n8n and Uptime Kuma, rate-limited to one alert per repository per day. Append-only mode is enforced on the server, so even a fully compromised client can add archives but never destroy existing ones, which is the property that keeps ransomware from eating your backup history. The monitoring view tracks storage consumption against each quota, a setup wizard walks new clients through onboarding (with a LAN variant for local transfers), and sign-in can delegate to GitHub, Google, Microsoft, GitLab, or any OIDC provider. A versioned REST API automates provisioning, and your passphrase never reaches the server: backups stay end-to-end encrypted on the clients. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. AGPL-3.0 licensed.

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.

Deploying container updates without blind surprises is what Drydock delivers through a monitor-first inspection plane that evaluates image registries, scans CVE vulnerabilities, and automates rollbacks across distributed Docker infrastructure. Systems engineers track container fleets across twenty-three public and private registries including Docker Hub, GitHub Container Registry, Harbor, and Quay using cursor-based pagination and semver classification. The integrated Update Bouncer runs Trivy and Grype static scanners against incoming candidate layers, blocking deployments that fail configurable CVE severity policies while verifying cryptographic signatures through cosign. Operators configure declarative update schedules with stabilization countdown gates that hold back brand-new releases until defined burn-in periods elapse. When updates execute, Drydock creates pre-upgrade container snapshots and evaluates post-launch container health checks, instantly restoring previous image digests and network configs if failures occur. Distributed Portwing edge agents stream live container output and system logs over encrypted WebSockets, allowing central consoles to coordinate remote daemon updates without opening inbound host firewall ports. Automated event triggers dispatch granular notifications and update payloads across seventeen communication channels including Slack, Discord, Telegram, and Home Assistant MQTT brokers. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. AGPL-3.0 licensed.

Komodo puts every server, container, and deployment pipeline behind a single dashboard where you build, ship, and monitor Docker workloads across unlimited hosts. Lightweight stateless agents install on each connected server and report CPU, memory, and disk metrics back to the Rust-powered core, giving you real-time visibility without heavyweight monitoring stacks. Docker Compose stacks deploy directly from the UI or link to Git repositories with webhook-triggered automatic redeploys on push. A built-in CI pipeline compiles versioned Docker images from source, with optional AWS spot instances for burst build capacity. For orchestration at scale, Docker Swarm management handles node configuration, service deployment, and multi-node stack orchestration from the same control plane. Browser terminal sessions open persistent named shells on servers and inside containers, complete with shared team access and scriptable Actions that chain executions into multi-stage procedures. Infrastructure-as-code support defines all resources declaratively in TOML files within a Git repository, keeping production state version-controlled and auditable. Granular role-based access control with user groups, per-resource permissions, and OAuth through GitHub and Google keeps teams operating within defined boundaries. A full OpenAPI specification, dedicated CLI, and typesafe client libraries for Rust and TypeScript make programmatic integration straightforward. With 12,000+ stars and active development, the community continues expanding multi-architecture builds and Swarm tooling.

With over 7,500 GitHub stars and 1 million Docker pulls — making it the most popular open-source database backup tool on GitHub ahead of pgBackRest and WAL-G — Databasus delivers production-grade backup management through a designer-polished web interface that replaces complex configuration files and CLI-only workflows. The platform supports PostgreSQL 14-18, MySQL 5.7-8, MariaDB 10-12, and MongoDB 4.2-8 with logical backups via pg_dump and mysqldump, while PostgreSQL 17+ enables physical backups using the native pg_basebackup engine with block-level incremental support via pg_basebackup --incremental and continuous WAL streaming via pg_receivewal for Point-in-Time Recovery to any second between backups. Storage destinations include local disk, AWS S3, CloudFlare R2, Google Drive, Azure Blob Storage, SFTP, NAS, and rclone-backed targets, while built-in AES-256-GCM encryption secures both backup files and stored credentials. Restore verification runs automated recovery into throwaway Docker containers, validating backups by comparing schema counts, table structure, and row counts against the source database — proving recoverability rather than merely checking checksums. The notification system integrates with Slack, Discord, Telegram, email, and webhooks for real-time backup status alerts. Deployment options span a single Docker container, Docker Compose with Caddy for automatic HTTPS, Helm charts for Kubernetes clusters, or a one-line install script. SSH tunnel support reaches databases in closed networks through bastion hosts without public exposure. 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.