Yes. Thousands of live production sites run on Pantheon.
Pantheon supports Drupal 6, 7, and 8 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 wp-config.php.
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 40+ 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, see Launch Essentials.
To learn more, see Using the Pantheon Workflow.
Yes, see 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. 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. 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 Site Networks created by WordPress' Multisite feature:
Yes. Pantheon comes with Drush pre-integrated with
@alias files. For more details, see 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, see Cron for Drupal.
This can occur if hardcoded links are found in the HTML source of your pages. To correct this, WordPress sites should run a search and replace using WP-CLI as mentioned in the WordPress Quick Tip: Search and Replace with WP-CLI blog post to exchange the platform domains with your custom domain, and then add a redirect to the primary domain.
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, see Cron for WordPress.
No. We do not have plans to add this feature. However, it is possible to run a site on the platform and integrate with a third-party transcoding service or multimedia platform that lets you create streaming-optimized videos. Those providers have optimized the highly complex process of transcoding and serving video content, and leveraging their infrastructure is often preferable to a custom solution.
No. Xdebug is not available on the platform.
The upper time limit for PHP processing on the platform is 120 seconds. This is outlined in the Timeouts documentation and it cannot be increased. If a script is processing a large amount of data, for example, we recommend that the process be done in smaller batches that can execute sequentially to ensure success.
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, see 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:
Each of these configurations is possible with Drupal’s built-in language switching.
You can associate multiple domains with a single site environment. See Launch Essentials for details.
If you need to use PHP's native session handling, please install the WordPress Native PHP Sessions plugin, which we maintain just for this purpose. This provides a horizontally scalable storage mechanism for sessions.
If you are seeing errors like this:
Warning: session_start(): user session functions not defined
You'll need the plugin. More information on sessions.
Yes. See 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.
Currently, the version of Solr on Pantheon is Apache Solr v3.6.
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.