# Acquia Source in Latin America: When to Run Your Content in a Single System ![2026-10_insight_acquia_source_en_latam_cuando_conviene_operar_tu_contenido_en_un_solo_sistema-v1](https://esinergia.widen.net/content/dudi3flyvs/web/2026-10_insight_acquia_source_en_latam_cuando_conviene_operar_tu_contenido_en_un_solo_sistema-v1.png?v=1026a2a1-a956-4c11-84d6-e454296c1d40) When a large organization feels that publishing content is slow, the usual conclusion is that it needs a better CMS. Teams compare editors, visual builders, and templates, and pick the one that looks easiest to use. The time usually goes somewhere else. The CMS editor tends to work fine; what slows a page down is the jumps between systems: finding the image in one place, checking accessibility in another, translating in a third, and repeating all of it on every site. Acquia Source is one answer to that problem, and it's worth evaluating with the problem first and the product second. ## **Why Did Running Content Across Many Sites Become a Systems Problem?** Running content across many sites became a systems problem because every step of editorial work grew its own tool. The CMS stores the text, the DAM stores the images, the governance tool checks accessibility and brand, and each site in the organization has its own instance. An [enterprise CMS](https://esinergia.co/en/services/ingenieria-de-plataformas-digitales/enterprise-cms) is a web content management system built for organizations with many sites, several editorial teams, and requirements for security, accessibility, and integration with internal systems. What sets it apart from a CMS for a small site is governance: roles, approval workflows, audit trails, and running many sites from a shared foundation. Here is the typical path of a single page at a university or a healthcare network in the region: | **Step** | **Where it happens** | **What gets lost in the jump** | |---|---|---| | Write and build the page | The site's CMS | Nothing yet | | Find an image with current rights | DAM or a shared folder | Search time and certainty about the license | | Check accessibility and brand | A governance tool, or nobody | Errors surface after publishing | | Translate | An outside vendor or a spreadsheet | The translated version goes stale at the first edit | | Publish on the organization's other sites | Each CMS separately | The same change is repeated site by site | Each jump adds a person, a wait, or a copy of the content. At a university with a portal per school, or a healthcare network with a site per location, that cost multiplies with every site and every change. ## **What Is Acquia Source?** Acquia Source is Acquia's digital command center for Drupal: it brings content management, digital asset management (DAM), content governance, and AI-powered site building into a single connected workspace. In its [product catalog](https://www.acquia.com/products), Acquia presents it as the layer where all of its products come together. Acquia Source has three entry points, and an organization can start with any of them: - **Acquia Source CMS**, the SaaS CMS built on Drupal, with Drupal Canvas as its visual page builder. We covered where Canvas is heading in [DrupalCon Rotterdam 2026: Where Drupal Canvas, AI in the Core, and Contribution Are Heading.](https://esinergia.co/en/insights/drupalcon-rotterdam-2026-where-drupal-canvas-ai-core-and-contribution-are-heading) - **Acquia Cloud Platform**, Acquia's managed hosting for Drupal sites with custom development. - **Acquia DAM**, the organization's digital asset library. The difference between Acquia Source and Acquia Source CMS matters when you evaluate. Acquia Source is the layer that brings the operation together; [Acquia Source CMS](https://www.acquia.com/products/source/acquia-source-cms) is one of the products that connects to it. How we work with the platform is on our [Acquia Source](https://esinergia.co/en/technologies/acquia/source) page, including when a SaaS CMS fits an enterprise operation. ## **What Changes When Content Runs in a Single System?** When content runs in a single system, the steps that used to happen after publishing move to before it, and the team stops copying the same content between tools. Three concrete changes explain the difference. ### **01. Reviews Happen Before You Publish** In Acquia Source CMS, accessibility scanning runs inside the publishing workflow, and brand policies also apply to AI-generated content. A contrast error or a missing alt text shows up while the page is still a draft, when fixing it takes minutes. For an institution that has to meet accessibility standards such as WCAG, the review no longer depends on someone remembering to run a separate tool. ### **02. Assets Come From the Same Place** Acquia DAM is one of the entry points to Acquia Source, so editors find and use approved images without leaving the workspace, and the organization keeps a single version of each asset with its license and expiration date. Why that consolidation became a priority for marketing teams in the region is the subject of [Enterprise Marketing Teams in Latin America Are Consolidating Media Assets in Acquia DAM](https://esinergia.co/en/insights/enterprise-marketing-teams-latin-america-are-consolidating-media-assets-acquia-dam). ### **03. AI Works Under Recorded Human Review** Acquia Source includes a site builder that drafts pages from a brief or a design, a writing assistant, and assisted translation. Acquia states that every AI-generated or AI-assisted action goes through human review before it's published, and translations stay in a "pending review" state until someone approves them. In regulated sectors, the risk committee's question is who approved each piece of content, and a single system keeps that record in one place. ## **What Does Your Team Still Own When the Platform Is SaaS?** A SaaS platform takes care of infrastructure, updates, and software security, and leaves the organization with the decisions that determine whether the operation works. That part doesn't appear in any product catalog, and it's where much of the outcome is decided in the organizations we work with across the region. Content governance stays with your team, in four responsibilities. **The content model and its owners.** The platform offers content types and components; deciding which ones the organization needs, which fields they carry, and who answers for each one is internal work. Without clear owners, a single system reproduces the disorder of separate systems in one place. **Governance across sites.** At a university with a portal per school, or a healthcare network with many locations, someone has to decide what's global and what's local: the brand, the shared components, the accessibility rules, and who can publish on each site. Acquia Source makes those rules easier to enforce; choosing them is still the organization's call. **Integrations with your own systems.** The systems that make an institution in Latin America unique, such as a university's student information system, a hospital's clinical system, insurer agreements, or local payment gateways, don't come connected out of the box. Before you choose a SaaS product, list the integrations each site needs and confirm with the vendor which ones it supports. **The AI approval process.** The platform records that someone reviewed the generated content; the organization defines who that someone is, what criteria they approve against, and which topics are never published without a second review. In regulated institutions, it pays to write that process down before turning AI on. ## **When Does Acquia Source CMS Fit, and When Does Another Option?** Acquia Source CMS fits when the marketing team needs to launch sites, microsites, and campaigns quickly without managing infrastructure. When a site depends on complex integrations with internal systems, the stronger option is managed Drupal on Acquia Cloud Platform or self-hosted Drupal with the provider the organization chooses. | **Criterion** | **Acquia Source CMS** | **Managed Drupal on Acquia Cloud Platform** | **Self-hosted Drupal** | |---|---|---|---| | Model | SaaS: Acquia runs the platform | Managed hosting with custom development | Infrastructure and operations owned by the organization or its provider | | Updates and security | Handled by Acquia | Acquia runs the infrastructure; the project team owns the code | Owned by the project team | | Integrations with internal systems (academic, clinical, ERP) | Limited | Full | Full | | Code customization | Limited to what the platform allows | Full | Full | | Typical use | Microsites, campaigns, short-lived sites | Integrated institutional portals | Portals with their own infrastructure requirements | At a university, an admissions campaign microsite fits Acquia Source CMS, and the academic portal connected to the student information system fits managed Drupal. A healthcare network sees the same split between a vaccination campaign and a patient portal connected to the clinical system. Both options coexist, and Acquia Source lets you run them from the same workspace. If you're evaluating a [Drupal agency](https://esinergia.co/en/insights/how-to-choose-best-drupal-development-team) or a partner to run these options in Latin America, the useful question is whether it can work with all three depending on each site, because in most large organizations they'll coexist. There are other valid compositions in the Drupal ecosystem. Dropsolid, for example, combines the CMS and marketing automation in a single data layer, as we explain in [Dropsolid Integrates Your Marketing Stack and CMS Into a Single Data Layer](https://esinergia.co/en/insights/dropsolid-integrates-your-marketing-stack-and-cms-single-data-layer). The difference between the version of Drupal built for marketers and an enterprise platform decision is covered in [Drupal CMS is for marketers. The enterprise decision does not change](https://esinergia.co/en/insights/drupal-cms-marketers-enterprise-decision). ## **How Do You Know if Your Operation Needs a Single System?** The fastest way to find out is to follow a real page from draft to publication and note every system it touches. Four questions organize the diagnosis, and you can answer them without buying anything. | **Question** | **Sign that a single system will help** | |---|---| | How many systems does a page touch before it's published? | More than three | | How many sites does your team manage? | More than five, with components and rules that should be the same | | Is accessibility checked before or after publishing? | After, or only during an audit | | Does AI-produced content have a recorded approver? | No approver, or the record lives outside the CMS | If most of your answers match the right-hand column, running separate systems already costs more than consolidating them. If your team runs one or two sites with little change, consolidation can wait. ## **What Should You Decide Now, and What Can Wait Three Years?** What's worth deciding now is what doesn't depend on the platform: the content model, governance across sites, and the AI approval process. The product choice for each site can follow the pace of your contracts and each portal's life cycle, because Acquia Source is adopted in parts, with no forced migration. | **Decision** | **When** | **Why** | |---|---|---| | Define the content model and its owners | Now | It works with any platform and takes the longest | | Write the approval process for AI-generated content | Now | Teams already use AI, whether or not a platform records it | | Consolidate assets in a DAM | Now, if image rights are a risk | It's the entry point with the least impact on existing sites | | Move microsites and campaigns to a SaaS CMS | When campaign volume justifies it | It frees the technical team for the integrated portals | | Migrate the integrated portals | At the end of support for their Drupal version or at contract renewal | It avoids migrating twice | Over the next three years, AI agents will produce a large share of a big organization's drafts. The bottleneck will move from writing to reviewing and approving, and organizations that have their content model, assets, and approval records in order will be able to publish more without losing control, whatever the platform. That's the promise of a DXP, or digital experience platform, as we explain in [What Is a DXP and Does Your Company Need One?](https://esinergia.co/en/insights/what-is-a-dxp-does-your-company-need-one). ## **Frequently Asked Questions About Acquia Source** ### **Does Acquia Source Replace Drupal?** Acquia Source is built on Drupal. Drupal is an open source CMS, and Acquia Source CMS delivers it as SaaS; according to Acquia, the Drupal skills, modules, and integrations an organization already has carry over. How we work with Drupal and Drupal CMS as the foundation for enterprise platforms is on our [Drupal](https://esinergia.co/en/technologies/drupal) page. ### **Do You Have to Migrate Every Site to Adopt It?** Acquia presents Acquia Source as a platform you adopt gradually, with no forced migration. An organization can start with Acquia DAM, with the sites it already runs on Acquia Cloud Platform, or with a new microsite on Acquia Source CMS, and add the other pieces later. esinergia is an Acquia Elite Partner and a Drupal Certified Partner Platinum, and has worked with enterprise organizations in Latin America since 2009. More on how we work across the ecosystem is on our [Acquia](https://esinergia.co/en/technologies/acquia) page. If you'd like the next analysis on running enterprise platforms, subscribe to Insights. ### Category - Plataformas Digitales Enterprise ### Gabriel Valencia Líder Enterprise Growth ### DATE 20 Oct, 2026