Broadcom’s Private Cloud Outlook 2025 — a survey by the vendor that sells VMware, so read it with that in mind — found 69% of organisations evaluating cloud repatriation and 53% prioritising private cloud for new workloads. The reasons vary — runaway cost, regulator pressure, AI data residency, predictable performance — but the architectural work is the same: identify the right workloads to move, run the move without breaking the application, and end up with a platform you can actually operate.
Ænix runs the technical engagement that turns “we need to leave AWS / Azure / GCP” from a board statement into a working plan with workloads ranked, costs modelled, and a destination architecture that won’t reinvent the public cloud the wrong way.
Pairs with the Ænix platform that matches the destination: Private Cloud Platform if you run the capacity for your own business units, Public Cloud Platform if you sell it on, AI Platform if the repatriated workloads are GPU-bound. Free Cloud Repatriation TCO Worksheet →. CTOs weighing the decision: see the CTO guide.
Who repatriation actually fits
Repatriation is not for everyone. The teams that benefit most share a common profile:
- Heavy public-cloud bills — annual spend in the seven figures, and the renewal trajectory is steeper than revenue.
- Predictable, steady-state workloads — not the elastic spike workloads hyperscalers were designed for.
- Sensitive data with sovereignty exposure — financial, healthcare, public-sector, or regulated-industry data that increasingly attracts regulatory pressure.
- AI / ML workloads with egress and inference cost concerns — model serving and training where hyperscaler economics break down at scale.
- An internal platform-engineering function (or one being stood up) — repatriation requires somebody to run the destination platform afterwards.
If your situation matches at least three of those, repatriation deserves a structured look. If you have a small IT team running a handful of services, the answer is almost always “stay in public cloud and tune your spend.”
Four reasons teams repatriate in 2026
1. Predictable cost on steady-state workloads Hyperscaler economics favor elasticity. For workloads that run 24/7 at predictable utilization, the unit economics on-prem or in private cloud are often clearly better once egress, idle resources, and underutilized commitments are counted honestly — how much better depends on your workloads, which the TCO calculator lets you model.
2. Regulatory and sovereignty pressure DORA (in force January 2025), NIS2, GDPR, sectoral data-residency rules, and procurement-led sovereignty mandates in several countries increasingly force critical workloads into an environment the organization controls itself.
3. AI and analytics on sensitive data GenAI, inference, and analytics workloads against regulated data classes face two-front pressure: model providers’ data-handling terms aren’t acceptable, and inference egress costs make hyperscaler economics unworkable at scale.
4. Operational and architectural control Hyperscaler-proprietary services lock the architecture into one vendor’s roadmap. Repatriation gives the platform team back the ability to choose, evolve, and audit the underlying components.
Where most repatriation projects go wrong
The TCO model is wishful, not honest Hardware cost is easy. Network, datacenter, storage tiering, observability, identity, backup, DR, ongoing platform-engineering capacity — usually missing or underestimated. The result: repatriation looks cheaper than it is, then disappoints the CFO 18 months in.
The destination architecture is left for later Workloads get moved to “an on-prem cluster” without a real platform underneath. The team rebuilds, in worse form, what hyperscalers spent a decade engineering. Self-service breaks. Velocity drops. Repatriation gets blamed.
Data gravity is treated as a checkbox “Move the database last” — without a real plan for how 50 TB of production data crosses the network, what the cutover window looks like, how the rollback path works, and where backups live during the move.
The exit is full-scope when selective is the right answer Most repatriations are not all-or-nothing. The right outcome is usually a subset of workloads on-prem (the steady-state, regulated, or expensive ones), with the rest staying in public cloud (the elastic, latency-sensitive, or hyperscaler-only ones). Treating repatriation as a binary decision destroys the economic case.
These failure modes are independent of cloud provider, vendor, or destination platform — they’re what happens when repatriation is run as a spreadsheet exercise instead of a platform-engineering program.
How Ænix helps
The repatriation engagement runs as part of our Platform Readiness Assessment, with the cost-and-cloud-spend workstream as primary focus. The 14- or 28-day engagement produces:
- Honest TCO model — current public cloud spend (incl. egress, commitment underutilization, hidden costs) vs. realistic destination cost on private cloud or hybrid.
- Workload repatriation ranking — every workload classified as “repatriate now / repatriate later / stay in cloud,” ranked by ROI and risk.
- Destination architecture — what the platform looks like that workloads land on, including compute, storage, network, identity, observability, DR, and the platform-engineering function that operates it.
- Cutover sequencing — repatriation cohorts that respect commitment expirations and minimize cross-environment data movement.
- Phase 2 implementation roadmap — what an Ænix-delivered Phase 2 would do, in what sequence, with effort estimates.
Delivered by Ænix engineers who have built production platforms for service providers, a bank and AI operators (see the case studies). The report’s bias is toward what we can stand behind technically.
Why Ænix specifically
- No hyperscaler bias. Repatriation advisory work from Big-4 consultancies is shaped by their hyperscaler partnerships. Our recommendations are not commercially tied to AWS, Azure, GCP, or any single provider — we say “stay in public cloud” when that’s the answer, and we say “fully on-prem” when that’s the answer.
- Engineers, not consultants. The engineers who run the repatriation engagement build the production platforms afterwards. The implementation effort estimates in the report are calibrated against work we have actually shipped — not against industry benchmarks.
- Open-source destination platform. We created Cozystack and co-maintain it — an open-source Kubernetes-native cloud platform (CNCF Sandbox project, CNCF Certified Kubernetes distribution). Where Cozystack fits the destination architecture better than the alternative, the report explains why with named architectural attributes. Where it doesn’t, we say so.
What the engagement looks like
Day 0 is a free 30-minute discovery call that fixes the scope. Days 1-13 (or 1-27) run four parallel workstreams with the cost-and-cloud-spend workstream emphasized, on daily async updates and three sponsor checkpoints. Day 14 (or 28) is a 60-90 minute executive readout against the written report — workload ranking, TCO model, destination architecture, cutover sequencing and Phase 2 roadmap. Full day-by-day methodology: Platform Readiness Assessment.
Companies running platforms built with Ænix
Hosting providers running Ænix Public Cloud Platform in production
Hosting providers running Ænix Public Cloud Platform in production. Repatriation-related work is written up on the case studies page, for example a Proxmox-to-Kubernetes move onto bare metal and GPU inference on owned hardware.
"Running Nuvolos on sovereign bare metal meant we needed hyperscaler-grade multi-tenancy without the hyperscaler. Cozystack delivered exactly that — isolated tenants, shared GPUs, KubeVirt for legacy workloads — and it's why we can promise our customers infrastructure control, not just a workspace."
Alexandru PopescuCEO, Nuvolos
Pricing and engagement scope
The repatriation-emphasized engagement runs as a Platform Readiness Assessment.
14-day (focused TCO + repatriation)
TCO modelling depth, workload portfolio ranking, destination architecture options, cutover sequencing for top-priority workloads. On request
28-day (full repatriation program)
Adds vendor shortlisting (compute / storage / network / observability), proof-of-concept scoping for 1-2 priority workloads, multi-BU stakeholder interviews, complete Phase 2 implementation roadmap. On request
Fixed-price. Single invoice. Mutual NDA at kickoff. Phase 2 implementation cost: assessment fee credited subject to scope.
We accept RFI / RFP through standard procurement channels; EU contracts are with AENIX s.r.o. (Czech Republic).
Start with a 30-minute discovery call
We confirm fit, identify the workloads worth moving, and name the 14-day or 28-day variant.
Or read more:
- Reverse cloud migration playbook — the long-form playbook
- Cloud cost optimization — adjacent FinOps trigger
- Platform Readiness Assessment — the engagement methodology
- Cozystack — the platform we typically recommend as repatriation destination
Ænix created Cozystack — a CNCF Sandbox project, CNCF Certified Kubernetes distribution, OpenSSF Best Practices — and co-maintains it. We run cloud-repatriation engagements and platform-engineering programmes.