DEV Community: Upsun

5 platform evaluation questions you are missing 🐘

Flora Brandão — Mon, 27 Jul 2026 12:51:18 +0000

It is easy to focus all your energy evaluating a platform for one custom application while ignoring the other three hundred apps in your stack. The questions that decide whether a platform choice ages well are rarely the ones that show up in the standard checklist.

Here is what you actually need to test before your next platform choice hardens into something difficult to change:

Check what percentage of your applications can actually run on the platform instead of sitting in unmanaged cloud accounts.
Ensure preview environments have data that matches production so reviewers can spot bugs before customers do.
Know exactly how long it would take to migrate if a customer asks you to run on a specific cloud or region.
Align your audit scope with your architecture diagram to avoid expensive gaps during compliance checks.
Standardize your workflow across teams so new engineers do not have to learn multiple deployment models.

Check out the full artcile to learn the thirty second test for each question and stop the multiyear migration projects before they start.

Five questions your platform evaluation is missing | Upsun

Avoid costly architectural mistakes. Discover five critical questions you need to ask during your next cloud application platform evaluation.

upsun.com

Stop trusting your preview environments 🛑

Flora Brandão — Mon, 27 Jul 2026 10:09:27 +0000

Your code passes the build and the preview URL looks great, but then your customer spots placeholder text during a live demo. The app branches nicely on every push, but the database is still stuck pointing at staging data or old fixtures.

Here is why your workflow is lying to you:

The UI layer renders correctly but operates on data that does not look like production.
Bugs survive review and break under real production scaling or history.
Upsun fixes this by cloning production data and services byte for byte in about a minute.
Reviewers get realistic data without looking at sensitive customer information.

Catch your data scaling bugs before your users do. Check out the link below to read the full technical write up.

Your preview environment is lying to you | Upsun

Code-only preview environments hide critical bugs until production. Learn how byte-for-byte data cloning gives you previews you can actually trust.

upsun.com

Stop losing hours to broken staging environments 🛠️

Flora Brandão — Fri, 24 Jul 2026 10:02:36 +0000

You are mid-feature, working on something interesting, and then a Slack message arrives: staging is broken. You spend the next four hours fixing your CI/CD pipeline instead of coding. This context-switching is expensive and slows down feature delivery.

Treating your platform like a basic hosting account forces you to act as an infrastructure manager. Here is how to fix it structurally:

Define your entire stack declaratively using a single config file.
Let the platform take responsibility for everything below the application layer.
Eliminate environment drift by ensuring your staging environment exactly matches production.

When your infrastructure stops asking for attention, you can finally focus on the application you are actually there to build.

Check out the full article to see how a single configuration file changes the division of labor.

Why your staging keeps breaking | Upsun

Staging breaks when runtime versions and services drift between environments. See how one config file makes environment debugging disappear for good

upsun.com

Escaping the sticky cloud ecosystem ☁️

Flora Brandão — Thu, 23 Jul 2026 14:56:37 +0000

Cloud providers sell ecosystems designed to keep you locked in as a tenant with no move-out rights. Adopting proprietary databases, specialized serverless runtimes, or provider-specific IAM policies makes moving exponentially expensive.

True cloud strategy is about having the freedom to move when you need to. By standardizing your infrastructure layer, you can take back control:

Decouple your architecture from proprietary traps.
Shift migration from a high-risk overhaul to a predictable data move task.
Use a unified configuration file that remains constant across providers.
Test production-perfect clones in your target environment before switching.
Save senior engineering capacity from the massive overhead of managing custom platforms.

Keep your team focused on building features rather than managing divergent cloud consoles.

Check out the full blueprint to see how to standardize your stack:

The cloud optionality blueprint to end lock-in | Upsun

Discover how standardizing your stack with a unified configuration file enables true cloud optionality and ends vendor lock-in without the Kubernetes tax.

upsun.com

Why your multicloud architecture is probably theater 🎭

Flora Brandão — Thu, 23 Jul 2026 10:07:55 +0000

