Acquia

Drupal's Entity/Field API underpinning Acquia is one of the most flexible content modeling architectures in any CMS. 20+ core field types (text, number, date, entity reference, media, geolocation via contrib, JSON via contrib), unlimited custom content types, schema-as-code via config export (YAML), and Paragraphs for deep nesting. Drupal 11 improved field reuse UX and text format enforcement. Not 92+ because schema-as-code is YAML config sync rather than a native programmatic API like Sanity or Optimizely's C# code-first.

Entity Reference fields provide robust cross-content-type references with autocomplete, select, and Views-based selection handlers. Bidirectional relationships achievable via Corresponding Entity References contrib module. Views integration enables reverse-reference lookups and filtered reference displays. Not graph-native, and bidirectional requires contrib rather than being built-in, which keeps it below 85.

Paragraphs module provides deep component nesting with unlimited depth and reusable paragraph types. Layout Builder adds layout-aware structured composition in core. Site Studio adds an additional component architecture with its own component library (50+ UIKit components). Drupal Canvas (CMS 2.0, early 2026) adds Content Templates with field slots — a drag-and-drop interface for structured content-type composition that replaces the forms-based Manage Display tab. Not 88+ because rich text output is still HTML, not portable structured text like Sanity's Portable Text.

Drupal's Typed Data / Validation API built on Symfony Validator supports field-level constraints, regex patterns, required fields, min/max, unique constraints, and custom error messages. Cross-field validation possible via custom constraint plugins or form alter hooks. Field Validation contrib module allows UI-configured rules without developer involvement. Powerful but complex rules require PHP development knowledge, keeping it below 80.

Content Moderation module in core provides configurable draft/published/archived states with full revision history. Diff module enables visual comparison between revisions. Scheduler module provides scheduled publishing. Drupal 11 unified entity revision editing across content blocks, nodes, and other entities. No content branching or forking capability, and the revision UI is functional but not as polished as purpose-built headless CMS offerings.

Drupal Canvas reached 1.0 GA (Dec 2025) and is now the default page-building experience in Drupal CMS 2.0 (early 2026) — a genuine drag-and-drop visual builder in core, free, with inline editing, reusable component libraries, Content Templates, and AI-assisted layout generation, replacing the legacy node/add form. Site Studio remains a premium add-on with 50+ UIKit components, and Layout Builder provides a third in-core option. Three visual editing tiers anchored by a now-default Canvas push this to the in-page drag-and-drop threshold; not higher because Canvas 1.0 is still maturing and Acquia Cloud customers must adopt Drupal CMS 2.0 to use it.

CKEditor 5 integration in Drupal 10/11 is mature with extensible plugin architecture, configurable toolbar per text format, inline media embedding via Media Library, and solid paste-from-Word handling. Custom CKEditor 5 plugins can add marks and annotations. Acquia AI Writing Assistant Agent (Source, Dec 2025) and the Conductor partnership add AI-driven writing assistance natively. Output is HTML rather than portable structured rich text (like Portable Text), which limits multi-channel reuse.

Acquia DAM provides enterprise-grade digital asset management with AI-powered auto-tagging via Google Gemini integration, video transcription, alt text generation, facial recognition, and an AI Copilot that gained .docx/.pdf document summarization in January 2026, plus 200+ integrations. Drupal core's Media Library is solid on its own with image styles for transforms and focal point via contrib. The combination is near-best-in-class, but Acquia DAM is separately licensed, so the base platform without DAM is more modest.

Acquia's Drupal-based platform does not provide native real-time co-editing. Content Lock contrib module enables pessimistic locking to prevent conflicts. CKEditor 5 Premium Features supports real-time collaboration but requires a separate CKEditor license and is not bundled with Acquia. No presence indicators or live activity feeds in the base platform. Acquia Source (SaaS CMS) added AI agents in Dec 2025 but has not announced built-in real-time co-editing.

Drupal core's Content Moderation provides customizable workflow states (draft, needs_review, approved, published, archived) with role-based transition permissions. The Workflows module allows defining multiple workflow configurations per content type. Scheduler module enables time-based transitions. Acquia Source's AI Web Governance Agent (Q1 2026) adds human-in-the-loop compliance scanning with queued review/approval and audit trails, but it augments rather than replaces workflow routing. Missing conditional routing and parallel approval paths without custom development.

JSON:API module in Drupal core provides a fully spec-compliant API with excellent filtering, sorting, pagination, sparse fieldsets, and includes for relationship loading. GraphQL available via mature contrib module. Both REST, JSON:API, and GraphQL can run simultaneously. Acquia promotes hybrid headless architecture with next-drupal for Next.js integration with preview and ISR support. Not 82+ because GraphQL is contrib rather than core.

Acquia Edge CDN is powered by Cloudflare or Akamai (per customer order) with global load balancing, DDoS protection, and WAF. Varnish caching layer is included on Acquia Cloud Platform. Drupal's cache tags system enables granular per-entity cache invalidation via the Purge module. Edge CDN is a separately purchased add-on. No edge computing or edge-side personalization capabilities.

Drupal has a robust internal hook/event system (Symfony Event Dispatcher + legacy hooks) but outbound webhook delivery to external systems requires contrib modules (Webhooks module, ECA). Acquia Cloud provides platform-level deploy hooks for CI/CD events. No built-in webhook management UI with retry logic, payload filtering, or HMAC signing in core. Functional but not as polished as purpose-built headless CMS webhook systems.

Drupal can operate fully headless via JSON:API/GraphQL, and Acquia promotes hybrid headless architecture. next-drupal provides Next.js integration with ISR. Acquia Content Hub enables content syndication across multiple Drupal sites. Acquia Source (SaaS CMS) is API-first but targets managed Drupal, not a standalone headless offering. Drupal was not born headless — going fully decoupled loses Canvas, Layout Builder, and Site Studio editorial UX. No official mobile SDKs. Rich text output is HTML, limiting true multi-channel portability.

Acquia CDP provides rule-based and ML-powered segmentation with 300+ filters for behavioral, demographic, and transactional data. Fuzzy clustering allows grouping into multiple ML segments with real-time evaluation. CDP is separately licensed — without it, segmentation is through Acquia Conversion Optimization (VWO-powered) which offers behavioral segmentation. Not higher because full capability requires CDP licensing.

Acquia Personalization (formerly Lift) reached end-of-life Jan 31, 2026, replaced by Acquia Conversion Optimization (powered by VWO, which merged with AB Tasty in early 2026). It provides segment-based content variants with a no-code Visual Editor for modals, banners, countdown timers, and content blocks, with per-segment preview. Not higher because the underlying engine is third-party (VWO) and CMS authoring integration is weaker than the legacy product.

Acquia Conversion Optimization (VWO) provides A/B, multivariate, and split URL testing with Bayesian statistics, plus heatmaps, session recordings, and on-page surveys for experiment insight. One-click rollout of winning variants. Not higher because it still lacks ML-powered auto-allocation or bandit algorithms found in Optimizely.

Acquia CDP provides ML-powered personalized recommendations with pre-built predictive models and fuzzy clustering. Content recommendations based on behavioral signals are available. However, there is no deeply integrated recommendation engine within the CMS authoring experience — recommendations are primarily CDP-driven and require integration work.

Acquia Search is transitioning from legacy Solr to Acquia Search powered by SearchStax in 2026, bringing enhanced analytics dashboards, search preview, and advanced configuration. Drupal's Search API provides a clean abstraction layer with faceting and autocomplete. Still lacks modern typo tolerance and NLP compared to Algolia; not lower because SearchStax upgrade meaningfully improves operational capabilities.

Drupal's Search API provides an excellent pluggable backend architecture supporting Elasticsearch, Algolia, Typesense, and Solr. Acquia has a formal Algolia TAP partnership for composable search. SearchStax migration provides additional Solr configuration options. Switching search backends is straightforward and well-documented.

Drupal Commerce provides a full native commerce solution with product catalog, cart, checkout, order management, and pricing engine. Acquia Commerce Framework (ACF) provides a lightweight reference framework for headless e-commerce. Mature and flexible but requires significant development effort; Acquia doesn't provide managed Commerce-specific infrastructure.

Acquia Commerce Framework (ACF) has established integrations with Shopify Plus, BigCommerce, and commercetools. Acquia DAM added native Shopify integration with automated asset synchronization in 2025. However, most integrations still require custom middleware development rather than being turnkey connectors.

Drupal Commerce product types with variations and attributes provide adequate product content modeling. Rich product descriptions leverage Drupal's flexible field system. Product media management via Media Library and Acquia DAM is solid with improved Shopify asset sync. Purpose-built PIM capabilities still require significant custom development.

Acquia CDP provides analytics dashboards with hundreds of summaries and visual insights. Acquia Conversion Optimization (VWO) adds heatmaps, session recordings, and on-page surveys. Acquia DAM Insights reveals content usage patterns. CMS-level content performance analytics (author productivity, content lifecycle) remain unavailable without CDP licensing.

GA4, Adobe Analytics, Segment, and other analytics platforms integrate via Drupal contrib modules (Google Tag Manager module, Analytics module). Acquia Conversion Optimization is a Google Analytics Integration Partner. Acquia CDP provides its own data integration capabilities. No platform-specific event helpers beyond CDP and Convert connectors.

Acquia Cloud Site Factory is a genuine differentiator — purpose-built multi-site management supporting hundreds of sites from a shared codebase with per-site configuration overrides and centralized governance. Acquia Content Hub enables cross-site content syndication with central admin and site-level autonomy. This remains one of Acquia's strongest capabilities.

Drupal's localization is mature and comprehensive: field-level translation (entity translation) in core, configurable locale fallback chains, native installation in 94 languages. Acquia Site Studio + Lionbridge integration provides a low-code localization workflow. A historical Drupal strength that remains highly competitive.

