Pantheon: Managed web platform

Learn about Pantheon’s WordPress and Drupal hosting, Dev-Test-Live workflow and team publishing model, with practical guidance on code and content changes.

Updated 8 September 2026

What Pantheon is designed to manage

Pantheon is a managed platform associated with WordPress and Drupal sites. Its workflow organizes changes into development, testing and live environments. That structure helps teams separate work in progress from the version visitors currently use.

An agency maintaining a client’s site can develop a feature, test it against representative content and then release it. Editors and developers are working on related systems, but they are not necessarily changing the same files or database records.

Understanding Dev, Test and Live

Pantheon’s workflow distinguishes code from the database and uploaded files. Moving application code toward production and copying content for testing are different operations. Treating them as one undifferentiated site copy can overwrite changes made by editors or customers.

For example, a new theme can move through testing without replacing the live database. A recent copy of live content may help test that theme, but it should not then be pushed back over newer production orders or articles.

Multidev, automation and site operations

Pantheon supports teams maintaining WordPress and Drupal sites through development environments and release workflows. Multidev provides environments for parallel work, while Terminus gives developers a command-line interface for platform operations. These tools help coordinate changes across a team rather than treating every update as a manual edit to the live site.

Delivery, backups and performance services

The platform’s documentation covers its Global CDN, caching, backups and performance tools. These services sit around the CMS: editors still work with WordPress or Drupal, while Pantheon handles hosting and delivery operations. Availability and environment limits depend on the service plan.

Planning maintenance and releases

Write a release checklist around the actual CMS behaviour: updates, cache clearing, forms and content editing. A test environment is useful only when it exercises the integrations and data shapes that matter to the production site.

Identify which settings vary by environment, such as email destinations and third-party credentials. Confirm that testing cannot send real customer messages or trigger production fulfilment. Those boundaries belong in the application’s operating process as well as in hosting configuration.

How DNSTrace.dev detects Pantheon

Detection correlates independent public signals. A single match is reported as strong evidence; agreement between a response header and the announcing network is reported as confirmed.

x-pantheon-styx-hostname — Names the Styx edge node that handled the request.
x-styx-req-id — Per-request identifier issued by the Styx layer.
CNAME targets under pantheonsite.io — The platform hostname a custom domain is attached to.

What a detection proves

The response was served through Pantheon's Styx edge, so the site is hosted on Pantheon.

What it does not prove

Whether the application is WordPress or Drupal. DNSTrace.dev reports the content management system separately from its own headers and markup, and the two detections are independent.

Common questions about Pantheon

Why does Pantheon separate code from content?

Code changes and database or file changes have different lifecycles. A team may deploy a new feature while preserving live editorial content and customer data. The environment workflow helps keep those operations distinct.

Does Pantheon tell me which CMS a site runs?

No. Pantheon hosts both WordPress and Drupal. The CMS is identified from its own signals and reported under the detected stack.

Can a Pantheon site sit behind another CDN?

Yes, and a customer-added proxy may strip the Styx headers, in which case Pantheon may not be visible at all.

Managed WordPress hosting