--- title: "Acquia Source was just a CMS. Now it's a bet on how content teams work with AI." url: https://www.axelerant.com/blog/acquia-source-cms-ai-content-teams published: 2026-07-20T10:00:00Z author: "Panshul Khurana, Staff Software Engineer" source: Axelerant Thinking --- # Acquia Source was just a CMS. Now it's a bet on how content teams work with AI. > A year ago, Acquia Source was a CMS conversation. Since then, it's become one tool doing five jobs at once: content, AI agents, digital assets, governance, and analytics. We got early access, looked under the hood, and mapped where it genuinely fits for Drupal teams. A year ago, if you asked us what Acquia Source was, the honest answer was "a CMS." That's no longer the honest answer. Source is now one tool covering five jobs that used to live in separate systems: website content, AI agents, digital asset management, governance, and analytics. It's still Drupal underneath, so the flexibility that made Drupal worth choosing in the first place hasn't gone anywhere. What's changed is that Acquia isn't positioning Drupal as the headline anymore. It's calling Source a command center, one place to do everything, and the intent is to make Drupal disappear into the background so marketers can move faster without touching the plumbing, while developers still get the extensibility they'd expect. ## What's actually under the hood We got early access and spent time in the resulting site rather than the provisioning dashboard itself, which is worth noting on its own: Acquia is positioning Source as something you configure once through their layer, not something your team operates hands-on the way you would a standard Drupal build. Underneath, the pattern is familiar to anyone who's worked with Acquia Lightning or similar installation profiles: a template that gets a site running fast, with modules pre-configured instead of a blank install. What's layered on top is mostly API surface, JSON API, webhooks, the kind of scaffolding that makes a site consumable by other systems and agents. The theme layer is standard Drupal, nothing Source-specific there. The real center of gravity is Experience Builder (XB). It's the primary way you interact with pages and add content through components, and it has an AI extension that lets you add those components by prompting instead of picking them from a library. Acquia is clearly building Source's story around XB, and that's worth our teams getting fluent in it as part of standard Drupal builds, regardless of whether a given client ends up on Source specifically. Alongside XB, the extension menu points to Acquia Convert, Acquia Optimize, and Acquia SEO. Convert is a conversion optimization layer, insights, testing, and personalization, with an AI co-pilot on top. Optimize is a governance layer covering accessibility, content quality, brand compliance, and privacy and consent. SEO adds AI-driven content recommendations and a writing assistant. That's the actual bundle: content, conversion, and governance tooling that used to live in three or four separate subscriptions, now sitting inside the same CMS you're already authoring in. ## Why this matters: three reasons The first is less tool chaos. Acquia's stated goal is fewer separate systems for digital teams managing content, DAM, and governance. That's a real cost for any team running Drupal alongside several bolted-on tools for asset management, workflow approval, and reporting. Fewer tools means less switching, less integration overhead, and fewer places for governance to quietly break down. The second is AI with brakes, not just speed. The agents inside Source can draft and publish content, but risky actions route through a human checkpoint first, and the agents inherit your team's existing permission structure rather than operating with their own elevated access. That's a meaningfully different posture than bolting a chatbot onto a CMS and hoping editorial judgment happens somewhere downstream. It's AI operating inside the governance model your compliance and legal teams already signed off on, which matters most for the regulated industries we work in: healthcare, financial services, and government among them. The third is being ready for AI search. The agents write content in a way language models can parse and cite cleanly, sometimes described as answer engine optimization. That structuring happens at the point of authoring rather than through a separate audit tool that checks legibility after the fact, which is a more durable way to solve the problem than a plugin that runs a report you have to act on manually. ## Where Source actually fits Based on what we've verified hands-on, Source earns its place for large enterprises operating under strict compliance requirements, existing Drupal-on-Acquia-Cloud customers ready to move to a managed SaaS model without giving up Drupal's flexibility, and brands consolidating point solutions for DAM, governance, and content tooling that were previously scattered across separate subscriptions. It's explicitly built for what Acquia calls a less technical audience, positioned to require no developer expertise, recommended but not mandatory. It's worth being precise about where Source stops. Acquia Cloud Site Factory and Multi-Experience Operations (MEO) solve a different problem: running many complex sites off a shared codebase, with centralized deployment and governance while each site keeps its own identity. MEO in particular is code-centric, built on Acquia Cloud Next's Kubernetes infrastructure, and assumes a Git-first, CI/CD-driven workflow. That's the right tool once a digital estate has sprawled past what Source's template and component model can reasonably handle. If a site outgrows Source, the right move is graduating it into Site Factory or MEO's architecture rather than forcing it to stay put, and we'd rather flag that boundary early than let a platform mismatch surface well into a build. ## What's next Acquia has announced support for Claude, Cursor, and GitHub Copilot through MCP. Once that lands, teams will be able to invoke Source's agents directly from the AI tools they're already working in, rather than switching context into a separate dashboard. That's a bigger unlock than it sounds, and the kind of integration that tends to shift adoption curves once it actually ships. Adoption is growing, and we expect more enterprise case studies to surface as it does, which will make the consolidation story more concrete for teams still evaluating it. Today's agents already handle things like campaign insights, content quality, and accessibility, and that library is expected to keep growing. On our side, we've spent twelve-plus years as one of Acquia's original professional services partners, across more than 150 DXP implementations spanning Site Factory, DAM, CDP, and Campaign Studio, and we've been invited to join Acquia's Platform Advisory Council for 2026. We're building proof-of-concept work on Source now and forming real opinions on where it's strong and where it isn't, and we'd rather earn our point of view on it the same way we earned it on the rest of the Acquia stack: by putting it under real load first. It's not really a CMS anymore. It's Acquia's bet on what the next version of the web looks like, one where [AI does the work inside a real operating model](/blog/ai-operations-newsletter-failures) and a human stays in charge. If you're mapping whether Source fits your [Drupal roadmap](/blog/drupal-migration-audit-automation), or where it sits against Site Factory and MEO, that's a conversation we're set up to have with the technical detail intact. ## Related reading - [Stop announcing AI. Start showing the operating model behind it.](/blog/ai-operations-newsletter-failures) - [One engineer, one hackathon, 1,500 hours erased: automating migration audits for a 500-site Drupal fleet.](/blog/drupal-migration-audit-automation) - [The problem nobody talks about with AI coding assistants.](/blog/ai-coding-context-gap) - [Bridging legacy and modern: connecting iMIS and Drupal without full data migration.](/blog/imis-drupal-api-first-integration-without-migration) --- Read on the web: https://www.axelerant.com/blog/acquia-source-cms-ai-content-teams