# Every Major Business Platform Now Has a Brain. They Are Not the Same Brain.

**A dated index of the AI layers inside twelve enterprise platforms — what each one is called, what it does, and what it used to be called.**

Last checked: 21 August 2026 · Method v1.1 · auxfirst
Canonical: https://auxfirst.com/news/ai-layers-name-index.html

| | |
|---|---|
| Platforms | 12 |
| Named products | 36 |
| Documented renames | 4 |
| New tiers reported as renames | 2 |

---

Every major business platform now ships an AI layer with its own product name. Notion has one. Salesforce has one. So do ClickUp, monday.com, Microsoft, Google, Adobe, ServiceNow, HubSpot, Atlassian, Slack and Klaviyo. If you run IT, platform engineering or operations, you are being asked to approve, license, secure and eventually audit several of them at once.

They are not twelve versions of the same thing. Some answer questions. Some do work while nobody is watching. Some are environments for building your own. At least one exists only to keep track of all the others. Sharing a category name — "AI" — obscures how differently they are built, how differently they are priced, and how differently they fail.

**This page is a reference, not an assessment.** It lists what each layer is called right now, what the vendor says it is for, and — where the name has changed — what it was called before. It does not rank anything. It exists so that when someone forwards you a roundup naming a product that no longer exists, you have somewhere to check.

## The naming pattern

Most vendors do not ship one AI product. They ship two, three or four, under separate names, frequently marketed under a single umbrella brand. Confusing them is the most common mistake in this category, and it is an expensive one — the four types have different pricing, different permission models, different rollout risk and different failure modes.

- **An assistant** — you ask, it answers, drafts or summarizes. On demand. Nothing happens unless you are there.
- **Agents** — they execute work, usually on triggers or schedules, often with nobody watching.
- **A builder** — a low-code or natural-language environment where non-developers create their own agents.
- **A control plane** — a management layer for the agents an organization has accumulated, including ones built somewhere else.

The distinction that matters most operationally is the first one: **an assistant cannot surprise you, and an agent can.** An assistant with a bad answer wastes five minutes. An agent with a bad instruction runs on a schedule at three in the morning and you find out on Monday.

A vendor's assistant and its agents are routinely sold under one umbrella brand — Breeze, Rovo, K:AI, Now Assist as it was. The brand implies one product with one security review. It is usually three products with three permission models, and in several cases the agents require a higher license tier than the assistant does.

## Why the names keep moving

This is a fast-renaming category. Checking twelve platforms against their own documentation in August 2026 turned up several products whose current name differs from the one still circulating in most published roundups — including roundups published this summer.

But renaming is only half of what is happening, and the smaller half. The more consequential pattern is this: **vendors are shipping new tiers above existing agent products, and the trade press is reporting them as rebrands.** Adobe and Klaviyo both did exactly this in 2026. In both cases the earlier product is still shipping, still supported, still what most customers are actually using — and in both cases the widely repeated summary is that it was renamed.

> A rename means one product with two names. A new tier means two products, one invoice, and a migration conversation you have not had yet.

Those are very different facts to carry into a renewal. If a product was renamed, your existing entitlement follows the name. If a new tier launched above it, your existing entitlement stays where it is and the new capability is a separate line.

### Every documented change in this index

| Type | Was | Now | Note |
|---|---|---|---|
| Renamed | Now Assist | ServiceNow Otto | Announced 5 May 2026, Knowledge 2026 |
| Renamed | Adobe Experience Cloud | Adobe CX Enterprise | Summit 2026, April |
| Renamed | Breeze Agents | Agent Hub | HubSpot |
| Renamed | Breeze studio | Agent Builder | HubSpot |
| **Not a rename** | Experience Platform Agents *(still shipping)* | + CX Enterprise Coworker | New tier above, GA 10 June 2026 |
| **Not a rename** | K:AI Marketing Agent *(still shipping)* | + Composer | New agent alongside, public beta 30 June 2026 |

The last two rows are the ones most commonly reported as renames in secondary coverage. In both cases the vendor's own announcement describes a new product and never claims the earlier one is being replaced.

Every entry below carries the date it was last checked, individually rather than as a single stamp across the page. Anything in this category older than a quarter should be treated as a lead, not a fact — including this page.

---

# Assistants

