Nine lines, because a bench, a box of iron in a cupboard, a hypervisor guest and a cloud tenant are four genuinely different jobs failing in four different ways. The ninth is the one most firms leave off, and it is the only one that proves the other eight.
Keeping the tenant up is what Microsoft and Google promise. Keeping a spare of the contents is a separate promise, and neither firm made it. Post that was cleared, a site somebody emptied, a folder tidied away in March, an account removed a fortnight too soon: none of those are outages, so none of them are theirs to fix.
Your ledger sits in exactly the same position. QuickBooks Online is a living database that somebody edits every working day. A botched import or a careless bulk action can unpick months of it, and reassembling that from bank statements by hand is an experience well worth a small monthly figure to avoid.
Backup software reports success. A report of success and a system that genuinely comes back are two separate claims, and most ruined Mondays live in the space between. Media gone unreadable, a database copied mid sentence, a chain that broke quietly in February.
The proving line takes the spares and genuinely stands them up on a rhythm, then hands you dated evidence that they ran. It is the nearest thing on this whole card to the timing certificate that comes home in the box with a serviced watch, and it is the line we would argue hardest for you to keep.
Every figure below leaves billing at the moment this page opens. Anything laid on the service card sits waiting there while you carry on reading.
One word in the tables below needs pinning down. Certified by names the person who did the work and put their name beside it, which is how a watchmaker certifies a service. It carries no claim that Fortify 24x7 holds a security certification, and buying a line confers none on your business either.
The cheapest line on the card and the one called on most. Somebody writes over the quote, shuts it, and then goes cold. This holds four weeks of earlier states for the folders people genuinely live in, so the answer is a click rather than a ruined afternoon.
| Serviced on | Windows benches you have brought onto the service card |
|---|---|
| Regulates | How far back one individual file can be walked |
| Interval | Earlier states taken through the working day, four weeks retained |
| Adjusted by | You name the folders, we confirm the pick covers where the work really lives |
| Certified by | Every run is logged and its outcome reported |
An image of the machine entire, because what goes wrong is seldom one file. A disk expires, a laptop is lifted from a van, something encrypts everything at half past two. What you want returned is the machine, set up the way its owner had it.
| Serviced on | Windows, macOS and Linux benches you have put on the card |
|---|---|
| Regulates | How much of a machine returns, and how fast it can be stood back up |
| Interval | Once a day as standard, more often where the work is worth it |
| Adjusted by | You set the rhythm and the depth, we size the allowance against real figures |
| Certified by | Outcomes are reported per machine and per run |
For the cupboard box that everything quietly leans upon. Images of the whole server, databases handled the way databases have to be, so what comes back is coherent instead of a pile of files caught mid sentence.
| Serviced on | Windows and Linux servers standing on iron of their own |
|---|---|
| Regulates | How much of a server returns, and whether its databases return usable |
| Interval | Once a day as standard, tightened where the tolerable loss is narrower |
| Adjusted by | You set the rhythm and the depth, we size the allowance against real figures |
| Certified by | Outcomes are reported per server and per run |
The same treatment for guests, reckoned per virtual server rather than per host, so a busy hypervisor does not turn a plain invoice into a disagreement at renewal.
| Serviced on | Windows and Linux guests riding on a hypervisor |
|---|---|
| Regulates | How much of a guest returns, and whether its databases return usable |
| Interval | Once a day as standard, tightened where the tolerable loss is narrower |
| Adjusted by | You set the rhythm and the depth, we size the allowance against real figures |
| Certified by | Outcomes are reported per guest and per run |
Keeping your tenant up is a Microsoft undertaking. Holding a spare of the contents is not. Post that was cleared, a site somebody emptied, a folder tidied away in March: none of those are outages, so none of them are theirs to put right.
| Serviced on | Microsoft 365 licensed users on the tenant you connect |
|---|---|
| Regulates | What can be fetched back after a deletion, and how far back it reaches |
| Interval | Taken repeatedly through the day on the tenant rhythm |
| Adjusted by | You authorise the connection, our engineers prove what it covers |
| Certified by | Runs and fetch requests are entered against the tenant |
The same argument again, this time on the Google side. Post, drives, contacts, calendars and tasks kept clear of the tenant owning them, with fetches fine enough to take back one item instead of obliging you to swallow everything.
| Serviced on | Google Workspace licensed users on the tenant you connect |
|---|---|
| Regulates | What can be fetched back after a deletion, and how far back it reaches |
| Interval | Taken repeatedly through the day on the tenant rhythm |
| Adjusted by | You authorise the connection, our engineers prove what it covers |
| Certified by | Runs and fetch requests are entered against the tenant |
Your ledger is a living database that somebody edits every working day. A careless bulk action, a botched import or a bookkeeper leaving in a hurry can unpick months of it. Reckoned per company file, because a mistake ruins exactly one of those at a time.
| Serviced on | QuickBooks Online company files you connect |
|---|---|
| Regulates | How far a ledger can be wound back after a careless edit or import |
| Interval | Unbroken, following each change as it is committed |
| Adjusted by | You authorise the connection, our engineers prove the file is being read |
| Certified by | Runs and fetch requests are entered against the company file |
Groups, roles, rules and the conditions attached to getting through the door. Removing the wrong group takes four seconds and makes no noise. Rebuilding it from memory nine months later takes a fortnight and makes plenty.
| Serviced on | The Entra ID tenant you connect |
|---|---|
| Regulates | How a change to the register can be reviewed and undone afterwards |
| Interval | Watched live, with configuration copies held under no retention cap |
| Adjusted by | You authorise the connection, our engineers prove what it covers |
| Certified by | Register changes are entered with a date against the tenant |
A spare nobody has tried is faith, not engineering. This line takes the copies, stands them up on a rhythm, and gives you dated proof they ran. Of everything on this card it is the closest thing to the timing certificate that comes home in the box with a serviced watch.
| Serviced on | Any system already sitting on one of the backup lines |
|---|---|
| Regulates | Whether a spare genuinely runs, put to the test rather than taken on trust |
| Interval | Drills on a repeating rhythm, not one drill at the beginning and no more |
| Adjusted by | You choose which systems get drilled and how often, we run the drills |
| Certified by | Each drill leaves dated proof fit to place before an auditor or an underwriter |
Each of the six sheets carries a block like this one. It is the section most suppliers quietly omit, and it is the section that settles whether you feel let down in a year.
Heads up: card statements show FORTIFY 24X7 - ServiceTrust Cyber is a Fortify 24x7 brand, and your subscription is billed by Fortify 24x7.