TMGMT module provides connectors to major TMS platforms including Smartling and Lionbridge. Acquia DAM supports metadata translation via Google Translate and OpenAI integrations. Batch translation operations are supported. The integration ecosystem is proven in enterprise multilingual deployments.

Acquia Site Factory + Content Hub provide a solid multi-brand governance foundation. Brand-level permissions via Drupal's role system, shared component libraries via Site Factory's shared codebase with brand-specific overrides, and centralized design system support (Site Studio is refocusing on design system and brand governance for 2026). Setup complexity is significant but the capability is strong once configured.

Acquia DAM (former Widen Collective) is a purpose-built enterprise DAM with unlimited custom metadata schemas, full version control with per-version metadata retention, asset-level usage tracking via Insights app, rights/expiry management with configurable alerts, bulk operations, AI auto-tagging (Amazon Rekognition), non-biometric facial detection with bulk backfill, and duplicate detection. Over 150 customizable roles with user audit trails. One of Acquia's strongest assets.

Acquia DAM delivers assets via Amazon CloudFront CDN with on-the-fly image and video transformations (resize, crop, format conversion, DPI/color space), and now confirmed full support for next-generation WebP and AVIF formats integrated with Drupal image styles for responsive delivery. Dynamic Embed Codes allow programmatic runtime optimization; focal point crop and ImageMagick transformations sync to Drupal (module v1.1.0). Strong modern asset delivery; not higher because transformation tooling is DAM-centric rather than a developer-facing image API like Imgix/Cloudinary.

Acquia DAM stores the highest-resolution master and transcodes on demand to requested formats, bitrates, frame rates, and resolutions. HLS adaptive bitrate streaming is native, automatically adjusting quality to device and bandwidth. DFXP, SRT, and VTT caption files are supported post-ingestion. Full-length video preview auto-generated; video clip creation supported. Vimeo native sync (asset + metadata) available. Strong enterprise video management for a DAM product.

Acquia Site Studio provides full drag-and-drop WYSIWYG page composition with in-place visual editing, a pre-built reusable component library, live preview, and a visual CSS style builder. Drupal Canvas (formerly Experience Builder) is now the default no-code drag-and-drop page builder in Acquia Source SaaS CMS and Drupal CMS 2.0; Site Studio is converging onto Canvas. Campaign Studio adds a separate visual email and landing page builder. A genuine strength of the Acquia platform.

Acquia Source supports multi-step content approval workflows with configurable states (Draft, Needs Review, Published, Archived, custom) via Drupal core Workflows/Content Moderation and role-based transition permissions. Acquia DAM Workflow adds annotation-based asset review with @mention, version comparison, and deadline assignment. However, workflows are not yet available for Drupal Canvas pages, SLA automation is not documented, and task assignment is basic.

Acquia Source SaaS CMS now provides native content scheduling for automated publication and unpublication, alongside Drupal's Scheduler and Scheduled Transitions contrib modules for date/time-specific publish/unpublish of moderated content. There is still no native branded editorial calendar view (requires an additional contrib module), and release bundles (atomic multi-item publish) are not a native product feature.

Acquia offers version history via Drupal Revisions and collaborative asset review via DAM Workflow (@mention, annotation, version comparison). DAM Collaborative Collections (2025) allow shared collection management, and Acquia Source supports inviting members with specific access levels. However, simultaneous multi-author editing with presence indicators is not a feature of Acquia Source or Drupal — last-write-wins locking is the model. No Google Docs-style collaborative CMS text editing.

Drupal Webform provides a rich native form builder with conditional logic (field-level show/hide, regex triggers), multi-step forms with progress bar, auto-save for authenticated users, submission storage exportable to CSV/XLSX/JSON, and handlers for Salesforce and HubSpot CRM. Acquia Campaign Studio Forms adds progressive profiling (different fields per contact visit) for known contact building. A genuine strength across the Acquia stack.

Acquia Campaign Studio (built on Mautic) provides a native multi-channel marketing platform with drag-and-drop email builder, dynamic content per segment, and channels including email, SMS, push notifications, web push, social, and direct mail. Native Salesforce CRM and Microsoft Dynamics 365 integrations are included. Acquia CDP connects to Salesforce Marketing Cloud. No native Marketo or HubSpot connectors (Campaign Studio competes with them).

Acquia Campaign Studio provides genuine native marketing automation: visual if/then journey builder, out-of-the-box and custom lead scoring models, multi-channel campaign management (email, SMS, push, social, ad tech, direct mail, IoT), drip campaign orchestration, and real-time journey analytics. Behavioral triggers from CMS events are supported. Comparable to Bloomreach's Campaign module in depth.

Acquia CDP (former AgilOne) unifies CRM, website, and third-party data with 300+ segmentation filters, ML-powered predictions and recommendations, real-time segment evaluation, and Privacy Management for GDPR/CCPA. Connects bidirectionally with Salesforce Marketing Cloud (audience segments + ML insights), Salesforce CRM, and CMS personalization via Conversion Optimization. Separately licensed but purpose-built and deeply integrated.

Acquia Exchange lists 219 integrations across 25 categories (AI, Analytics, Commerce, PIM, Search, Marketing Automation, etc.) with Native, Partner, and Community connector tiers. Drupal.org contributes thousands of additional modules. The 700+ global implementation partner network is one of the largest in the DXP space. Named integrations include Adobe Analytics, Adobe Commerce, Akeneo PIM, commercetools, Salesforce, and Algolia.

Webhooks exist across multiple Acquia products: DAM (9 event types: created, deleted, updated, category/tags/release date/expiration/group/version changes), Acquia Source CMS (node create/update/delete with webhook history and retry visibility), Campaign Studio (HTTP callbacks), and Content Hub (publisher-subscriber). No unified event streaming platform or Kafka-style bus. Signed payload documentation is unclear across products.

Acquia Cloud provides standard Dev/Stage/Prod environment tiers. Draft content preview connects to a configured Next.js frontend via Next.js Preview Mode integration; Acquia Source supports preview vs. production application role differentiation. Acquia CMS Headless ships an official Next.js starter kit. No on-demand per-branch preview URLs — preview requires developer-configured environments; not as capable as Vercel/Netlify preview deploys.

Acquia Cloud supports custom role definition (collections of specific permissions) and SAML 2.0 SSO (SP-initiated). Drupal provides field-level and content-type-level permissions via contrib modules. Acquia DAM offers 150+ customizable roles with SAML/LDAP/OpenID support. However, SCIM is explicitly not supported, IdP role mapping is not available, and a deprovisioning gap leaves SSH/Git credentials active after IdP deactivation.

Drupal's JSON:API is spec-compliant with consistent resource naming, filtering, includes, and sparse fieldsets, Acquia adds a JSON:API Query Builder for visual query construction/code generation and the sitestudio_jsonapi submodule to expose Site Studio layout data, and Acquia Cloud Platform API v2 exposes 200+ RESTful endpoints with OAuth 2.0 and interactive docs at cloudapi-docs.acquia.com. Not higher because Drupal's entity system complexity (entity types, bundles, field naming) leaks through in API responses and developer ergonomics lag purpose-built API-first platforms like Contentful or Sanity.

Acquia Cloud provides Varnish caching, Nginx reverse proxy, and integrated CDN with global POPs for cached content delivery, and Cloud Next's re-architected file system delivers up to 10 GB/s. Uncached API requests still hit Drupal's PHP stack which is inherently slower than purpose-built API services, rate limits are configurable but not well-documented publicly, and performance at scale requires deliberate caching architecture.

No official Acquia/Drupal multi-language SDK ecosystem comparable to Contentful or Sanity — the community-maintained next-drupal package provides Next.js integration (SSG/SSR/ISR, multi-language) with TypeScript support, Acquia DAM has an official TypeScript SDK (acquia-dam-ts-sdk on npm) with typed requests/responses, and PHP SDKs exist for backend integration. Python, Ruby, Go, and .NET SDKs are absent — teams use raw HTTP against JSON:API. Not lower because next-drupal is well-maintained and the DAM SDK is TypeScript-first.

Drupal.org hosts 50,000+ contributed modules covering virtually every integration category, Acquia CMS includes automated integrations with Acquia products (Site Studio, Acquia Search), Drupal Canvas 1.0 launched as default page-building experience with Site Template Marketplace, and the Acquia AI Provider service in Cloud Platform Enterprise acts as a gateway to supported LLMs. Module quality varies enormously — many are unmaintained — and the Acquia-curated enterprise integration set is much smaller.

Drupal's hook/plugin/event system is one of the most extensible architectures in any CMS: custom field types, custom entity types, form alters, middleware, Symfony event subscribers, and an attribute-based plugin system in Drupal 10/11. Drupal AI module provides an LLM integration framework, Drupal Canvas adds visual page composition, and there is virtually nothing you cannot customize or extend — this is a genuine platform strength.

SAML SSO via Acquia Cloud Shield, OIDC via contrib module, MFA via the TFA module, and API authentication via Simple OAuth (OAuth 2.0). The enterprise SSO stack requires assembling contrib modules rather than being built-in, adding friction compared to purpose-built enterprise platforms. Not lower because the functionality is fully achievable.

Drupal's permission system offers granular RBAC with unlimited custom roles, the Group module enables content-level access, Field Permissions enables field-level access, and the Node Access API enables instance-level restrictions. The permission UI is complex with hundreds of checkboxes and permission inheritance is limited — mostly flat role-permission mapping. Not higher because field-level and instance-level permissions require contrib modules.

Acquia Cloud holds SOC 1 & SOC 2 Type 2 (2025 cycle, Jan–Dec 2025), ISO 27001, CSA STAR, HIPAA, a 2026 PCI DSS Attestation of Compliance (released May 8, 2026), and FedRAMP authorization — Acquia is the only non-governmental Drupal hosting provider with FedRAMP, with a positive 3PAO recommendation secured March 2025. This is one of the strongest compliance postures in the CMS/DXP space and a meaningful differentiator versus peer DXPs.

