Drop
Recovery you have already rehearsed.
Disaster recovery as a service across the Nwan fabric. Your workload replicates to a HyperNext campus in a different seismic and grid zone, recovery is rehearsed on a schedule rather than hoped for, and the evidence is kept for your regulator.

Recovery as a service, not a plan in a drawer.
Most disaster recovery exists as a document and a contract. Drop exists as a running copy of your environment, replicated continuously, with failover and failback exercised on a schedule you set and reported on each time.
How it works
- Replicate
- Continuous replication from your primary site over Nwan, with the recovery point measured, not estimated
- Rehearse
- Failover drills on a schedule, in isolation, without touching production
- Fail over
- Declared from the console. Networks re-point, services come up in order
- Fail back
- Return to the primary site when it is ready, with the delta replicated back first
HN-3 Nava Raipur, built for this.
A 100 MW campus in a different seismic zone and a different grid region from the primary HyperNext campuses, positioned as the recovery site for Indian enterprises and banks. Live April 2028.
Replication over Nwan.
Drop runs on the Nwan Cloud WAN, so replication travels on committed, path-diverse private circuits rather than the public internet, and failover re-points the network from the same control plane that moves the workload.

Nwan path trace · replication on diverse routes
Proof, kept for your regulator.
Every rehearsal, failover and failback is recorded with its recovery time and recovery point, and the record is exportable as evidence for audit.
Also offered as a service
Talk to the engineering team.
Specifications, drawings and deployment planning for the 800 VDC product line. Designed by HyperNext Engineering, Toronto. Made in India.
