Download websites that use Acquia Cloud Platform

About Acquia Cloud Platform

Site counts measure reach rather than value, and enterprise hosting is where the two come apart. Acquia Cloud Platform is a managed PaaS platform built specifically for Drupal, launched in 2008 by Acquia and sold as a Proprietary service. As of October 2026 we detect it on 2,029 sites, a modest number set against the contract value each one represents.

The platform comes from the company founded by Drupal's own creator, and it exists because large Drupal estates are genuinely hard to operate. Acquia supplies managed PHP infrastructure with automated scaling, continuous integration pipelines, CDN integration, code and database tooling, and the security and compliance controls that regulated buyers insist on. The customers are enterprises, government agencies, universities and media organisations running content platforms they cannot afford to have fall over.

For a researcher, a domain on this platform carries a stack of implications at once. The organisation runs Drupal rather than a hosted CMS, which usually means a bespoke content model and a real integration surface. The organisation also has a procurement process, a signed contract and a budget large enough to pay for managed hosting instead of a virtual server. And there is almost certainly an implementation partner attached, because very few organisations operate a platform of this size without an agency or a systems integrator alongside them.

Which is why the list matters disproportionately to people selling into enterprises. Drupal agencies and integrators read it as a direct prospect list. Competing enterprise hosting and platform vendors read it as a displacement target. Search, personalisation, asset management, translation and accessibility vendors read it because a large Drupal estate nearly always buys those categories separately. Analysts read it to track whether enterprise Drupal is growing or being displaced by headless and hosted alternatives, which is a question only answerable by comparing full lists over time.

Hosting attribution is inferential, and it is harder here than usual. Enterprise sites sit behind CDNs and firewalls that terminate connections and rewrite headers, custom domains conceal the underlying platform, and a large organisation may run part of its estate on this platform and the rest somewhere else entirely. Our attribution comes from network and response evidence rather than from any customer register, so the recorded figure is a visible subset rather than a client list, and the error runs in one direction only.

A single domain lookup answers where one site is hosted, on the day you ask. The downloadable PaaS dataset answers which organisations sit on enterprise Drupal infrastructure at all, which of them moved on or off it since the last export, and how the estate distributes across countries and suffixes. Procurement questions live at the level of the population, and a lookup tool cannot reach them.