Operations | Monitoring | ITSM | DevOps | Cloud

When was the last time you asked a developer if they actually use the platform you built for them, or whether they’ve found a faster way around it? We talk with companies every day who deal with this exact scenario. They spend months or even years building their IDP. Then a new project requires a stack or workflow that the IDP doesn’t support. The developer is under pressure to deliver, so they spin up their own solution. This is why most IDPs fail quietly.

By standardizing the unified configuration file, Upsun enables true cloud optionality, moving provider migration from a re-architect project to a data move project.

A customer asked me once, in the middle of a demo, "what is lorem ipsum?" That is the moment. The preview URL loaded. Every page rendered. The merge was clean, the build was green, the tests passed. And a customer I was trying to sell to was reading placeholder copy out loud on a shared screen. I've thought about that moment a lot. Not for the embarrassment, though I earned it. For what it told me about what a preview environment actually is, which is not what most of us think it is.

Before I worked in tech, I worked in logistics. I saw a specific pattern repeat itself at office supply companies over and over, until I could see it coming before the customer did. The pattern went like this. A small office supply company would sell paper and pens to local businesses. One day a customer asked, "can you deliver a box of paper?" The salesperson said yes, drove the box over in their car after work, and thought nothing of it. The customer told their friend.

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.

Last year, at the annual conference for an open source framework you've definitely heard of, I walked up to the founder in a room outside the main stage. He was hunched over his laptop, frantic. We've known each other for a few years. "What's going on? Is everything okay?" He looked up with the specific shade of white people only get when they realize they've made a big mistake.

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.