*You ask, it answers, drafts or summarizes. On demand. Nothing happens unless you are there.*
**10 products · 10 platforms**

## ClickUp Brain

**Lives in:** ClickUp
**What it is:** The conversational layer across ClickUp's tasks, docs, chat and connected apps. Brain MAX is the desktop companion; the AI Hub is where the agent estate is managed from.
**Typical uses:** Summarizing a task or chat thread, answering questions about work in ClickUp and connected apps, drafting content in place.
**Checked:** 20 August 2026

## Notion Agent

**Lives in:** Notion
**What it is:** Notion's on-demand assistant, in the corner of the workspace. Notion states the distinction from its Custom Agents plainly: Notion Agent is on-demand, Custom Agents are autonomous.
**Typical uses:** Drafting, editing and summarizing content, answering questions about pages and databases, one-off tasks while you work.
**Checked:** 21 August 2026 — re-verified against vendor documentation

## monday sidekick

**Lives in:** monday.com
**What it is:** monday's personal assistant, designed for conversational support and on-demand help. monday draws an explicit line between sidekick and its agents: sidekick assists, agents execute.
**Typical uses:** Asking about board and project status, drafting, help with configuring other parts of the platform.
**Checked:** 20 August 2026

## Rovo Chat and Rovo Search

**Lives in:** Jira, Confluence, Jira Service Management, Jira Product Discovery
**What it is:** Atlassian's conversational and search layer, grounded in Atlassian content and connected third-party sources.
**Typical uses:** Finding organizational knowledge across tools, asking questions in natural language, working alongside content in Jira and Confluence.
**Checked:** 20 August 2026

## Microsoft 365 Copilot

**Lives in:** Microsoft 365
**What it is:** The employee-facing assistant across Microsoft 365, grounded in organizational data. Distinct from Copilot Studio, which builds agents, and from Agent 365, which governs them — three products, one word.
**Typical uses:** Drafting and summarizing in Office applications, answering questions grounded in work content, meeting support.
**Checked:** 20 August 2026

## Gemini in Google Workspace

**Lives in:** Gmail, Drive, Docs, and the rest of Workspace
**What it is:** Google's assistant layer inside Workspace, distinct from Workspace Studio, which is the automation product.
**Typical uses:** Drafting, summarizing and answering questions using Workspace content.
**Checked:** 20 August 2026

## ServiceNow Otto

> **RENAMED** — Now Assist → ServiceNow Otto · announced 5 May 2026, Knowledge 2026

**Lives in:** the ServiceNow AI Platform
**What it is:** ServiceNow's assistant layer — summarization, drafting, search and recommendations — as distinct from its agents, which plan and execute. Otto is broader than a straight rename of Now Assist: it consolidates **three** previously separate brands — Now Assist, Moveworks and AI Experience — into one assistant surface. Otto also carries orchestration responsibilities, so the clean assistant-versus-agents split is a simplification in ServiceNow's case.
**Typical uses:** Summarizing records and cases, drafting responses, search across the platform.
**Checked:** 21 August 2026 — re-verified against vendor documentation

## Breeze Assistant

**Lives in:** HubSpot
**What it is:** The assistant inside HubSpot's Breeze umbrella brand. Note that Breeze remains the umbrella even though two products underneath it have been renamed away from it — see Agent Hub and Agent Builder below.
**Typical uses:** Working with CRM records conversationally, drafting, answering questions about account data.
**Checked:** 20 August 2026

## Adobe AI Assistant

**Lives in:** Adobe Experience Platform and **Adobe CX Enterprise** applications — the brand formerly called Experience Cloud
**What it is:** The conversational entry point to Adobe's agents. Under the hood, Agent Orchestrator selects which specialist agents answer a given request.
**Typical uses:** Asking questions about audiences and data, product knowledge questions, exploring platform behavior.
**Checked:** 21 August 2026 — re-verified against vendor documentation

## Slackbot

**Lives in:** Slack
**What it is:** Slack's own assistant, grounded in messages, files and channels. Slack is unusual in this index: as well as its own assistant, it functions as the conversational surface through which *other vendors'* agents are reached. If you are inventorying agents, the ones reachable in Slack are frequently not Slack's.
**Typical uses:** Answering questions from conversation history, summarizing channels and threads, working with connected apps.
**Checked:** 20 August 2026

