Servatum checks every backup job against its schedule, catches the ones that failed or never ran, and reports to your monitoring or to a proof page your customers can see. Then it keeps an offsite copy that nothing can delete.
Know your backups work. Prove they exist. Keep them out of reach.
Your proof page shows which parts of the rule you actually meet, from what your jobs report rather than what your policy says.
A hook for JetBackup and cPanel, a wrapper for restic, borg and rclone, a webhook for anything else, or forward the emails your paid tools already send.
servatum run -- restic backup /home
Each tier gets a schedule and a retention target. Late, failed or missing runs raise an alert and are logged as incidents with cause and recovery time.
Into PRTG, Zabbix, Prometheus, Uptime Kuma, Slack or Telegram, and onto a proof page if customers should see it. Names, mailboxes and file lists are never published.
Pick a system to see how Servatum connects to it. Ingest is where results come from; egest is where we send them.
Turn backups from a line in your terms into something customers can check. JetBackup and cPanel hooks, a white-label page per client.
Wrap the restic, borg or rclone jobs you already run. Get told when one stops, and have an answer ready when a security questionnaire asks.
Every client's backups in one place, from whatever tool they use. No client minimum, reports and pages under your own brand.
We're onboarding a small group of hosts and teams first. Tell us where to write.