Solution 07 — Backup Orchestrator, live at backuporchestrator.com
A backup you have never restored is a guess.
Backup Orchestrator takes the backup, restores it every night into an isolated standby machine, and questions the result — did the database open, did the machine boot, did the archive decrypt — then keeps the evidence. The data stays on your premises; only the answers leave.
Operated in-house by Stan Technology
How proof works
Not "backup succeeded". Proven, and shown.
Backing up is the easy part. Coming back is the part nobody tests. Each system gets a runbook that knows how to back it up and, more importantly, how to prove it came back.
Restored every night
The backup is restored onto a second machine on your premises — a standby, isolated from production — and started. Not copied and counted: brought back and asked to work.
Questioned, not just started
A till database is opened and read. A virtual machine is booted. An encrypted offsite archive is decrypted — a hash match proves the copy arrived; only a decrypt proves you can get it back.
A runbook for the system you actually run
Actian Zen and Btrieve databases behind point-of-sale and ERP packages, whole Hyper-V machines, Plesk hosting servers to encrypted offsite storage. Niche systems are the specialty; most of the library started as somebody asking.
Silence is an alarm
Every run has a deadline. A backup that never reports, an agent that goes quiet, a database growing faster than it should — each one pages someone. Nothing fails quietly, including the control plane itself.
No inbound access. No shell. No appliance.
The agent only ever calls out, over HTTPS, and only runs a fixed set of named actions — never a command line. Nothing opens a port into your network, and nothing installs a box in your rack.
Evidence leaves. Data does not.
What the platform keeps is booleans, timestamps, counts and fingerprints — that the restore worked, when, and how big. Never invoice contents or customer names. Judgements leave the site; data never does.
Why the restore is the point
- 74%
- of businesses back up to the cloud
- 25%
- have a plan for the day they need it back
- 48%
- of ransomware victims paid anyway
UK Cyber Security Breaches Survey 2025/26
the same survey
Sophos, State of Ransomware 2026
How it starts
Install, prove, then relax
The first night answers a question every business should already know the answer to.
-
01 An afternoon
Install
A small agent on the machine that holds the system, and a standby machine to restore into. Nothing inbound, no VPN, no appliance.
-
02 That night
First restore
The runbook backs the system up, restores it to the standby and questions it. Most environments learn something on night one — better here than during an outage.
-
03 Ongoing
Every night after
The same run, the same questions, the same evidence — kept for eighteen months. Deadlines and watchdogs page someone the moment a night is missed.
-
04 Any morning
Ask the panel
The client dashboard answers the only question you open it with: did my backup work last night?
Where it fits
Standalone, or inside Managed IT
Backup Orchestrator is its own product with its own plans, priced for Canada, the US, the UK and the EU — and it is also the backup layer inside Managed IT, where "backups that restore" was always the floor. Managed IT clients get it as part of the arrangement; everyone else gets it on a plan of its own.
Runs a system nobody else will touch? That is the specialty. If a runbook does not exist for it yet, that means one has not been written — not that it cannot be.
- Windows and Linux agents today; more platforms as runbooks are written
- Ninety days of raw events, eighteen months of runs and evidence — enforced, not promised
- Set up with you in conversation, not by a checkout page
Verified Backups
Find out whether yours come back.
The full product, the runbook library and the plans live at backuporchestrator.com. Or describe what you run and get a straight answer on whether it can be proven — and what the first night would show.