Acquia sells two enterprise-tier products for Drupal: Cloud Enterprise (single site, beefy) and Site Factory (multi-site, lots of them). Most teams shopping the platform end up on whichever one their salesperson led with rather than the one their workload actually needs. The choice is not subtle but the marketing makes it look that way.
The honest one-liner
- Cloud Enterprise: one Drupal site that needs serious horsepower, observability, and process. Starts $5,000/month and goes up.
- Site Factory: many Drupal sites (10 to 1000+) that share a codebase but want isolated content. Starts $5,000/month with multi-site consolidation savings.
If you have one site, Site Factory is the wrong product. If you have a hundred sites with shared theme and module set, Cloud Enterprise will burn budget. The trap is in between: teams with 5 to 15 sites often end up on whichever they bought first because switching is painful.
What Cloud Enterprise actually buys
The honest summary: enterprise infrastructure with Acquia-paid Drupal expertise wrapped around it.
- Production scale. Multiple application servers, load balancing, separate database clusters, geographic redundancy.
- Observability. Insight (Acquia's monitoring + advisory) is included on Enterprise plans. Cloud IDE, Cloud Hooks, Pipelines, Memcache.
- Compliance posture. SOC 2, HIPAA-eligible deployments, FedRAMP-eligible environments, GDPR documentation. Real if you actually need them; expensive if you don't.
- Support. 24x7 with response SLAs that are contractually binding. Premier support adds dedicated technical account managers.
The cost: Cloud Professional starts around $2,500/month, Cloud Enterprise starts around $5,000/month, and large enterprise contracts go to $20,000 to $50,000/month for traffic-heavy sites with all the trimmings.
What Site Factory actually buys
Multi-tenant Drupal at industrial scale. The pitch: one codebase, hundreds of sites, central administrative control, independent content per site.
- Site provisioning. Spin up a new tenant site in minutes, not days. The reason franchise organizations, universities, and government parent agencies use Site Factory.
- Codebase governance. One install profile, one set of modules, one theme system, propagated to all tenants. Site-level overrides exist but are bounded.
- Centralized operations. One backup pipeline, one update pipeline, one security patch deploy across all tenants.
The cost: starts $5,000+/month. The math gets favorable around 20 to 30 sites; below that you are paying multi-tenant overhead for not enough tenants.
The real decision
One question: do you have one site or many?
If one site: Cloud Professional or Cloud Enterprise depending on traffic. If your site does $10M+ in revenue or is regulated, you probably need Enterprise; if not, Professional is enough.
If many sites: Site Factory if there are 20+ tenants and they share a codebase. If 5 to 15 tenants, the math is genuinely close — Site Factory's overhead may exceed running each on Cloud Professional, depending on how much shared codebase work you actually need.
If many sites that don't share a codebase: neither product fits cleanly. You are running a portfolio of independent Drupal sites and the multi-tenant pitch does not apply. Look at managed Drupal hosting per site, with a shared engineering retainer covering the operational layer.
When Acquia is the wrong product entirely
Acquia's pricing model assumes you need enterprise compliance posture, dedicated TAMs, and 24x7 support with binding SLAs. Many Drupal sites don't.
For sites in the $100K to $5M annual revenue range without specific compliance needs, the WebEvra care plans ($499 to $1,999/month) cover the same operational ground (managed hosting, monthly Drupal updates, security patching, backups, dev hours) at a quarter of the cost. The trade-off: no Acquia-branded documentation for an auditor, no premier support contract.
For multi-site portfolios under 20 tenants, the same care plan model applied per site is usually cheaper than Site Factory plus its operational overhead.
The hidden line items
Same as Pantheon: the listed plan price is the entry point. Real Acquia invoices include:
- Pro Services. Acquia's professional services bench, billed at $200 to $300/hour. Most enterprise contracts include some hours; most contracts run over.
- Acquia DAM, Personalization, Site Studio. Each is a separately licensed product. Adding them is not a small line item.
- Premier support uplift. Standard support is included; Premier is several thousand a month additional.
- Site Factory tenant minimums and overage. Site Factory plans price by tenant count; going over the contracted count is an upsell event, not a smooth scale-up.
The actual annual Acquia spend for an Enterprise customer with Site Studio, Personalization, and Premier support is often $200K to $500K. Big numbers; not always wrong; rarely cheaper than the alternatives for teams that don't have the compliance need.
If you are evaluating Acquia today
Three things to do before you sign:
- Get the actual quote, not the list price. Acquia salespeople negotiate; the discount is often 10 to 30 percent for multi-year commits.
- Strip the add-ons you don't need. Site Studio is great if you'll use it; expensive shelfware if you won't. DAM is valuable if you don't already have one; redundant if you do. Personalization is real engineering work plus license cost.
- Run the math on the alternative. The cost calculator on our Acquia alternative page takes your Acquia plan, dev hours, and rate, and outputs a real comparison against a WebEvra care plan. Five minutes; no email gate.
Acquia is a good product for the workload it was built for. It is not the only good product, and for many teams it is genuinely the wrong shape of expensive.