Add ZCP to your hyperscaler.
Keep what works. Fix what doesn't.
You do not have to rip and replace your hyperscaler to take back control of cost, sovereignty, and resilience. Run ZCP alongside AWS, Azure, or GCP, and move only the workloads where the hyperscaler economics work against you: runaway data-transfer fees, sovereignty-sensitive data, disaster recovery, and steady, always-on capacity.
4 - 6 week pilot · CAD billing · No disruption to your hyperscaler commit · Your tools work unchanged
- Egress
- $0 always
- Object storage
- $0.024 / GB / mo
- Hybrid pilot
- 4 - 6 weeks
- Foundation
- Open source
Why hybrid, why now
The hyperscaler is not wrong. It is not the only answer.
Hyperscalers solved a real problem and still do it well: global reach, managed services, elastic burst, deep ecosystems. The pain is concentrated in a handful of workloads where the pricing model, the jurisdiction, or your dependence on a single vendor becomes the real risk to the business. Those are the workloads ZCP is built for.
Cost control
Data-transfer fees, premium tiers, and per-feature add-ons compound into a bill no one can fully predict. Hybrid moves the expensive parts to a vendor whose pricing rewards how you actually use it, so the savings show up on the line your CFO watches.
Concentration risk
Most enterprises put 80 %+ of their footprint on a single hyperscaler. A second operator under a separate corporate jurisdiction is the cheapest insurance you can buy against vendor lock-in, a regional outage, and a policy or pricing change you never voted for.
Sovereignty by workload
Not every workload needs the same jurisdiction. Move the ones that do onto ZCP, and stop forcing a single global compliance decision onto an entire estate that does not need it.
Reference architectures
Four ways to slot ZCP into your hyperscaler estate.
Each pattern stands on its own, so pick one and start there, then stack the others as the results earn it. Our engineers help you choose the entry point with the fastest payback for your environment.
Egress offload
Move data-heavy storage to ZCP. Keep hyperscaler compute.
AWS, Azure, and GCP charge $0.05 - $0.12 per GB to move data out, and a single data-heavy pipeline can spend $5 k - $12 k a month on transfer fees alone. Park that data on ZCP at $0.024 / GB / mo with $0 egress, and read it from whichever hyperscaler runs your compute. Your team keeps the tools it already uses, with nothing to rewrite.
- Data lakes and analytics storage
- Origin storage for media and static assets
- AI and machine-learning datasets read repeatedly
- Backup and snapshot retention
- Video, audio, and image archives
Sovereign workloads
Move regulated or jurisdiction-restricted data to ZCP.
You do not have to re-platform everything to satisfy a residency requirement on a subset of workloads. Move the data that needs sovereign isolation onto ZCP and leave the rest on AWS, Azure, or GCP. For the regulated portion, a single named operator sits on the contract and region selection is enforced by the platform, so the residency commitment is verifiable rather than assumed.
- PII and PHI subject to jurisdictional rules
- Customer data with residency clauses
- Audit-sensitive workloads with disclosure obligations
- Government and quasi-government tenants
- Sector workloads regulators want clearly located
DR target · cold tier
ZCP as your independent recovery site or archive destination.
Disaster recovery inside the same hyperscaler still leaves you exposed to a single vendor. ZCP gives you an independent recovery site under a different operator with auditable replication, so one provider failing does not take your recovery plan down with it. For long-term archives, cold storage runs at $0.024 / GB / mo with no restore charges, where restoring a 10 TB archive from a hyperscaler cold tier can cost more than storing it for a year.
- Cross-cloud DR for production hyperscaler workloads
- Point-in-time backups with predictable restore cost
- 7-year regulatory archives
- Snapshot replication to a different operator
- Disaster-recovery exercise targets
Predictable baseline · burst
Move always-on workloads to ZCP. Burst on the hyperscaler.
On-demand hyperscaler capacity costs 3 - 5× the reserved equivalent, and reserving it locks you into a region and term. Either way, your steady, always-on workloads pay a flexibility tax for demand that never moves. Run that 24/7 floor on ZCP at predictable CAD rates, with 1-year reserved at 15 % off and volume discounts past 10 instances, and keep the hyperscaler for the genuine spikes: campaign traffic, batch peaks, training bursts.
- Web applications and APIs with steady load
- Internal services and business tooling
- Databases and core back-end services
- Scheduled batch jobs
- Long-running queues and pipelines
Honest scoping
Where the hyperscaler is still the answer.
Hybrid only works if you know what stays where. We are upfront about the workloads the hyperscaler is still the better home for today, because a partner who only ever says yes is not one you can plan around.
Hyperscaler-native managed services
If your application is built around a proprietary managed service that only your hyperscaler offers, keep it there. We will not pretend otherwise.
Global edge presence
When you need content served from dozens of locations worldwide, the hyperscaler edge network wins today. ZCP has two live regions and five planned, so global edge is not our story yet.
Hyperscaler marketplaces
If you buy software through your hyperscaler marketplace contract, keep the procurement workflow you already have. There is no reason to disrupt it.
Elastic burst
If your traffic spikes 10× and back in minutes, on-demand hyperscaler capacity still wins. ZCP is for the steady floor; the hyperscaler is for the spike.
What customers ask before they pilot
Six questions, answered.
We have AWS / Azure / GCP consumption commits. Is hybrid still viable?
Yes. Hybrid lets you keep spending against your existing commit while you go, so nothing is wasted. Most teams phase ZCP in alongside the current commit, then negotiate the next one downward at renewal. Our engineers help model the phase-in so you do not overpay on either side.
Will our team need to learn a new platform?
Less than you fear. ZCP works through the standard interfaces and tools your team already uses day to day, so they operate it with skills they have, not a new certification to chase. We handle the platform underneath. Your people stay focused on your product.
How does the connection between hyperscaler and ZCP work?
A secure site-to-site connection over the internet is the default and works for most workloads, with no change to how your applications talk to each other. For latency-sensitive traffic we use direct exchange paths that avoid hyperscaler transfer fees, and dedicated private interconnect is available on the Enterprise tier.
Does this complicate how we deploy and operate?
No more than running across multiple regions inside one hyperscaler. Your existing deployment pipelines stay as they are; ZCP simply becomes another target. We provide reference templates and example pipelines for the four patterns above, so your team starts from a working blueprint rather than a blank page.
What if we want to go further and migrate fully?
Hybrid is the entry point; full migration is a path, not a precondition. Once one pattern proves out, we scope a migration plan workload by workload. We never pressure you to commit beyond what is already working for you.
How quickly is a first pattern ready?
Most teams have one of the four patterns live within a paid 4 - 6 week pilot: scope in week 1, your ZCP environment provisioned and connected in week 2, the workload moved or replicated in weeks 3 - 4, and run-rate validated in weeks 5 - 6. Pilot cost depends on the pattern, and we publish the number before you sign.
Or, if you're ready to go further
Hybrid is the entry point. Full migration is a path.
Most customers start with one of the four patterns above. Some keep the hyperscaler indefinitely. Others find the economics work end to end and move the rest. Either way, we scope the next step from your real numbers, not a slide deck.
Start with one workload
Bring us one workload.
We'll show you the architecture.
A 30-minute scoping call. Bring the workload hurting the most on your hyperscaler bill, the transfer-heavy one, the sovereignty-sensitive one, or the stubborn 24/7 floor. We come back with an approach, a number, and a pilot plan.