Platform
Push, pull, verify, forget
Agents push. The vault pulls. Nothing that can reach your production network can reach the air-gapped copy.
Design decisions
Forever-incremental
One full, then changed blocks forever. Synthetic fulls are assembled in the vault, not on your network.
Source-side dedup
Variable-block deduplication before the data leaves the machine. Typical fleet ratio is 6.4:1, so 41 TB of change becomes 6.4 TB on the wire.
Write-once landing zone
Agents can create objects and never modify or delete them. Compromising an agent gives an attacker the ability to add garbage, not to remove history.
Content indexing
File-level search across every recovery point, so 'find the version of this file from before March' is one query.
Bandwidth shaping
Per-site schedules and ceilings. Backup windows that respect the fact that people also work here.
Evidence by default
Every copy, verification and restore is recorded in an append-only log you can export for an audit.
Retention and immutability
Copies
- Landing vault
- object lock, governance mode
- Off-site copy
- different region, compliance mode
- Air-gapped copy
- pull-only, offline credentials
- Verification
- hash + boot test per recovery point
Retention presets
- Operational
- 30 daily, 12 weekly
- Standard
- 30 daily, 12 weekly, 12 monthly
- Regulated
- adds 7 or 10 annual, compliance-locked
- Custom
- any GFS scheme, priced per stored TB