Most teams silo separate workloads on separate providers with unique toolchains. Moving anything between them means starting from scratch. That is not portability. That is just redundancy with extra operational weight.

True portability means your application configuration travels with your code. Here is how to achieve it:

Write infrastructure configuration in version controlled files that travel with your code.
Describe what your application needs rather than provider specific commands.
Handle provider and region selection at the platform level.
Store data in formats that can be migrated without a bespoke project.

This separates the where from the how. Engineers only need to understand one configuration interface for major providers like AWS and Google Cloud. You configure the application once and choose the provider independently.

Check out the article to read the full technical write up on achieving true cloud portability.

Cloud portability: what it is and how to achieve it | Upsun

Learn how true cloud portability allows you to move applications across providers without reconfiguration. Stop vendor lock-in with Git-driven infrastructure

upsun.com

Stop pitching ideas with boring slide decks that engineering teams just wince at 🛠️

Flora Brandão — Wed, 22 Jul 2026 14:30:05 +0000

Most product managers and marketers are told to learn to vibe code to make ideas tangible, but managing separate project folders and manual cloud configs is a grind. You can skip the setup headache by keeping your tools, templates, and principles in a single project directory. Pairing an agentic coding tool with a centralized dashboard allows you to spin up functional prototypes quickly without getting bogged down in infrastructure.

Here is how to optimize the workflow:

Pick one folder for your template, dashboard, and every proof of concept so the AI retains all past context.
Frame your initial prompt like a technical product brief by outlining explicit guardrails and architectural tradeoffs.
Deploy the entire system together to a cloud application platform using an MCP server to generate shareable URLs instantly.
Structure your dashboard with a dedicated tab detailing existing primitives and what actually needs to be built to earn engineering trust.

Want to see the exact setup steps and prompts? Check out the full walkthrough to start shipping your own proofs of concept.

Ship a POC in an afternoon with Claude Code | Upsun

Learn how to use Claude Code and Upsun to go from idea to deployed POC in an afternoon - no DevOps experience needed

upsun.com

Stop paying the invisible infrastructure tax 🐢

Flora Brandão — Tue, 21 Jul 2026 14:05:03 +0000

When shipping speeds drop, the gut reaction is often to demand more headcount. But adding more developers to a broken process just creates a longer queue of people waiting on staging environments. The real culprit is an invisible infrastructure tax that quietly kills velocity during handoffs.

Here is what the friction actually looks like when you map it:

Teams spend days of full-team effort just standing up infrastructure and pipelines before writing a single line of product code.
DevOps talent is scarce, and throwing headcount at inherited tech debt burns budget without moving the ship date.
The friction is treated as a normal part of the development lifecycle rather than a fixable bottleneck.

The fix is moving the environment logic out of your team's day and into a standardized platform layer. By eliminating this drag, developers can focus entirely on writing code and shipping features faster.

Why your ecommerce dev team ships slow | Upsun

Are your developers stuck managing staging queues and pipelines? Learn how Upsun preview environments accelerate ecommerce development velocity.

upsun.com

Why code review is not infrastructure validation 🛠️

Flora Brandão — Mon, 20 Jul 2026 14:08:34 +0000

AI tools can check your code syntax all day, but they are completely blind to infrastructure context. When an AI agent auto-approves a low risk pull request, it ignores whether the application actually runs in a production environment.

Here is why text only reviews fail us:

Syntax is not state. AI catches logic errors but misses connection timeouts or failed schema migrations.
Traditional staging environments are rarely identical to production, which is exactly where regressions live.
While language models are probabilistic and prone to hallucination, a container build is deterministic.

By defining your stack in a unified configuration file, Upsun acts as the ground truth layer. It triggers instant, data complete preview environments for every branch using copy on write clones. This ensures your infrastructure validates system wide state before execution.

Check out the full technical article to see how to end review theater:

Why code review is not infra validation | Upsun

Stop relying on "looks good to me." use upsun to validate ai-generated code against byte-level clones and ensure true production-readiness for every pr.

upsun.com

The hidden cost of scaling ecommerce on hyperscalers 💸