Drupal has a dedicated Security Team with responsible disclosure and published Security Advisories, but 2026 has been a heavier critical-vulnerability year: a highly critical SQL injection in core's database abstraction API (SA-CORE-2026-004 / CVE-2026-9082, PostgreSQL-affected, May 2026) and eight advisories on June 17–18, 2026 including a critical PHP object injection via JSON:API write paths (SA-CORE-2026-005). Acquia adds platform-level security layers and all issues were patched responsibly, but there is no public Acquia bug bounty and large open-source ecosystem exposure (core + contrib) keeps this mid-band.

Acquia offers managed cloud hosting on AWS (Cloud Platform / Cloud Next) with Cloud Next on Kubernetes (EKS) using container-based isolation, EFS, and Aurora, and self-hosted Drupal is always available since it's open source. Acquia Cloud is AWS-only with no multi-cloud option, but the combination of managed cloud plus self-hosted fallback provides good flexibility.

99.95% uptime SLA on Cloud Platform Enterprise with a public status page at status.acquia.com, but 2026 incident frequency remains higher than ideal for an enterprise platform: a code-deployment outage on April 17, 2026 (~2.9 hours, git push rejections) and an Acquia Edge/Cloudflare service interruption resolved June 22, 2026, plus third-party monitors logging Campaign Studio/Site Factory login and CDP issues. The SLA commitment is competitive but actual reliability is mixed.

Cloud Next runs on Kubernetes (EKS) with a Cluster Autoscaler tuned for Drupal, self-healing infrastructure with auto pod pruning, a re-architected file system up to 10 GB/s, Aurora with up to 5x database throughput, and integrated CDN with global POPs plus Varnish/Nginx caching. Not higher because Drupal's PHP/database architecture still has inherent horizontal scaling limits at extreme scale.

Well-documented DR: RPO of 1 hour for production, RTO of 1 hour per 50GB, snapshot schedule of hourly (3h retention) / daily (7d) / weekly (4w) / monthly (3mo) stored in S3 via EBS, with multi-region failover available as an add-on with hot cloud recovery and real-time DB replication, plus drush sql:dump for content export. Multi-region failover is an add-on at extra cost and RPO degrades for environments over 500GB.

DDEV provides official Acquia integration for pulling databases and files into local Docker environments, Lando with Acquia plugin is supported, Acquia CLI replaced BLT (March 2025) for cloud platform interaction, and Cloud IDE plus Cloud Development Environments (CDEs) provide browser-based dev with Composer, Drush, and Git. Not higher because there is no official Acquia local dev server and local-production parity requires effort.

Code Studio (GitLab partnership, upgraded to GitLab 18.6 in early 2026) provides managed CI configuration with pre-built Drupal automation — no YAML config needed for standard workflows — alongside Acquia Pipelines, Acquia CLI (replacing BLT as of March 2025), dev/staging/prod environment management, Drupal config sync (drush config:import/export) for schema migration, and CDEs for branch-based environments. Not higher because there are no built-in deploy preview URLs and the workflow is not as streamlined as modern JAMstack platforms.

Documentation is split between docs.acquia.com (platform-specific, restructured developer portal, well-organized) and drupal.org/docs (community-maintained, inconsistent quality), with Acquia Copilot AI assistant for product docs and troubleshooting. Code examples are adequate but not excellent and the split documentation ecosystem creates friction for developers who must context-switch.

next-drupal provides TypeScript support with typed helper methods for Next.js integration, Acquia DAM has an official TypeScript SDK (acquia-dam-ts-sdk), and the TypeScript Definition Generator module on drupal.org can generate TS types from Drupal entity types. Auto-generated types from content models are still not a seamless first-party workflow and there is no typed JS SDK for the content API.

Acquia shipped Acquia AI to general availability and expanded Acquia Source into a 'digital command center' (April 28 / May 5, 2026), building on the December 2025 AI agents (Site Builder, Writing Assistant, Web Governance), with MCP-compatible agent integration (Claude, Cursor, GitHub Copilot). Drupal CMS 2.0 launched Drupal Canvas 1.0 as the default page builder, Drupal 11.4.0 shipped June 2026, and Drupal 12.0.0 is on track for H2 2026 — keeping core's 6-month minor cadence. Cadence is solid for a traditional DXP but still trails pure SaaS headless platforms.

Acquia maintains structured release notes across Cloud Platform, DAM, Optimize, and CLI products at docs.acquia.com, and Drupal core change records remain detailed. However, changelogs are still fragmented across multiple product docs rather than unified, breaking changes are not always prominently flagged, and migration guides can be incomplete for edge cases.

Drupal published a detailed AI 2026 roadmap (AI page generation, intelligent content creation/discovery, context management, AI governance) with 32+ organizations and 50+ contributors pledged, and Acquia maintains a public roadmap at acquia.com/product/roadmap with roadmap webinars. Drupal Canvas 1.0 hit production-ready status in late 2025. Still high-level rather than tactical with hard dates, and no public Canny-style voting portal.

Drupal's formal deprecation policy with @deprecated annotations, long deprecation windows, and Drupal Rector for automated code migrations keeps the 9->10->11->12 upgrade path relatively painless. The GitLab migration is well-documented but introduces workflow changes for contributors. Contrib module compatibility lag remains a pain point, and Acquia Source as managed SaaS shields end users from most of this.

Drupal still has one of the largest open-source CMS communities: 8,000+ individual and 1,100+ corporate contributors annually, 51,000+ modules, 1M+ registered drupal.org users, and DrupalCon plus Acquia Engage as major events. The AI Initiative has grown to 32+ organizations and 50+ active contributors. Mass remains huge but new-developer share continues to drift toward JavaScript-native platforms.

The Drupal AI Initiative has grown to 32-34 organizations and 50+ contributors pledging full-time staff with weekly velocity updates, and in May 2026 Acquia launched a 'Fair Trade Initiative' directing 2% of eligible partner-deal revenue to the Drupal Association — a structural funding boost to community sustainability. Acquia remains the #1 contributor to Drupal core, and the GitLab migration is reducing process friction. Outside these initiatives, day-to-day engagement is still concentrated among a small group.

Acquia's partner network spans 800+ global agencies, SIs, and technology providers, with Capgemini named 2025 Global Partner of the Year and a new 'Drupal AI Certified Partners' track recognizing AI delivery expertise. The May 2026 Fair Trade Initiative further binds the partner channel to Drupal Association funding. Formal certification, partner finder, and annual Engage Awards remain in place.

Drupal/Acquia content volume remains substantial: DrupalCon recordings, Acquia Academy, TheDropTimes news coverage, and Acquia's own blog. Third-party tutorials and books continue to age, and new entrants still skew toward JavaScript-based platforms. Newer Acquia Source and Acquia AI content is starting to land but is still sparse outside official channels.

LinkedIn shows 987 Drupal Developer jobs in the US and ZipRecruiter lists Drupal roles at $92k-$141k; TheDropTimes carries 131 dedicated Drupal Developer vacancies and 104 US Drupal jobs. Demand is concentrated in government, higher-ed, and enterprise agencies, and senior Drupal developers command premium rates due to relative scarcity. New developer talent continues to gravitate toward JavaScript-based platforms.

2026 Engage Awards highlighted strong customer outcomes — Arizona State University migrated 426 Drupal sites via Site Factory saving 3,408 hours/quarter, Rathbones consolidated sites for a 110% search visibility lift, and Yuhaaviatam of San Manuel Nation hit 98% accessibility compliance. Acquia AI GA and MCP-compatible integrations are strong forward signals. Net new tier-1 enterprise logo announcements outside the existing base remain moderate.

Acquia headcount stabilized at ~1,097 (April 30, 2026), modestly up from ~1,077 in December 2025 after the 2024-2025 onshore layoffs and shift to offshore hubs in India and Costa Rica. Vista Equity (owner since 2019) continues a margin-focused, cost-optimization strategy with no new funding since the 2015 Series G and no IPO/exit signals. Continued product investment (Acquia Source, Acquia AI, Fair Trade Initiative) and a profitable, scaled base offset the persistent PE squeeze, but long-term stability remains a moderate risk.

Acquia is positioned as a Leader in the Gartner Magic Quadrant for DXP for the sixth consecutive year alongside Optimizely and Adobe, recognized for its open-source community, 50,000+ plugins, and centralized development environment. The Acquia Source 'digital command center' plus Acquia AI GA and MCP-compatible agent integration strengthen its positioning. Competitive pressure from modernizing traditional DXPs and headless platforms remains real.

Acquia DXP holds 4.3-4.4/5 on G2 with strong review volume and was named a Leader in 41 G2 Winter Grid Reports, while Gartner Peer Insights shows the Acquia DXP at 4.4 overall (4.5 Integration & Deployment, 4.5 Service & Support) and DAM/Widen at 4.4. Common praise: customizability, reliable support, enterprise-grade security, managed infrastructure. Common complaints persist: pricing, complexity, learning curve.

Acquia Cloud Platform still publishes only five tier names (Entry/Standard/Plus/Premium/Elite) as feature-comparison grids with no dollar amounts — all sales-gated. Only the Professional sub-line shows partial pricing (~$141/mo Personal); DAM, CDP, Personalization, Content Hub, and Site Studio remain fully sales-gated. Among the least transparent platforms in the dataset; not lower because Professional pricing and overage rates are at least documented.

Per-product licensing with bundled infrastructure; enterprise deployments commonly $100K+/year per buyer reviews. Views/Visits overages billed at $100 per 15,000 Monthly Views or 4,500 Monthly Visits over allowance (whichever is greater), with a 30% buffer and three months of overage protection on new Cloud Plus subscriptions. Bot traffic still inflates Views/Visits at the infrastructure level despite Acquia's filtering, creating unpredictable spikes; each Acquia product (DAM, CDP, Personalization, Content Hub) adds a separate subscription line.