**Two absences worth stating.** Salesforce and Klaviyo have no separately named general assistant in this index. Salesforce's conversational surfaces are folded into Agentforce and the wider Einstein brand rather than sold as a standalone assistant product; Klaviyo's AI is organized under the K:AI umbrella as agents rather than as an assistant. Absence here means no distinctly named product was found, not that the capability is missing.

---

# Agents

*They execute work, usually on triggers or schedules, often with nobody watching.*
**11 products · 11 platforms · 2 renames, 2 new tiers**

## Super Agents and Autopilot Agents

**Lives in:** ClickUp
**What they are:** Two distinct types. **Super Agents** are described as adaptive teammates that perform multi-step work with memory. **Autopilot Agents** act on defined triggers and conditions and are simpler by design. The distinction is worth keeping straight when scoping a rollout: one is bounded by rules, the other by instructions.
**Typical uses:** Drafting creative and feature briefs from task context, turning meeting notes into follow-up emails, maintaining escalation summaries, generating job descriptions.
**Checked:** 20 August 2026

## Custom Agents

**Lives in:** Notion
**What they are:** Agents that run in the background on schedules and workspace events, as distinct from Notion Agent, which is on demand. Triggers documented include page creation, page updates, property changes and comments, plus Slack triggers and recurring schedules.
**Typical uses:** Recurring reports, triage queues, knowledge-base maintenance, routing feedback from Slack into Notion databases.
**Availability:** Business or Enterprise plan
**Checked:** 21 August 2026 — re-verified against vendor documentation

## monday agents

**Lives in:** monday.com
**What they are:** Agents that monitor activity, apply judgment within defined guardrails, and execute work inside boards and workflows. In gradual release at the time of checking; agent creation requires admin permissions.
**Typical uses:** Capturing and triaging incoming requests, researching and summarizing, routing work to owners, drafting follow-ups, maintaining records.
**Checked:** 20 August 2026

## Rovo Agents

**Lives in:** Atlassian Cloud products
**What they are:** Configurable agents that can be invoked from chat, triggered by automation rules, or called from service playbooks. Parent agents can delegate to subagents. Atlassian ships prebuilt ones alongside custom builds.
**Worth knowing:** An agent used inside an automation rule is limited to a text response and cannot use its own tools. If your rollout plan assumes agents run unattended through automation, check that constraint before you scope it.
**Typical uses:** Service request handling, ticket triage, delivery work in Jira, working alongside content in Confluence.
**Checked:** 20 August 2026

## Autonomous agents in Copilot Studio

**Lives in:** Microsoft 365 and the Power Platform
**What they are:** Agents that act without waiting for a prompt. Microsoft's own description: they perceive events, make decisions and execute tasks independently using triggers, instructions and guardrails, operating continuously in the background — monitoring data, reacting to conditions and running workflows at scale — rather than responding only in conversations.
**Typical uses:** Processing updates, triaging events, initiating follow-up actions.
**Checked:** 20 August 2026

## Workspace Studio flows

**Lives in:** Google Workspace
**What they are:** No-code automations built in natural language that act across Gmail, Drive, Sheets and third-party apps, including via webhook.
**Worth knowing:** **The history changes what a claim about this product means.** At launch, Studio could assist with tasks such as drafting an email but could not execute them autonomously. Autonomous and cross-user execution arrived with the August 2026 release. Any capability claim about Workspace Studio dated before August 2026 describes a different product. Flows carry a unique flow identifier into the downstream audit record, and agent identities run least-privileged with unique auditable identifiers.
**Typical uses:** Drafting recurring updates, routing and filing incoming material, multi-step automations across Workspace and connected apps.
**Availability:** End-user rollout from 2 March 2026; enterprise controls rolling out by release track from August 2026
**Checked:** 21 August 2026 — re-verified against vendor documentation

## ServiceNow AI Agents

**Lives in:** the ServiceNow AI Platform
**What they are:** Agents that classify, enrich, act and resolve against enterprise workflows, coordinated in teams by **AI Agent Orchestrator**, and reaching third-party systems through **AI Agent Fabric**.
**Typical uses:** Incident routing and triage, request fulfillment, HR and service workflows.
**Checked:** 20 August 2026

## Agentforce

