3 min Reading Time<\/p>\n
The cloud promised lower costs, unlimited scalability, and operational simplicity. For many workloads, that\u2019s true. For some, it isn\u2019t. An increasing number of companies are bringing certain workloads back – not out of cloud skepticism, but based on cold, hard math. Cloud repatriation isn\u2019t a step backward; it\u2019s a sign that cloud strategy is maturing.<\/strong><\/p>\n The most prominent example: 37signals (Basecamp, HEY) left AWS and saved $7 million over five years, according to CTO David Heinemeier Hansson. The reason? Stable workloads with predictable demand and high data volume – exactly the profile where cloud costs lose out against dedicated hardware.<\/p>\n The math is simple: A server with 128 GB RAM and 2 TB NVMe costs a one-time \u20ac5,000-\u20ac8,000 and runs for five years. The cloud equivalent costs \u20ac500-\u20ac1,000 per month – amounting to \u20ac30,000-\u20ac60,000 over the same period. With stable demand, owning hardware is five to ten times cheaper.<\/p>\n Add data egress fees: AWS charges $0.09 per GB of outbound traffic. Companies transferring terabytes per month pay thousands – just for networking.<\/p>\n Stable baseline workloads<\/strong> with predictable demand: databases, build servers, monitoring systems. Here, the cloud offers no scaling advantage – only ongoing costs.<\/p>\n Data-heavy workloads<\/strong> with high storage and transfer volume: video encoding, big data analytics, backup systems. Data egress fees make the cloud disproportionately expensive.<\/p>\n Latency-sensitive workloads<\/strong> that must run close to the data source: edge computing, IoT processing, local AI inference.<\/p>\n Unsuitable candidates include: variable workloads (seasonal business), global applications (multi-region), startups in growth phase (unpredictable scaling), and teams without ops expertise.<\/p>\n Repatriation isn\u2019t free. Total Cost of Ownership (TCO) includes: hardware procurement, colocation costs (rack, power, cooling, network), personnel for operation and maintenance, software licenses (VMware, backup, monitoring), and one-time migration expenses.<\/p>\n The critical factor is personnel: a qualified Linux administrator or network engineer costs \u20ac70,000-\u20ac100,000 per year. Companies without existing ops capacity must factor in these costs. 37signals already had an established ops team – that\u2019s not a given.<\/p>\n The reality for most companies: neither fully in the cloud nor fully on-premise, but a hybrid model. Stable baseline workloads on dedicated hardware (colocation or on-premise), variable workloads and burst capacity in the cloud.<\/p>\n Kubernetes makes this hybrid approach practical: workloads are portable between on-premise and cloud. Tools like Rancher, Anthos, and Azure Arc enable unified management across both environments. GitOps with ArgoCD deploys the same code everywhere.<\/p>\n Three questions determine the answer: How variable is the demand?<\/strong> Variable load \u2192 cloud. Stable load \u2192 on-premise feasible. How high is the data volume?<\/strong> High egress volume \u2192 on-premise more attractive. Low volume \u2192 cloud costs acceptable. Do we have ops expertise?<\/strong> No ops team \u2192 cloud (your cloud provider is your ops team). Experienced team \u2192 repatriation becomes calculable.<\/p>\n The decision should be workload-specific, not blanket. Even 37signals didn\u2019t move everything out of the cloud – only the workloads where the math was clear.<\/p>\n It\u2019s a growing trend, but not a mass movement. Most companies optimize their cloud usage rather than return completely. Partial repatriation – bringing back individual workloads – is more common than full cloud exits. Analysts estimate that 10-15% of cloud workloads will be repatriated in the medium term.<\/p>\n<\/details>\nWhy companies are bringing workloads back<\/h2>\n
Which workloads are suitable for repatriation<\/h2>\n
The hidden costs of returning<\/h2>\n
The hybrid compromise<\/h2>\n
Decision framework: Cloud, Hybrid, or Repatriation?<\/h2>\n
Frequently Asked Questions<\/h2>\n
Is cloud repatriation a trend or a niche?<\/strong><\/summary>\n