Drupal core and contrib are free open source, providing a solid baseline. But every meaningful enterprise capability is a separate paid product: Site Factory (multi-site), Content Hub (syndication), Personalization (targeting), CDP (customer data), DAM (assets), Site Studio (visual editing). Each capability requires its own subscription, creating heavy upsell pressure as use cases expand. Not bad gating per se — the open-source core helps — but the suite is bundled-by-design.

Acquia Cloud bills monthly with hourly-usage charges; Professional plans available monthly from ~$141/mo. A free Drupal CMS trial exists but the enterprise DXP remains annual-only with multi-year commits common, and the hosted platform trial is now heavily time-limited. A dedicated nonprofit solutions page exists but no public startup program or education discount; Capchase third-party financing enables monthly payment of annual contracts. Exit provisions depend on negotiation.

No meaningful free tier on Acquia's managed platform. The former Acquia Cloud Free sandbox now redirects to Professional starting at ~$141/mo, and the hosted platform trial is heavily time-limited. Drupal CMS itself is free open source — a no-expiration desktop trial and free download let developers evaluate the underlying CMS at no cost — but Acquia's managed cloud, DAM, CDP, and Personalization all require paid subscriptions.

Going from Acquia signup to first deployed content takes days to weeks: Drupal installation, content type modeling, theme setup, environment provisioning, deployment pipeline. The Drupal CMS (Starshot) initiative improves out-of-box onboarding — a free trial spins up Drupal CMS in-browser quickly — but production readiness on Acquia Cloud still requires Drupal expertise. Significantly slower than SaaS headless platforms where APIs can deliver content within hours.

Acquia DXP implementations typically run 3–9 months. Simple Drupal sites on Acquia Cloud can be delivered in 6–10 weeks; full DXP rollouts with Site Factory, Personalization, Content Hub, and DAM run 6–12 months. CRM/ERP/ecommerce/CDP integrations add significant complexity and SI partner involvement. Accelerated timelines require team scaling and higher cost.

Drupal/Acquia specialists carry a meaningful premium over generalist web devs. US averages cluster at $111,938–$115,303/year ($53.82–$55/hr); 25th–75th percentile $92K–$128.5K with top earners ~$147.5K. Freelance rates $61–80/hr globally, $50–$100/hr in US markets; Acquia-certified developers cost more upfront but deliver ~15% faster on enterprise setups. PHP/Drupal talent pool remains a specialist niche as JavaScript-first frameworks dominate broader hiring markets.

Acquia Cloud bundles hosting in platform licensing, eliminating separate infrastructure management. Professional Personal starts ~$141/mo with bundled storage, plus data transfer overages at $0.25/GB beyond 50GB/mo and disk storage at $0.275/GB/mo. The 30% capacity buffer helps with predictable months but bot-driven CDN cost spikes (cited up to 70% increase) create unpredictable hosting bills. Cheaper to self-host raw Drupal but you lose managed services.

Acquia Cloud meaningfully reduces ops burden vs. self-hosted Drupal — infrastructure, backups, security patching, and platform updates are managed. App-level ops remain: Drupal module updates, cache management, performance tuning, content migrations, security monitoring, and increasingly bot traffic management (WAF rules, traffic filtering). Most enterprise Acquia deployments require part-time to full-time DevOps attention.

Drupal core is open source with full data portability via MySQL dumps, Migrate API, and JSON:API — no proprietary content format — and Acquia's terms commit to making Customer Data and Applications available within 7 days of a termination request. But Acquia-specific products create meaningful lock-in: Site Factory configs, Content Hub syndication rules, Personalization segments, CDP profiles, and DAM assets are not portable to non-Acquia environments. Acquia's acquisitions (Widen DAM, AgilOne CDP, Monsido) form a closed ecosystem, and Drupal major-version upgrades remain expensive forklift efforts.

Developers must learn 15+ Drupal-specific concepts (entities, bundles, fields, render arrays, plugin system, hooks/events, config management, Twig theming, Views) plus Acquia-specific layers (Site Studio, Content Hub, Cloud Platform APIs, Acquia Source/Canvas). Canvas 1.0 (default in Drupal CMS 2.0, early 2026) adds a React/Tailwind component and page-building model on top, easing the author surface but not reducing the developer concept count. Not higher because Drupal's concept count remains among the highest in the CMS market.

Acquia Academy provides structured learning paths and certification courses, and Acquia Source SaaS offers dramatically faster onboarding — complete site installs in under three minutes with pre-built templates. Drupal CMS 2.0 ships guided site templates, Recipes, and AI-assisted setup, and a browser-based Cloud IDE removes local-environment friction. Not higher because resources remain scattered across Acquia Academy, Drupal.org, and community sites, and enterprise Drupal onboarding still requires deep platform knowledge.

Drupal remains PHP/Symfony with Twig, fundamentally different from the React/Next.js ecosystem, but Canvas 1.0 is now React + Tailwind + Single Directory Components with in-browser and local React tooling, narrowing the gap for component authoring, and the official next-acms Next.js starter provides a decoupled path. Not higher because backend module development still requires deep PHP/Drupal expertise that is non-transferable to mainstream JS web frameworks.

Acquia provides official Drupal Starter Kits including a Next.js starter (next-acms) with monorepo structure, default content model, OAuth, content preview, and on-demand revalidation wired in, and Drupal CMS 2.0 adds pre-built site templates and Recipes for faster launches. Community distributions (Varbase, Thunder) provide pre-configured starting points. Not higher because framework coverage beyond Next.js is limited — no official Nuxt, Astro, or SvelteKit starters — and starters remain less polished than purpose-built headless CMS platforms.

Drupal's configuration surface area is enormous — enterprise sites generate hundreds of YAML configuration files, requiring Config Split for per-environment management plus settings.php, services.yml, and environment overrides, and Acquia platform layers (Cloud Platform, Site Studio, Content Hub) each add significant surface. Acquia Source SaaS eliminates hosting/infra config, but enterprise self-hosted deployments remain complex. Not lower because config-as-code via config sync is well-supported and Acquia Source reduces initial setup burden.

Adding new content types and fields is straightforward in Drupal, but modifying or removing existing fields with data is risky and requires careful migration via update hooks and the Migrate API, and field type changes on populated fields require data migration scripts. Breaking changes cascade to Views, templates, and API responses. Not higher because schema changes with existing content carry real risk compared to schemaless headless platforms like Sanity or Contentful.

Drupal CMS 2.0 ships Canvas 1.0 as the default editor — a React + Tailwind experience builder with live preview, real-time in-place editing, and a reusable design-system component model — and Acquia Source delivers it as fully managed SaaS. For decoupled/headless Drupal, the next-acms Next.js starter now bundles content preview and on-demand revalidation, easing what was previously custom integration. Not higher because decoupled preview still requires a frontend codebase and SDK wiring rather than being fully plug-and-play.

Significant Drupal specialization is required for production work — Acquia offers four distinct certification tracks (Site Builder, Developer, Front End Specialist, Back End Specialist), reflecting the breadth of specialized knowledge needed across PHP, Drupal APIs, module development, theming, and config management, so a generalist web developer needs weeks to months of focused learning. Not lower because Acquia Source SaaS and Canvas reduce the barrier for simpler, non-enterprise projects.

Enterprise Acquia implementations typically require 3-8 people in specialized roles (backend Drupal developer, frontend/themer, DevOps/infra, and often Site Studio and platform specialists), and full multi-product DXP deployments commonly need 5-10+ team members. Acquia Source SaaS and AI Site Builder agents reduce the burden for simpler campaign sites. Not higher because multi-product DXP deployments demand larger specialized teams than headless CMS competitors.

Canvas 1.0 (default in Drupal CMS 2.0) lets marketers and content authors drag-and-drop components onto pages with live preview and no Drupal knowledge required, and Acquia Source AI agents automate site building from briefs, SEO/AEO content writing, and accessibility/governance scanning, while Site Studio adds no-code page assembly. Not higher because the Drupal admin interface still requires training for advanced content operations and complex workflows.

Drupal 10→11 is smoother than prior majors thanks to Rector automation and a deprecation-first approach, but contrib module readiness remains the bottleneck — many enterprise sites are deferring D11 into late 2026, with Drupal 10 EOL tied to the Drupal 12 release. Acquia Cloud handles infrastructure-layer updates, but the concurrent Cloud Next platform migration stacks a second upgrade track on top of core upgrades, including the forced Aurora MySQL 5.7→8.0 cutover (production Oct 2025) and PHP 8.5 introduction that surface breaking changes like reserved MySQL keywords and charset validation. Not higher because complex enterprise sites still routinely need weeks of work to clear contrib gaps and config changes.

Acquia Cloud auto-applies platform-level patches (OS, PHP, infrastructure) and holds ISO 27001 and CSA STAR certifications, and the Trust Center showed rapid response to React2Shell, Shai-Hulud 2.0 supply-chain activity, and the Gainsight OAuth token compromise. Drupal Security Team publishes advisories on a predictable Wednesday cadence with clear severity ratings. Not higher because Drupal core and contrib security patches still require customer-initiated code deployments — Acquia does not patch application code for you.

Multiple concurrent vendor-forced migrations remain active through 2026: Cloud Classic→Cloud Next enforced with only a 4-week postponement maximum, MySQL/Aurora 5.7→8.0 forced upgrade (production Oct 2025), Ubuntu 20.04→22.04 OS migration, Acquia Search sunset in 2026 forcing a SearchStax cutover, and the AcquiaID identity migration completed in 2025. The compressed, overlapping timelines and limited postponement options create unusually high migration burden for an enterprise DXP.

