Why We Host Drupal Projects on Pantheon

We've been on Pantheon since 2014. By The Way Labs is a Premier Pantheon Partner. That relationship reflects more than tenure — it reflects a consistent, deliberate choice. Here's why we make it.

Pantheon is a managed hosting platform purpose-built for Drupal and WordPress. It's not a generic host that happens to support Drupal — it's a platform designed around how Drupal applications actually behave: their caching architecture, database structure, and update cycles.

Running Drupal on generic hosting is like running a commercial kitchen in a home kitchen. Technically possible. Wrong tool for the job.

Three environments, built in

Every Pantheon project ships with Development, Test, and Live environments by default. Changes are built in Development, validated in Test, and only promoted to Live once confirmed. Security updates, new features, content model changes — all of it goes through the pipeline before touching your live site.

Problems get caught before visitors see them. That's the whole point.

Performance and security by default

Pantheon routes traffic through a global CDN, serving your site from infrastructure close to your visitors. Combined with Drupal's caching and Pantheon's object cache layer, page delivery stays fast under real traffic loads. On security: Drupal requires regular updates applied correctly and promptly. Pantheon makes that process systematic. Automated backups, uptime monitoring, and security scanning are platform defaults — not add-ons we configure separately. And the Dev→Test→Live pipeline means a security patch never goes live untested.

When Pantheon appears in your project scope, it's not a default choice — it's a considered one. Over the years, we've hosted Drupal on a variety of platforms. We standardized on Pantheon because it consistently reduces emergencies and gives us the tooling to manage serious Drupal applications responsibly.

The alternative — unmanaged environments, platforms not designed for Drupal — introduces risk that eventually surfaces as a support crisis. We'd rather design that risk out from the start.