DEV Community: Upsun

Stop waiting on shared staging: Provision per-branch environments automatically 🚀

Flora Brandão — Thu, 24 Sep 2026 15:44:38 +0000

Shared staging servers are queues, not test beds. You push code and immediately wait for seed data to refresh, for someone to fix broken migrations, or for the server to free up.

The problem:

Shared environments accumulate everyone's half-finished changes and reflect no single developer's work.
Configurations quietly drift from production, causing tests to pass in staging and fail on release.

The fix:

Provision an isolated environment automatically as a direct byproduct of pushing a Git branch.
Build environments from the exact same single declarative configuration file used by production.
Promote the tested container image directly to production upon merging instead of triggering a rebuild.

Why it matters:

Ten active branches mean ten independent, production-aligned environments running in parallel.
Environments automatically tear down when branches close, removing manual cleanup and keeping costs down.

Check out the full article for a detailed breakdown of how to eliminate staging bottlenecks:

Turn every branch into a production-like environment | Upsun

Stop queuing behind shared staging. Git-native environment provisioning gives every branch its own full, production-aligned environment the moment it's pushed — no manual setup required.

upsun.com

Fixing multicloud chaos with policy guardrails ☁️

Flora Brandão — Thu, 24 Sep 2026 09:04:11 +0000

Running multiple cloud providers usually means managing separate consoles, disjointed identity models, and runbooks that silently drift out of sync.

The problem: Rebuilding deployment, monitoring, and compliance workflows for every new cloud provider fragments your tooling.
The fix: Separate your application configuration from platform provisioning, and write governance guardrails directly as code.
Why it matters: Your code and security rules travel together across any cloud without multiplying operational complexity or audit debt.

Check out the full article to see how to structure portable, policy-aware environments:

Portable multicloud environments with guardrails | Upsun

Deploy one YAML config across AWS, Azure, Google Cloud and more, with governance guardrails that travel with your app. Multicloud control, no lock-in

upsun.com

Stop multicloud sprawl before it ruins your on-call ☁️

Flora Brandão — Wed, 23 Sep 2026 14:24:51 +0000

When every cloud setup grows its own custom pipeline and runbook, operating model debt accumulates fast.

The grind:

Teams optimize for hosting capacity instead of delivery workflow
Separate cloud providers bring fragmented pipelines, audit processes, and dashboards
Duplicated operational overhead ends up costing more than the cloud bill

The fix:

Treat cloud providers as deployment targets sitting under one delivery layer
Define applications, declare policies, and establish workflows once
Keep the developer workflow identical regardless of where the workload runs

Why it matters:
Using a single, consistent delivery layer eliminates sprawl at the source and keeps your delivery process fast and auditable.

Read the full article for a practical walkthrough on fitting app delivery into a multicloud operating model:

Multicloud operating model: a practical guide | Upsun

Multicloud operating models fragment over time. Learn the four signs of sprawl and how a single delivery layer keeps governance and ops consistent

upsun.com

Why Let's Encrypt renewals fail 🔒

Flora Brandão — Wed, 23 Sep 2026 09:01:53 +0000

Failed certificate renewals are a classic engineering grind that can quietly break your site. The HTTP-01 challenge usually fails due to subtle routing and infrastructure misconfigurations.

Here is what breaks your renewals:

The problem: Forgotten AAAA IPv6 records, restrictive CAA policies, or CDN features like Cloudflare Bot Fight Mode blocking challenge requests.
The fix: Ensure your request path correctly forwards challenge traffic and set up early alerts for renewal failures.
Why it matters: Understanding how the HTTP-01 challenge moves through your stack prevents surprise downtime and saves you from emergency SSL debugging.

Check out the full technical write-up to learn more about troubleshooting certificate renewals:

Why Let's Encrypt certificate renewals fail - Upsun Developer

Certificate renewals fail for a handful of recurring reasons. Here's how the HTTP-01 challenge works and what breaks it, from IPv6 records to CDN rules.

