Cloud Platform

Cloud Platform

Maximum control, without the infrastructure

Your Drupal application, your modules, your content model in code; Acquia hosts it on a Drupal-optimized platform. You keep the control, and the open source, that made you choose Drupal, without running the infrastructure under it.

Install and authenticate acliCompare all the paths

What you can do with it

The whole application lifecycle, from a laptop clone to production, without building the platform yourself.

• Run Drupal your wayCustom modules, contributed modules, a content model in code: the application is yours, serving rendered pages or an API for a frontend you build.
• Promote code through environmentsMove changes through Dev, Stage, and Prod, reach any environment from your terminal, and roll back when a release goes wrong.
• Develop locally against real dataRun the site on your own machine in containers, with the database and files pulled from a real environment.
• Automate the pipelineBuild and deploy on every push, with Pipelines or the CI your team already runs.

Where you are coming from

Open by design, wherever you are coming from: each move keeps what already works and adds what was missing. The application stays standard, open-source Drupal, shipped with git; nothing about it changes shape to fit the host.

• Coming from self-hosted DrupalYou keep your codebase, modules, and git workflow: no lock-in, no starting over.You add what you were building by hand: environment promotion, a cache tier in front, and logs to diagnose from.
• Coming from generic cloud hostingYou keep infrastructure off your plate.You add a platform that knows what Drupal is: database and file syncs between environments, remote drush, and Drupal-aware caching.
• Coming from a fully managed CMSYou keep someone else running what sits below the application.You add code-level control: your own modules and a content model that lives in code review, not in an admin screen.

Questions developers ask

+−What do I own, and what does Acquia run?

You own the Drupal application: contributed and custom modules, custom PHP, and the content model in code. Acquia runs the Drupal-optimized hosting under it.

+−How does code reach production?

A built codebase lands in the application’s Acquia git repository, and that repository’s branches and tags promote the same build through Dev, Stage, and Prod.

+−Can I work from the terminal?

Yes. The Acquia CLI runs your routine work from the terminal: logs, databases, remote commands, and deploys, against whichever environment you point it at.

+−Do I have to use Acquia’s CI?

No. Pipelines builds and deploys on every push if you want it, and the CI provider your team already runs can build the artifact instead.

+−What caching sits in front of the site?

Varnish in front of the application, and memcached behind it once you enable it. A request Varnish can answer never reaches PHP; memcached makes the requests that do get through cheaper.

+−Can I run Drupal Canvas on it?

Yes. Canvas is an open-source Drupal module you add to a codebase you control, and the same components and push workflow work against any Canvas-enabled site.

Start shipping

• 01Get a Cloud Platform application →A free trial is self-serve and arrives with its codebase in place, or ask your subscription admin for access.
• 02Install and authenticate acli →The CLI on your own machine, authenticated against your subscription.
• 03Set up local development →Run the site on your machine, with an environment’s database and files.
• 04Ship one change →Push it, and watch the dev environment deploy.