As often as every 15 minutes
Small incrementals mean frequent copies without saturating the WAN. Nightly is still available for systems that barely change.
How It Works
How cloud backup works.
Classic backup images the disk, then fights the size of the copy. We track changes on the host, send small incrementals to isolated cloud storage, and restore by filling in what is missing.
The path
Three steps. No appliance in the middle.
01
Change tracking on the host
An agent watches the disk in the background. Temporary files and cache are skipped. Only the bytes that changed are queued — not a full image scan at backup time.
02
Direct to isolated cloud
Those incrementals go straight to regional cloud storage. Copies are encrypted in transit and at rest, immutable by default, and off the production network.
03
Restore only what is missing
A recover identifies blocks already on the target and pulls the rest. That is why a restore is faster than writing a whole disk from a nightly image.
Why it stays small
Frequent copies without a nightly image war.
Image-level jobs often recopy a large slice of the disk because defrag, tracking, and temp files look like change. We read the disk from the inside, skip the noise, and send the bytes that actually moved. That is how 15-minute copies stay practical.
No appliance to babysit
We run the platform — patching, storage, and the console. Your people are not watching backup jobs at 2 a.m.
Optional local cache
Cloud-first is not cloud-only. A local copy can sit on hardware you already own for a faster large restore. It is not required to be protected.
One console
Servers, workstations, VMs, and Microsoft 365 in one place. Failures surface by exception instead of a wall of green jobs.
FAQ
How the copies actually run.
Do copies go through a box in our rack?
No. Changed blocks go direct to isolated cloud storage. A local cache is optional for faster large restores. It is not required.
Will this saturate the WAN?
After the first copy, only changed bytes move. That is what makes 15-minute incrementals practical. We set the window to the recovery point you actually need.
Can we keep a local copy anyway?
Yes. Cloud-first is not cloud-only. Use a share or host you already own as a cache. The isolated cloud copy is still the one ransomware cannot reach.
Who patches the backup platform?
We do. You are not running an appliance OS, filling disk, or chasing failed jobs.
Same-day quote
Request a backup quote.
Tell us the servers, workstations, and Microsoft 365 seats.
Get a backup quote.
Tell us what must come back. We return a scoped quote.