Platform.sh

What Is Platform.sh?

Platform.sh is the most developer-workflow-aware PaaS on the market — and it is not particularly close. While other platforms give you a place to deploy code, Platform.sh gives every Git branch a fully functional environment complete with its own databases, services, URLs, and data. This is not a simplified staging environment. It is a byte-for-byte clone of production, spun up automatically when you push a branch, torn down when you merge or delete it.

Founded in Paris in 2014, Platform.sh grew out of the Drupal ecosystem and expanded to support Symfony, Laravel, Node.js, Python, Go, Java, and more. The company has raised significant venture funding and serves enterprise customers including major media companies, government agencies, and e-commerce platforms. In 2023, Platform.sh launched Upsun, a next-generation version of the platform with resource-based pricing.

The core philosophy is infrastructure-as-code, enforced through YAML configuration files that live in your repository alongside your application code. Every environment gets exactly the configuration you define — same services, same versions, same data. This eliminates the "works on my machine" problem at the infrastructure level, not just the application level.

For teams that take development workflows seriously — code review, staging, QA, performance testing — Platform.sh offers capabilities that no other PaaS matches. The question is whether those capabilities justify the premium price.

Key Features

Branch-Per-Environment Architecture

This is Platform.sh's defining feature and the reason teams choose it over simpler alternatives. When you create a Git branch, Platform.sh automatically provisions a complete environment: application runtime, databases, search engines, caches, and object storage. The data is cloned from the parent environment, so your feature branch has real data to work with.

The implications are significant. QA teams can test against production-quality data without manual database dumps. Developers can experiment with schema migrations on a branch without risking production. Product managers can preview features at a unique URL before merge. Every pull request becomes a live, testable deployment.

Infrastructure-as-Code

Platform.sh configuration lives in three YAML files in your repository: .platform.app.yaml (application configuration), services.yaml (databases and services), and routes.yaml (HTTP routing and caching). These files define everything — runtime versions, build hooks, deploy hooks, cron schedules, worker processes, and relationships between services.

This is powerful but comes with a learning curve. The YAML format is proprietary to Platform.sh, meaning configuration knowledge does not transfer to other platforms. Migration away requires translating these files into whatever your next platform expects — Dockerfiles, Terraform, Helm charts, or something else entirely.

Multi-Cloud Deployment

Platform.sh deploys across AWS, Azure, Google Cloud, and OVHcloud. EU customers can select European regions on any of these providers, or choose OVHcloud for fully EU-sovereign hosting. Enterprise customers can configure multi-region setups with geographic routing and failover.

Source Operations

Source Operations automate repository maintenance tasks — dependency updates, security patches, upstream merges. You define operations as scripts that Platform.sh runs on a schedule, committing changes back to your repository. This is particularly valuable for CMS-heavy projects (Drupal, WordPress) where upstream updates are frequent and testing them manually is tedious.

Blackfire.io Integration

Platform.sh owns Blackfire.io, a PHP and Python performance profiler. The integration is seamless — you can profile any environment, compare performance between branches, and catch regressions before they reach production. For PHP-heavy teams, this is a genuinely differentiating capability.

Upsun: The Next Generation

Upsun is Platform.sh's newer offering, using the same underlying infrastructure but with resource-based pricing instead of fixed tiers. You pay for CPU, RAM, and storage consumed, which can be more cost-effective for applications with variable resource needs. Upsun also features a modernised UI and simplified onboarding.

Pricing

Platform.sh's pricing is its most contentious aspect. Professional plans start at around EUR 25 per month for a single production environment with a small number of development environments. This sounds reasonable until you factor in that meaningful use typically requires larger resource allocations and more environments.

For a mid-sized project with a production environment, staging, and several feature branches running simultaneously, monthly costs can reach EUR 100-300. Enterprise pricing is custom and can run into thousands per month, though it includes dedicated infrastructure, SLA-backed support, and compliance certifications.

Upsun's resource-based model offers more pricing flexibility, but requires careful monitoring to avoid bill surprises. You pay for what you provision, and environments with cloned production data can consume significant storage.

The honest assessment: Platform.sh is expensive relative to simpler PaaS options. A comparable setup on Render or Railway would cost a fraction of the price. But those platforms do not offer branch-per-environment cloning, and that capability is worth paying for if your workflow depends on it.

EU Compliance & Data Privacy

Platform.sh is a French company (Platform.sh SAS) with strong EU compliance credentials. The platform holds SOC 2 Type II certification and offers data residency in EU regions across multiple cloud providers. Choosing OVHcloud as your infrastructure provider keeps everything within a fully EU-sovereign stack.

For GDPR compliance, Platform.sh's infrastructure-as-code model has an underappreciated benefit: your infrastructure configuration is version-controlled, auditable, and reproducible. Compliance teams can review exactly what services process data, where they are hosted, and how they are configured — directly from the Git repository.

The company serves government and healthcare customers in Europe, which speaks to the robustness of its compliance posture. Data processing agreements are available, and the platform supports the isolation requirements that regulated industries demand.

Who It's Best For

Enterprise development teams with serious workflow requirements — code review, staging, QA, performance testing. If your merge process involves multiple reviewers testing against real data, Platform.sh's branch environments are transformative.

Drupal and Symfony shops where Platform.sh has the deepest integration and the most battle-tested configurations. The ecosystem support for these frameworks is unmatched by any competitor.

Agencies managing multiple client sites who need isolated environments, easy cloning, and the ability to hand off projects with self-contained infrastructure definitions.

Regulated organisations that need auditable, reproducible infrastructure with EU data residency options and enterprise compliance certifications.

The Verdict

Platform.sh is the most capable PaaS available for teams that take development workflows seriously. The branch-per-environment model is genuinely unique, and for teams that need it, nothing else comes close. But this power comes at a cost — both financial and in learning curve. The proprietary configuration format creates meaningful lock-in. The pricing puts it beyond reach for small teams. And for applications that do not need full environment cloning, simpler and cheaper alternatives exist. Platform.sh is best understood as a workflow investment, not just a hosting choice.

Frequently Asked Questions

What is the difference between Platform.sh and Upsun?

Upsun is Platform.sh's next-generation platform using the same infrastructure but with resource-based pricing instead of fixed tiers. It offers a modernised UI and more flexible scaling. Existing Platform.sh customers can continue using the original platform or migrate to Upsun.

Does Platform.sh support WordPress?

Yes, Platform.sh supports WordPress alongside Drupal, Symfony, Laravel, and many other frameworks. WordPress configurations are well-documented, though the platform's Drupal support is more mature given its heritage.

Can I migrate away from Platform.sh easily?

Migration requires translating Platform.sh's proprietary YAML configuration into your target platform's format. Your application code is portable, but the infrastructure definitions are not. Plan for a meaningful migration effort if switching platforms.

Is Platform.sh worth the price?

For teams that actively use branch-per-environment workflows — multiple developers, code review processes, QA testing against real data — the productivity gains justify the cost. For simple applications with straightforward deployment needs, cheaper alternatives like Railway or Render offer better value.

Where is Platform.sh data hosted?

Platform.sh offers deployment across AWS, Azure, Google Cloud, and OVHcloud. EU customers can select European regions on any provider. For fully EU-sovereign hosting, OVHcloud regions keep all data within European-owned infrastructure.