VolumeVault turns Docker volume backups into a routine you can prove: it schedules them, stores them off the box, and restores them into brand-new volumes so original data is never the test subject. A guided web dashboard discovers every Docker volume on the host and shows backup coverage per volume or per Compose and Swarm stack, including the size of the latest known backup, so gaps are visible before they matter. Each job runs on an hourly, daily, weekly or cron schedule with retention by days or archive count, include and exclude filters, and a choice of whether containers stop during the run. Archives land where you keep them: AWS S3, Cloudflare R2, any S3-compatible store, WebDAV, SFTP, Azure Blob, Dropbox, Google Drive or a local path, with credentials encrypted at rest. Restores download and verify the archive first, then unpack it into a new volume by default; overwriting the original demands an explicit confirmation. Several volumes can ride one grouped schedule that reports once for the whole set, and containers can volunteer themselves for backup through Docker labels. Small agent containers extend the same jobs to other Docker hosts, including encrypted cross-host restores into fresh volumes, while API tokens let scripts and dashboards drive everything the UI can. 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.

BackupX puts every server backup you are responsible for into one web console, so cron lines scattered across machines become scheduled, visible, and verifiable tasks. Files and directories from multiple sources, MySQL, PostgreSQL, SQLite, SQL Server, and SAP HANA databases all back up on cron schedules you can also build in a visual editor, with automatic retention by days or count cleaning up what expires. More than seventy destinations are reachable through rclone, from S3 and other object stores to Google Drive, WebDAV, FTP, SFTP, Azure Blob, Dropbox, and OneDrive, and storage targets show connection health and live capacity before a job ever fails against a full disk. A master and agent design lets remote servers poll outward only, even through proxies, private certificate authorities, or SSH bastions, so agents run tasks locally with no inbound connectivity to defend. Per-node bandwidth caps and concurrency limits keep a small node polite and a big node busy, each at its own pace. Success and failure notifications arrive by email, webhook, or Telegram, while Prometheus metrics, health probes, an SLA breach gauge, and a full audit log keep the platform observable, and signed audit webhooks forward events to SIEM or WORM storage for compliance records. 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.

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.

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.

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.

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.

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.

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.

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.

Created by the developer behind Uptime Kuma and carrying over 23,000 GitHub stars, Dockge brings the same clean, reactive design philosophy to Docker Compose stack management with a web interface that makes Portainer's compose handling feel like editing YAML in a terminal over SSH. The interactive editor provides syntax highlighting, inline validation, and a live preview of your compose.yaml files while keeping every stack stored as a standard file on disk in /opt/stacks by default, meaning you can seamlessly switch between the web UI and the docker compose CLI without lock-in or proprietary database formats. Real-time WebSocket updates stream pull progress, container start/stop transitions, and build output directly to the browser with no polling delays. The built-in web terminal opens a shell session inside any running container for quick debugging, while the docker-run-to-compose converter transforms single-container run commands into proper compose.yaml definitions with one click. Multi-agent support introduced in version 1.4.0 connects multiple Docker hosts to a single Dockge dashboard, enabling centralized management of stacks distributed across different servers. Image update detection shows which stacks have newer versions available, and one-click updates pull the latest images and recreate containers without manual intervention. The stack is a single Docker container running on Node.js with Socket.IO for reactivity and stores no external database. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

Portabase takes a zero-trust approach to database backups: lightweight Rust/Tokio agents deploy next to each database, encrypt dumps with AES-GCM before data ever leaves the host, and poll the Next.js control plane outbound every five seconds requiring zero inbound firewall rules. This architecture contains blast radius if the dashboard is compromised while supporting ten engines with stable backup and restore: PostgreSQL 12 through 18, MySQL 5.7 through 9, MariaDB 10 and 11, MongoDB 4 through 8, SQLite 3.x, Redis 2.8+, Valkey 7.2+, Firebird 3.0 through 5.0, Microsoft SQL Server 2017 through 2022 including Azure SQL, and Docker volumes on Engine 20.10+. Encrypted backups store on configurable backends including local filesystems, any S3-compatible provider (AWS, MinIO, RustFS), Google Cloud Storage, and Azure Blob Storage. Cron-based scheduling with Grandfather-Father-Son retention policies automates backup lifecycle management, while on-demand restore targets any compatible server for cross-environment recovery. The CLI installs agents with a single command and auto-updates when new versions ship. A RESTful API with MCP server integration enables automation from CI/CD pipelines and AI agent workflows. Developed by a non-profit under Apache-2.0. 1,270+ stars and 174 releases since October 2024. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console.

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.

