Sitecore has two products that come up in almost every enterprise conversation right now. SitecoreAI and Content Hub.

Both are impressive. Both are growing. And without a clear mental model for how they relate, it’s easy to think you are buying the wrong one or underestimate what the right combination could do.

This is my attempt to draw that line clearly.

SitecoreAI: the experience delivery platform

SitecoreAI is the evolution and rebrand of XM Cloud. It’s not just a name change – the platform has grown significantly, adding agentic studio, MCP connectivity, a marketplace, and content supply chain capabilities that weren’t part of the original XM Cloud story.

At its core it’s still a cloud-native headless CMS. But the ambition is considerably broader than that now.

What SitecoreAI is built for:

• Managing and delivering digital experiences across websites, apps, and channels
• Visual page building with a marketer-friendly authoring experience
• Personalisation and A/B testing through embedded CDP and Personalize
• AI agents via Agentic Studio – automating campaign briefs, content workflows, and repetitive marketing tasks
• MCP connectivity for integrating with external tools and services
• A marketplace of pre-built integrations and extensions
• Content supply chain management and campaign orchestration built in

If a customer is coming at this from a CMS lens

we need to manage and deliver our digital experience

SitecoreAI is the right conversation.

Content Hub: the content operations platform

Content Hub is a different product solving a different problem.

It’s not trying to deliver digital experiences. It’s trying to govern, structure, and manage the content and assets that feed into those experiences – wherever they’re delivered.

Its strength is in things that don’t exist in SitecoreAI:

• Advanced taxonomy and knowledge graph – content relationships modelled at a level that goes well beyond what a CMS content model handles
• DAM – proper digital asset management with rights management, version control, and a single source of truth for assets at scale
• PCM – product content management, structured product data modelled and governed for multichannel distribution
• CMP – campaign planning and editorial management for large marketing operations
• MRM – budget and resource management tied directly to content production

Content Hub doesn’t need CDP or personalisation. It doesn’t need a page builder. Its job is upstream of all of that, solving structural business problems around how content and product data are created, governed, and distributed.

If a customer is coming at this from a content operations or product data lens

we need to model, govern, and distribute complex content at scale

Content Hub is the right conversation.

The overlap is real – and it doesn’t change the decision

There is genuine overlap, particularly around campaign management. SitecoreAI has content supply chain and campaign capabilities. Content Hub has CMP and MRM. Both can claim to help you plan and manage campaigns.

Behind the scenes, Sitecore is moving toward shared services between the two platforms – same storage layer, same underlying infrastructure – so that overlap will likely increase over time. Imagine if the Content Hub graph lands in SitecoreAI.

But the overlap doesn’t change the primary decision. Get the primary lens right first. If the question is about experience delivery, SitecoreAI. If the question is about content operations complexity, Content Hub.

The shared licensing angle could change the conversation

The reason this matters is simple. You don’t have to choose one and ignore the other. Sitecore’s model means you effectively could get both products and solve all of your problems.

That changes the starting line completely. Rather than a single decision, you’ve actually got three.

Operations first

You come for Content Hub. DAM, PCM, taxonomy, content governance at scale. That’s your primary problem and it’s the right product for it. But included in that conversation is entry-level SitecoreAI: search, CDP, personalisation, agentic capabilities.

You didn’t budget for a delivery platform. You get the foundation of one anyway. If it clicks, scaling it up is a much easier conversation than starting from scratch.

Delivery first

You come for SitecoreAI. Headless CMS, agentic studio, experience delivery, personalisation. That’s your world. But entry-level Content Hub DAM comes with it.

For a lot of organisations, that’s enough to get meaningful asset management in place without a separate procurement process. If your asset complexity grows, the path to the full DAM is already open.

Everything first

You’ve got both problems and you know it. Product data complexity plus experience delivery complexity. This is where the full combination makes the most sense, and where the value of the shared infrastructure under the hood

same storage layer

converging services

really starts to compound.

The entry-level access in both directions isn’t a throwaway. It’s a real capability you can evaluate, build on, and scale. For anyone starting a platform search right now, that’s worth understanding before you narrow the conversation down to one product.

My take

These two platforms are not in competition and they’re not interchangeable.

The mistake I see most often is organisations trying to solve a content operations problem with a CMS, or buying Content Hub when what they actually needed was a better delivery platform.

Get the primary lens right first. The licensing model means you’ll get meaningful exposure to the other platform regardless – which makes the evaluation easier, and the case for expanding harder to ignore.