**Lives in:** Salesforce
**What it is:** Salesforce's agent layer, structured as **agent types** — such as the Agentforce Service Agent and the Sales Development Rep agent — each with its own topics, instructions and actions, wrapped in the Einstein Trust Layer.
**Worth knowing:** "Subagents", which appears in a good deal of third-party coverage, is not the documented primitive here. The architecture is agent type → topics → topic instructions → actions.
**Typical uses:** Handling service conversations with defined escalation points, working leads under admin-defined engagement rules, executing CRM actions.
**Checked:** 20 August 2026

## Agent Hub

> **RENAMED** — Breeze Agents → Agent Hub · HubSpot

**Lives in:** HubSpot
**What it is:** Where HubSpot's agents now live — agents that analyze data, generate outputs and take actions in the CRM, including writing to records. The name is new and the direction of the change is the opposite of what most coverage reports: **Breeze Agents became Agent Hub**, and separately the builder became Agent Builder. Breeze remains the umbrella brand over HubSpot's AI generally.
**Worth knowing:** The underlying product has churned heavily. HubSpot retired its earlier custom assistants on 13 July 2026 and a further set of agents on 23 July 2026. If you are reconciling an inventory against documentation written before August 2026, expect names in it that no longer resolve.
**Typical uses:** Preparing internal handoffs after a deal closes, researching companies, generating outreach, updating CRM records.
**Availability:** Professional and Enterprise tiers; public beta at the time of checking; consumes HubSpot credits
**Checked:** 21 August 2026 — re-verified against vendor documentation

## CX Enterprise Coworker

> **NOT A RENAME** — Experience Platform Agents *(still shipping)* + CX Enterprise Coworker · new tier above, GA 10 June 2026

**Lives in:** **Adobe CX Enterprise** — the brand renamed from Experience Cloud at Summit 2026
**What it is:** A new tier above Adobe's existing agents, not a replacement for them. Adobe describes it as taking a goal, then planning, executing, validating and returning the finished work for approval. **Coworker Campaigns** is a templated version aimed at small teams.
**Worth knowing:** This entry is the most commonly misreported item in this index. Adobe's Experience Platform Agents — the ten-plus specialist agents introduced at Summit 2025 — are still shipping and still in production. Coworker sits above them; it does not succeed them. Adobe's own launch announcement never describes Experience Platform Agents as being replaced. If a comparison you are reading says Coworker is the new name for those agents, it is describing an entitlement change that has not been documented.
**Typical uses:** Campaign creation and execution, audience assembly, multi-step marketing workflows.
**Availability:** Generally available 10 June 2026
**Checked:** 21 August 2026 — re-verified against vendor documentation

## Composer

> **NOT A RENAME** — K:AI Marketing Agent *(still shipping)* + Composer · new agent alongside, public beta 30 June 2026

**Lives in:** Klaviyo, under the K:AI umbrella
**What it is:** Klaviyo's flagship marketing agent, which identifies opportunities and builds complete cross-channel campaigns. Notably, it is designed *not* to publish: everything it creates is staged for review, and nothing goes live without a person approving it.
**Worth knowing:** Composer is a new product, launched March 2026, that sits *alongside* the earlier **K:AI Marketing Agent** rather than replacing it. K:AI is the umbrella over both. Coverage describing Composer as the Marketing Agent renamed has the relationship wrong.
**Related:** **Customer Agent**, Klaviyo's customer-facing service agent, is a separate product again.
**Typical uses:** Building campaigns and flows from a described goal, auditing existing flows for conflicts, generating sign-up forms.
**Availability:** Public beta from 30 June 2026
**Checked:** 21 August 2026 — re-verified against vendor documentation

**If you take one thing from this section.** Two of the eleven agent products here were announced in 2026 as additions and are widely described as replacements. That is not a trivia point. It determines whether the capability you are being sold is covered by an entitlement you already hold, or is a new line on the renewal — and in both cases the vendor's own announcement is the document that settles it, not the roundup that summarized it.

---

# Builders

*A low-code or natural-language environment where non-developers create their own agents. A builder does not run — it produces things that do.*
**9 products · 9 platforms · 1 rename**

## Super Agent Builder

**Lives in:** ClickUp
**What it is:** A natural-language conversation with ClickUp Brain that configures multi-step agents, with a catalog of prebuilt agents as a starting point.
**Checked:** 20 August 2026

