The Resilient Private Cloud OS
VergeOS runs compute, storage, networking, and data protection in one code base. Resiliency, repair, and recovery are platform features at no additional software cost.
- Workloads keep running through drive and server failures
- Recovery happens inside the platform, not in a second product
- DR moves the entire data center, network included
Resiliency and Protection Are Different Jobs
Resiliency keeps the workload running. Protection restores data after resiliency runs out, and that is when the recovery clock starts.
A Second Product Handles Recovery
The array protects blocks. HCI restarts workloads. Neither design moved recovery into the platform, so four jobs still fall to a separate backup stack:
- Application recovery
- Archiving
- Failures that exceed the resiliency factor
- Single file restores
Each one runs on separate hardware, under a separate license, in a separate console.
The Same Jobs, Answered Inside the Platform
VergeOS was designed for cloud service providers and built for the enterprise private cloud.
- RF2 and RF3 protect data per workload
- ioGuardian holds data online past the resiliency factor
- Snapshots bring back a VM or a single file
- Virtual data centers move the whole environment to a second site
A backup product becomes optional, used for GUI-based file recovery and long term archiving.
Resilient. Repairable. Recoverable.
Each word covers one stage of a failure, handled by the same platform that runs the workload.
Resilient
The workload never stops.
- RF2 or RF3, chosen per workload
- A failed drive is invisible to the application
- Server loss triggers automatic restart elsewhere
Repairable
The purchased redundancy is spent, and the data stays online.
- ioGuardian delivers missing data segments in real time
- VMs keep reading through the failure window
- The system repairs itself with workloads running
Recoverable
Recovery runs from the interface that runs the workloads.
- Unlimited snapshots, retention bounded by capacity
- Instant recovery of a deleted VM
- File recovery through a hot plug drive
Three Strategies, Scored on the Same Five Jobs
Score any design against what a recovery plan has to cover. The difference shows up in the bottom rows.
Resiliency Inside the Code Base
- RF2 and RF3 set per workload, no array console in the path
- Automatic restart of workloads on healthy nodes
- ioGuardian target, a dedicated server, supplies missing data past the limit
Recovery Inside the Code Base
- ioClone snapshots behave as independent copies, not a dependent chain
- VM and file recovery from the same interface that runs the workloads
- Virtual data centers encapsulate VMs, network, and storage settings
Every Failure Has an Answer in the Platform
From a single drive to a full site, the response comes from VergeOS itself.
No Restore Job
- Drive and server failures never start a recovery clock
- No operator in the loop
One Interface
- Snapshots, recovery, and DR run where the workloads run
- No separate backup console
Whole-Site DR
- The DR site is a running copy
- Networking fails over with the workloads it serves
Resiliency Has a Price
Every step up in resiliency costs more. The difference is whether a step also costs performance.
- RAID 5: lowest cost, least resilient, highest performance impact
- RF2: costs more, almost no performance impact
- RF3: costs more again, no performance impact
- Longer retention: highest capacity cost, most resilient
| Capability | What it does |
|---|---|
| RF2 and RF3 | Protects data per workload |
| High availability | Restarts workloads on surviving nodes |
| ioGuardian | Keeps data online past RF2 or RF3 and repairs the system |
| ioClone snapshots | Unlimited independent copies, bounded by capacity |
| Instant recovery | Brings back a deleted VM |
| File recovery | Restores individual files through a hot plug drive |
| Virtual data centers | VMs, networking, and storage settings fail over as one object |
| Software cost | All of the above included in VergeOS |
| Hardware | Runs on existing servers and refurbished hardware |
Five Questions to Ask Before You Choose a Platform
Answer these for your own data center. The platform decision follows from what you find.
On a scale of 1 to 5, how confident are you that you can recover all your data inside the expected SLA?
Most IT teams answer three. The gap usually traces to a recovery path that crosses several products, each with its own console, that nobody has tested end to end recently.
Is your backup environment a separate architecture inside your data center?
Count the storage, networking, servers, and software that exist only to protect production. Each is a license, a refresh cycle, and a skill set. On VergeOS, snapshots, replication, and DR run in the same code base as the workloads.
What is your first point of recovery at the DR site?
Storage, backup, or replication. The answer sets your recovery time. A VergeOS virtual data center fails over with its networking intact, so the DR site is a running copy.
What happens when failures exceed your resiliency factor?
In most designs the plan hands the problem to a restore. ioGuardian keeps data online past RF2 or RF3 and repairs the system, so the workload stays up.
Does your DR plan move the network, or only the data?
Array replication moves blocks and leaves applications and networking to be rebuilt by hand. A virtual data center replicates VMs, network, and storage settings as a single object.
Fewer Products Between You and Recovery
The protection jobs that used to need their own products run inside VergeOS.
Leaving VMware
- The exit rebuilds every layer under the VMs
- Fix recovery in the same project
Reusing Hardware
- Runs on servers already on your floor
- Refurbished hardware made resilient
Modernizing DR
- Replicate a whole virtual data center
- Fail over and fail back as one object
Go Deeper on Resiliency and Recovery
HA, Data Protection, and Disaster Recovery
High availability, snapshots, replication, and DR inside one platform.
Read the architecture pageioGuardian
How VergeOS stays online and repairs itself past the resiliency factor.
Explore ioGuardianBeyond the Hypervisor Swap White Paper
The VergeOS 2026 architecture, from the single code base to virtual data centers.
Get the white paperCommon Questions
What is the difference between resiliency and protection?
Resiliency is maintaining operation with zero application downtime and zero data loss. Protection is restoring data after the resiliency factor has been exceeded. Raising the resiliency limit costs more, which is why RF3 costs more than RF2.
What is ioGuardian?
ioGuardian delivers missing data segments to VMs in real time during multiple drive or server failures. A dedicated server, the ioGuardian target, keeps data readable past RF2 or RF3 as the system repairs itself.
How many snapshots can VergeOS keep?
Unlimited. ioClone snapshots behave like independent standalone copies rather than a dependent chain, so retention is bounded by capacity.
How does VergeOS recover a deleted VM or a single file?
A deleted VM comes back instantly from a snapshot. Individual files recover through a hot plug drive attached to the running VM, from the same interface that manages the workloads.
What does a virtual data center include?
VMs, network, and storage settings. The environment replicates and is managed as a single object, so applications and their networks reach the DR site together.
Do I still need a backup product?
It becomes optional, used for GUI-based single file recovery and long term archiving. VergeOS supports the backup platforms customers already run, including Veeam.
What do these capabilities cost?
RF2 and RF3, ioGuardian, unlimited snapshots, instant recovery, and DR orchestration come with VergeOS at no additional software cost, on existing or refurbished hardware.
Resilient on the Hardware You Already Own
Resiliency, repair, and recovery at no additional software cost, on the servers already on your floor. See it run against your own recovery requirements.