Application Launcher

Docs

Acquia AI is a set of AI capabilities inside Acquia Source, Acquia's platform for digital experiences. You ask an AI agent about your sites and applications, and you hand it routine work: a fix, an update, or a new page. Nothing the agent produces goes live until a person approves it.

Acquia AI requires no installation. Acquia enables it for accounts in phases and notifies each account when it is enabled. For details, visit Getting started with Acquia AI.

Who Acquia AI is for

Acquia AI serves three roles. An administrator decides which users get access, so access does not depend on job title. Anyone with access can ask questions and get answers drawn from Acquia product documentation.

Marketer: owns campaigns and the pages behind them. Uses Acquia AI to build campaign pages, check pages for accessibility, readability, and spelling, and find assets in Acquia DAM.
Site builder: assembles the site in the browser, including content types, layouts, and navigation, without a code editor. Uses Acquia AI to build and update Source CMS sites and to apply suggested fixes for a reviewed set of accessibility errors.
Operator: owns uptime. Uses Acquia AI to find out whether a slow or failing application is caused by the application or the platform.

Acquia AI does not change application code or infrastructure configuration. That work stays in the Acquia command-line interface and Acquia APIs, which are documented separately.

Capabilities

Task	Outcome
Ask a grounded question	The agent provides answers from Acquia product documentation with sources. The agent takes no action.
Build or update a Source CMS site	Users describe the requirements, such as a campaign page, microsite, or site structure change. The agent proposes a plan for approval and generates a draft. Publication requires a separate approval.
Run a governance check and apply a fix	The agent evaluates a page for accessibility, readability, and spelling, returns a score with plain-language findings, and fixes reviewed accessibility errors on a connected Acquia Source site.
Diagnose a slow or failed application	The agent analyzes logs and metrics for a specified environment and time window, then reports whether the cause resides in the application or the platform. The agent returns structured findings instead of raw log lines.

Acquia AI requires no installation. Acquia enables it for accounts in phases and notifies each account when it is enabled. For details, visit Getting started with Acquia AI.

Who Acquia AI is for

Marketer: owns campaigns and the pages behind them. Uses Acquia AI to build campaign pages, check pages for accessibility, readability, and spelling, and find assets in Acquia DAM.
Site builder: assembles the site in the browser, including content types, layouts, and navigation, without a code editor. Uses Acquia AI to build and update Source CMS sites and to apply suggested fixes for a reviewed set of accessibility errors.
Operator: owns uptime. Uses Acquia AI to find out whether a slow or failing application is caused by the application or the platform.

Acquia AI does not change application code or infrastructure configuration. That work stays in the Acquia command-line interface and Acquia APIs, which are documented separately.

Capabilities

Acquia AI requires no installation. Acquia enables it for accounts in phases and notifies each account when it is enabled. For details, visit Getting started with Acquia AI.

Who Acquia AI is for

Marketer: owns campaigns and the pages behind them. Uses Acquia AI to build campaign pages, check pages for accessibility, readability, and spelling, and find assets in Acquia DAM.
Site builder: assembles the site in the browser, including content types, layouts, and navigation, without a code editor. Uses Acquia AI to build and update Source CMS sites and to apply suggested fixes for a reviewed set of accessibility errors.
Operator: owns uptime. Uses Acquia AI to find out whether a slow or failing application is caused by the application or the platform.

Acquia AI does not change application code or infrastructure configuration. That work stays in the Acquia command-line interface and Acquia APIs, which are documented separately.

Capabilities

Task	Outcome
Ask a grounded question	The agent provides answers from Acquia product documentation with sources. The agent takes no action.
Build or update a Source CMS site	Users describe the requirements, such as a campaign page, microsite, or site structure change. The agent proposes a plan for approval and generates a draft. Publication requires a separate approval.
Run a governance check and apply a fix	The agent evaluates a page for accessibility, readability, and spelling, returns a score with plain-language findings, and fixes reviewed accessibility errors on a connected Acquia Source site.
Diagnose a slow or failed application	The agent analyzes logs and metrics for a specified environment and time window, then reports whether the cause resides in the application or the platform. The agent returns structured findings instead of raw log lines.

Task	Outcome
Ask a grounded question	The agent provides answers from Acquia product documentation with sources. The agent takes no action.
Build or update a Source CMS site	Users describe the requirements, such as a campaign page, microsite, or site structure change. The agent proposes a plan for approval and generates a draft. Publication requires a separate approval.
Run a governance check and apply a fix	The agent evaluates a page for accessibility, readability, and spelling, returns a score with plain-language findings, and fixes reviewed accessibility errors on a connected Acquia Source site.
Diagnose a slow or failed application	The agent analyzes logs and metrics for a specified environment and time window, then reports whether the cause resides in the application or the platform. The agent returns structured findings instead of raw log lines.
Find assets in Acquia DAM	The agent returns matching assets with previews, metadata, usage rights, and links, and can update them within the permissions a DAM administrator has granted.

Operational framework

Three factors determine the output generated by the agent:

Drupal and Acquia integration: The agent utilizes the existing content model, component library, and deployment path of the site.
Standards compliance: Work produced on a Source CMS site adheres to WCAG 2.1 Level AA, meets performance standards, and follows provided brand guidelines.
Two-stage approval: The agent proposes a plan and takes no action without human approval. Publication requires a second, distinct approval.

Operational modes

Acquia AI operates in two modes. The selected mode determines accessible resources and AI credit consumption.

Advisor mode: Answers questions using product documentation and basic account or subscription details. Advisor mode cannot access sites, applications, or environments, takes no action, and does not consume AI credits.
Work mode: Performs actions using a dedicated identity separate from the user. Work mode reaches only assigned applications and sites, requires approval for all changes, and consumes AI credits.

