
Getting Started with Cyberity Backup Governor
Cyberity Backup Governor watches the backups you already run and turns them into proof: verification results, restore evidence, and anomaly alerts.
Cyberity Backup Governor watches the backups you already run and turns them into proof: verification results, restore evidence, and anomaly alerts. To start, create a free account (it covers one node), install the agent on a Windows or Linux machine, and point it at the backup files your existing software produces. Nothing about your current backup setup changes.
What it does, in one paragraph
Backup Governor does not replace your backup software; it verifies what your backup software produces. Whatever tool writes your backups, the result is files: database dumps, file archives, VM images. The Backup Governor agent checks those files on a schedule, from a quick freshness-and-integrity pass up to an actual test restore with validation of the data that comes back. The results flow to a dashboard your team (and your boss, and your auditor) can read.
Step 1: Create your free account
The free tier covers one node: one machine you protect, using your own storage. One server running five databases and an HRMS is still one node. Our suggestion: spend the free node on the machine your business can least afford to lose, usually the server carrying your core database or HR/accounting system.
Step 2: Install the agent
The agent runs on Windows and Linux (deb/rpm packages). Install it on the machine where your backups live or land: the backup server, or the production server that writes backups to a local disk or NAS. The agent runs as a background service and comes with a desktop console for setup and configuration.
Two things worth knowing before you install:
Credentials stay on the machine. Storage credentials are kept in the operating system's own keychain/credential store; they are never sent to us.
Evidence is redacted before it leaves. When a VM restore produces a console screenshot as proof, sensitive on-screen data is redacted on your machine first; the unredacted original never egresses.
Step 3: Point it at your backups
Tell the agent where your backup files are. Two options, and you can mix them:
Local or network paths: the folder your backup software writes to.
Your own cloud storage: Amazon S3, Azure Blob, Google Cloud Storage, Cloudflare R2, Backblaze B2, or a Synology NAS, plus S3-compatible stores such as MinIO and Wasabi. The agent downloads a copy, verifies it, and deletes the temporary copy when done.
For each backup target you set the type (SQL Server, MySQL, PostgreSQL, file backup, or a Hyper-V/VMware VM image), how fresh the newest copy must be, and how deep verification should go. Formats are auto-detected, and compressed and archived backups (zip, 7z, tar, gzip and friends) are unpacked automatically.
Step 4: Your first verification
Verification runs at four levels, and you choose the depth per target:
The four verification levels
Level What it proves
L1: Existence & freshness The backup file exists, is non-empty, and is recent enough to matter.
L2: Integrity The file's checksum and format headers check out; it isn't silently corrupted.
L3: Actual restore The backup is really restored: the database mounts, the VM boots, the files extract.
L4: Data validation What came back is checked against what should be there: row counts, expected content, no unexplained drift.
Start with L1/L2 on everything to get immediate signal, then schedule L3/L4 restores for the targets that matter most. Each real restore also records how long it took. That number becomes your measured recovery-time evidence.
Step 5: Reading the dashboard
The portal gives you three views that answer three different questions:
Health overview: is everything green right now? Which targets are verified, which are stale, which failed?
Anomalies: what changed? Backups that stopped arriving, sizes that shrank or ballooned, and ransomware indicators found while scanning restored data. Anomalies can be acknowledged and triaged, and a compromised finding quarantines the affected verification until an admin clears it.
Evidence: what can I show someone? Verification history, restore outcomes with timings, and downloadable reports, the raw material of the monthly backup report.
The portal and desktop console are available in ten languages, including Bahasa Malaysia and Chinese. Your team works in their own language.
What the paid tier adds
Honestly: mostly more nodes. The free tier is full verification for one machine on your own storage. When you want the same proof for the rest of your servers, or scheduled disaster-recovery drills across many VMs at once, that is the paid conversation. There is no feature bait on the free node; it exists so you can see a month of real evidence before spending anything. See pricing for current details.
Put your most valuable server under real verification
One free node, your own storage, no change to your backup software. See what a verified restore looks like this week.
Get started