Acquia, the commercial engine behind Drupal, remains a prominent name in the “digital experience platform” (DXP) landscape. Backed by private equity (Vista Equity Partners since 2019), it has followed in the footsteps of Adobe and Sitecore - expanding aggressively into adjacent domains like personalization, DAM, CDP, and accessibility. But like those peers, Acquia now presents a dilemma: a growing suite of offerings that can feel misaligned with the principles of a modern 4.0 architecture - where modularity, interoperability, and customer-centric orchestration take precedence over vendor-led suites.

Beneath the surface, Acquia is walking a fine line between growth & bloat, openness & lock-in, and innovation & distraction. If you’re an existing Acquia customer, or evaluating the stack, there are real reasons to be cautious.

Private Equity Priorities: Margin > Innovation

Sixteen straight years of top-line growth once fueled talk of an Acquia IPO, but Vista Equity Partners has clearly pivoted the playbook from “grow at all costs” to “squeeze out margin.” In practice that means the long-cherished IPO dream is shelved and leadership is laser-focused on cutting expenses while protecting and ideally expanding recurring subscription revenue. Over the past year Acquia has quietly reorganized, shifted more support near/offshore, and trimmed North-American headcount. The result? A leaner cost base, but the potential for thinner customer support and slower product cadence.

Prospective customers should press hard on support SLAs, roadmap transparency, and funding commitments. Ask which products are receiving net-new investment versus those simply being kept on life support.

The D7 Timebomb: Who Really Benefits?

Drupal 7’s official end-of-life (EOL) finally landed in January 2025. Tens of thousands of sites remain on D7 because migration to D8 is a forklift:  expensive, labor-intensive, and requiring a higher level of PHP skills under the covers. And make no mistake, Acquia and its partners stand to benefit from the forced rebuild cycle, as well as maintenance of a more sophisticated platform underneath.

This isn't an indictment of EOL itself (tech debt is real), but the lack of credible tools to make migrations simpler has fueled resentment. D7 users feel like they’ve been set up for a vendor-friendly services push.

If you're still on D7, treat migration as a moment to reassess and make the effort to explore other modernization paths and solutions that could offer better flexibility, stack fit, and cost-effectiveness. You certainly don’t lack for solid choices.

Starshot and “Drupal CMS”: Rebrand or Rebuild?

Acquia has heavily promoted the new Starshot initiative, a bundled Drupal distribution seemingly meant to compete with WordPress by offering a better out-of-the-box experience. The idea makes sense: reduce time-to-value, offer React-based editing, and appeal to non-dev teams.

But concerns are mounting about Acquia’s influence over the direction of the project, especially given how many of the contributing engineers are on its payroll. Some community members worry Starshot will evolve into a quasi-proprietary front-end atop open Drupal, a subtle but significant shift in governance.

If you’re evaluating Drupal now and are willing to trade off sophistication for a less bespoke implementation, test Starshot in a sandbox, but be wary of dependencies it introduces. Don’t assume broad community support yet; this is still experimental.

Toolset Sprawl: Open DXP or Just Another Suite?

Acquia bills itself as an “Open DXP,” but their acquisitions - like Widen (DAM), AgilOne (CDP), and Monsido (accessibility) - are increasingly stitched into a platform that behaves more like a proprietary Adobe or Sitecore suite. And while openness is the marketing message, interoperability and shared data layers across the stack still require custom glue.

AI is now a big talking point, with Acquia touting GenAI capabilities in its DAM and CDP. But actual product maturity varies, and it’s unclear how these features integrate meaningfully into content and campaign operations.

Avoid bundling temptations. Each Acquia tool must stand on its own merit; compare to best-of-breed alternatives before buying the full suite.

Community Fatigue and Talent Pipeline Woes

The Drupal community is aging, and younger developers are gravitating toward more modern, JavaScript-native frameworks. Drupal’s power comes in managing complex structured content, but few enterprises need the full website-in-a-box codebase anymore.

For ten years now Acquia has been experiencing a kind of drift, leaning into secure hosting for enterprise buyers and relying on agencies to keep onboarding dev talent. But even agency enthusiasm is waning as newer tools offer faster time to market with less overhead.

If you're planning a 5+ year digital roadmap, ask where Drupal fits in that horizon. Consider hybrid, headless, or legless models that preserve structured content benefits without locking you into a declining talent pool.

Acquia Is Not the Enemy, But It’s No Longer the Underdog

Acquia isn’t good or bad. It’s doing what any profit-oriented PE-owned enterprise software company would do: drive reasonable growth, upsell the suite, and push for profits and lock-in, in part by shaping the future of the open-source project it supports. But that alignment creates tension, and the burden falls on you, the customer, to make smart choices.

If you’re already on Acquia:

• Audit your license costs and usage regularly
• Decouple where you can
• Engage in the community, not just the vendor roadmap
• Review lighterweight alternatives

If you’re evaluating Acquia:

• Look past the Big Analyst grids
• Assess integration overhead and team skill match
• Demand clear separation between open source flexibility and vendor-delivered lock-in

Acquia’s version of Drupal can still serve some sophisticated use cases, but the era of blind faith is over.

Curious about what true WCM 4.0 looks like in practice and how to cut through the buzz to build a stack that actually delivers? Join our upcoming webinar, How to Get to Web CMS 4.0