Ask five people what Sitecore Content Hub is and you’ll get different answers. A DAM. A CMS add-on. A PIM. A marketing platform. All of them are half right, which is exactly the problem.

So let’s start properly. What is it, actually.

The short version

Content Hub is Sitecore’s content operations platform. Not a content management system in the website-building sense. Not a single tool with one job. It’s the system that sits upstream of everything else, governing, structuring, and distributing the content and assets that feed your actual channels, wherever those channels live.

If SitecoreAI (the artist formerly known as XM Cloud) is where content gets delivered, Content Hub is where content gets made, approved, and made sense of before it ever gets there.

Two halves, not four modules

Content Hub gets pitched as four separate capabilities, but that’s not really how it’s built or sold. It splits into two natural groups, and understanding the split tells you more about the platform than memorising four acronyms ever will.

Below is one of the early diagrams I had. Inside the big circle is Group 1. Outside left circles are group 2.

Group 1: Content modelling – DAM + PCM

This half is about structuring and governing the raw material. Assets and product data, consistent, findable, and reusable everywhere downstream.

DAM (Digital Asset Management)
A searchable, taggable, permissioned home for every image, video, audio file, and layout you produce. Digital rights management is built in, so you control who can use what, and where. AI-assisted tagging helps once you’re past the point of labelling things by hand.

PCM (Product Content Management)
The system of record for product data. SKUs, specs, descriptions, pricing structure, category hierarchies. It sits close enough to DAM that a product record can reference its approved images without anyone re-uploading anything.

Together, DAM and PCM are what Sitecore actually sells as Content Hub DAM. If your problem is “our assets and product data are a mess and nothing talks to anything else,” this half solves it on its own.

Group 2: Content operations – CMP + MRM

This half is about planning and running the work that uses all that structured content.

CMP (Content Marketing Platform)
Editorial calendars, campaign lifecycles, content strategy, performance measurement. It covers the whole arc from idea to published output, not just a to-do list bolted onto DAM.

MRM (Marketing Resource Management)
Budgets, resourcing, and project tracking for content production. Less glamorous than the other three, but if you’ve ever tried to work out why a campaign is late or over budget with the answer spread across four spreadsheets, you’ll understand why it exists.

Add CMP and MRM to the first group and you get Content Hub Operations, the superset offering. Both packages can be extended for additional cost with Experience Edge (think it might be included now actually) and Content Publisher (formerly Chili Publish) for getting content out to downstream channels.

So when someone says “we’re on Content Hub,” the first useful question is which half they’ve actually got. DAM alone answers a different set of problems than DAM plus full operations.

What it isn’t

It’s not a CMS. It won’t build or serve your website (it could though).

It’s not trying to compete with SitecoreAI on page building, personalisation, or experience delivery, because that’s not its job.

It’s also not automatically a PIM replacement, even though PCM covers a lot of the same ground. If your product data needs are genuinely deep (complex variant structures, heavy ERP integration, multi-entity pricing) a dedicated PIM may still earn its keep. I’ve written about that trade-off in more detail if you want the longer version.

And it’s not “just DAM with some extra menus,” even though that’s how most implementations start. The DAM entry point is real, but it’s the front door, not the whole house.

Where it sits next to SitecoreAI

If you’re new to the Sitecore world, the names SitecoreAI and Content Hub can make it feel like two different vendors somehow ended up under the same roof. They didn’t. They’re both part of the Sitecore platform, each solving a different part of the content lifecycle.

Content Hub is where content gets created, enriched, approved, and governed before it ever reaches a website. It’s the operational layer that keeps assets, product information, metadata, workflows, and brand consistency under control.

SitecoreAI is where content gets delivered and experienced. It’s your headless CMS, page builder, personalisation engine, and increasingly the home of Sitecore’s agentic AI capabilities.

A simple way to think about it is this: SitecoreAI is where experiences happen. Content Hub is where those experiences are prepared. One delivers the finished product. The other makes sure the finished product is actually worth delivering.

Most enterprise conversations end up needing both eventually, and Sitecore’s licensing model reflects that. I go into the “which one first” question properly in a separate post, because it deserves more than a paragraph here.

Why any of this matters if you’re new to it

The reason Content Hub confuses newcomers isn’t that the individual modules are complicated. Each one, on its own, is fairly easy to grasp.

The confusion comes from the fact that it refuses to be just one thing, and most software categories (DAM, PIM, CMP) exist precisely because vendors used to sell those as separate products.

Content Hub’s bet is that keeping them separate is the actual problem. Whether that bet pays off for your organisation depends entirely on whether you have one of those problems or all of them.

I’ll be honest you probably have all of them.