billed monthly, in advance
| Scope | Selected files and folders on a Windows PC |
|---|---|
| Platform | Windows |
| Cadence | 2 passes per day |
| Version depth | 28 days of prior versions |
| Transfer | Change-tracked: only what moved since the last pass |
| Encryption | AES-256 applied before data leaves the machine; TLS in transit |
| Custody | Cloud vault, off the machine and off its network |
| Restore unit | One file · one folder · the whole selection |
| Administration | Central: selection and schedule set once, for everyone |
| Billing unit | Per Windows workstation, per month |
What goes into the vault
The live document set. Spreadsheets and proposals, the Access database somebody built in 2014, CAD exports, Visio maps, brand artwork, signed PDFs, and the shared folder the business has quietly been running out of since 2019. You select the paths; the agent keeps them.
This line is deliberately narrow. It does not carry the operating system or the installed applications. It carries the material that changes hourly and is missed within the hour, at the lowest rate in the catalog.
How it runs
A lightweight agent runs on the workstation and takes two passes each day, transmitting only the blocks that changed. Twenty-eight days of versions accumulate behind every file, so a document is not a single object but a stack of daily states you can step back through.
Selection and schedule are administered centrally, which matters more than it sounds. Coverage that depends on an individual remembering to tick a box is coverage with a hole in it. Nobody on your side is required to do anything for this to keep working.
Version history is the security control
Everything is encrypted with AES-256 before it leaves the machine, remains encrypted across the wire, and remains encrypted in the vault. That is table stakes. The element that actually saves you is where the versions live.
Ransomware encrypts what it can reach: the local disk, the mapped drive, and the sync folder that dutifully replicates the damage to the cloud within seconds. The stack of earlier states is not on that list. It sits in a vault the infected machine has no route to and no credentials for, which is how a two-dollar line item determines whether a week is merely expensive or genuinely terminal.
Getting it back
Retrieve one file from any day inside the 28-day window, take a folder tree exactly as it stood on a chosen date, or bring down the entire selection. Single-file restores are typically complete in under a minute and require no other change to the machine.
Where this line stops
Working Files does not rebuild a computer. If the drive fails or the laptop is stolen, this line returns your documents to a working machine; it does not return the machine. For the operating system, applications, settings, and bare-metal recovery, select Full Machine instead. Many clients run Working Files on field workstations and Full Machine on the systems that would be painful to rebuild.