Operations | Monitoring | ITSM | DevOps | Cloud

Hosting an MCP (Model Context Protocol) server on Upsun lets AI IDEs like Cursor, Codex, Claude Code and Windsurf reach real infrastructure context (database schemas, service logs, environment variables), closing the gap between local coding assistants and your cloud environment.

For most IT leaders, multicloud didn't arrive as a decision. It arrived as a fait accompli. A team chose AWS for one workload. Azure came in through a Microsoft enterprise agreement. A SaaS acquisition brought its own cloud dependencies. A DR requirement pointed to a second region with a different provider. Nobody declared a multicloud strategy; the organization just became one. Today, 87% of organizations run a multicloud strategy, balancing an average of 2.6 public cloud providers simultaneously.

Application autoscaling has existed for years. Database autoscaling has lagged behind. Today, that changes on Upsun. Managed PostgreSQL and MariaDB read replicas now autoscale, joining worker autoscaling in production since March 2026. Apps, workers, and managed databases all autoscalead replicas saturate first, connection pools max, someone getse on one platform - natively, without a third-party database engine or a Kubernetes layer to operate. Three operational headaches just disappeared.

As Staff Engineers and Principal Architects, most of us have spent years thinking about long-term system health. We are considerate of the company’s business objectives and strategy, accumulation of technical debt, and operational risk. For us it is not about whether code works today, but whether the engineer who inherits it in three years will be able to understand what it was trying to do and why. That's what makes a codebase maintainable rather than just functional.

Database migrations are where the mock data problem shows up most clearly. A migration that adds an index to a table with 500 rows in the development database runs in milliseconds and passes every test. The same migration against a production table with 8 million rows locks the table for 90 seconds during peak traffic. Nobody saw it coming because nobody tested it against 8 million rows. This isn't an edge case.

There is a question a lot of engineering leaders are quietly sitting with right now: we have rolled out AI tools across the team, the developers seem faster, so why isn't more software actually shipping? It is a reasonable thing to consider. Pull requests are opening faster. Lines of code per sprint are up. The boilerplate that used to take full afternoons now takes minutes. By every local measure, the investment is paying off.

Standardizing the fleet: automated updates for multi-site management There's a specific kind of update that Drupal agencies and enterprise teams dread: a security release in something the whole fleet runs on, the PHP runtime, the database engine, or a shared service, with a patched version available now and a deadline attached. For a team managing a single site, moving to the patched version is an afternoon of work.

If you've shipped software in fintech, healthcare, or government, you probably know the specific dread of an upcoming compliance audit. Not because the software isn't secure, but because proving it is requires reconstructing a paper trail for decisions that were made in Jira tickets, Slack threads, and pull request comments over the last six months. The software is fine. The documentation of the software is the problem.

When we introduced Upsun Dispatch last week, we said we were building the platform layer for everything around the code. Today, you can apply to join as a founding design partner. Starting July 1, 2026, a number of engineering organizations will join us in prerelease. This is a selective, high-touch collaboration with teams who want to help shape what comes next. If you missed the introduction, you can catch up on Upsun Dispatch here.

The staging bottleneck: why your framework needs ephemeral preview environments There's a specific kind of Friday afternoon that frontend and backend developers both recognize. A feature is ready to test. Staging is occupied. Someone else pushed a half-finished migration to the shared database last Tuesday and it's been "almost fixed" ever since. You either wait or you merge blind and hope. Most teams treat this as a scheduling problem. It isn't. It's an architecture problem.