Deploy each application to the cloud and region that fits it best, without changing how you build or operate it.

AWS, Azure, GCP, IBM, OVHCloud and more. Deploy each application to whichever provider fits, using identical workflows across all of them.
Place each application in a specific region to meet performance, regulatory, or data residency requirements. Managed as part of your platform configuration through Git, not through manual infrastructure setup.
A regional edge proxy and HTTP cache at the entry point to every region. For global delivery, the managed CDN option provides 60+ points of presence with centralized cache and routing management.
One deployment pipeline across every provider. No custom tooling, no fragmented workflows.
Deploy workloads to specific regions to meet data residency requirements. Pin European data to OVHCloud Germany, US data to AWS Virginia, all from the same deployment pipeline.
Run applications in the regions closest to your users. Add edge caching for global delivery with 60+ points of presence, without managing separate infrastructure stacks.
Distribute your application portfolio across Azure, AWS, and more. Reduce provider dependency without fragmenting the workflows that keep everything running.
Security controls applied consistently across every cloud and region. TLS by default, network isolation, encrypted traffic, and auditable configuration changes. SOC2, ISO, GDPR and more.
One platform means one place to see where applications are running and what they cost. Centralized oversight via CLI, API, or console.
Portable configurations and repeatable workflows make disaster recovery possible across providers and regions. Build automated cross-cloud failover without rebuilding your platform model.
Upsun Cloud runs on AWS, Azure, Google Cloud and OVHcloud. You choose the provider and region when you create a project, and the docs list every region that's available.
Yes. You describe your app and its services in configuration files kept in Git, and Upsun Cloud builds and deploys them on AWS, Azure, Google Cloud or OVHcloud. The same configuration works across providers and regions, so running an app on another cloud doesn't mean building a new toolchain for it.
Not today. Upsun Cloud runs your applications in regions it manages on AWS, Azure, Google Cloud and OVHcloud, and it can't deploy into a cloud account your company owns. If you need workloads on a particular provider or in a particular region, you can choose that when you create a project.
Moving to another cloud means moving your Upsun Cloud project to a region on that cloud. You create a project in the new region, push the same code and configuration, copy your files and data across, then switch your DNS. Plan for a brief outage at the switch, as with any site relaunch.
Yes. Each Upsun Cloud project runs in the region you pick when you create it, so you can keep an app and its data on a specific provider in a specific location. To change region later, you move the project to a new region.
For many web applications, yes. Kubernetes gives you fine-grained control over how containers run, but your team has to set up, secure and maintain the clusters. Upsun Cloud builds and runs your containers from configuration in your Git repository, so there are no clusters to manage. The trade-off is less low-level control than running Kubernetes yourself.
Not by default, but you can add one. Upsun Cloud offers a managed Fastly CDN that Upsun sets up and runs for you, which you add by contacting sales. You can also connect a CDN you manage yourself, such as Fastly or Cloudflare. Every project also has built-in HTTP caching, which is on by default.