Operations | Monitoring | ITSM | DevOps | Cloud

Your preview environment is lying to you

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.

Your free credits are leading to a 30-person nightmare

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.

The cloud optionality blueprint: standardizing the stack to end vendor lock-in

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.

What happens when you delete everything? Three minutes, or thirty hours.

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.

Five questions your platform evaluation is missing

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.

Stop watching the looms: why the AI era belongs to infrastructure

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.

Anything but that cloud

"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.

Beyond the frontend: choosing between Vercel and Upsun for full-stack applications in 2026

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.

Why your ecommerce dev team ships slower than your competitors (and how to fix it)

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.