Log entry Nº 305 · the stack watch

Bearing SW 225° · November 13, 2026 · 6 min read

AI in MarketingSW 225°Watch log

DXP Label Fades as CMS Vendors Reposition Around AI Agents

Thirteen of 28 tracked CMS vendors changed category since 2023 as DXP use fell from 12 to 6. Documentation shows which vendors give AI agents their own accounts — and which run them as proxies.

By Tom Whitfield6 min read1,125 words

The DXP Label Is Fading. Agent Documentation Shows Who Governs
Fix Nº 305The DXP Label Is Fading. Agent Documentation Shows Who Governs — 3844328 / pixabay

Thirteen of 28 content and experience vendors tracked since October 2023 have changed their category label, and DXP usage has fallen from 12 vendors to six. AI-led or "agentic" wording rose from one vendor to 10 over the same period. The numbers come from a homepage-positioning review of 28 vendors, run from October 2023 to October 2026, coding the category word in each page's title, description or headline.

Acquia relaunched on September 14 as "the Agentic Content Platform." Five weeks later, its page title still read "Digital Experience Platform for Content, Community, Commerce" — unchanged since 2023 and still in place as of November 13. Contentstack and Optimizely dropped the DXP label between June and September. All three cited governance when they did.

Which vendors changed category?

  • DXP use fell from 12 vendors to six.
  • AI-led or "agentic" wording rose from one vendor to 10.
  • CoreMedia, HCLSoftware, Kentico and Liferay kept "DXP" untouched for three years.
  • At least five vendors, including Kontent.ai and Optimizely, use "Agentic CMS" further down the page — none puts it in a title or headline.
  • Vendors now scatter across five labels, including DXP, CMS, AI-led wording and "agentic" platform names, and none dominates.

Sitecore CEO Eric Stine told CMSWire at the company's customer conference in Orlando that he is not focused on labels and will leave that question to analysts. He is focused on customers.

When vendors scatter across five labels, the label stops being a useful basis for comparison. The comparison has to move to something a vendor cannot change by editing a homepage.

What did vendors promise with the new names?

The three vendors that dropped the DXP label made governance the centerpiece. Contentstack's June 9 release said agents without both context and governance "are just expensive guesses." Optimizely's SVP of Product Kevin Li said in the Virtual Teammates release that even when AI does its part, "you don't always know who did what," and that every Virtual Teammate has "their own identity and permissions." Acquia founder Dries Buytaert made the same governance case on his blog.

The page captures add something the announcements don't. Contentstack's page title already read "Agentic Experience Platform" in April, two months before launch. Optimizely's homepage called itself an "AI-powered, all-in-one platform for marketing" in April 2025, well over a year before its Opticon conference at the end of August.

Do agents get their own accounts?

A documentation review of 10 CMS vendors — including Contentstack, Optimizely, Acquia, Sitecore and Adobe — graded what each says about running AI agents inside a content workflow, using public pages only, no trials, no logins. On one design choice, they split cleanly: three of 10 are "colleagues," six are proxies, and one could not be read.

Colleagues — agents with their own accounts:

  • Optimizely: each Virtual Teammate "has its own Opti ID account," acts as itself inside Optimizely products with "only the access you grant it," and "keeps its own usage separate from human usage."
  • Acquia: its agent holds a dedicated Agents Team role that "never inherits permissions from the requesting user," with a caveat on its own Source CMS, where the agent holds a fixed member role.
  • Kontent.ai: expert agents have their own permissions model.

Proxies — agents on the requester's permissions:

  • Contentstack: an on-demand run "acts as the person who ran it," unless the author fixed an account.
  • Sitecore: its MCP server works with access that "follows existing Sitecore permissions."
  • Adobe: Experience Manager and Coworker agents work with "permissions inherited from your Adobe organization."
  • Storyblok, Hygraph and Contentful do the same.

Branding does not predict the choice. Kontent.ai kept its CMS label and sits with the colleagues; Contentstack and Sitecore moved away from DXP and sit with the proxies.

The audit record matters as much as the account. Acquia's documentation states "No customer-visible record of agent activity is provided" for its Work mode in the current release. Contentstack keeps a separate execution log of agent steps, but its content audit log does not label agent writes as the agent. Sitecore and Adobe state that audit logging exists, and no page in the review says agent actions are labeled as agents.

Why identity matters for approval

Nine of the 10 vendors describe a person approving agent output before it goes live. In six of those nine, the agent works with the starter's permissions, so the person who asked for the work is often the one who approves it. That collapses the four-eyes principle — the control, known in finance, that the person who makes a change should not be the one who approves it.

The practical case: a content manager asks an agent to rewrite 50 product pages. If the agent runs on her permissions, the log shows her name on every page, and maker and checker become one person. Three weeks later, when a page carries a claim legal never cleared, the record cannot say who wrote or approved it.

Human approval only works as a control when the approver is someone other than the requester.

What should buyers ask?

Forrester analyst Joe Cicman told CMSWire in April that "Agents are a forcing function on the operating model." Six questions test that, each answerable from documentation rather than a demo:

  1. Does the agent have its own account and permissions, or does it run as the person who started it? A good answer is a named agent account with its own scope.
  2. When the agent changes content, does the audit log name the agent? Look for a log entry labeling the actor, plus a sample.
  3. Who approves the output, and can that be someone other than the requester? Look for a review step with its own permission.
  4. Which actions need approval, and who sets that? Look for per-action settings an administrator controls.
  5. What happens when an agent goes wrong mid-run? Look for a documented threshold, alert or stop.
  6. What can be undone, and where is the record? Look for version history that includes agent changes, and a revert.

Optimizely already answers questions 1, 2 and 5 in writing — the last on its specialized agents, which document deviation thresholds, the only documented stop in the set. Acquia answers 1 plus a separate approval step before publication; Kontent.ai answers 2 and 6. If most answers come back as "we'd have to check," ask the vendor to put them in writing before the contract is signed.

Whatever vendors call themselves next year, the checks stay the same: the agent's account, its approver and its line in the log. Documentation was read on October 22, 2026, and it moves — ask for the page again before you sign.

Plot points

  1. 13 of 28 tracked CMS vendors changed category between October 2023 and October 2026; DXP use fell from 12 to 6, agentic wording rose from 1 to 10.
  2. Acquia relaunched as 'the Agentic Content Platform' on September 14; Contentstack and Optimizely dropped DXP between June and September.
  3. Three of 10 vendors document AI agents with their own accounts (Optimizely, Acquia, Kontent.ai); six run agents on the requesting user's permissions.
  4. Optimizely is the only vendor in the set documenting a stop mechanism, with deviation thresholds on its specialized agents.
  5. Six documentation questions let buyers test agent governance claims without a sales call.

via feeds2.feedburner.com (Source)

Filed under

  • ai-agents
  • content-management-systems
  • digital-experience-platforms
  • ai-governance
  • martech-platforms
Share this article:

More from Tom Whitfield

Tom Whitfield

Show full bio

News editor covering money, funding and market shifts around marketing technology at Martech Beacon.

34 articles

Neighbouring fixes

‹ Previous articleNext article ›