## monday AI agent builder

**Lives in:** monday.com
**What it is:** monday's in-product builder, where agents are configured through chat and a settings panel covering instructions, knowledge, tools, permissions and triggers.
**Not the same as:** **Agent Factory**, a separate standalone monday product outside monday.com for independent agent creation. The two are frequently conflated, including in vendor comparison material.
**Checked:** 20 August 2026

## Rovo Studio

**Lives in:** Atlassian
**What it is:** Atlassian's environment for creating and editing agents, either through chat or manual configuration.
**Worth knowing:** Open to everyone in an organization *by default*; creation rights can be restricted. If you have Rovo and have not looked at that setting, every licensed user can currently build agents.
**Checked:** 20 August 2026

## Copilot Studio

**Lives in:** Microsoft
**What it is:** Microsoft's low-code environment for building both conversational and autonomous agents, connected to the Power Platform.
**Checked:** 20 August 2026

## Workspace Studio

**Lives in:** Google Workspace
**What it is:** Google's no-code environment for building agentic automations in natural language. Launched December 2025. It is both the builder and, through flows, the thing that runs — which is why it appears in two categories here.
**Checked:** 21 August 2026 — re-verified against vendor documentation

## AI Agent Studio

**Lives in:** the ServiceNow AI Platform
**What it is:** A natural-language environment for building and customizing agents, setting roles and guardrails, and testing behavior.
**Checked:** 20 August 2026

## Agent Builder

> **RENAMED** — Breeze studio → Agent Builder · HubSpot

**Lives in:** HubSpot
**What it is:** Where custom HubSpot agents are defined — instructions, actions, knowledge and inputs — including connections to external systems.
**Worth knowing:** HubSpot made two renames in this area, not one, and they are easily transposed: the *agents* became Agent Hub, and the *builder* became Agent Builder. Descriptions that place Agent Hub in the builder role have the pair the wrong way round.
**Availability:** Professional and Enterprise tiers; in beta at the time of checking; consumes HubSpot credits
**Checked:** 21 August 2026 — re-verified against vendor documentation

## Agent Composer

**Lives in:** Adobe Experience Platform
**What it is:** Adobe's environment for grounding agents in an organization's own definitions, taxonomies, brand guardrails and eligibility rules, with support for bringing your own agents.
**Not the same as:** Klaviyo's Composer, which is an agent, not a builder, and belongs to a different vendor entirely. The collision is unfortunate and is the reason both entries name their platform in full.
**Checked:** 20 August 2026

## Building agents on Slack

**Lives in:** Slack
**What it is:** Slack is unusual here — rather than a single named builder, it publishes a platform, a set of APIs, and unusually detailed design guidance for building agents that live in Slack conversations, alongside Slackbot as its own assistant.
**Worth knowing:** Slack's published guidance covers agent identity, approval gates, undo flows and progressive authority in more depth than most vendors' own products implement. It is addressed to third-party developers, which means it describes what agents in your Slack workspace *should* do rather than what they will do. Worth reading before you approve one.
**Checked:** 20 August 2026

---

# Control planes

*A management layer for the agents an organization has accumulated, including ones built somewhere else. This category barely existed a year ago.*
**3 products · 3 platforms**

## Microsoft Agent 365

**Lives in:** Microsoft 365
**What it is:** Microsoft's control plane for agents, organized around three stated functions: **observe, govern and secure**. It includes a registry that inventories agents from Microsoft *and non-Microsoft* sources. Agent identities are handled through Microsoft Entra Agent ID.
**Worth knowing:** The licensing has a prerequisite that is easy to miss in planning. Microsoft E5 is a **required** prerequisite for new purchases from 1 June 2026 — not a recommendation — and the specific requirement varies by segment: E5 for enterprise, F5-level Defender and Purview for frontline, Business Premium for SMB. Microsoft 365 E7 bundles E5, Agent 365, Copilot and the Entra Suite together.
**Availability:** Generally available for the Commercial segment since 1 May 2026, licensed per user
**Checked:** 21 August 2026 — re-verified against vendor documentation

## ServiceNow AI Control Tower

