Skip to content
alikhan.tech

Writing

Sitecore Stream vs SitecoreAI — What I Tell Teams Still on XM/XP

Muhammad Ali Khan · 29 Oct 2026 · 07 Mins read

Sitecore Stream vs SitecoreAI — What I Tell Teams Still on XM/XP

The question shows up in the first fifteen minutes of a discovery call, and it is almost never the question the slide was written to answer. A team still running XM or XP has seen the SitecoreAI launch, someone has forwarded the November 2025 press release, and they want to know whether Stream is now a dead product they should stop paying for, or whether SitecoreAI is a module they can install on the CM they already operate. Both readings are wrong, and they produce opposite kinds of waste. One team budgets a replatform they do not need this year. The other team waits for an agent workspace to appear on a launchpad that was never going to grow one.

I split the products by who they were built for, using the pages Sitecore has actually published, and then I talk about the work that remains on the XM/XP side. This is the version of that conversation I use in October 2026.

Two announcements that got collapsed into one product name

Sitecore introduced Stream at Symposium in October 2024. The 19 February 2025 seasonal release is the public description I still hand people, because it is specific. Stream embeds three capabilities across the DXP: brand-aware AI grounded in brand documents, copilots for brand, campaign, content, experience, and optimization work, and agentic workflows that range from a human in the loop to a fuller automated sequence. The same release said those capabilities were landing across the CMS, the digital asset management product, and the customer data platform. That is a portfolio story. It is not a statement that every Sitecore runtime became one SaaS tenant.

SitecoreAI is a later, narrower claim, and it is the one I refuse to stretch. The London press release on 4 November 2025 described SitecoreAI as a composable SaaS platform built on XM Cloud, hosted on Microsoft Azure, with Agentic Studio, a set of prebuilt agents, and a path for current XM Cloud customers that does not require a content migration. The developer FAQ puts the global launch on 10 November 2025 and says XM Cloud customers are upgraded automatically. I cite both dates. The 4th is the announcement. The 10th is the date the FAQ uses for the upgrade of existing XM Cloud organizations.

The sentence in that FAQ that ends the argument is short. Stream remains part of XP and XM only. SitecoreAI is the AI-native product, with agents and assistants in the experience. XM Cloud customers pick up the Stream Premium-style capabilities through SitecoreAI, subject to the terms Sitecore asks them to sign. If a stakeholder wants a single product name for both estates, I do not give them one.

What "still on XM/XP" actually has

An XM or XP estate that wants AI in the Experience Platform is installing a module and holding a subscription. Sitecore's XP documentation lists three prerequisites: a Sitecore Stream subscription, the Sitecore Stream for Platform DXP module installed, and XM/XP 10.2 or later. The module download page is more precise about the builds it was published against. It lists compatibility with XP 10.2, 10.3, and 10.4. I read both pages before I tell a team their version qualifies. "10.2 or later" on the feature page and a compatibility matrix that names specific minors are not the same sentence, and a 10.1 CM is out on either reading.

The module is downloaded from the Stream app in the Sitecore Cloud Portal and installed into the existing deployment with the package Sitecore ships for that purpose. It talks to Sitecore's Stream service. It does not turn the CM into SitecoreAI, and it does not bring Content SDK, Experience Edge for XM Cloud, or the page builder with it. Authors reach the AI surfaces Sitecore documents for this module from the Stream section of the Launchpad: Projects, the Assistant, and Brand kits. Brand kits are a Stream Premium capability. The free tier and the Premium tier are different shopping decisions, and I keep them as a line item instead of assuming the subscription they already have includes ingestion of a brand book.

What Premium buys, once the kit is published, is the structured brand knowledge Stream builds from uploaded documents. The sections Sitecore documents — brand context, global goals, tone of voice, dos and don'ts, checklists, grammar, visual guidelines, image style — are the same vocabulary I see on the SitecoreAI side later. The storage and the license are not the same object. A brand kit published for an XP authoring team is not automatically the brand kit an XM Cloud site was using in the Pages editor in March 2025, and it is not automatically the brand context an Agentic Studio flow reads. If both estates must sound like one company, somebody owns the document set and republishes it where each product looks for it.

I also tell the team what the module will not do. It will not migrate templates. It will not replace a head application. It will not give them the Agent API, the Marketer MCP server, or Spaces. Those are SitecoreAI surfaces. Asking an XP administrator to "turn on Agentic Studio" sends them looking for a button that the product line does not have.

What I tell the team that already moved to XM Cloud

They are the other half of the same confusion. In March 2025 I wrote about Stream inside the XM Cloud page editor: optimize-content actions, tone and length, brand adherence when a kit was linked, and A/B/n on the AI variant when the JSS version allowed it. That was an accurate description of the product I had in front of me. By the SitecoreAI launch, the FAQ's instruction to those customers is that they use the AI capabilities through SitecoreAI, and that Stream as a named product stays with XP and XM.

