Upsun review

Upsun is a hosted, managed multi-cloud PaaS: a control plane that provisions infrastructure, runs builds and deploys applications from Git repositories. It sits between your repository and cloud infrastructure, automating deployment and application lifecycle tasks rather than acting as a library or a self-hosted server.

Application stacks, routing and service topologies are declared in repository YAML files, such as .upsun/config.yaml. Git branches and pull or merge requests can provision isolated environments that mirror application code and connected services. Teams can also declare managed data services, including PostgreSQL, Redis, MongoDB, Kafka and Elasticsearch.

Upsun Flex meters fine-grained container sizing; Upsun Fixed offers predefined resource tiers. The platform runs across AWS, Google Cloud, Microsoft Azure, OVHcloud and IBM Cloud, with 14 regions listed by the vendor. That makes it an infrastructure abstraction for teams that want Git-driven releases and managed services without operating the underlying platform themselves.

The main integration path is repository-based: configure the application and services in YAML, then connect a Git forge. The vendor lists GitHub, GitLab and Bitbucket, including cloud and self-hosted instances. Open-source CLI tools, SDKs and configuration libraries are maintained on GitHub, but the vendor does not name the SDK languages here; confirm SDK support and current installation instructions in its docs.

For automation, Upsun lists an open REST API, generic incoming and outgoing webhooks, custom Activity Scripts, and a Model Context Protocol (MCP) server. Activity Scripts have built-in integrations for HTTP and Jira. Other named integrations include Fastly CDN, Slack, PagerDuty, email alerts, Blackfire and New Relic.

The platform supports runtimes including PHP, Python, Node.js/TypeScript, Java, Go, Ruby, .NET, Rust and Elixir. Check the docs for the current runtime and framework matrix, CLI commands, API authentication and rate limits before building deployment automation around them.

The pricing page lists a 15-day free trial, but no free platform plan. Pay as you go starts with a €9 project fee and €10 per user per month. Each project includes 10 GB of egress, 500,000 ingress requests, 2.5 CPU-hours and 5 GB-hours of build resources monthly. The page shows EUR prices and publishes no USD conversion or annual rate. A Reddit announcement separately says Upsun Dispatch includes 20 agent-minutes per day on its Free plan; that is not a free plan for the broader PaaS.

Overages include €0.03/GB for egress, €1 per 100,000 additional ingress requests, €0.033 per build CPU-hour and €0.013 per build GB-hour. Disk costs €0.49/GB/month, backups €0.10/GB/month, and object storage €0.0833/GB/month with a 512 GB minimum. Managed service resources have separate rates and a minimum commitment. Standard support adds 10% of global spend; advanced and premium support cost more and require a 12-month term. Ask for a workload estimate before production; total spend depends on usage and service choices.

Upsun's core platform is proprietary commercial software. The vendor does not offer a self-hosted or on-premises version of its control plane. It does maintain open-source CLI tools, SDKs and configuration libraries, but that does not make the managed PaaS itself open source.

Application code and YAML configuration live in your repository, which gives you a route to retrieve those assets. The vendor does not publish specific data-export guarantees here; ask how to export databases, object storage, logs and other service data before adopting it. Moving application code is different from replacing platform-managed services, routing and deployment workflows. Those dependencies can make a migration more involved than moving a repository to another host. Treat managed databases and platform-specific configuration as potential lock-in points, and confirm what can be exported and in which formats.

The vendor lists DDoS defense, a web application firewall, automated TLS certificates, and SOC 2 Type 2, ISO 27001 and PCI DSS Level 1. It offers paid uptime options: advanced is 99.9% for an additional 20% of project value, and premium is 99.99% for 45%. Both require advanced support or higher and a 12-month minimum term. Confirm how the chosen SLA applies to the services and regions in your architecture.

Budget for egress, ingress, build resources, storage and managed-service commitments; the base allowance is limited and extra usage is priced separately. The vendor lists five cloud providers and 14 regions, but check availability and service-specific limits for your target region. A Reddit user trying to connect Route 53 described using a CNAME to the platform.sh production address and running into the apex-domain restriction on CNAME records. That is a DNS integration detail to resolve during cutover. The same thread reports confusion about the setup, not a platform outage.