The Platform.sh Enterprise and Elite tiers have minimum annual contract commitments of USD$15,000 and USD$75,000, respectively.

We often use the terms “site” and “project” and “app” interchangeably, but depending on your application, they may or may not mean the same thing.

At its simplest, a “site” as we define it here is a set of application code that is deployed to a Platform.sh project. Most of the time, you’ll want a 1:1 relationship between sites and projects, so that you can manage each site independently. Enterprise and Elite customers can use Source Operations™ to manage fleets of sites.

We also support multiple apps per project as well as Drupal multisite and WordPress multisite architectures, which allow multiple domains to operate from within a single project.

An environment on Platform.sh is a logically separate instance of an application, complete with all the services that application requires. You can think of an environment as a complete working website, related to, but safely isolated from others in the project. Each project includes multiple environments–typically the production environment and three or more additional environments that can be used for development, testing, staging, review, and so on.

New environments can be created in moments through a Git clone via the Platform.sh Command Line Interface, or via the Platform.sh web console, and will be an exact replica of their parent environments. This means new environments will have all the data and the services (e.g., databases, network storage, queues, and routing) instantly cloned.

The relationships between environments is hierarchical and can be organized in any way that suits your organization, rather than mandating a strict development → staging → production workflow. An environment is tied to a Git branch and can be created on demand. With Bitbucket and GitHub integrations, you can even get a “development server” automatically for each and every pull request. Read more about Platform.sh environments.

No, we don’t charge for pageviews or unique visitors. Your billing is based on the plans you select for your projects and the additional resources you add.

The pageviews indicated in the tables above are guidelines, not limits. Capability of a given plan will depend on how your application works and the nature of the traffic (e.g., cacheable vs non-cacheable visits).

Yes, we have a comprehensive agency Digital Agency Partner Program, with benefits available for agencies of all sizes.