- English
 - français
 - Deutsche
 
- Contact us
 - Docs
 - Login
 
If your week keeps evaporating into incidents, flaky staging, and hand-built scripts, you are not alone. Many developers spend far too much time searching for answers and wrestling with tools, rather than building features. In Stack Overflow’s 2024 survey, 61 percent said they spend more than 30 minutes each day just searching for solutions.¹ Deloitte notes that time spent on configuration, tool integration, and debugging directly crowds out feature work.² SRE leaders even set a hard cap on toil because they know operational busywork expands to fill the day.³
This practical guide was created to help you get closer to what you actually want to do: ship ideas, improve user experience, and eat dinner on time.
It is easy to default to building your own infrastructure and development platform. It feels faster to spin up a cluster, wire a pipeline, and add a logging agent. Then reality shows up:
You do not need another dashboard. You need a calmer path to production.
Upsun uses a single configuration file in your Git repository to describe your apps, services, build hooks, deploy hooks, and routes, so your pipeline is versioned alongside your code. For this reason, each branch gets a live, production-grade preview environment with cloned services and code to ensure safe and realistic testing.
To learn more, read how to configure your project and explore environment management product guide.
Creating a new branch can spin up a complete clone of your infrastructure, including your application, services, caches, data, and storage, so you can test against the same shape of data and services as if it were production. When you need to protect sensitive data, Upsun also supports database sanitization workflows out of the box. See sanitization concepts and a PostgreSQL example.
# .upsun/config.yaml
applications:
  app:
    type: "python:3.11"
    relationships:
      database: db:postgresql
    hooks:
      deploy: |
        if [ "$PLATFORM_ENVIRONMENT_TYPE" != "production" ]; then
          ./scripts/sanitize_db.sh  # mask PII for previews
        fi
services:
  db:
    type: postgresql:15
Profiling and metrics are included, allowing you to identify and resolve performance bottlenecks before users complain about slow load times or broken features. Full access to Blackfire for PHP and Python projects is included, along with additional continuous profiling views for other runtimes. Explore Upsun observability and Blackfire details.⁴
If you are considering building your own platform with managed hosting against Upsun, here is a fast, developer-first view:
If you want to dig deeper, Upsun’s YAML overview is a quick tour of what you can standardize.
Running Adobe Commerce or Magento at scale magnifies these issues: realistic testing, safe data, and predictable operations. Adobe’s own managed services guidance outlines shared responsibilities across performance, security, and compliance, such as SOC 2 and PCI.⁵ Upsun’s preview environments help teams working on extensive catalogs and promotion engines validate changes on real data shapes before peak traffic.
Cost. Fewer bespoke scripts and fewer escalations make spending more predictable.
You trade firefighting for focus. You define infrastructure once, preview every change on the real shape of production, and keep performance visible. That is how you get back to what you want to do: building.

