Operations | Monitoring | ITSM | DevOps | Cloud

Key takeaway: Real cloud strategy isn't about running the same workload everywhere at once; it’s about the freedom to move when you need to. By standardizing the unified configuration file, Upsun enables true cloud optionality, moving provider migration from a re-architect project to a data move project.

Years back I sat in on a platform evaluation with a customer who spent forty-five minutes of the meeting focusing on one thing: their custom PHP content management system. They had opinions about the CMS. Strong opinions. They had benchmarks, a migration plan, a proof of concept. They had a diagram. They had questions about the deployment pipeline for this CMS that were, for a single application, more thoroughly considered than most organizations' entire infrastructure strategies.

I live in Manchester, England now. I moved here from Texas last summer (which is its own story), but the thing I wasn't prepared for is how the Industrial Revolution isn't history here. It's the city itself. And if you're American like me, you might need to hear this: the Industrial Revolution didn't start in the US. It started here. Manchester is where the modern world was born. You see it everywhere. The old cotton mills converted into apartments.

Key takeaway: AI agents and RAG pipelines only reach production-grade accuracy when they are developed against byte-level clones of real production data. Without environment parity, the "repro gap" leads to inevitable AI failure.

"Anything but that cloud." I asked why. "Our biggest customer is a giant retailer," he said. "That hyperscaler's parent company is the retailer's biggest competitor. So our customer refuses to do business with anyone who uses that cloud. We use that cloud, we lose our biggest customer. Full stop." That was the entire conversation about cloud choice. It wasn't a technical preference. It wasn't a pricing optimization. It wasn't a sovereignty concern.

If you're building a modern web application in 2026, Vercel is almost certainly on your shortlist, and probably near the top of it. The developer experience Vercel pioneered for Next.js and the frontend ecosystem around it is a real achievement. Push a branch, get a preview URL, ship. It works, it's fast, and an entire generation of frontend teams have built their workflow around it. This article is not here to argue with any of that.

Key takeaway: Development velocity in e-commerce is often throttled not by headcount, but by invisible infrastructure friction that forces developers to spend time on environment management and deployment pipelines instead of shipping revenue-generating features. Ecommerce teams rarely think they have an infrastructure problem.

Key takeaway: Upsun eliminates the need for code freezes during ecommerce migrations by using instant, data-complete preview environments to validate replatforming efforts against production-grade data without interrupting the live store. Ecommerce replatforming is one of the highest-stakes decisions an online retailer makes, and for most, the biggest risk is what happens to revenue during the migration.

Code review and infrastructure validation are distinct problems. While AI can review syntax, only an active, data-complete environment can validate system-wide state. Upsun provides the unified configuration file needed to turn "looks good to me" into verified production-readiness.

This post is also available in German and in French. Tracking environmental impact can be fragmented, time-consuming, and disconnected from operational data. Beyond simply checking ESG reporting boxes or making sure your company is CSRD compliant, actively monitoring environmental impact is the foundation for building an effective sustainability strategy. At Upsun, we know that measuring progress is the first step toward improvement.