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.

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.

Backed by 27,700+ GitHub stars and actively developed with the v0.9.x architectural overhaul introducing an event-driven plugin ecosystem, ArchiveBox delivers the open-source self-hosted web archiving platform that preserves websites, bookmarks, social posts, media, source code, and research material in durable formats before link rot, platform shutdowns, and censorship erase them permanently. Feed it URLs one at a time or schedule automated imports from browser history, RSS feeds, Pocket, Pinboard, Instapaper, Wallabag, Shaarli, JSON, CSV, HTML bookmark exports, and browser extension captures. Each snapshot stores redundant copies as original HTML, rendered single-file HTML via SingleFile, full-page PDF, screenshot PNG, WARC archive, article text via Readability, favicons, HTTP headers, media files via yt-dlp, git repository clones, and structured metadata in SQLite. The Docker Compose deployment bundles Chrome, wget, curl, yt-dlp, SingleFile, and Readability parsers with automatic dependency management and isolation. Interact through the self-hosted web UI with search, tagging, and admin controls, the comprehensive CLI for batch operations, the REST API for programmatic access, or the Python API for custom integrations. The new abx-plugins system enables community extractors with per-plugin configuration, while the append-only-log architecture provides resumable crawls and audit trails. S3, B2, and Google Cloud storage backends sync archives to remote storage via rclone. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT 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.

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.

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.

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.

Homeio turns a Linux box into a desktop you open in a browser tab, with draggable windows, a dock, a lock screen, and a command palette sitting on top of your Docker apps, files, and disks. The App Store installs Docker Compose stacks from the CasaOS catalog or your own store sources, and each app's ports, volumes, environment variables, and compose file stay editable before and after install. Containers you started elsewhere still appear with live CPU and memory stats, streaming logs with keyword filters, and one-click restarts. The file manager uploads with progress, previews images, audio, video, and PDFs, edits text in a built-in code editor, mounts USB drives and SMB shares, and shares folders over Samba. A real login shell lives in the Terminal window, with exec access into any container, so routine fixes never need a separate SSH client. Cron-style scheduled tasks restart apps, pull images, or run backups on a timer, and scheduled archives of the database, files, and compose stacks restore from the same interface. Tailscale puts the whole desktop on your private network, while Cloudflare Tunnel can publish a single app on a public hostname with its DNS record created for you. Live metrics stream to widgets and the status bar, and notifications flag crashed containers, filling disks, and failed tasks. 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.

Telegram Desktop's export is a file you make once by hand; Telegram Archive is a self-hosted backup that keeps saving your chats on a schedule and in real time, then lets you read them in a viewer that looks like Telegram. After one login with the code Telegram sends you, it stores messages, photos, videos, voice notes, stickers, documents, and link previews, saving each file once even when several chats share it. A live listener captures new messages, edits, and reactions as they happen, and a daily full pass fills any gaps. Every edit keeps its earlier text as a version, and with deletion tracking switched on, deleted messages stay in the archive marked as deleted. The viewer offers folders, forum topics, archived chats, pinned messages, polls, shared media, and search across every chat, plus a What changed feed of deletions, edits, and transcripts. Voice notes can be transcribed into searchable text by a server you run or rent. Family or colleagues get logins limited to chosen chats, or a share link that opens a single chat. One archive holds several accounts, a Telegram Desktop export can be imported for older history, and twelve themes suit phones and desktops. 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-or-later 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.

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.

Tools and applications that already speak S3 can use RustFS as their storage backend, so backup jobs, data pipelines, and services keep working while the data stays on infrastructure you control. A built-in web console on port 9001 manages buckets, object uploads and downloads, access keys, users, groups, and IAM policies, with a status page for cluster health, capacity, and scanner activity. Versioning, Object Lock retention, bucket quotas, and server-side encryption with Vault or AWS KMS backends protect objects once they land. Lifecycle rules expire or transition data, and tiering moves cold objects to remote targets such as Amazon S3 or Wasabi. Bucket replication and site replication keep clusters in sync, and event notifications call webhooks when objects change. Single-node mode suits a lab or small server, while distributed mode adds erasure coding, bitrot protection, background healing, and pool expansion or decommissioning as capacity grows. Sign-in works with local users, OIDC single sign-on, or OpenStack Keystone, and FTPS and WebDAV are available by default, with SFTP and the Swift API as opt-in builds. A preview of S3 Tables exposes an Iceberg REST catalog for tools such as DuckDB and PyIceberg, and a documented migration path moves existing MinIO deployments across. Typical uses include backups, container registries, logs and traces, data lakes, and AI training sets. 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.

With over 110,000 GitHub stars and one of the fastest-growing open-source communities in the self-hosted space, Immich delivers a Google Photos-grade experience entirely on your own hardware. The platform handles automatic background backup from Android and iOS devices, deduplication, and support for RAW formats, LivePhotos, and MotionPhotos. Its machine learning pipeline runs facial recognition and clustering locally on your server, enabling you to group photos by person without sending a single image to the cloud. CLIP-based semantic search lets you find images by describing their content in natural language, while metadata-driven search covers EXIF data, dates, and locations. The web interface built with SvelteKit provides a responsive timeline view, albums, shared albums with configurable permissions, public sharing links with optional passwords and expiry dates, partner sharing for family libraries, and a global map plotting photos by GPS coordinates. Administrative features include multi-user support with per-user storage quotas, OAuth integration, API key management, and a user-defined storage structure for organizing files on disk. The architecture uses PostgreSQL for metadata, Redis with BullMQ for background job queues handling thumbnail generation, video transcoding, and smart search indexing, and exposes over 400 REST API endpoints documented via OpenAPI with auto-generated SDKs for web, mobile, and CLI 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.

Configuring recurring cron jobs via version-controlled YAML manifests becomes seamless with GoCron, giving systems engineers and DevOps administrators a responsive web console to orchestrate scheduled commands with hot-reloading and sandboxed execution. Administrators can declare schedules using standard five-field cron syntax, establish global default configurations, and inherit execution timeouts, retry policies, and environment variable expansions across individual tasks. The interactive web interface provides immediate visibility into upcoming runs, past execution durations, status badges, and expandable terminal output logs stored in local SQLite databases. Operators can trigger ad-hoc job runs on demand, cancel stalled processes, and utilize a built-in sandboxed terminal utility governed by strict command whitelists. Automated health check webhooks dispatch HTTP notifications to external monitoring services upon job initiation, successful completion, or unexpected execution failure. The container environment bundles common server utilities including Restic, BorgBackup, and Rclone, streamlining automated offsite database backups and cloud storage synchronization routines without additional dependencies. Dynamic configuration reloading automatically detects filesystem modifications to YAML manifests without restarting the daemon, ensuring zero-downtime schedule updates. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.