Databasement puts scheduled backup and restore for nine database engines behind one polished web interface, deployed as a single Docker container on port 2226. The Laravel and Livewire backend uses native CLI tools for MySQL 5.6 through 9.x, PostgreSQL 12 through 18, MariaDB 10.x through 12.x, Microsoft SQL Server 2017 through Azure SQL, MongoDB 4.2 through 8.0, SQLite 3.x, Firebird 3.x through 5.x, Redis 2.8+, and Valkey 7.2+ with full restore support including cross-server recovery. SSH tunnel connectivity reaches databases behind firewalls via bastion servers with password or private key authentication, and remote agents handle isolated networks by connecting outbound over HTTPS without inbound ports. Scheduling supports arbitrary cron expressions with GFS grandfather-father-son retention alongside simple time-based cleanup. Storage spans local disk, S3-compatible services including AWS and MinIO, Azure Blob, Samba/SMB shares, and SFTP/FTP servers. Scheduled restores automate production-to-staging synchronization on recurring intervals. Failure notifications alert via Email, Slack, Discord, Telegram, Pushover, Gotify, and webhooks with detailed job logs. The REST API and built-in MCP server enable CI/CD pipeline integration and AI assistant access from Claude, Cursor, and VS Code Copilot. 1,700+ stars since November 2025. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

When a bad migration or disk failure strikes at 3 AM, DBackup guarantees that your PostgreSQL, MySQL, MariaDB, MongoDB, SQL Server, Redis, Valkey, SQLite, and Firebird databases, along with the application directories that belong to them, are encrypted, verified, and ready to restore in a few clicks. Connect directly over TCP or tunnel through SSH with zero agents installed on your target servers. Bundle database dumps and Docker volumes or remote SFTP directories into a single atomic job so your schema and uploaded assets always share the exact same recovery point. Every archive is compressed with Brotli or GZIP, sealed with AES-256-GCM encryption before leaving the host, and pushed simultaneously to up to 14 storage backends including Amazon S3, Cloudflare R2, Hetzner, Google Drive, Dropbox, OneDrive, SMB, and WebDAV. Reusable Grandfather-Father-Son retention policies prune daily, weekly, monthly, and yearly snapshots automatically. Need to inspect live tables or recover a single file? Use the built-in Database Explorer, remap a dump into a staging schema, or extract individual files over HTTP byte ranges without downloading the entire archive. Even if your backup server goes offline, the downloadable Recovery Kit decrypts standard SQL dumps and plain TAR archives using a standalone script. 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.

Automating PostgreSQL backup lifecycles across local volumes and S3-compatible object storage, PG Back Web gives database administrators and developers a self-hosted web console to schedule, encrypt, monitor, download, and restore database dumps without writing manual shell scripts. Instead of maintaining fragile crontab entries across individual database servers, you register PostgreSQL 13, 14, 15, 16, 17, or 18 instances in one dashboard and define recurring backup schedules with custom retention policies and timezone-aware timestamps. Each backup execution can target local directories or multiple S3 buckets across providers like AWS S3, MinIO, Backblaze B2, and Cloudflare R2, with built-in connection testing and presigned download links for rapid archive retrieval. To protect sensitive production records at rest and in transit, the platform applies PGP encryption to dump files while encrypting stored database connection strings and bucket credentials. Real-time execution logs record exact archive sizes, durations, and output streams, and the web interface lets operators trigger on-demand dumps, duplicate existing backup jobs, or run direct browser-based restorations when disaster recovery is required. Automated background health checks continuously verify connectivity to every registered PostgreSQL database and storage destination, firing configurable HTTP webhooks to Slack, Discord, or incident pipelines whenever a backup completes, fails, or changes health status. 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.

Alarik is a self-hosted S3-compatible object storage server that lets you store files, backups, media, and application data on your own hardware while keeping the S3 APIs your tools already expect. Create buckets, upload objects with multipart support for large files, and retrieve them again through core operations, range reads, presigned URLs, and bucket or object tagging. Versioning keeps earlier copies, delete markers, and listings under your control, while lifecycle rules expire old versions and clean up incomplete uploads automatically. The web console lets you drag and drop files or whole folders, search recursively across nested folders, edit metadata in place, preview individual versions, and share time limited public links. Administrators manage users, access keys, bucket policies, and public access blocks from the same console, with live charts for CPU, memory, traffic, and storage. Bucket webhooks send event notifications when objects change, and replication rules continuously copy data to remote S3 compatible targets, synchronously or asynchronously per rule. Clusters add erasure coded storage across nodes, read repair, bit rot scrubbing, and automatic rebalancing when nodes join, drain, or return. 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.