Operations | Monitoring | ITSM | DevOps | Cloud

Your engineers have agents running. Not one agent, but several, spread across the team. Some run in a terminal on a laptop, some are wired into your CI jobs, and some live inside whatever coding tool each person prefers. Each one got set up separately, by whoever needed it, in whatever way worked that week. That is the state most teams are in right now. Code stopped being the slow part a while ago.

Somewhere in the last year, your team's code output went up. Pull requests are opened faster. The backlog of small fixes and routine changes started clearing quicker than it used to. If delivery still feels roughly as slow as it did before, that's what happens when you speed up one part of a process without touching anything downstream of it.

At some point this year, you likely approved a request to expand AI coding tool access across the team. The pitch was straightforward: engineers write code faster, the team ships more, the investment pays for itself. The first half happened. Engineers are writing code faster. If you're now being asked whether the investment paid off, and you're finding the honest answer is more complicated than a yes, you are not alone, and you have not been sold something broken.

Several platforms now ship agents capable of investigating problems, proposing fixes, and deploying, with real permission models and sandboxing behind them. This is a genuine engineering achievement, not just a demo.

Two Upsun Cloud customers, two very different starting points. Easypara needed to stop losing revenue to outages. ROLLIN needed to stop losing time to manual compliance checks on regulated client work. Here's how each one solved it.

Upsun Dispatch is generally available to the public as of today. Our previous article explains what it is and why we built it. This round, we take you into the details of how it works, the primitives it consists of, and the functionality available right away. You'll also get a glimpse of our roadmap at the end of the article.

Most of what runs on a modern platform is built to stay up. Applications serve requests, workers process queues, and managed services keep databases and caches available around the clock. But a meaningful share of the real work does not fit that always-on shape.

One multinational running on Upsun operates more than 400 websites. Each subsidiary has its own sites, its own team, its own release schedule, and its own local requirements. What they share is one infrastructure control layer: the same access model, the same encryption defaults, the same activity records, the same region and backup policy on every project. Adding the 401st site does not add a 401st set of infrastructure controls for someone to review.

Somewhere in every compliance program is a person who spends the week before an audit pulling logs out of several different systems, reconstructing who had access to what, and hoping the screenshots match what the auditor actually asks for. None of this work makes the system more secure. It just makes the existing security visible to someone who's checking. That gap, between the controls that are actually in place and the evidence that proves it, is where most audit prep time goes.

GitHub's research found that developers using Copilot completed tasks 55% faster than those who didn't. Tools like GitHub Copilot and Cursor, powered by large language models such as Claude or GPT, are designed to automate the tedious parts of programming so engineers can focus on harder, more creative problems. With this. new repos spin up every week. The promise is being kept. But where are the products?

Ask a compliance team where their EU customer data lives, and most will point confidently at a dashboard showing a Frankfurt or Dublin region. Ask their legal counsel whether that data is beyond the reach of a foreign government demand, and the confidence usually drops. Those are two different questions. Since 12 September 2025 there has been a dated EU obligation that turns on the second one rather than the first.

Before he joined Upsun, Andrew Kester spoiled the biggest sale of a client's year. He was one of two or three web developers at a creative agency that did branding, logos, print, and websites. A design boutique was about to run its annual trunk show, and the discounts and featured brands were meant to stay secret until the reveal on Tuesday at noon. The client asked for a preview. The preview reached production.

A team ships at a steady pace for most of the year. Then an audit approaches, and delivery slows. Engineers get pulled off feature work to support the audit, producing the configuration exports, logs, and environment checks that the evidence depends on. The slowdown lasts as long as the audit does. It is tempting to read this as a team that needs to move faster or be bigger. It is usually neither.

As a product manager at Upsun with a computer engineering background, Kateryna Dvornichenko had spent months researching competing tools in the agentic development space, running tests, comparing features, and building a picture of where the market was heading. She realized the tools were impressive, but something kept standing out. "Collaboration was not the strong point of any of them," she says. "Everyone stays on their own machine with their own setup.".