**Lives in:** the ServiceNow AI Platform
**What it is:** A governance layer above ServiceNow's own AI and third-party AI alike, covering discovery, observation, governance, security and cost measurement. The name is unchanged by the Otto consolidation.
**Worth knowing:** It connects to Microsoft's agent ecosystem, and vice versa. The control planes now govern each other, which is either reassuring or the beginning of a new problem depending on how many you end up running.
**Checked:** 21 August 2026 — re-verified against vendor documentation

## Adobe Agent Orchestrator

**Lives in:** Adobe Experience Platform
**What it is:** The layer that plans work and selects which specialist agents execute it. Less a management console than a runtime, but it plays the coordinating role in Adobe's architecture, which is why it sits here rather than under builders.
**Checked:** 20 August 2026

---

# Quick reference

Thirty-six named products across twelve platforms. The fourth column separates the two cases that get conflated: a documented rename, and a product that is still shipping underneath something new.

| Product | Platform | What it is | Previously called |
|---|---|---|---|
| ClickUp Brain | ClickUp | Assistant | — |
| Super Agents / Autopilot Agents | ClickUp | Agents | — |
| Super Agent Builder | ClickUp | Builder | — |
| Notion Agent | Notion | Assistant | — |
| Custom Agents | Notion | Agents | — |
| monday sidekick | monday.com | Assistant | — |
| monday agents | monday.com | Agents | — |
| monday AI agent builder | monday.com | Builder | — |
| Agent Factory | monday.com | Standalone builder | — |
| Rovo Chat / Rovo Search | Atlassian | Assistant | — |
| Rovo Agents | Atlassian | Agents | — |
| Rovo Studio | Atlassian | Builder | — |
| Microsoft 365 Copilot | Microsoft | Assistant | — |
| Autonomous agents | Microsoft | Agents | — |
| Copilot Studio | Microsoft | Builder | — |
| Agent 365 | Microsoft | Control plane | — |
| Gemini | Google Workspace | Assistant | — |
| Workspace Studio | Google Workspace | Builder and agents | — |
| ServiceNow Otto | ServiceNow | Assistant | Now Assist, Moveworks, AI Experience |
| ServiceNow AI Agents | ServiceNow | Agents | — |
| AI Agent Studio | ServiceNow | Builder | — |
| AI Control Tower | ServiceNow | Control plane | — |
| Agentforce | Salesforce | Agents | — |
| Breeze Assistant | HubSpot | Assistant | — |
| Agent Hub | HubSpot | Agents | Breeze Agents |
| Agent Builder | HubSpot | Builder | Breeze studio |
| Adobe AI Assistant | Adobe | Assistant | — |
| Adobe CX Enterprise | Adobe | Brand / suite | Adobe Experience Cloud |
| CX Enterprise Coworker | Adobe | Agents | **New tier — not a rename** |
| Experience Platform Agents | Adobe | Agents | *Still shipping* |
| Agent Composer | Adobe | Builder | — |
| Agent Orchestrator | Adobe | Coordinating layer | — |
| Composer | Klaviyo | Agents | **New agent — not a rename** |
| K:AI Marketing Agent | Klaviyo | Agents | *Still shipping* |
| Customer Agent | Klaviyo | Service agent | — |
| Slackbot | Slack | Assistant | — |

---

# Method

This page exists to establish what things are called. It makes no assessment of quality, maturity or fitness, and it does not rank the platforms it lists.

## What counts as a source

Names, descriptions and availability details come from vendor documentation, product pages, developer documentation, release notes and official product descriptions — published by the vendor, retrieved and dated in August 2026. Where a vendor's own framing of what a product is for was available, it has been used in preference to ours.

## What is not a source

Analyst reports, third-party reviews, listicles and vendor briefings were not used. Nothing here comes from hands-on product testing, and no vendor was contacted for this edition. Where a name or capability could only be found in secondary coverage, it was left off rather than included on weaker evidence.

## Renames, and the thing that is not a rename

A "previously called" entry means the vendor has publicly documented the change, either by naming a successor product or by stating the rename directly. Informal name drift, internal codenames and marketing variations are not recorded.

Where a vendor has launched a *new* product above or alongside an existing one, and the earlier product is still shipping, the entry is marked **not a rename** and both products are listed. This distinction was added in method v1.1 after re-verification found two cases where secondary coverage had reported an addition as a replacement. It is the only structural change from v1.0.

## Availability and pricing

