Operations | Monitoring | ITSM | DevOps | Cloud

Migrate your app to Upsun Cloud without a rewrite

Application migrations stall for a predictable reason: the demanding part is rarely the application code itself. It is the infrastructure around it: the deployment logic, pipeline, and environment configuration that has to be rebuilt. That surrounding work is what turns a migration into a multi-month project, and it is why teams stay on infrastructure that no longer serves them. Upsun Cloud reduces migration to a much smaller task.

Turn every branch into a production-like environment, automatically

You push a branch. If your team is like most, that branch now waits: for the shared staging server to free up, for someone to remember to refresh the seed data, for whoever broke staging last to fix it. By the time you actually test your change, you're testing it in an environment that's drifted from production in ways nobody fully tracked. The alternative isn't a better staging server. It doesn't need one.

How task containers give AI agents real infrastructure without idle cost

Infrastructure for AI agents usually forces a choice between two bad options. A sandbox is safe but blind, cut off from the data and services that would make the agent's output useful. Full access means paying to keep a container idle between runs, waiting on a prompt that might not arrive for hours. Task containers, which Upsun released on August 12, 2026, are built to avoid that choice. A task container is a single-purpose container defined in a project's.upsun/config.yaml file.

Stop paying for compute that does nothing six days a week

Most teams are paying for a container that stays awake all week to run one job on Friday. Task containers are the fix: they spin up on an API call, run exactly one command, then remove themselves. In this Product Highlights conversation, Corey Dockendorf, a senior solutions architect at Upsun with most of 25 years in tech behind him and five at the company, breaks down how ephemeral task containers cut idle spend and give AI agents production context without production access. His take: "They spin up when they're triggered directly by an API call.

Why AI agents don't need infrastructure running 24/7

AI agents don't need a server sitting there while they wait for the next prompt. They need infrastructure that shows up, does the job, and disappears. In this Product Highlights conversation, Nicolas Gommenginger, director of product at Upsun with more than four years leading the platform's core functionality, breaks down Upsun's newest primitive: task containers. His take: "What really triggered us to go ahead and implement it is the rise of AI agents, because tasks are something ideal for running them." We get into.

Trust you can verify: security assurance for the AI era

When you choose a cloud platform, you're entrusting a provider with sensitive business information, customer data, critical applications, and a growing share of your operational resilience. Increasingly, you are also entrusting it with AI. And that changes the questions you should be asking. Marketing claims cannot answer these questions. Independent evidence can. Here is what that evidence looks like at Upsun and why it matters to your next supplier review.

The infrastructure work you should not have to touch just to ship a feature

You wrote the feature. It works locally. Then you spend the next two hours on things that have nothing to do with the feature: a Terraform plan that wants to replace a database you didn't touch, a Kubernetes manifest that needs a new ingress rule, an IAM policy that's one permission short of what the deploy needs. None of this is the job. All of it is the job today. Here's what that list actually looks like, and why none of it should be sitting on your plate.

Your preview environment is lying to you without production data

A preview link with an empty database tells you almost nothing about a content-managed site. Most teams find that out the expensive way, in front of a client. In this Product Highlights conversation, Andrew Kester, a senior cloud support engineer at Upsun whose team handles everything from product questions to sites under active attack, twenty four hours a day, every day of the year, breaks down why cloning services and data into every environment is the feature he would have paid for at his old agency job. His take: "You click a button. We clone your services. We clone the data." We get into.

What build-versus-buy actually looks like in agentic engineering

Most build-versus-buy debates assume you're choosing once, at the start, and living with it. Agentic engineering doesn't work that way. The decision shows up at every layer of the stack, and the teams getting it right aren't the ones who picked "build" or "buy" as a philosophy. They're the ones who know which layer is which.

Migration feasibility checklist for IT leaders

Feasibility is a prioritization question that comes before strategy. The five-question check produces a "now, later, or fix blockers first", before anyone touches a target architecture. Strategy earns its place once feasibility returns "now." Feasibility comes before strategy. Before anyone designs a target architecture, builds a runbook, or commits to a multicloud operating model, the question is whether the migration is the right move now, and what would make it fail.