Drupal uses Composer for PHP dependency management, and enterprise sites typically run 30–80+ contrib modules, producing a large transitive tree with variable maintainer responsiveness. Acquia Cloud manages server-side dependencies (OS, PHP, DB, cache), but Composer update cycles, security update review, and contrib compatibility testing remain a recurring customer responsibility. Not higher because the contrib ecosystem still produces meaningful per-release coordination work — including the active scramble to ship D11-compatible releases.

Acquia provides Insight monitoring out of the box and bundles New Relic on higher tiers, plus the public Acquia status page for platform incidents. However, Cloud Next has documented monitoring gaps — no logs captured for SSH, Cloud Hooks, or scheduled tasks; downloaded logs may have extra or missing entries; FedRAMP memcache_admin metrics misreport because of per-instance mcrouter topology. Full application-level observability still requires layered tooling on top.

Drupal content operations stay manual-heavy: taxonomy management, broken-link detection (via contrib Link Checker), orphaned content cleanup, and content model upkeep all rely on editorial discipline plus contrib tooling rather than first-party automation. Reference integrity is not self-healing — broken entity references require manual cleanup, and Paragraphs-heavy content models multiply the ops surface. Not higher because there have been no significant platform-level content hygiene improvements in recent releases.

Acquia Cloud bundles Cloud Edge CDN and Varnish, and Cloud Actions automate cache clearing on deploys, reducing baseline perf work versus raw self-hosted Drupal. But Cloud Next introduces concrete frictions: web requests over 10 minutes can be interrupted by routine maintenance, and cVCL-based IP restrictions conflict with the Acquia Purge module. Teams still need to understand Drupal's multi-layer caching and tune database queries, so performance is not a hands-off concern.

Acquia offers 24/7 tiered support with dedicated TAMs and CSMs on enterprise plans, and 2026 G2/Capterra reviews highlight strong relationships with named contacts and deep Drupal/Acquia technical expertise. The persistent counter-signal is slow first responses and generic doc links on initial tickets, plus quality that scales sharply with tier. The March 13–14, 2026 multi-region load balancer outage also tested incident response across customers. Not higher because mid-tier customers still report markedly lower responsiveness than enterprise.

Drupal has one of the largest open-source communities — thousands of contributors on the D11 release, active Drupal.org issue queues, Drupal Slack channels, and Stack Exchange coverage. Acquia contributes significantly upstream and runs Acquia Academy for free e-learning. Quality varies — simple questions get answers in hours, but deeply technical or niche contrib problems can stall for weeks. Not higher because developer mindshare for Drupal continues a gradual decline relative to headless ecosystems.

Drupal core critical bugs are typically fixed in days to weeks via the standard release cycle, and Acquia platform issues follow SLA-based resolution. Contrib module fix velocity is highly variable — popular modules respond fast, niche modules can sit for months. The Cloud Next known-issues list shows several platform bugs persisting across releases, and the March 2026 multi-region outage is a reminder that infrastructure incidents still happen on a high-tier DXP. Not higher because the persistent backlog of Cloud Next known issues drags average velocity down.

Drupal Canvas — now the default page-building experience in Drupal CMS 2.0 (Jan 2026) and free in core — provides a no-code drag-and-drop page builder with inline editing, component libraries, content templates, and AI-assisted layout generation from text prompts. Site Studio continues as the design-system-focused visual component editor; the Acquia Source Site Builder Agent converts a creative brief into a live multi-page campaign site in hours. Marketers have three page-building paths without developer involvement. Not higher because Canvas's component ecosystem is still maturing and marketer autonomy still requires upfront component library setup.

Acquia Campaign Studio (Mautic-based) provides genuine campaign management: visual campaign builder, multi-channel orchestration (email, SMS, web), campaign analytics, and contact segmentation. Acquia CDP adds ML-powered audience segmentation and predictive analytics. However, Campaign Studio remains separately licensed with shallow CMS content integration — campaign content and CMS content live in different systems. Not higher because content calendaring within the CMS requires custom development and the campaign-CMS bridge remains shallow.

Drupal's SEO module ecosystem remains among the strongest in CMS: Metatag, Simple XML Sitemap, Redirect (co-maintained by Acquia), Pathauto, Schema.org modules, bundled in the Drupal CMS SEO Tools recipe. Acquia SEO powered by Conductor (native OEM integration, Feb 2026) provides content-level SEO scoring with body copy suggestions directly in the CMS. The April 2026 Acquia Source/Acquia AI release adds built-in Answer Engine Optimization (AEO) directly in the content creation workflow — content is structured for LLM readability out of the box for ChatGPT, Perplexity, and Google AI Overviews — eliminating fragmented third-party audit tools. Not higher because Conductor is separately licensed and the underlying Drupal SEO modules still require assembly.

Webform module provides excellent form handling and lead capture with conditional logic, multi-step forms, and CRM integrations. Campaign Studio adds conversion tracking and lead scoring. Acquia CDP provides audience segmentation and predictive analytics with ML capabilities. These tools are assembled from separate products rather than an integrated performance marketing suite, and CTA management has no native solution. Not higher because there's no unified performance marketing dashboard and CTA management remains custom.

Acquia Personalization reached end-of-life on January 31, 2026. The replacement, Acquia Convert (powered by VWO), focuses primarily on A/B testing and conversion optimization rather than rule-based content personalization. Acquia CDP provides ML-powered audience segmentation that can feed targeting logic. Without a native personalization engine, delivering personalized content experiences now requires assembling CDP segmentation with Convert testing and custom Drupal integration. This moves the story from native capability to orchestrated third-party integration.

Acquia Convert, powered by VWO (a leading experimentation platform), provides robust A/B testing, multivariate testing, split URL testing with Bayesian statistics, plus heatmaps, session recordings, and on-page surveys. As a first-party Acquia product it qualifies as a tight integration rather than a generic third-party tool. Campaign Studio also supports multivariate testing on landing pages with winner criteria including form submission rate, bounce rate, and dwell time. Not higher because Convert requires separate licensing and is not embedded natively into the CMS authoring interface.

Drupal Canvas enables drag-and-drop layout creation without development, with AI-assisted layout generation from prompts. Acquia Source Site Builder Agent can generate a complete multi-page campaign site from a brief in hours. Template cloning and reusable content blocks reduce cycle time. Content Moderation with configurable approval stages supports rapid-approval shortcuts. Inline editing is available in Drupal. Not higher because standard Drupal publishing cycles — particularly for sites requiring content review — involve multiple moderation steps, and complex new page templates still require developer involvement to create new Canvas components.

Acquia Content Hub enables content syndication across channels and sites. Campaign Studio orchestrates multi-channel delivery to email, SMS, web, and social. Drupal's API-first architecture enables structured content delivery to mobile apps and other digital touchpoints. Acquia DAM serves assets across channels with 80+ integrations. Not higher because multi-channel orchestration is assembled across three separate products (Content Hub + Campaign Studio + Drupal API) rather than being managed from a single publishing workflow.

Standard tag management via GTM module and GA4 integration enables page-level analytics. Conductor's native CMS integration (Feb 2026) surfaces SEO content performance within the authoring interface. The April 2026 Acquia Source release positions the platform as a unified workspace where teams manage content, applications, AI agents, and analytics in one place — consolidating analytics alongside content rather than only in external tools. Acquia CDP provides campaign-level engagement analytics. Not higher because the depth of native content-performance dashboards (views, engagement, decay tracking, heatmaps) in the consolidated workspace remains early and unproven relative to dedicated analytics platforms.

Site Studio is explicitly positioned as Acquia's design system management tool — enforcing brand guidelines through locked component palettes, style tokens, typography configuration, and approved overrides at the platform level. Marketers create within pre-approved component libraries, preventing off-brand pages. Site Factory extends this to multi-brand scenarios with brand-level theme isolation. Not higher because implementing Site Studio requires significant upfront design system work and the enforcement model depends on correct curation of the approved component set.

Metatag module provides comprehensive OG/Twitter card management with field-level control over social previews. Schema.org module adds structured data for content discovery. However, there is no native social scheduling, push-to-social workflow, or social media queue management. Social sharing buttons require contributed modules. UGC embedding requires custom development. Not higher because Acquia offers no native social scheduling — publishing to social requires external tools like Hootsuite or Buffer.

Acquia DAM (formerly Widen Collective) is a genuine enterprise DAM platform: AI-powered auto-tagging, video transcription, alt text generation, image transforms, rights management, usage tracking, and brand portal management. Over 80 pre-built integrations including Salesforce Marketing Cloud Content Builder and WordPress. Native integration with Acquia CMS for asset picker in content editing. Delivers up to 2x faster campaign launches and 100% brand compliance according to customer data. This is one of Acquia's strongest capabilities.

Drupal's multilingual architecture is mature and comprehensive: core Language, Content Translation, Configuration Translation, and Interface Translation modules enable full site localization. Locale-specific campaign content variants are possible via Drupal's translation system. Acquia Source AI Writing Assistant supports AI-powered content translation and market localization. Content Moderation supports locale-specific approval workflows. Not higher because transcreation workflows (human-in-the-loop localization with brand voice adaptation) and market-level campaign scheduling are not native — they require assembly of Drupal translation modules with custom workflow configuration.

Acquia's MarTech connectivity is broad: Campaign Studio (Mautic) includes 100+ out-of-the-box MarTech integrations spanning CRM, MAP, and CDP categories. Acquia DAM has native Salesforce Marketing Cloud integration. Drupal's connector library covers Salesforce CRM, HubSpot, Marketo, and Pardot. Acquia CDP connects to ad platforms for audience activation. Webhook and event-based triggers available via Campaign Studio and REST APIs. Not higher because some integrations are community-contributed rather than first-party maintained, and the overall connectivity requires assembly across separate Acquia products.