Plan, tier and licensing details appear only where the vendor documents them publicly. Most entries have no availability line, and that means we could not verify one — not that the product is unrestricted. Treat an absent line as unknown.

## Dating

Every entry carries the date it was last checked, rather than the page carrying a single date. Entries re-verified on 21 August 2026 say so; entries carrying 20 August 2026 were compiled then and not re-opened. That mixed freshness is deliberate and will get more pronounced with each revision. An entry is never re-dated unless it was actually re-checked.

## Limits worth knowing

1. This is a documentation review. A product may do more, or less, than its documentation describes.
2. Several products listed are in beta or gradual release. Where that was documented, the entry says so; where it was not, availability may vary by account.
3. Re-verification on 21 August covered the dated claims, the renames and the availability lines — the things most likely to be wrong and most costly if they are. Descriptive claims on entries dated 20 August were not re-opened.
4. Product names in this category change faster than most published references are updated. This one will go stale too — the dates are there so you can tell when.
5. Twelve platforms is a selection, not a survey. Absence from this page is not a judgment.

## Corrections

If a product here has been renamed, retired or replaced, tell us and we will update the entry and log the change with a date. Corrections are shown alongside what they replaced rather than silently overwriting them. Cite the vendor page that supports a different reading and we will re-check against it.

Send a correction: https://auxfirst.com/index.html#contact

## Revision history

| Date | Change |
|---|---|
| 21 August 2026 | First publication. Method v1.1. Twelve platforms, thirty-six named products. Ten entries re-verified against vendor documentation; four documented renames and two new tiers recorded. |

This page is maintained. It keeps the same URL through every revision, so a link to it stays good. What changes is the dates on the entries and the rows in the revision history above — which is the only honest way to publish a reference in a category that moves this fast.

---

# Sources

**Work management**
- ClickUp — What are Super Agents? https://help.clickup.com/hc/en-us/articles/31010910371991-What-are-Super-Agents
- Notion — Custom Agents. https://www.notion.com/help/custom-agents
- monday.com — AI Agents on monday.com. https://support.monday.com/hc/en-us/articles/33347027353746-AI-Agents-on-monday-com
- Atlassian — Rovo data usage and privacy. https://www.atlassian.com/software/rovo/guides/admin-guide/rovo-data-usage-privacy

**Productivity suites**
- Microsoft Learn — Agent 365 overview. https://learn.microsoft.com/en-us/microsoft-agent-365/overview
- Microsoft Learn — Autonomous agents guidance, Copilot Studio. https://learn.microsoft.com/en-us/microsoft-copilot-studio/guidance/autonomous-agents
- Google Workspace Updates — Enterprise security controls for Workspace Studio. https://workspaceupdates.googleblog.com/2026/08/new-enterprise-security-controls-for-Workspace-Studio-enable-expanded-collaboration-use-cases.html
- Slack — Agent governance. https://docs.slack.dev/ai/agent-governance/

**Enterprise platforms**
- HubSpot — Create and customize agents in the agent builder. https://knowledge.hubspot.com/ai/create-and-customize-agents-in-the-agent-builder
- Salesforce — Agentforce guardrails and trust patterns. https://trailhead.salesforce.com/content/learn/modules/trusted-agentic-ai/explore-agentforce-guardrails-and-trust-patterns
- ServiceNow — Product documentation. https://www.servicenow.com/docs/
- Adobe — Newsroom. https://news.adobe.com/
- Klaviyo — Product and newsroom pages. https://www.klaviyo.com/

**Related on auxfirst**
- The Agent Supervision Register — the same twelve platforms, scored on capability and supervision. https://auxfirst.com/news/agent-supervision-register.html
- How we score agent supervision — the method. https://auxfirst.com/news/agent-supervision-method.html
- The agent development lifecycle. https://auxfirst.com/agent-development-lifecycle.html
- Can I prove what the agent did? https://auxfirst.com/news/can-i-prove-what-the-agent-did.html
- The agent buyer's map. https://auxfirst.com/news/agent-buyers-map.html
- The AUX Heuristics. https://auxfirst.com/heuristics.html

---

*Emil Krzemiński is the founder of auxfirst (https://auxfirst.com/), the agentic experience design agency — helping product, developer and business teams design AI systems that remember, adapt, and earn the right to act. For how machines read auxfirst, see https://auxfirst.com/ai-info.html.*