This page includes commonly asked questions to give you more information about Pantheon, including what our platform offers and supports.
Review Platform Considerations for more technical information.
Yes. Thousands of live production sites run on Pantheon.
Pantheon supports Drupal 7+ sites. As of February 2016, the Drupal community no longer supports Drupal 6. Drupal 6 sites will continue to run on Pantheon, but there will no longer be any updates to fix bugs or security issues.
Pantheon supports the most recent release of WordPress via our upstream, which includes platform integration plugins and a pre-configured
You can develop new sites for free on Pantheon. Billing starts when you're ready to go live and direct traffic to a site. See available plans on our pricing page.
In addition to the United States data center, new sites can be created in Australia, Canada, and the European Union (EU). Pantheon's Global CDN serves content from 70+ POPs (points of presence) distributed around the world.
Only WordPress and Drupal applications are officially supported, but the PHP runtime is complete. Some users have experimented with running applications with custom PHP code.
Pantheon supports toggling between local development mode using
git push to transfer all code changes, and an on-server development mode, which provides access to the codebase via SFTP.
Pantheon can handle any domain name you point at it, however DNS configuration is still your responsibility. For more information, refer to Launch Essentials.
- Dev has lower TTL on Varnish caching and shows errors to site users.
- Test has the same caching configuration as Live and does not show errors to users. If the Live environment has multiple application containers, Test will have two.
- Live has optimal caching and does not show errors to users, and (depending on the plan) can have multiple application containers for high availability and high performance.
To learn more, refer to Using the Pantheon Workflow.
Yes, refer to Professional Services for more information.
Yes. Pantheon sites run on a highly available clustered infrastructure.
Yes. While your Pantheon site will only run from code in your Pantheon Git repository, this can be mirrored from an external repository by setting up a continuous integration workflow, or by syncing your code to multiple remotes.
No. Instead of a traditional Drupal Multisite setup, Pantheon designed a better solution called Custom Upstreams. Pantheon's architecture is designed to provide high performance and a rich feature set for individual Drupal sites. Individual sites can end up in states of configuration that make module or Drupal core updates impossible to do across all the sites of a multisite setup. The codebase also becomes a single point of failure.
Our solution is to deliver granular resources and powerful code management tools so that users who want to run a large portfolio of sites can do so easily, without running the risks inherent in multisite.
Yes, Pantheon supports the following use cases of WordPress Multisite:
- Blogs for faculty at a university
- Franchise sites under a parent organization site
- Sections within a media publication
Yes. Pantheon comes with Drush pre-integrated with
@alias files. For more details, refer to Drupal Drush Command-Line Utility. You can invoke Drush commands on Pantheon sites using Terminus, the Pantheon CLI.
Yes. You can invoke WP-CLI commands on Pantheon sites using Terminus, the Pantheon CLI.
Yes. Local development is a great best practice, and Pantheon supports a wide array of local development tools (e.g. MAMP, WAMP, Homebrew, etc).
The platform will use Drush to run cron on an hourly basis automatically. More fine-tuned cron control is in development. If you need to run cron more frequently, you are free to do so using your own timing system and Drush aliases. For more information, refer to Cron for Drupal.
WordPress runs its own internal cron-like system as visitors load your site. You can also use external services to schedule and create tasks. For more information, refer to Cron for WordPress.
Pantheon is home to many polylingual and non-English sites, and hosting a multi-language site on Pantheon requires no additional platform configuration.
For detailed information on how to configure a multilingual Drupal site, refer to the Multilingual Guide on Drupal.org.
Pantheon doesn’t enforce any particular site layout or architecture for multilingual sites, but the blog entry Working with multi-regional websites from The Google Webmaster Central Blog has some fantastic recommendations.
It’s possible to specify a site language given a particular domain or path. In order of preference:
- ccTLDs (country-code top level domain names)
- Subdomains with gTLDs eg: de.site.com, fr.site.com, etc.
- Subdirectories with gTLDs eg: site.com/de/, site.com/fr/, etc.
Each of these configurations is possible with Drupal’s built-in language switching.
You can associate multiple domains with a single site environment. Refer to Launch Essentials for details.
Yes. Refer to Public Distributions for details.
Yes. We recommend that you ensure that you are enforcing HTTPS only at the outer CDN and assuming HTTPS in the application. Check your CDN for how to redirect all traffic to HTTPS. Pantheon also provides advanced caching addons for WordPress & Drupal.
Currently, Pantheon provides Apache Solr v3.6 and v8.0 as a service for all plans except the Basic plan.
The Platform logs users out after 24 hours of inactivity, and forces all users to log back into the Platform every 30 days. This includes all users authenticated via Terminus.
Since you can alter your code on Pantheon, you must certify your own applications. PCI compliance for applications deployed on any platform cannot be guaranteed by the platform alone. We recommend architectures designed to work with PCI SAQ-A to minimize both risk and compliance efforts.