developer.upsun.com

Stop spending hours on infrastructure YAML just to ship one feature 🛠️

Flora Brandão — Tue, 22 Sep 2026 14:21:59 +0000

You wrote the feature and it works locally. Then you spend the next two hours dealing with Terraform state drift, Kubernetes YAML sprawl, and cryptic IAM permission errors. None of this is your feature, but all of it blocks your deploy.

Here is why this infrastructure grind slows you down and how to fix it:

Terraform state files trigger merge conflicts, drift, and accidental resource replacements.
Kubernetes manifests require hundreds of lines of configuration for small microservices.
IAM policy scoping forces a choice between broken build pipelines and overly permissive access.
Centralizing infrastructure into a shared platform layer handles low-level provisioning automatically.
Developers can focus on business logic while environments stay consistent across every deploy.

Read the full article to learn how to streamline your app delivery without the infrastructure burden:

The infrastructure work you shouldn't own | Upsun

Terraform, Kubernetes, and IAM eat into feature time. See why a platform should own infrastructure so developers can focus on code

upsun.com

Choosing a tech stack for interactive AI apps 🤖

Flora Brandão — Tue, 22 Sep 2026 09:02:54 +0000

Coding agents completely changed how teams select a tech stack. The old grind of choosing tools based solely on how fast you can write code causes real headaches when you try to actually run interactive AI applications in production.

Here is how to approach stack selection today:

The problem:
Evaluating tools based on writing speed ignores operational reality.

The fix:
Focus on whether you can reliably run the app rather than just write it. Take a tour of 8 key ecosystems and eliminate bad options before making a choice.

Why it matters: Selecting a resilient ecosystem ensures your interactive AI app stays manageable as coding agents evolve.

Check out the full technical write-up to explore the ecosystem breakdown and selection criteria:

Which stack would you pick for an interactive AI app today? - Upsun Developer

Coding agents changed how new teams pick a tech stack. A tour of 8 ecosystems for interactive AI apps, and why "can we run it" beats "can we write it".

developer.upsun.com

Streamline your agentic workflows with Upsun Dispatch, for free 🎉

Celeste van der Watt — Thu, 17 Sep 2026 09:00:00 +0000

Upsun Dispatch™ is live! 🚀

Upsun Dispatch acts as the software factory for human-AI workflows. It provides an agentic software development lifecycle where workflows are the primitive. Agents and humans ship together with built-in structure, traceability, and cost transparency.

A workflow in Upsun Dispatch is a structured sequence of agent and human steps. This sequence runs the exact same way every time you trigger it. Avoid putting agents on individual laptops where output, cost, and context remain invisible. Upsun Dispatch runs workflows in a shared layer your whole team can see and execute. Every action taken by a human or an agent is logged and traceable. You can reference the llms-full.txt file to configure your models and environments.

This platform grew in the open with the teams experiencing the problem first. Today it is available to everyone.

Get started on Upsun Dispatch with the free tier. You receive 20 agent-minutes a day, no credit card, and no commitment.

Offloading heavy jobs: running tasks with on-demand containers ⚡

Flora Brandão — Thu, 10 Sep 2026 09:14:22 +0000

Running long, resource-hungry jobs directly in standard crons is a constant grind. Database imports and search reindexing can easily choke your environment and hog shared resources.

Here is how to offload heavy background work:

The problem: Long-running jobs strain resources and slow down standard cron execution.
The fix: Move heavy processes into on-demand Upsun task containers that are authorized and triggered by a lightweight cron.
Why it matters: Your core app stays fast, while heavy tasks get dedicated environment resources only when fired.

Check out the full technical write-up to see how to define, authorize, and trigger task containers for your stack:

Offload Heavy Jobs to Upsun Task Containers, Triggered by Cron - Upsun Developer

Move long, resource-hungry jobs out of your crons and into on-demand Upsun task containers. Learn how to define a task, authorize your app to trigger it, and fire it from a lightweight cron for database imports or search reindexing.

