- Automatically detects when new updates are available
- Performs the updates in an isolated Multidev environment
- Tests the updates with automated visual regression testing (VRT)
- Optionally deploys the updates
If you build or maintain WordPress and Drupal sites, Autopilot is for you.
Site upkeep can be tedious with constant monitoring, building, maintaining websites, and working cross-functionally to deliver digital experiences for customers. Autopilot relieves you of the continual maintenance work it takes to keep sites updated.
Autopilot requires Multidev, and is available to Pantheon Gold Accounts or higher.
Autopilot is enabled for Pantheon sites at the organization level.
Yes. Access to Autopilot is account-based and individual sites in that account can turn Autopilot on and off as desired. See Enable Autopilot
Yes. Configure Autopilot activity digests and notifications in your Personal Workspace settings Notifications tab.
Currently, Autopilot only supports Drush 8 for all sites up to Drupal 9. Drupal 9 uses Drush 10 and is compatible with Autopilot.
However, Autopilot does not use Drush when updating an Integrated Composer site; you can use any Drush version when using Integrated Composer. Refer to the documentation on Drush versions for more information.
You can specify the environments to which Autopilot deploys. See the next page for configuration options.
No. Autopilot always tests updates against a Multidev based on the current Dev environment.
For Autopilot to compare updates to the Live environment, keep the Dev environment synchronized with the Live environment, to ensure Autopilot test updates against the most up-to-date state of the Live environment.
No. If you encounter any issues about Multidev limits, contact Support.
Not yet. Currently, Autopilot only supports tests on anonymous access versions of pages. Support for authenticated (logged-in user) page tests is planned for a future release.