An Environment is a copy of your application, complete with all of the data, files, configurations, and running services. Environments are based on Git branches; every Git branch can be promoted to a full, active environment.
Development on Platform.sh is driven by Git, so you’ll want to have at least the basics down. That’s all that’s needed to get started!
Platform.sh has been designed to support the widest range of technologies. At the moment, however, the stack is limited to PHP-FPM (with Composer and Drush support), MariaDB 5.5, Solr, and Redis. This stack is ideal for running Drupal and WordPress, as well as applications built with the Symfony or Zend frameworks.
Site owners, agencies, and developers all benefit from Platform.sh, in terms of reduced deployment costs, faster development cycles, and zero-Ops scaling.
Platform.sh Enterprise should be your first choice if you need highly available clusters around every running service, or if it is important to you to run 100% of your site on SSL/HTTPS and have full front-end caching support, or if a 24/7 support SLA is important to you. Any site getting more than a million page views is also a prime candidate for Platform.sh Enterprise.
Platform.sh uses super-fast SSD-based network storage. While storage is limited to 30GB on Development and Production plans, enterprise customers can get up to 320 GB of SSD storage, and unlimited spinning disk storage if needed.
Choosing resources for a running site is an inexact science that is influenced by many factors. We’re happy to have a discussion with you about your needs. Generally, sites that are either mission critical or that receive more than 1 million page views a month should consider Platform.sh Enterprise.
As many as you need. Platform.sh is designed to be used by your entire team from day 1. Developer licenses are billed from the time they’re added to a project to the time they’re removed, so your developers can move on and off of the project as needed at the various phases, and you’re billed only for the resources you use.
Your card is charged at the end of each month for the resources that you have actually used.
Yes. You will be billed for the resources that you have used, and no more.
Billing is done at the end of the month and it covers only resources that you have actually used. You can see what your upcoming bill will look like by visiting your user account which has a full order history and running usage reports.
You can upgrade or downgrade your account at any time, including inviting more developers, creating new environments, and increasing storage. If you don’t find what you’re looking for, just contact our support team to help you.
Yes, indeed! Platform.sh has special support for profiles and distributions by allowing you to specify them in a Drush Make file in your Git repository. Platform.sh will build the profile or distribution for you whenever you push the Make file.
Absolutely! Platform is Git-based from the ground up, so once you’ve pushed your repo you can simply carry on with your existing agile workflow. Full webhooks integrations with services like Github mean that your current processes can be kept or improved by using Platform.sh.
Yes, Platform.sh allows you to configure more than one SQL database, enabling cases such as Drupal Multisite, or Drupal + CiviCRM.
Yes! Our short list of technologies for the near future includes Node.js, MongoDB, PostgreSQL, and the HipHopVM. Let us know what other services would be useful to your projects.