Upsun (Platform.sh) Lets You Pick an EU Region — Its Own Docs Show Most Run on AWS, Azure, or Google Cloud

If you evaluated Platform.sh in the last few years, the name you're looking for now is Upsun — the company rebranded in September 2025, and the old platform.sh domain redirects straight to upsun.com. Upsun is one of the more enterprise-credible names in the EU-adjacent PaaS space: founded in Paris in 2010, SOC2/ISO27001/PCI-certified, ten years of production traffic behind it. It also gives you a region picker with several EU-labeled data centers. What its own documentation doesn't advertise on the pricing page is which cloud each of those regions actually runs on — and for most of them, the answer is a US hyperscaler.

What Upsun actually is

Upsun is a config-as-code cloud application platform: you define your app, its services, and its routes in a single .upsun/config.yaml file (generated by upsun init), and Upsun builds and deploys it across your choice of underlying infrastructure. Per Upsun's own developer documentation, a minimal Node.js config declares the runtime (type: 'nodejs:22'), build hooks, service dependencies like type: 'postgresql:16', and route mappings — all before your first deploy. That's a different model from an auto-detected, zero-config deploy: it's explicit infrastructure-as-code, which teams with an existing DevOps practice generally want and teams shipping a first side project generally don't.

The platform's own positioning backs that up: Upsun markets itself as serving "over 6,000 enterprise clients and 16,000 developers" since 2015, with e-commerce and SaaS platforms named as core use cases — the kind of teams that already have a platform engineer reading YAML for a living.

The regions story: "EU region" and "EU infrastructure" aren't the same claim

Upsun's own regions documentation lists the following EU/UK-adjacent data centers, each tagged with its underlying cloud provider:

Six of these seven regions run on top of AWS, Google Cloud, or Microsoft Azure — all three US hyperscalers with a US corporate parent subject to the CLOUD Act (18 U.S.C. §2703), regardless of where the physical servers sit. Only one region, fr-3 in Paris, runs on OVHcloud — a French-owned cloud provider with no US parent. Picking a European city from Upsun's region dropdown doesn't tell you which of those two categories you landed in unless you check the small print next to the region code.

This matters because Upsun's own Data Processing Agreement doesn't promise EU-only processing by default either — it explicitly authorizes processing "outside the European Economic Area to the extent required for the provision of Services," backed by Standard Contractual Clauses rather than a hard data-residency guarantee. That's a legally sound and common approach (SCCs are the standard post-Schrems-II mechanism), but it's the opposite of an architectural guarantee that EU customer data never touches a jurisdiction where a US legal demand can reach the infrastructure provider.

The corporate structure: a French SAS, but also a US Inc.

Upsun operates through wholly owned subsidiaries in seven countries, all listed on its own contact page:

• Platform.sh SAS — 22 rue de Palestro, 75002 Paris, France
• Platform.sh, Inc. doing business as Upsun — 106 S Main St Ste 4, Brooklyn, MI 49230, USA
• Platform.sh GmbH doing business as Upsun — Köln, Germany
• Platform.sh Limited doing business as Upsun — Bristol, UK
• Platform.sh PAAS SP, SL doing business as Upsun — Madrid, Spain
• Platform.sh Pty Ltd trading as Upsun — Barton, Australia
• Platform.sh Canada Sub, Ltd. — Vancouver, Canada

The French SAS is real and is the historical entity, which is more than most US-headquartered PaaS competitors can say. But the corporate group also includes a registered US Inc. entity operating under the same "Upsun" brand and the same platform. Which entity is contractually your counterparty, and which one operates the support tooling and admin access to your project, isn't something we can verify from public pages — that's a question for Upsun's sales/legal team on a specific contract, not something a marketing site answers either way. What is verifiable: a genuine US legal entity exists inside the same corporate family that operates the infrastructure your app runs on, on Google Cloud, AWS, and Azure regions in three of the seven EU-labeled locations.

sota.io's answer to the same question is simpler because the surface area is smaller: mamarx GmbH, registered at Amtsgericht Charlottenburg (Berlin), HRB 213877 B — one entity, one jurisdiction, hosted on Hetzner Cloud in Germany. No US parent, no US subsidiary, no hyperscaler in the stack.

Pricing: à la carte meters vs. one flat number

Upsun's fixed-pricing page bills across five separate meters instead of a single monthly price:

Per Upsun's own pricing FAQ, production compute is billed continuously (per second, not just at build time) — the project fee's included allocation ("2.5 CPU-hours, 5 GB-hours") only covers build resources, not the app actually running. Applying Upsun's own published rates to a workload roughly comparable to sota.io's entry tier — 2 guaranteed vCPU, 4 GB RAM, one user, running 24/7 (730 hours/month) — comes out to approximately:

€9 (project) + €10 (user) + €73 (2 vCPU × €0.10/h) + €38 (4 GB × €0.013/h) ≈ €130/month, before a database is added (PostgreSQL is a separate service meter, not itemized on the public pricing page).

sota.io's equivalent: €9/month flat, 2 dedicated vCPU and a managed PostgreSQL instance included, currently available through invite-only early access (Enterprise onboarding on dedicated EU capacity is open now via info@sota.io; public self-serve pricing lands at general availability). These are illustrative numbers from each provider's own published rate card — confirm current figures directly before making a switching decision, since usage-metered pricing by definition varies with your actual workload.

What Upsun is genuinely better at

None of the above makes Upsun a worse product — it makes it a different one, built for a different buyer:

• Compliance certifications sota.io doesn't have. SOC2 Type 2, PCI Level 1, and ISO27001 are real, audited certifications that some procurement processes require outright. sota.io doesn't hold any of these yet.
• True multi-cloud choice. If you specifically want AWS in Dublin for one workload and OVHcloud in Paris for another, under one platform, Upsun genuinely offers that. sota.io is Hetzner-only, single-cloud by design.
• A decade of enterprise production traffic, HIPAA availability as an add-on, and a partner ecosystem (Pimcore, Drupal, and other CMS/commerce platforms build official Upsun integrations) that reflects real operational maturity sota.io — pre-GA — hasn't had time to build yet.
• Config-as-code is a feature, not just overhead, for teams that want infrastructure changes reviewed in a pull request rather than clicked through a dashboard.

Where sota.io fits instead

If your team doesn't have a platform engineer, doesn't need multi-cloud region arbitrage, and just wants git push to result in a running app with a managed Postgres database attached — without writing a services/routes YAML file first, and without a five-line-item monthly invoice to reconcile — that's the gap sota.io is built for. It's also the simpler answer if CLOUD Act exposure is the actual reason you're evaluating alternatives to a US-headquartered PaaS: one EU entity, one EU cloud provider, no hyperscaler and no US subsidiary anywhere in the chain.

See Also

• EU Region vs EU Jurisdiction: Why Railway Frankfurt Is Still Under US Law — the general legal framework behind the region-vs-jurisdiction distinction applied here to Upsun specifically
• Render Pro Is $85/Month. sota.io Is €9. Both Give You 2 vCPU. — the same flat-vs-metered pricing comparison against a US-based platform
• Best European PaaS Providers 2026: GDPR, DORA, and Real EU Jurisdiction Compared — full jurisdiction comparison across Clever Cloud, Scalingo, Sliplane, Northflank, and sota.io