Enterprise Drupal, engineered for scale.

What people ask before deciding

What is Acquia Site Studio?

It is a visual building layer for Drupal where components are defined as versioned configuration rather than drawn freely on a canvas. Editors assemble pages from a component library that engineering defined; what is not in the library cannot be used. That restriction is the product: it is what lets you give the content team autonomy without the design system dissolving within six months.

Are Site Studio and Cohesion the same thing?

Yes. The product was called Cohesion DX8, was acquired by Acquia and renamed Acquia Site Studio. Older installations still carry the Cohesion name in modules, tables and internal documentation, which is why both words still appear together in search. If your base still says Cohesion somewhere, it is probably on a version worth reviewing before any further work.

Does Drupal handle millions of visits?

It does, and Drupal is rarely the bottleneck. At high volume what decides is the caching strategy and the database access pattern: cache tag granularity, BigPipe for what is dynamic per user, and a proxy or CDN in front that can invalidate without flushing everything. A platform that falls over at peak almost always has invalidation that is too coarse, not a CMS that is too weak.

What is the difference between Drupal and Acquia?

Drupal is the open source CMS; Acquia is a company selling hosting, tooling and Site Studio on top of it. Choosing Acquia is a decision about who owns operational responsibility, not about which CMS to use: Drupal is the same Drupal on any host. The useful question is not "Drupal or Acquia", it is how much of the operation you want in house.

Is Drupal suitable for large enterprises?

It is, and the reason is governance, not features. Drupal models permissions, editorial workflow, revisions and translation as first class structure, which matters when dozens of people publish across countries with different responsibilities. In small operations that is overhead; in large ones it is exactly what simpler CMSs lack.

When does Site Studio get in the way?

When it is treated as a page builder. If every campaign earns a new component, the library becomes a warehouse, the design system stops being verifiable, and maintenance cost comes back worse than before. What works is treating the component library as the rendered form of the design system, with the same review that code gets.

Do you do headless Drupal?

We do, and the question before that is whether it pays off. Headless separates content from presentation and earns that complexity when more than one consumer uses the same content: site, app, kiosk, partner. With a single consumer it usually costs more than it delivers.

Can we run several sites on the same base?

Yes, and that is either multisite or a shared design system, which are different things. Multisite splits the codebase and separates the database; a shared design system keeps one site with reused themes and components. The choice changes the cost of operating for years, not of building.

What is a custom module, and when is it worth it?

It is your own code extending Drupal where the out-of-the-box answer does not fit: an integration, a business rule, a content type with its own behaviour. It is worth it when the alternative is bending a third-party module until it breaks on the next update.