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.

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.

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.