developer.upsun.com

Migrating apps without rewriting code 🚀

Flora Brandão — Tue, 08 Sep 2026 14:44:41 +0000

Application migrations often stall because rebuilding deployment pipelines and environment setups takes months of tedious work. Your application code is rarely the problem, but rebuilding the surrounding infrastructure is a massive headache.

Here is how you can simplify the process:

Declare your runtimes, services, and routes once in a single configuration file stored in your repository.
Push a Git branch to automatically launch an isolated environment for testing.
Sync real production data into your branch to validate changes safely before merging.
Keep your existing application logic, CLI tools, and CI pipelines intact without refactoring.

Testing happens on a dedicated branch, so you never have to test in production or risk live site downtime.

Check out the full article see the step-by-step workflow:

Migrate your app to Upsun without a rewrite | Upsun

Migrating to Upsun doesn't mean rewriting your app. Add one config file, push a branch, test against real production data, and merge only when it works.

upsun.com

The real cost of cloud lock-In ☁️

Flora Brandão — Mon, 07 Sep 2026 14:40:51 +0000

Cloud dependency rarely starts with a massive strategic decision. It accumulates quietly through thousands of reasonable technical choices until switching becomes a multi-million dollar constraint.

The core issues:

Egress fees consume 10 to 15 percent of total monthly cloud budgets
AI workloads accelerate lock-in due to provider-specific GPU hardware and proprietary tooling
Enterprise migration costs range from $500,000 to millions when leaving a vendor

The fix:

Standardize on portable environment definitions at the delivery layer
Build pipelines using open standards rather than vendor-specific APIs
Maintain true architectural optionality before proprietary dependencies stack up

Why it matters:
Portability gives your team real leverage during contract renewals and prevents pricing changes or service deprecations from disrupting your roadmap.

Check out the full technical artcile for the complete breakdown and migration reference architecture:

The real cost of hyperscaler dependency | Upsun

AWS, Azure and GCP hold 60% of cloud infrastructure. See how hyperscaler dependency erodes your leverage — and what real portability requires

upsun.com

Upsun is recognized in the Gartner® Magic Quadrant™ for Cloud-Native Application Platforms

Flora Brandão — Mon, 07 Sep 2026 10:30:59 +0000

We have done it again. 🎉

For the third consecutive year, Upsun is recognized in the Gartner® Magic Quadrant™ for Cloud-Native Application Platforms.

We believe this recognition reflects the platform you rely on every day to ship software, manage infrastructure, and keep pace with the demands of modern development, now including AI-powered workflows and agentic software delivery.

Unlock critical insights to future-proof your cloud strategy with the 2026 Gartner® Magic Quadrant™ for Cloud Application Platforms report:

Upsun acknowledged for its Ability to Execute and Completeness of Vision | Upsun

Upsun acknowledged for its Ability to Execute and Completeness of Vision for third consecutive year in Gartner® Magic Quadrant™ for Cloud-Native Application Platforms.

upsun.com

How exposed is your stack to cloud lock-In? ☁️

Flora Brandão — Fri, 04 Sep 2026 14:14:22 +0000

Maintaining separate CI/CD pipelines for every cloud provider and manually gathering audit evidence across consoles is a painful engineering grind.

The problem:
Cloud dependency concentrates in four places and slows down every change: - Applications tightly bound to provider-specific services

High friction and long timelines for planned migrations
Inconsistent delivery workflows across different teams
Non-portable governance and audit controlsThe Fix:

Consolidate at the delivery layer to fix the root cause:

Store one portable application definition in Git
Declare policy as code at the platform layer
Use a single delivery workflow for every target cloud

Why it matters:
You lower switching barriers and make provider choice a downstream decision without rewriting your whole architecture.

Read the full article to score your own cloud exposure:

Multicloud exposure assessment for IT leaders | Upsun

Assess how exposed you are to cloud lock-in in about 15 minutes. Score four areas of multicloud dependency and see which risks to address first

upsun.com