So I stop describing their roadmap as "more Stream." The tenant they already have is the SitecoreAI tenant. Items, sites, and the Experience Edge content the head reads stayed put, which is the continuity claim I covered earlier this week. The authoring AI they knew in Pages is exercised from Agentic Studio, from brand kits on that tenant, and from the page builder. A renewal conversation that still says "Stream Premium for the XM Cloud site" needs a commercial check with Sitecore, because the FAQ explicitly points that entitlement at SitecoreAI and at a terms signature. I do not improvise the contract. I do stop the architecture diagram from showing Stream as a fourth box next to a SitecoreAI organization that already absorbed the work.

Content SDK follows the same line. The October 2025 SDK lifecycle was about the SaaS product. JSS remains the JavaScript story on the XM/XP versions it supports. I do not plan a Content SDK upgrade for an XP CM, and I do not plan a Stream module install for a SitecoreAI organization that is already past the launch upgrade.

The decision I write down before anyone asks for a quote

I keep this as a short record in the engagement notes. It is a classification, not a tool.

type SitecoreEstate =
  | { kind: "xm-xp"; version: string; streamModuleInstalled: boolean; streamTier: "none" | "standard" | "premium" }
  | { kind: "sitecoreai"; organizationLive: boolean };

type AiRecommendation =
  | "install-stream-module"
  | "confirm-stream-premium"
  | "smoke-test-brand-kit"
  | "use-sitecoreai-tenant"
  | "out-of-range-version"
  | "commercial-check";

export function recommendAiPath(estate: SitecoreEstate): AiRecommendation {
  if (estate.kind === "sitecoreai") {
    return estate.organizationLive ? "use-sitecoreai-tenant" : "commercial-check";
  }

  const [major, minor] = estate.version.split(".").map((part) => Number(part));
  const versionKnown = major === 10 && minor >= 2 && minor <= 4;
  if (!versionKnown) {
    return "out-of-range-version";
  }
  if (!estate.streamModuleInstalled) {
    return "install-stream-module";
  }
  if (estate.streamTier !== "premium") {
    return "confirm-stream-premium";
  }
  return "smoke-test-brand-kit";
}

The last branch is deliberate. A module that is already installed still needs a working subscription, a published brand kit, and a smoke test from the Launchpad. "Installed" is not "authors can adhere to brand." out-of-range-version means I go back to the compatibility page for that exact build before anyone downloads a package. I do not treat the function as a license oracle. Stream tier names on an invoice do not always match the words I used in the type, which is why commercial-check exists as soon as money or a contract signature is the real question.

What the two paths change in delivery

On XM/XP, Stream helps an author write and check content that still goes through the workflow, publishing, and CD servers they already have. Cache invalidation, indexing, and the head or MVC app are unchanged by the presence of a brand kit. If the site is headless on XM/XP, JSS or the ASP.NET rendering stack they already run continues to read layout data from that estate. A generated headline is just a field value after the author accepts it.

On SitecoreAI, the same acceptance still has to become a publish before Experience Edge will serve it, and the head still has to know the rendering. I have repeated that enough this month because it is the failure both products share. An assistant that drafts inside a field the component already renders is useful on day one. An assistant that invents a template is a project. Stream on XP and agents on SitecoreAI are equally capable of the second mistake if nobody has written down the component contract.

Search is the other place the names mislead. SitecoreAI's launch language folds search into the platform story. Sitecore Search as a product, with its own domain, sources, and widgets, still has to be configured. Stream's question-and-answer feature on a Search domain, which I wrote about earlier this week, is a Search configuration. It is available to a SitecoreAI program because search is part of that platform story. It is not installed by the XP Stream module, and it does not start returning answers because a brand kit exists.

The sequence I actually run

  1. Name the estate. XM, XP, or an organization that was XM Cloud and is now SitecoreAI. Version numbers from the CM, or the organization name from the Cloud Portal. I do not accept "Sitecore" as an answer.
  2. For XM/XP, read the Stream module compatibility page for that version, confirm the subscription, and confirm whether brand kits are in the tier they bought.
  3. Install and configure the module only after those two are true. Then publish one brand kit from documents the brand team already stands behind, and run the Assistant against a page the component set already renders.
  4. For SitecoreAI, confirm the organization is on the upgraded tenant, confirm Agentic Studio is visible to the roles that need it, and keep Content SDK, Search, and any head work on their own lines. I covered that split on 25 October.
  5. If both estates must stay in the field, assign an owner for the brand documents and accept that each product has its own published kit. I do not promise a sync button I have not seen documented.

The teams that leave the call clear are the ones who can point at a launchpad or a SitecoreAI workspace and say which one they will open on Monday. The teams that leave with a single "AI migration" budget are the ones I will be writing a change request for in a quarter. Stream is the supported AI path on the XM and XP versions Sitecore still lists. SitecoreAI is the path for the SaaS tenant that grew out of XM Cloud. I keep those sentences intact.

Related notes