Acquia PIM centralizes product data management with AI-assisted enrichment, product hierarchies, distribution channel management, and marketplace connectors for real-time or scheduled distribution to ecommerce platforms. Combined with Acquia DAM for product media and Drupal Commerce for product modeling, the product content story is solid. Not higher because Acquia PIM is still maturing relative to dedicated PIM platforms, and deep variant hierarchy management and bulk attribute editing remain areas where specialized tools excel.

Acquia PIM adds product catalog management and distribution channel configuration, improving the merchandising content story. Acquia Digital Commerce with Commerce Framework provides commercetools-powered merchandising on the commerce side. Drupal taxonomy and Views enable basic category/collection pages. Native CMS-side merchandising features like search merchandising, visual merchandising, or automated cross-sell remain absent — merchandising intelligence still comes from the commerce backend. Not higher because Acquia has no purpose-built merchandising UI in the CMS layer.

Acquia Commerce Framework (ACF) is listed on the commercetools marketplace and includes BigCommerce integration via Third and Grove (the connector imports BigCommerce product data into Drupal as content nodes). Commerce Factory (TA Digital, Acquia's preferred composable commerce solution) integrates commercetools with planned deeper content integrations to Acquia DAM and PIM. Drupal Commerce offers a native commerce engine. ACF integrations remain partner-built rather than first-party Acquia connectors, and UI-level product reference in the content editor still requires implementation work. Not higher because integrations lack the deep API federation of AEM CIF or native marketplace connectors.

Drupal Commerce enables contextual commerce patterns — articles can embed add-to-cart buttons, and buying guides with inline product references are documented use cases. Acquia blogged about 'opening new doors for contextual commerce in Drupal' as an architectural pattern. However, shoppable editorial content (lookbooks, shop-the-look) is not a first-class authoring experience in the Drupal/Acquia UI — it requires custom content type design and frontend theming. Not higher because there is no native shoppable content editor or inline product picker in the CMS authoring interface.

Drupal Commerce owns the checkout flow, and CMS-managed content blocks can technically be injected into checkout templates through custom block regions. Acquia provides no documented native mechanism for CMS-managed trust badges, upsell banners, or shipping callouts in cart/checkout without modifying Drupal Commerce templates. This requires custom development work per deployment. Not higher because cart/checkout content management is not a documented or first-class Acquia capability.

Campaign Studio (Mautic) handles post-purchase email sequences triggered by commerce events — order confirmation, delivery tracking, review solicitation, loyalty messaging. This covers email post-purchase content management effectively. However, CMS-managed post-purchase web page content (order confirmation pages, onboarding sequences tied to purchase) remains in Drupal Commerce templates and requires custom development to make marketer-editable. Not higher because the CMS layer has no native mechanism to bind order events to CMS-managed content delivery.

Drupal Commerce includes B2B modules for quoting, invoicing, and group purchasing. The Group module enables account-based content visibility — gated catalogs, spec sheets, and account-specific content are achievable via Drupal's permission system. Drupal's 'Byte' template enables production-ready B2B SaaS site setup rapidly. Acquia Cloud adds enterprise-grade SSO for account authentication. Not higher because dedicated B2B UX patterns (customer-specific pricing display, quote-request flows with approval chains) require significant custom implementation rather than being native platform features.

Acquia Search (Apache Solr-powered) provides faceted search with content enrichment capabilities. Search API module enables blended content-product search results. Acquia + Yext AI search integration adds natural language understanding and AI-powered relevance for more intelligent product discovery. Search landing pages are buildable via Drupal Views. Not higher because dedicated search merchandising (pinned results, synonym management, search-driven promotional content) requires custom implementation, and the Yext integration adds cost.

Drupal's Scheduler module enables time-based content activation and deactivation — promotional banners, sale messaging, and countdown-adjacent content can be scheduled precisely. Drupal Views + Blocks enable channel-specific promotional content configuration. Campaign Studio adds promo-driven email and SMS campaigns with time triggers. However, there is no dedicated promotional content management UI — no countdown timer widget, no promo code display management, and no visual merchandising calendar. Marketers must work through Drupal's content editing interface. Not higher because the lack of a promo-specific layer means significant editorial overhead.

Acquia Site Factory provides the multi-storefront architecture — separate Drupal instances per brand/region sharing a codebase, with Acquia PIM providing shared product content distributed to each storefront. Content Hub Pull Syndication enables shared editorial content across storefronts with storefront-specific customization. Each storefront can have independent editorial and legal content while drawing from shared PIM product data. Not higher because the integration between Site Factory, PIM, and storefront-specific editorial layers requires deliberate architectural setup and adds operational complexity.

Acquia DAM provides strong foundational media management: image transforms (auto crop, resize, format conversion), video hosting with transcription, alt text generation, and structured media delivery. Product image galleries and video embeds in PDPs are well-supported. However, 360-degree product views, AR/3D model references, and image hotspot experiences require custom frontend implementation and third-party integration. Not higher because commerce-grade interactive media (360°, AR, zoom) is not native to the Drupal/Acquia stack.

Drupal's multi-author content system supports multiple contributors creating product descriptions, and Content Moderation enables editorial oversight. However, there are no marketplace-specific features: no seller profile management, no seller-contributed product description workflows, no review aggregation system, and no content quality moderation queue designed for marketplace scale. This use case is achievable only through extensive custom development. Not higher because Acquia has no marketplace content management product or documented marketplace implementation pattern.

Drupal's multilingual stack applies fully to product content — locale-specific product descriptions, translated attributes, and market-specific metadata are all achievable via Drupal's Content Translation module. Acquia PIM distributes product content by channel and region with locale-specific product listings. Market-specific regulatory content (EU labels, Prop 65) is manageable via locale-specific content variants. Not higher because currency-aware content blocks and regional promo calendar automation require custom implementation, and Acquia PIM's localization depth is limited compared to dedicated PIM platforms.

Acquia CDP can ingest commerce transaction data and correlate it with content engagement to support revenue attribution analysis. Campaign Studio provides conversion tracking for campaign-driven commerce. Acquia Convert (VWO) supports content-to-conversion testing analytics. However, none of these surfaces content-to-revenue attribution natively within the CMS editing interface. Content performance relative to commerce outcomes requires manual data assembly in external analytics tools. Not higher because there is no native CMS content performance-to-commerce dashboard.

Drupal's permission system remains among the most granular in CMS: the Group module enables audience-based content visibility by department/team, content-instance permissions are native, and field-level access control is possible. Acquia Cloud provides SAML SSO via Cloud Shield for enterprise authentication. LDAP integration is mature. This is one of Drupal/Acquia's genuine strengths for intranet use cases. Not higher because the permission architecture requires careful planning and significant upfront configuration effort.

Drupal's taxonomy system provides strong content organization. Acquia Search (Solr-powered) delivers quality internal search, enhanced by Yext AI search integration for Drupal-powered intranets with natural language understanding. Content lifecycle management via Content Moderation and Scheduler. Version history is built into Drupal core. Not higher because there are no purpose-built knowledge management features — no knowledge graph, no FAQ patterns, no article feedback — everything must be assembled from Drupal building blocks.

Acquia has a defined Employee Experience solution with Yext AI search integration for intelligent intranet search. Acquia Source's AI capabilities (content creation, governance scanning) improve the authoring experience for portal managers. Proven case studies like Pegasystems' Pega Portal show viability. However, there's still no native notification system, no employee directory, no personalized dashboard, and no mobile app. Not higher because Acquia remains a development platform for intranets, not a purpose-built employee experience product — building a full EXP requires extensive custom frontend work.

Drupal's content types and taxonomy support department-targeted news and announcements. The Group module enables department-specific content visibility for audience-targeted communications. Scheduler supports timed publication of internal announcements. Content Moderation provides approval workflows for communications content. However, there is no acknowledgment tracking, mandatory-read workflow, or read-receipt capability natively — these require custom module development. Not higher because targeted internal comms without acknowledgment tracking falls short of enterprise intranet requirements.

Drupal's Profile module enables basic employee directory with custom fields for skills and expertise. Team pages are buildable as content types. However, org chart visualization is not native — it requires third-party visualization libraries integrated with custom development. HR system integration (Workday, BambooHR) requires custom connector development. Acquia has no documented employee directory or org chart product feature. Not higher because a functional employee directory with org chart requires substantial custom Drupal development.

Drupal provides solid foundations for policy management: versioned content with full revision history, Content Moderation for approval workflows, Scheduler for review reminders, and content ownership via user assignment. File entity management for policy documents. However, acknowledgment tracking (required reads), automated expiry notifications, and audit trails for policy compliance are not native — they require custom development. Acquia Source's AI Web Governance Agent adds automated compliance scanning but focuses on accessibility and brand policy rather than document acknowledgment. Not higher because enterprise policy management requirements exceed Drupal's native capabilities.

Drupal's Role system and Group module enable role-specific content access restrictions, allowing new-hire content paths to be scoped by job function. Content types can be structured for onboarding sequences. However, progressive disclosure over 30/60/90 days, task checklists, HR-triggered portal access, and structured onboarding journeys are not native Drupal/Acquia features — they require significant custom module development or integration with an HCM system. Acquia has no documented onboarding delivery product or solution accelerator. Not higher because onboarding delivery requires extensive custom implementation.

Acquia Search powered by Apache Solr provides solid enterprise search with full-text indexing, faceted filtering, and relevance tuning. The Yext AI search integration adds natural language understanding, conversational search, and AI-powered relevance for Drupal intranets, meaningfully raising search quality for employees. Search API module enables multiple content source indexing. Not higher because federated search across external systems (SharePoint, Confluence, Google Drive) requires custom connectors, and the Yext AI integration carries additional licensing cost.

Drupal themes are mobile-responsive by default, providing basic mobile web access. Drupal PWA (Progressive Web App) modules exist for installable web app experiences with limited offline capabilities. However, Acquia provides no native mobile app for intranet access, no push notification system, and no documented frontline or deskless worker solution. Low-bandwidth optimization requires custom frontend work. Not higher because responsive web without native app, push notifications, or offline support is insufficient for frontline workforce access requirements.

Drupal can host training content as structured content types and serve as a learning content repository. Some community-contributed modules add basic course management. However, there is no native Acquia LMS integration with Cornerstone, Workday Learning, or similar platforms. Completion tracking, certification management, and course assignment require custom development or third-party LMS integration. Acquia has no documented learning or training product feature. Not higher because learning content hosting without tracking and certification is insufficient for enterprise L&D use cases.

Drupal provides foundational social features via the Comment module (commenting on content), Flag module (likes/reactions), and community-contributed Forum module for discussion boards. Polls module is available. However, there are no native peer recognition features, idea submission workflows, or structured community spaces by department or interest group without significant custom development. Acquia has no documented social or engagement layer product for intranets. Not higher because basic commenting without community management, engagement analytics, or peer recognition falls short of modern employee engagement platforms.

Drupal supports basic webhook and REST API integrations that could technically push content notifications to Slack or Teams channels. Community-contributed modules exist for basic Microsoft 365 or Slack webhook integration. The April 2026 Acquia AI roadmap signals MCP-compatible interfaces for external AI tools (Claude, Cursor, Copilot), but this targets developer environments rather than employee workplace tool integration. Acquia has no native, first-party integration with Microsoft Teams, Google Workspace, or Slack providing embedded content cards, bot-driven notifications, or single-pane experiences. Not higher because the lack of deep workplace tool integration significantly limits the platform for modern digital workplace deployments.

Drupal's Scheduler module handles automated publish and unpublish dates, enabling content expiry workflows. Content Moderation provides archival states in the content lifecycle. Content ownership is tracked via Drupal's user system. With the April 2026 Acquia AI launch, the Web Governance Agent is now GA (no longer projected) — automated governance scanning for stale and non-compliant content runs across sites from within the unified Acquia Source workspace. However, automated review-date reminders and content freshness dashboards still depend on the separately licensed governance tooling rather than core platform features. Not higher because governance capabilities require the Acquia Source/AI add-on rather than being core platform features.

Basic page view analytics are available via GA4 integration or Drupal's statistics module. Acquia CDP can provide audience-segmented engagement data. Acquia Search's Solr analytics can surface failed search terms. However, there is no native department-level content analytics dashboard, engagement heatmaps, adoption dashboards, or intranet ROI reporting built into the Acquia platform. Surfacing meaningful intranet analytics requires custom dashboard development combining multiple data sources. Not higher because the gap between basic page view data and actionable intranet engagement analytics is substantial.

Acquia Site Factory provides genuine multi-tenant architecture with separate databases per site, configuration isolation, brand-level settings, and independent content. Each site is a separate Drupal instance sharing a codebase. Site Factory Stacks support multiple dev teams, regions, brands, and even different Drupal versions. Confirmed deployments at scale: 437 sites in 50+ languages in 18 months. Not higher than AEM because the isolation model is codebase-shared rather than fully independent content models.

Site Factory's shared codebase model enables centralized component libraries consumed by all brand sites. Site Studio focuses on design system management and brand governance (explicitly differentiated from Canvas), enabling centralized component sharing with brand-level overrides. Content Hub with Pull Syndication enables cross-site content sharing. Acquia DAM serves as a shared media library. Not higher because there's no native design token versioning system — brand variations depend on theme configuration and the shared-with-overrides pattern requires deliberate architecture.

Site Factory provides centralized governance with granular permissions, enforced code standards, centralized updates, and cross-brand content policies. Content Hub enables cross-brand content publishing with approval workflows. The April 2026 Acquia AI launch brings the Web Governance Agent to GA — automated accessibility and policy compliance scanning across sites from a unified workspace. Multi-level governance (global → region → brand → site) is well-documented. Not higher because cross-brand approval workflows still require custom implementation via Content Moderation + Group patterns rather than being native to Site Factory.

Site Factory's shared codebase model provides genuine infrastructure efficiency — adding a new brand site costs less than deploying a separate Drupal instance. Centralized updates reduce per-site maintenance overhead. Volume licensing exists for multi-site. Acquia Source's SaaS model may further reduce per-site operational overhead. However, each site still requires database and hosting resources, Content Hub and PIM add cost for cross-site capabilities, and the absolute cost remains enterprise-level. Not higher because per-brand licensing increments are moderate rather than minimal.

Site Studio is explicitly designed for brand governance with per-brand theming: design tokens, typography, color palettes, logo treatment, and approved component overrides applied at the tenant level while sharing underlying component structures. Site Factory's brand-level configuration isolation enables independent visual identity per brand. This is a genuine differentiator for Acquia in multi-brand deployments. Not higher because implementing brand theming requires significant Site Studio configuration work, and true design token versioning (propagating token updates to downstream brands) requires deliberate architecture.

Site Factory's brand isolation combined with Drupal's multilingual stack enables per-brand localization with independent translation workflows per site. Content Hub can manage cross-brand translation coordination. Regional legal content can be isolated per brand site. However, a unified governance dashboard for the brand × locale matrix — managing per-brand translation approvals alongside cross-brand shared content — requires custom implementation. Not higher because managing the intersection of brand governance and locale governance is a complex operational problem that Acquia does not solve natively.

Site Factory's centralized dashboard provides operational visibility across sites (status, deployments, code versions) but does not provide content performance analytics. Per-brand GA4 integration delivers brand-level page analytics. Acquia CDP can aggregate engagement data. However, a portfolio-level analytics dashboard showing content velocity, engagement comparison across brands, publishing cadence benchmarking, and aggregate content performance is not a native Acquia feature. Not higher because cross-brand analytics requires manual aggregation from separate brand analytics accounts.

Content Moderation module supports independently configurable approval workflows per Drupal site on Site Factory — each brand can have its own review stages, approval chains, and scheduling logic. Site Factory's centralized management console provides some audit visibility across brands. However, a unified cross-brand audit log and centrally auditable workflow compliance dashboard requires custom implementation. Not higher because while per-brand workflow configuration is achievable, centralized audit trail management is not native.

Acquia Content Hub with Pull Syndication directly addresses corporate-to-brand content syndication: content created at the corporate level is published to a hub, brand sites subscribe and pull content with configurable override control. Legal disclaimers, product announcements, and press releases can be syndicated with local adaptation points. Controlled push updates propagate content changes to subscriber sites. This is a genuine first-class capability in Acquia's product. Not higher because override management requires deliberate configuration, and real-time push updates across large site portfolios can encounter latency.

Site Factory's per-brand site isolation enables independent compliance configurations per brand and region. EU Cookie Compliance module manages GDPR consent per site. Acquia Cloud's data residency options support regional data storage requirements. Acquia's AI Web Governance Agent (now GA, April 2026) scans for accessibility and policy compliance violations across sites. However, publishing guardrails that prevent non-compliant content publication are not native — compliance enforcement depends on workflow configuration and governance agent scanning rather than pre-publication blocking. Not higher because compliance is reactive rather than preventive at the platform level.

Site Studio is purpose-built for federated design system management: a core component library maintained centrally, brand-level extensions with controlled overrides, and centralized update propagation across tenant sites. With Drupal Canvas now the default page builder, Acquia has confirmed Site Studio's go-forward focus is specifically design system management and brand governance — features Canvas will not cover. Components are versioned and brands can be restricted to approved component subsets. This is Acquia's strongest multi-brand capability alongside tenant isolation. Not higher because design token versioning and structured update propagation to downstream brands requires careful orchestration and the tooling for managing component version updates at scale is not fully automated.

Site Factory provides centralized user management with SSO across all brand sites, granular per-brand permissions, and a central admin role that manages all brands from a single dashboard. Brand teams can operate autonomously within their site while central administrators maintain oversight and cross-brand access rights. SAML/SSO via Acquia Cloud Shield ensures consistent authentication. Not higher because cross-brand contributor roles (an editor who contributes to multiple brands but not all) require custom permission configuration and Site Factory's user management UI can be complex to administer at large brand counts.

Site Factory's shared codebase model allows globally defined content types to be shared across all brand sites. Brand-specific extensions to content models are achievable via Drupal's field system — Brand A can add video fields and Brand B can add comparison table fields to a shared base type via codebase-level configuration. However, this requires codebase management coordination rather than UI-level self-service model extension. Brands cannot independently extend content models without developer involvement at the codebase level. Not higher because the extension model is developer-mediated rather than brand-team self-service.

Site Factory's centralized dashboard provides operational portfolio visibility: site status, code versions, deployment history, and security patch status across all brand sites. This is operational reporting, not editorial or business performance reporting. Content freshness by brand, publishing SLA adherence, and cost allocation per tenant are not available natively. Building executive portfolio reporting requires integrating Site Factory operational data with per-brand analytics from GA4 and custom data warehousing. Not higher because the gap between operational monitoring and executive editorial reporting is substantial.

Acquia provides a pre-signed, self-serve DPA (not enterprise-only) with EU/Switzerland SCCs and UK IDTA for cross-border transfers, plus CCPA/CPRA and US state privacy law provisions. EU data residency available via AWS EU regions with contractual guarantee Acquia will not move data without prior written consent. Public sub-processor list and per-product GDPR Product Notices published, with Acquia Sarl/Acquia LTD appointed as EU and UK Article 27 representatives. Not higher because the large sub-processor count (40+) creates complexity for strict GDPR governance.

Acquia is one of the few enterprise CMS platforms offering a HIPAA BAA, available at contract time, with HIPAA-eligible Drupal hosting that logically separates HIPAA from non-HIPAA customers and adds filesystem/database encryption. Healthcare is a documented vertical with a dedicated HIPAA-compliant AEM-alternative offering, and the SOC 2 Type 2 report maps controls to HIPAA. Not higher because the BAA covers Acquia infrastructure only — customers remain responsible for application-level HIPAA controls in their Drupal code.

Acquia Cloud Next holds FedRAMP Authorized status with an agency ATO from the U.S. Department of the Treasury, making it the only commercial Drupal hosting company with this designation (+15). DPA covers CCPA/CPRA, UK IDTA, VCDPA, CPA, CTDPA, UCPA; PCI-DSS listed for commerce; LGPD addressed via DPA. Not higher because IRAP (Australia) and C5 (Germany) certifications are not documented.

Acquia released the 2025 SOC 2 Type 2 report covering January 1–December 31, 2025, with Security, Confidentiality, and Availability trust service criteria. Audit scope includes Acquia Cloud (Classic & Next), CDP, Campaign Studio/Factory, and DAM. SOC 1 Type 2 also maintained; reports available via SafeBase-powered Trust Center at security.acquia.com. Not higher because Processing Integrity and Privacy TSCs are not confirmed in scope.

Acquia released the 2025 ISO 27001 certificate with supporting Statement of Applicability, confirming platform-scope certification (not just AWS inheritance), with annual surveillance audits maintained. ISO 27018 for cloud PII processing is not explicitly listed among Acquia's certifications, which caps the score below 80 per the rubric. Not lower because the ISO 27001 scope is comprehensive and current.

Strong additional certification portfolio: CSA STAR certification (third-party Level 2 audit, not self-assessment), FedRAMP Authorized, FISMA, PCI-DSS, and SOC 1 Type 2. This is among the strongest additional cert portfolios in the DXP space, driven by government and healthcare vertical focus. Not higher because certifications like IRAP, C5, ENS, or Cyber Essentials Plus are absent.

Customers select geographic region at contract time from US, EU, and APAC options. DPA provides contractual guarantee that Acquia will not move data without prior written consent unless required by law. Sub-processor list confirms AWS customer-selected regions and Google Cloud regions (us-central1, australia-southeast1, europe-west1). Not higher because CDN (Cloudflare) distributes cached content globally, which may impact strict residency requirements, and APAC availability is limited to specific products.

Privacy Trust Center includes a DSR self-service portal for deletion, access, and updates, and the DPA documents retention and post-termination deletion terms. Content export via Drupal-native capabilities and Acquia APIs; platform logs retained 30 days in user-accessible UI and 390 days in SIEM. Not higher because self-service data export tooling is primarily Drupal-native rather than purpose-built, and specific retention periods for customer content are not publicly documented.

Acquia Cloud Platform provides comprehensive logging at application and platform layers, with a SIEM system retaining logs for 390 days. The Notifications API provides detailed audit logs of team and permission actions at the organizational level via Cloud Platform UI, supporting FedRAMP compliance, and log forwarding is available for Cloud Next and Classic environments. Not higher because configurable retention periods for customers and native push to third-party SIEM (vs. log forwarding) details are limited.

Acquia has targeted WCAG AA since 2017 engineering standards and now aims to adhere to WCAG 2.2 Level AA; Drupal core conforms to WCAG 2.1 and ATAG 2.0. Testing methodology includes Lighthouse, axe, VoiceOver, and keyboard testing, with ACRs completed for select products. Acquia acknowledges software is not yet fully AA compliant but is working toward it. Not higher because full AA conformance is stated as a goal rather than formally verified across the platform.

Acquia publishes ACRs/VPATs for select products (notably DAM) at docs.acquia.com, moving beyond just an accessibility statement, alongside its published accessibility statement. However, VPATs cover only select product areas, not the full platform, and no separate Section 508 formal conformance statement is published. Not higher because VPAT coverage is partial rather than comprehensive across all Acquia products.

The AI Writing Assistant Agent (part of Acquia Source) structures content for SEO and answer-engine optimization (AEO), and the April 2026 'Acquia AI' launch added a no-code platform to build/deploy content-optimization agents with built-in domain knowledge plus ready-made agents. Generative content creation is embedded in Drupal CMS. Held below 70 because brand-voice controls and custom prompt templates are not yet documented as mature, and the Writing Assistant was still maturing from Limited Availability.

Acquia DAM applies computer vision and generative AI across the lifecycle: AI-generated alt text (via ChatGPT vision with a customer-supplied OpenAI key), AI captions, and computer-vision auto-tagging; alt text also auto-generates when assets enter the Drupal Media Library. DAM 'Asset Intelligence' AI agents are announced for later in 2026. No native image generation (DALL-E/Firefly) found, capping it below 65.

Acquia DAM offers AI-assisted translation and transcreation for copy, product info, metadata, and video, and Drupal AI editorial workflows now cover localization and tone. With Acquia AI's connection to 48+ model providers, customers can route translation to their preferred LLM. Brand-voice fidelity across locales and bulk quality scoring remain lightly documented, keeping it mid-range.

Multiple AI metadata layers: Acquia Optimize (formerly Monsido) automates SEO auditing across domains, the Writing Assistant generates SEO/AEO-optimized content, DAM computer vision auto-tags and auto-generates alt text, and a Conductor OEM partnership embeds AI content optimization natively. Acquia AI's content-optimization agents extend this further. Held below 70 as a single unified auto-generate-titles/descriptions/schema-with-scoring workflow is not documented end-to-end.

Several AI workflow assists are woven into editorial: DAM computer-vision auto-tagging, Drupal AI tagging, the Writing Assistant for bulk generation, the Web Governance Agent for automated policy/accessibility remediation, and—new in April 2026—a no-code Acquia AI builder for deploying custom content-ops agents. Acquia Search (SearchStax) adds no-code search optimization. Multiple production AI assists place it above 60.

Acquia AI (April 2026) is a no-code platform to build, manage, and deploy AI agents, shipping with ready-made named agents — Site Builder (brief-to-live-site), AI Writing Assistant, and the Web Governance Agent (continuous scan + remediation) — alongside human-in-the-loop governance with full audit trails and batch approval. This is production agentic automation with named agents and governance, squarely in the 55–75 band; not 80+ because some agents (e.g. DAM Asset Intelligence) and full GA of MCP-agent integration are still rolling out.

The Web Governance Agent continuously scans properties for content-quality gaps, SEO risks, accessibility deficiencies, and privacy concerns; Acquia Optimize tracks content health and stale content; and Acquia CDP adds predictive analytics for next-step anticipation. Still no dedicated AI content-intelligence dashboard with topic clustering or ROI attribution, keeping it below 60.

Acquia Optimize (formerly Monsido) plus the AI Web Governance Agent form a strong audit suite: continuous scanning and in-platform remediation across accessibility (WCAG), content quality, SEO, and data-privacy (GDPR/CCPA) — at scale with human-in-the-loop review. This covers quality + accessibility + compliance, justifying the high-60s; held below 70 because explicit brand-voice compliance scoring is still maturing.

Acquia Search powered by SearchStax (GA Feb 2025) provides NLP, Smart Match Assist, related searches, and predictive keyword recommendations across tiered plans, with semantic/vector search on Solr 9 documented in production for Drupal sites. The new Acquia Source MCP server also exposes content for RAG-style agent retrieval. Held below 65 because the most capable AI tiers are paid add-ons and native embedding/RAG APIs are not fully documented.

Acquia CDP ships pre-built predictive ML models, persona-based clusters, personalized recommendations, real-time adaptive targeting, and predictive analytics that anticipate the customer's next step — a genuine ML personalization layer, not just rules. Held below 70 because the depth of cold-start handling and the tightness of CDP-to-CMS personalization orchestration are less documented than dedicated engines like Bloomreach Loomi or Sitecore CDP.

Acquia now ships an official Acquia Source MCP server (documented at docs.acquia.com) that exposes resources, resource templates, and tools letting AI agents read/list content types, media types, vocabularies, and Drupal Canvas, plus create and manage content; an official Drupal-as-MCP-server developer guide complements it. MCP-compatible agents (Claude, Cursor, GitHub Copilot) can connect directly, with full GA planned for a future release — placing it in the official-server-with-limited-ops band rather than 75+.

Acquia AI (April 2026) connects to 48+ AI providers — including OpenAI, Anthropic, Google Gemini, Azure, and AWS Bedrock — with no code changes, so customers are not locked to a vendor model; the DAM alt-text integration already uses a customer-supplied OpenAI key. This breadth of provider choice meets the full-BYOM bar (75+); kept at 76 rather than higher pending explicit data-residency/region controls for model routing.

Acquia exposes agent-ready extensibility: the official Source MCP server and a published Drupal-as-MCP developer guide, a no-code agent builder, connectivity to 48+ model providers, and direct integration with MCP clients (Claude, Cursor, Copilot) — on top of Drupal REST/JSON:API/GraphQL and the Acquia AI Provider module. Strong agent-oriented tooling with official guides approaches the 70+ tier; held at 66 because a packaged Acquia AI SDK and LangChain/LlamaIndex guides are not yet published.

Acquia Source enforces human-in-the-loop governance: every high-risk AI action requires human review before reaching production, queued with full audit trails and batch approval. The Web Governance Agent adds brand/policy consistency enforcement, and ISO 27001/CSA STAR underpin infrastructure trust. Good governance with audit trails plus brand guardrails lands it in the 50–70 band; below 75 as AI-specific hallucination/confidence scoring and IP indemnification are not documented.

Acquia Source's approval queues and audit trails give administrators visibility into AI actions, and SearchStax Premier tiers provide search analytics. But dedicated AI cost/credit tracking, per-user AI consumption metrics, prompt-effectiveness analytics, and quota/billing dashboards are not documented despite the 48-provider BYOM model — leaving observability minimal.