For additional details, visit Modes in Acquia AI.

Governance framework

Governance in Acquia AI is four things:

Administrator-controlled access. When Acquia enables Acquia AI for your organization, only organization owners and administrators have access. An administrator then grants access to each user who needs it and can remove it at any time. Both changes take effect immediately. Access covers both modes. See Get access to Acquia AI.
A bounded set of capabilities. The agent can do only what this release allows. It does not change application code or infrastructure configuration.
A scoped agent role. The agent holds the Agent role. This role was built for the agent and is not borrowed from a person, so the agent never inherits a user's permissions. On Cloud Platform, an administrator chooses exactly which permissions the Agent role holds. See Give the agent access to applications and sites.
Human approval at two points. The agent does nothing until a person approves its plan. Publishing is a second, separate approval.
This release does not include a customer-visible record of agent activity. Every user with access can delegate the same tasks, because the Agent role applies to the whole project, not to the person asking. See What Acquia AI does not do.

Note

This release does not include a customer-visible record of agent activity or automatic reversals for approved changes. Users with access to Acquia AI can delegate the same set of tasks because the agent role applies to the entire project. For additional details, refer to Governance and control management.

Acquia AI and Drupal AI

Acquia AI and Drupal AI operate at different structural layers:

Acquia AI: Works across installed Acquia products, including Acquia Source CMS, Acquia Cloud Platform, Acquia Web Governance, and Acquia DAM. This integration enables page checks, content creation, and platform health evaluation within a single conversation.
Drupal AI: Represents the open-source Drupal community ecosystem of contributed modules, recipes, and practices. Acquia contributes to this ecosystem.

Organizations can run both solutions simultaneously.

Access to Acquia AI

If an administrator has given you access:

Log in at source.acquia.com.
Open Acquia AI, or start a chat in Acquia Source.

When Slack integration is configured, Acquia AI sends Slack notifications when work requires review. Approvals must take place in Acquia Source. For details, visit Connect Slack for review notifications.

Next steps

To begin use of Acquia AI:

Confirm that your account is eligible and that an organization administrator has given you access to Acquia AI. For details, visit Accessing Acquia AI.
If you administer the organization, give the agent access to the applications and sites it should reach. For details, visit Assign the agent to an application and a site.
Ask a question first. Asking uses no AI credits, so it is the safest way to learn what the agent knows about your setup. For details, visit Ask a question in Advisor Mode.
Delegate a small task and approve the result. For details, visit Delegate a task and approve the work.

Did not find what you were looking for?

If this content did not answer your questions, try searching or contacting our support team for further assistance.

Operational framework

Three factors determine the output generated by the agent:

Drupal and Acquia integration: The agent utilizes the existing content model, component library, and deployment path of the site.
Standards compliance: Work produced on a Source CMS site adheres to WCAG 2.1 Level AA, meets performance standards, and follows provided brand guidelines.
Two-stage approval: The agent proposes a plan and takes no action without human approval. Publication requires a second, distinct approval.

Acquia AI operates in two modes. The selected mode determines accessible resources and AI credit consumption.

Advisor mode: Answers questions using product documentation and basic account or subscription details. Advisor mode cannot access sites, applications, or environments, takes no action, and does not consume AI credits.
Work mode: Performs actions using a dedicated identity separate from the user. Work mode reaches only assigned applications and sites, requires approval for all changes, and consumes AI credits.

For additional details, visit Modes in Acquia AI.

Governance framework

Governance in Acquia AI is four things:

Administrator-controlled access. When Acquia enables Acquia AI for your organization, only organization owners and administrators have access. An administrator then grants access to each user who needs it and can remove it at any time. Both changes take effect immediately. Access covers both modes. See Get access to Acquia AI.
A bounded set of capabilities. The agent can do only what this release allows. It does not change application code or infrastructure configuration.
A scoped agent role. The agent holds the Agent role. This role was built for the agent and is not borrowed from a person, so the agent never inherits a user's permissions. On Cloud Platform, an administrator chooses exactly which permissions the Agent role holds. See Give the agent access to applications and sites.
Human approval at two points. The agent does nothing until a person approves its plan. Publishing is a second, separate approval.
This release does not include a customer-visible record of agent activity. Every user with access can delegate the same tasks, because the Agent role applies to the whole project, not to the person asking. See What Acquia AI does not do.

Note

Acquia AI and Drupal AI

Acquia AI and Drupal AI operate at different structural layers:

Acquia AI: Works across installed Acquia products, including Acquia Source CMS, Acquia Cloud Platform, Acquia Web Governance, and Acquia DAM. This integration enables page checks, content creation, and platform health evaluation within a single conversation.
Drupal AI: Represents the open-source Drupal community ecosystem of contributed modules, recipes, and practices. Acquia contributes to this ecosystem.

Organizations can run both solutions simultaneously.

If an administrator has given you access:

Log in at source.acquia.com.
Open Acquia AI, or start a chat in Acquia Source.

To begin use of Acquia AI:

Confirm that your account is eligible and that an organization administrator has given you access to Acquia AI. For details, visit Accessing Acquia AI.
If you administer the organization, give the agent access to the applications and sites it should reach. For details, visit Assign the agent to an application and a site.
Ask a question first. Asking uses no AI credits, so it is the safest way to learn what the agent knows about your setup. For details, visit Ask a question in Advisor Mode.
Delegate a small task and approve the result. For details, visit Delegate a task and approve the work.

Did not find what you were looking for?

If this content did not answer your questions, try searching or contacting our support team for further assistance.