Flora Brandão — Fri, 17 Jul 2026 14:28:50 +0000

Running a major ecommerce campaign only to be greeted by an unpredictable cloud bill is a massive headache. Traditional hyperscaler pricing models often penalize growth due to unpredictable egress fees and unbounded auto-scaling.

Here is why ecommerce workloads break predictable pricing:

Autoscaling spins up additional compute instances without natural business-logic limits.
Data egress fees add up quietly and create significant charges across regions.
Database capacity grows fastest during campaigns and is harder to scale down quickly.
Multi-service architectures create cost fragmentation and high operational overhead.

The fix is shifting from a fragmented list of services to a resource-based provisioning model. By using a unified management platform like Upsun to abstract hyperscaler complexity, you can tie costs directly to environment resources like CPU, RAM, and disk with defined ceilings. This turns infrastructure costs into a predictable business decision before the flash sale even begins.

Check out the full article to learn how to keep your budget fully under control:

The hidden cost of scaling ecommerce | Upsun

Hyperscaler pricing penalizes e-commerce growth. Discover how to manage scaling costs and avoid expensive over-provisioning during peak events.

upsun.com

Why Emacs is still my interface to my computer 💻

Flora Brandão — Thu, 16 Jul 2026 14:00:00 +0000

Managing a modern development setup often feels like a fragmented mess of jumping between separate text editors, Git clients, terminal windows, and AI tools. Keeping these disparate utilities in sync is a constant mental tax that slows down your daily flow.

Here is why keeping Emacs at the center of the workflow solves this:

The problem: Developers waste time switching context between editors, command-line interfaces, and separate project tools.
The fix: Emacs acts as a single, consistent interface for editing, Git integration with Magit, active terminal emulation, and dedicated coding agents.
Why it matters: You get a unified environment where everything from project configuration to throwaway workflows lives in one window.

Check out the full write-up to see how a unified interface can streamline your daily development workflow:

Why Emacs is still my interface to my computer - Upsun Developer

Why I still use Emacs every day: one consistent interface for editing, Git with Magit, terminals, a Claude Code agent per project, and the rest of my computer.

developer.upsun.com

Killing the two year feature freeze: modernizing banking tech in isolation 🛠️

Flora Brandão — Thu, 16 Jul 2026 10:34:05 +0000

Forcing your engineering team into a two year feature freeze for a "Big Bang" cloud migration is a great way to watch competitors pass you by. When you freeze releases, you cannot ship customer value and you risk falling behind on evolving compliance requirements like DORA.

Traditional migrations compress all your risk into a single cutover window. We need a better way to modernize without standing still.

Here is how we can escape the migration trap:

Build isolated, production-like preview environments directly from Git branches.
Run legacy code against new cloud configurations to catch bugs early.
Inherit key infrastructure-level compliance controls instead of rebuilding them from scratch.
Keep shipping features and maintaining operational resilience throughout the entire migration.

By testing every migration step in isolation, you keep your development momentum alive.

Check out the full article to see how preview environments keep your workloads moving.

Bank cloud migration without a feature freeze | Upsun

Escape the big bang migration trap. Learn how financial institutions use preview environments to modernize legacy systems without a feature freeze.

upsun.com

Does code even matter anymore? Finding value in the age of cheap code 💻

Flora Brandão — Wed, 15 Jul 2026 10:14:06 +0000

AI has made writing and discarding code cheaper than ever, leading many to think it matters less. Yet, engineering velocity, code reviews, and debugging still depend entirely on the quality of that code.

Here is how we are rethinking the value of code:

The problem: Naive approaches to AI generation make code cheap to write, which can lead to treating it as entirely disposable.
The fix: We need to shift focus from just writing raw code to building actual software.
Why it matters: High quality code still determines how fast we can review, debug, and ship stable systems.

Check out the full write-up to explore why code quality matters more than ever:

Code matters less than ever, and more than ever - Upsun Developer

AI made code cheap to write and cheap to throw away, so it matters less than ever. It also matters more, because debugging, reviews, and velocity all depend on it.

developer.upsun.com