[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"blog-site-config":3,"$fVOU_Nd3tA1Bq53shXVUFdG70QKJoeQaDl_gsT3JExcs":6,"mdc--dcw5r1-key":87},{"gaMeasurementId":4,"bookingUrl":5},"G-7BYTDCVDDR","https:\u002F\u002Ftidycal.com\u002Fcmdcntr\u002F30-minute-meeting",{"post":7,"related":54},{"id":8,"slug":9,"title":10,"description":11,"summary":12,"content":13,"coverImageUrl":12,"coverImageAlt":12,"tags":14,"targetKeywords":20,"faq":21,"howTo":12,"demo":12,"featured":22,"tool":12,"status":23,"reviewNote":12,"metaTitle":24,"metaDescription":25,"canonicalUrl":26,"sourceTicketId":12,"agentGenerated":27,"publishedAt":28,"publishedBy":12,"createdAt":29,"updatedAt":28,"authorId":30,"clusterId":31,"ctaId":32,"author":33,"cluster":43,"cta":47,"tools":53},"560d1ca1-ccb4-4e65-9690-3b39e448e5a9","sitecore-dxp-composable-explained","Sitecore DXP: What Composable Actually Changed, and What It Costs","Sitecore's move from one monolithic DXP to a composable product suite changed what you buy, what you integrate, and who owns the seams. Here is the honest accounting.",null,"For about fifteen years, Sitecore's digital experience platform was one thing. You licensed Sitecore Experience Platform, you got content management, delivery, analytics, personalization, testing, email, and the data layer under them, and it all shipped as a single .NET application you installed and ran. The integration between those capabilities was Sitecore's problem, because they were all the same program.\n\nThat is no longer how Sitecore is sold. The composable DXP replaced one platform with a suite of separately licensed products that talk to each other over APIs. The capabilities did not disappear. The seams between them moved from inside Sitecore's codebase to inside your architecture, and that is the part the license comparison does not show you.\n\nWe work on both sides of this line: XP estates that have not moved, and composable builds that are live. Here is what actually changed.\n\n## What is Sitecore DXP?\n\nSitecore DXP is Sitecore's digital experience platform: the set of products that handle content management, delivery, customer data, personalization, search, and commerce for large organizations. Historically it was one installable product, Sitecore Experience Platform (XP). Today it is a composable suite of independently licensed software-as-a-service products that integrate over APIs.\n\nThe word doing the work in that definition is \"independently.\" That is the whole change, and every consequence below follows from it.\n\n## What does composable mean in Sitecore's case?\n\nComposable means you buy the capabilities you need and connect them, rather than licensing one platform that contains all of them whether you use them or not.\n\nIn XP, personalization was a feature of the rendering pipeline. A rule evaluated as the page composed, against visitor data that lived in the same system, written by the same vendor, versioned in the same release. You turned it on. In the composable stack, personalization is Sitecore Personalize, typically sitting on Sitecore CDP, integrated with your front end through their SDK and API. It is a better product than XP personalization by most measures. It is also a product, with its own onboarding, data model, contract, and integration project.\n\nMultiply that by every capability and you have the shape of the change.\n\n## The Sitecore composable product map\n\nSitecore renames and repackages these more often than any other enterprise vendor we work with, so treat this as the shape rather than the current price sheet. Verify naming against Sitecore's current documentation before you put it in a procurement document.\n\n| Capability | Composable product | What XP did instead |\n|---|---|---|\n| Content management and delivery | XM Cloud | Sitecore XP content management and delivery roles |\n| Digital asset management | Content Hub (DAM) | The Sitecore media library |\n| Content operations and planning | Content Hub (CMP) | Nothing native, usually a third-party tool |\n| Customer data | Sitecore CDP | xDB and xConnect |\n| Personalization and testing | Sitecore Personalize | XP personalization rules and Experience Optimization |\n| Site search | Sitecore Search | Solr or Azure Search, self-operated |\n| Email and marketing automation | Sitecore Send | Email Experience Manager |\n| Commerce | Sitecore OrderCloud | Sitecore Experience Commerce |\n| Integration and workflow | Sitecore Connect | Custom .NET pipelines |\n\nRead the right-hand column carefully. Almost everything in it was included, in the sense that it came with the platform and Sitecore made the pieces work together. Some of it was genuinely weak (Email Experience Manager was nobody's favorite), and the composable replacements are mostly better products. But \"included and mediocre\" and \"excellent and separately licensed and separately integrated\" are different budget lines, and the second one has an integration cost attached that the first did not.\n\n## What did XP do in one box that now takes several?\n\nThree things, and they are the three that surprise people mid-project.\n\n**Identity resolution across the session.** In XP, the same system that rendered the page held the contact record, so knowing that this visitor was the same person who downloaded a paper last month was a lookup. In the composable stack, that identity lives in Sitecore CDP, your front end has to identify the visitor to it, and the personalization decision comes back over an API call that has to complete inside your render budget. It works well. It is also a real engineering problem with latency and caching implications, and nobody owns it by default.\n\n**Content and assets in one editorial surface.** XP's media library was not a serious digital asset management system, but it was right there. Content Hub is a serious DAM, and it is a separate application with its own permissions, taxonomy, and publishing path. Authors who used to drag an image into a rich text field now work across two systems, and the connector between them has to be configured and maintained.\n\n**One upgrade.** This is the underrated one. Upgrading XP was painful, but it was one event with one release note. In a composable suite, each product versions on its own schedule, and the integrations between them are yours. There is no big upgrade any more. There is instead a permanent, low-grade integration maintenance obligation that never appears in a project plan because it is not a project.\n\nThat last point is the one we most often end up making to a steering committee. Composable does not remove upgrade cost. It converts a large periodic cost into a continuous one, which is easier to absorb and much easier to under-resource.\n\n## Do you need the whole composable stack?\n\nAlmost certainly not, and Sitecore does not really claim you do. The most common healthy configuration we see is narrower than the sales deck:\n\n- **XM Cloud alone**, with the front end handling everything else. Appropriate when you need enterprise content governance and multi-site management but personalization is aspirational. This is a large share of real deployments and there is nothing wrong with it.\n- **XM Cloud plus Search.** Site search is the capability most often underestimated in a headless move, because Solr came free with XP and self-operating a search index is genuinely unpleasant.\n- **XM Cloud plus Content Hub.** Correct when brand assets are a real governance problem, typically at organizations with regulated claims, licensed imagery, or many regional teams.\n- **The engagement products (CDP and Personalize)** only when there is an owner. Personalization without a named person accountable for the strategy produces expensive infrastructure serving one banner variant. We have seen this more than once.\n\nThe discipline that helps: for each product, name the person who owns the outcome it produces, before it is licensed. If you cannot name them, you are buying capability you will not operate. That test has saved our clients more money than any architectural recommendation we have made.\n\n## What composable costs that the license does not show\n\nFour line items, consistently missing from early budgets.\n\n**Integration engineering.** Every seam between two products is code you own: authentication, data mapping, error handling, retries, and the monitoring that tells you when the seam broke. Budget it as real engineering, because a failed personalization call that silently renders the default experience is exactly the kind of bug that runs for months undetected.\n\n**Front-end responsibility.** Composable assumes a capable front end. Rendering, caching, metadata, and search visibility all become yours. We covered the general shape of this in [headless CMS SEO](\u002Fblog\u002Fenterprise-cms\u002Fheadless-cms-seo-complete-guide), and it is the most common source of post-launch traffic loss we get called about.\n\n**Author change management.** Two or three applications instead of one, with different permission models. Authors absorb this badly when it arrives as a surprise and well when it arrives as training. The cost is the same either way; only the goodwill differs.\n\n**Observability across products.** When a page renders wrong, the cause could be in XM Cloud, Edge, the CDP call, the Personalize decision, or your front end. In XP, it was in XP. Cross-product tracing is not optional at this architecture, and it is not included.\n\nNone of this makes composable the wrong choice. It makes it a different choice than the license comparison implies, and the teams that go in knowing this do fine.\n\n## In what order should you adopt composable products?\n\nSequencing matters, and the order that works is not the order the products are usually presented in.\n\n**Content first, always.** XM Cloud (or whatever holds your content) before anything else. Everything downstream depends on the content model, and adopting engagement products on top of a model you are about to change means integrating twice.\n\n**Search next, if you need it.** It is the capability most commonly underestimated in a headless move, and it is largely independent of the engagement products, so it can proceed in parallel without creating coupling.\n\n**Assets when governance demands it, not before.** Content Hub is a platform in its own right. Adopt it when asset governance is a named problem with an owner, not as part of a bundle.\n\n**Customer data before personalization.** Sitecore Personalize on top of a customer data platform with no meaningful data in it produces rules firing on nothing. Get the data flowing, verify it is correct, then personalise on it. Teams that do this in the other order build sophisticated infrastructure that decides between two identical experiences.\n\n**Commerce on its own timeline.** It has its own stakeholders and its own risk profile, and coupling it to a content migration means one slip delays both.\n\nThe general rule: adopt in dependency order, and let each product be genuinely in production before starting the next. Parallel adoption of three composable products is how organizations end up with three half-integrated systems and no working seam between any of them, which is materially worse than having adopted none of them.\n\n## How should you decide?\n\nWork backwards from operations rather than forwards from capability.\n\n**Start with what you will actually run in two years.** Not what you would like to run. Personalization programs that nobody staffed are the most expensive shelfware in this category, because they carry both license and integration cost.\n\n**Then check who owns the seams.** Composable pushes integration ownership to you or your partner permanently. If your model is a systems integrator who builds and leaves, composable will degrade quietly after they go, because there is no longer a vendor whose job it is to make the pieces agree.\n\n**Then look at the content model.** Whether you go composable or stay on XP, the content model is the asset that outlives the decision. If it is a mess, moving it to a nicer platform makes it a mess on a nicer platform. The [Sitecore XP technical debt audit](\u002Fblog\u002Fenterprise-cms\u002Fsitecore-xp-technical-debt-audit) is the version of this we run for clients before any platform decision, because platform choice made on top of an unmeasured content model is a guess.\n\n**Finally, price the do-nothing option honestly.** Staying on XP is a real option with real risk, and it deserves a number rather than a shrug. Running XP well for another three years is often cheaper than moving badly, and much cheaper than moving to a composable stack you do not staff.\n\nComposable is not hype and it is not a trap. It is an unbundling, and unbundling moves work rather than removing it. Sitecore made the products better and handed you the seams. Whether that trade works depends almost entirely on whether anyone owns them.\n\nIf you are pricing a composable move, staring at a stack you already bought and have not integrated, or trying to decide what to license before committing, that is our work. We put senior specialists on the architecture and the integration seams, and our support hours never expire, so you can scale help to the phase you are actually in rather than to a retainer calendar. [Book a call](https:\u002F\u002Ftidycal.com\u002Fcmdcntr\u002F30-minute-meeting), or read about our [Sitecore development and support](\u002Fservices\u002Fsitecore) practice.\n\n## Read next\n\n- [Enterprise CMS in 2026: How to Choose the Platform and the Partner](\u002Fblog\u002Fenterprise-cms\u002Fenterprise-cms-2026-platform-and-partner): the cluster pillar and the wider platform decision.\n- [Is Sitecore a Headless CMS?](\u002Fblog\u002Fenterprise-cms\u002Fis-sitecore-a-headless-cms): what headless means inside Sitecore, and how XM Cloud and XP differ.\n- [The Sitecore XP Technical Debt Audit](\u002Fblog\u002Fenterprise-cms\u002Fsitecore-xp-technical-debt-audit): the six domains that decide what any move off XP costs.\n- [Enterprise Headless CMS, Explained](\u002Fblog\u002Fenterprise-cms\u002Fenterprise-headless-cms-explained): what the enterprise tier is actually buying.\n- Work with us: [Sitecore development and support](\u002Fservices\u002Fsitecore), or our [headless CMS agency](\u002Fservices\u002Fheadless-cms) practice.",[15,16,17,18,19],"sitecore","sitecore dxp","composable dxp","xm cloud","enterprise cms",[],[],false,"published","Sitecore DXP: What Composable Changed and What It Costs","Sitecore's composable DXP replaced one platform with a product suite. What each piece does, what XP did for free, and the integration cost nobody quotes.","https:\u002F\u002Fcmdcntr.io\u002Fblog\u002Fenterprise-cms\u002Fsitecore-dxp-composable-explained",true,"2026-08-18T11:16:57.775Z","2026-08-18T04:05:16.996Z","ed80da88-f3d1-4aa9-9373-18c39fecb740","23d49753-baf2-4629-b6fc-df27c558f48d","c0fcf6a1-58d2-4262-8996-3ad29d58eea5",{"slug":34,"name":35,"avatarUrl":36,"role":37,"bio":38,"isPublic":27,"expertiseSummary":39,"linkedin":40,"github":41,"twitter":12,"website":42},"michael-graham","Michael Graham","\u002Fapi\u002Fpublic\u002Favatar\u002F7452d3cc-b0aa-46e4-96e6-da9c0225c471","Founder & Software Engineer","Obsessed with building top-tier web software and crafting unique, polished user experiences.","From frontend design to a fully deployed application, I can build the entire pipeline.","https:\u002F\u002Fwww.linkedin.com\u002Fin\u002Fmikemartire\u002F","https:\u002F\u002Fgithub.com\u002Fmichaelchristophergraham","https:\u002F\u002Fcmdcntr.io",{"slug":44,"name":45,"color":46},"enterprise-cms","Enterprise CMS Delivery","#0EA5E9",{"id":32,"name":48,"ctaType":49,"heading":50,"description":51,"buttonText":52,"url":5,"leadMagnetUrl":12},"Book a Call (blog)","book_call","Shipping AI-generated code that keeps breaking?","Book a free 30-minute call with a senior engineer. We diagnose what is going wrong and give you a concrete fix plan, no obligation.","Book a free call",[],[55,66,76],{"id":56,"slug":57,"title":58,"description":59,"coverImageUrl":12,"coverImageAlt":12,"tags":60,"featured":22,"tool":12,"publishedAt":28,"author":64,"cluster":65},"56859dc5-edd2-4bc8-8057-88ac90687556","sitecore-managed-cloud","Sitecore Managed Cloud: What It Is and When It Is the Right Call","Sitecore Managed Cloud takes the infrastructure off your plate and leaves the application firmly on it. The responsibility split is the whole decision.",[15,61,62,63,19],"managed cloud","sitecore hosting","azure",{"slug":34,"name":35,"avatarUrl":36,"role":37,"bio":38,"isPublic":27},{"slug":44,"name":45,"color":46},{"id":67,"slug":68,"title":69,"description":70,"coverImageUrl":12,"coverImageAlt":12,"tags":71,"featured":22,"tool":12,"publishedAt":28,"author":74,"cluster":75},"d31e5a8a-2739-4f2e-89fc-295bc0a53628","is-sitecore-a-headless-cms","Is Sitecore a Headless CMS? XM Cloud, XP, and What Actually Goes Headless","Sitecore can run headless, but XM Cloud and XP get there by different routes with different costs. Here is what headless actually means inside Sitecore, and where teams get hurt.",[15,72,18,73,19],"headless cms","experience edge",{"slug":34,"name":35,"avatarUrl":36,"role":37,"bio":38,"isPublic":27},{"slug":44,"name":45,"color":46},{"id":77,"slug":78,"title":79,"description":80,"coverImageUrl":12,"coverImageAlt":12,"tags":81,"featured":22,"tool":12,"publishedAt":28,"author":85,"cluster":86},"b32ba2ef-3e87-4300-a42e-a8c6787ef9ed","sitecore-digital-asset-management","Sitecore Digital Asset Management: Media Library, Content Hub, or Third Party?","The Sitecore media library is asset storage, not asset management. Knowing which one you need is a governance question, not a feature comparison.",[15,82,83,84,19],"digital asset management","content hub","dam",{"slug":34,"name":35,"avatarUrl":36,"role":37,"bio":38,"isPublic":27},{"slug":44,"name":45,"color":46},{"data":88,"body":89},{},{"type":90,"children":91},"root",[92,100,105,110,117,122,127,133,138,143,148,154,159,354,359,365,370,381,391,401,406,412,417,462,467,473,478,488,507,517,527,532,538,543,553,563,573,583,593,598,604,609,619,629,647,657,662,684,690],{"type":93,"tag":94,"props":95,"children":96},"element","p",{},[97],{"type":98,"value":99},"text","For about fifteen years, Sitecore's digital experience platform was one thing. You licensed Sitecore Experience Platform, you got content management, delivery, analytics, personalization, testing, email, and the data layer under them, and it all shipped as a single .NET application you installed and ran. The integration between those capabilities was Sitecore's problem, because they were all the same program.",{"type":93,"tag":94,"props":101,"children":102},{},[103],{"type":98,"value":104},"That is no longer how Sitecore is sold. The composable DXP replaced one platform with a suite of separately licensed products that talk to each other over APIs. The capabilities did not disappear. The seams between them moved from inside Sitecore's codebase to inside your architecture, and that is the part the license comparison does not show you.",{"type":93,"tag":94,"props":106,"children":107},{},[108],{"type":98,"value":109},"We work on both sides of this line: XP estates that have not moved, and composable builds that are live. Here is what actually changed.",{"type":93,"tag":111,"props":112,"children":114},"h2",{"id":113},"what-is-sitecore-dxp",[115],{"type":98,"value":116},"What is Sitecore DXP?",{"type":93,"tag":94,"props":118,"children":119},{},[120],{"type":98,"value":121},"Sitecore DXP is Sitecore's digital experience platform: the set of products that handle content management, delivery, customer data, personalization, search, and commerce for large organizations. Historically it was one installable product, Sitecore Experience Platform (XP). Today it is a composable suite of independently licensed software-as-a-service products that integrate over APIs.",{"type":93,"tag":94,"props":123,"children":124},{},[125],{"type":98,"value":126},"The word doing the work in that definition is \"independently.\" That is the whole change, and every consequence below follows from it.",{"type":93,"tag":111,"props":128,"children":130},{"id":129},"what-does-composable-mean-in-sitecores-case",[131],{"type":98,"value":132},"What does composable mean in Sitecore's case?",{"type":93,"tag":94,"props":134,"children":135},{},[136],{"type":98,"value":137},"Composable means you buy the capabilities you need and connect them, rather than licensing one platform that contains all of them whether you use them or not.",{"type":93,"tag":94,"props":139,"children":140},{},[141],{"type":98,"value":142},"In XP, personalization was a feature of the rendering pipeline. A rule evaluated as the page composed, against visitor data that lived in the same system, written by the same vendor, versioned in the same release. You turned it on. In the composable stack, personalization is Sitecore Personalize, typically sitting on Sitecore CDP, integrated with your front end through their SDK and API. It is a better product than XP personalization by most measures. It is also a product, with its own onboarding, data model, contract, and integration project.",{"type":93,"tag":94,"props":144,"children":145},{},[146],{"type":98,"value":147},"Multiply that by every capability and you have the shape of the change.",{"type":93,"tag":111,"props":149,"children":151},{"id":150},"the-sitecore-composable-product-map",[152],{"type":98,"value":153},"The Sitecore composable product map",{"type":93,"tag":94,"props":155,"children":156},{},[157],{"type":98,"value":158},"Sitecore renames and repackages these more often than any other enterprise vendor we work with, so treat this as the shape rather than the current price sheet. Verify naming against Sitecore's current documentation before you put it in a procurement document.",{"type":93,"tag":160,"props":161,"children":162},"table",{},[163,187],{"type":93,"tag":164,"props":165,"children":166},"thead",{},[167],{"type":93,"tag":168,"props":169,"children":170},"tr",{},[171,177,182],{"type":93,"tag":172,"props":173,"children":174},"th",{},[175],{"type":98,"value":176},"Capability",{"type":93,"tag":172,"props":178,"children":179},{},[180],{"type":98,"value":181},"Composable product",{"type":93,"tag":172,"props":183,"children":184},{},[185],{"type":98,"value":186},"What XP did instead",{"type":93,"tag":188,"props":189,"children":190},"tbody",{},[191,210,228,246,264,282,300,318,336],{"type":93,"tag":168,"props":192,"children":193},{},[194,200,205],{"type":93,"tag":195,"props":196,"children":197},"td",{},[198],{"type":98,"value":199},"Content management and delivery",{"type":93,"tag":195,"props":201,"children":202},{},[203],{"type":98,"value":204},"XM Cloud",{"type":93,"tag":195,"props":206,"children":207},{},[208],{"type":98,"value":209},"Sitecore XP content management and delivery roles",{"type":93,"tag":168,"props":211,"children":212},{},[213,218,223],{"type":93,"tag":195,"props":214,"children":215},{},[216],{"type":98,"value":217},"Digital asset management",{"type":93,"tag":195,"props":219,"children":220},{},[221],{"type":98,"value":222},"Content Hub (DAM)",{"type":93,"tag":195,"props":224,"children":225},{},[226],{"type":98,"value":227},"The Sitecore media library",{"type":93,"tag":168,"props":229,"children":230},{},[231,236,241],{"type":93,"tag":195,"props":232,"children":233},{},[234],{"type":98,"value":235},"Content operations and planning",{"type":93,"tag":195,"props":237,"children":238},{},[239],{"type":98,"value":240},"Content Hub (CMP)",{"type":93,"tag":195,"props":242,"children":243},{},[244],{"type":98,"value":245},"Nothing native, usually a third-party tool",{"type":93,"tag":168,"props":247,"children":248},{},[249,254,259],{"type":93,"tag":195,"props":250,"children":251},{},[252],{"type":98,"value":253},"Customer data",{"type":93,"tag":195,"props":255,"children":256},{},[257],{"type":98,"value":258},"Sitecore CDP",{"type":93,"tag":195,"props":260,"children":261},{},[262],{"type":98,"value":263},"xDB and xConnect",{"type":93,"tag":168,"props":265,"children":266},{},[267,272,277],{"type":93,"tag":195,"props":268,"children":269},{},[270],{"type":98,"value":271},"Personalization and testing",{"type":93,"tag":195,"props":273,"children":274},{},[275],{"type":98,"value":276},"Sitecore Personalize",{"type":93,"tag":195,"props":278,"children":279},{},[280],{"type":98,"value":281},"XP personalization rules and Experience Optimization",{"type":93,"tag":168,"props":283,"children":284},{},[285,290,295],{"type":93,"tag":195,"props":286,"children":287},{},[288],{"type":98,"value":289},"Site search",{"type":93,"tag":195,"props":291,"children":292},{},[293],{"type":98,"value":294},"Sitecore Search",{"type":93,"tag":195,"props":296,"children":297},{},[298],{"type":98,"value":299},"Solr or Azure Search, self-operated",{"type":93,"tag":168,"props":301,"children":302},{},[303,308,313],{"type":93,"tag":195,"props":304,"children":305},{},[306],{"type":98,"value":307},"Email and marketing automation",{"type":93,"tag":195,"props":309,"children":310},{},[311],{"type":98,"value":312},"Sitecore Send",{"type":93,"tag":195,"props":314,"children":315},{},[316],{"type":98,"value":317},"Email Experience Manager",{"type":93,"tag":168,"props":319,"children":320},{},[321,326,331],{"type":93,"tag":195,"props":322,"children":323},{},[324],{"type":98,"value":325},"Commerce",{"type":93,"tag":195,"props":327,"children":328},{},[329],{"type":98,"value":330},"Sitecore OrderCloud",{"type":93,"tag":195,"props":332,"children":333},{},[334],{"type":98,"value":335},"Sitecore Experience Commerce",{"type":93,"tag":168,"props":337,"children":338},{},[339,344,349],{"type":93,"tag":195,"props":340,"children":341},{},[342],{"type":98,"value":343},"Integration and workflow",{"type":93,"tag":195,"props":345,"children":346},{},[347],{"type":98,"value":348},"Sitecore Connect",{"type":93,"tag":195,"props":350,"children":351},{},[352],{"type":98,"value":353},"Custom .NET pipelines",{"type":93,"tag":94,"props":355,"children":356},{},[357],{"type":98,"value":358},"Read the right-hand column carefully. Almost everything in it was included, in the sense that it came with the platform and Sitecore made the pieces work together. Some of it was genuinely weak (Email Experience Manager was nobody's favorite), and the composable replacements are mostly better products. But \"included and mediocre\" and \"excellent and separately licensed and separately integrated\" are different budget lines, and the second one has an integration cost attached that the first did not.",{"type":93,"tag":111,"props":360,"children":362},{"id":361},"what-did-xp-do-in-one-box-that-now-takes-several",[363],{"type":98,"value":364},"What did XP do in one box that now takes several?",{"type":93,"tag":94,"props":366,"children":367},{},[368],{"type":98,"value":369},"Three things, and they are the three that surprise people mid-project.",{"type":93,"tag":94,"props":371,"children":372},{},[373,379],{"type":93,"tag":374,"props":375,"children":376},"strong",{},[377],{"type":98,"value":378},"Identity resolution across the session.",{"type":98,"value":380}," In XP, the same system that rendered the page held the contact record, so knowing that this visitor was the same person who downloaded a paper last month was a lookup. In the composable stack, that identity lives in Sitecore CDP, your front end has to identify the visitor to it, and the personalization decision comes back over an API call that has to complete inside your render budget. It works well. It is also a real engineering problem with latency and caching implications, and nobody owns it by default.",{"type":93,"tag":94,"props":382,"children":383},{},[384,389],{"type":93,"tag":374,"props":385,"children":386},{},[387],{"type":98,"value":388},"Content and assets in one editorial surface.",{"type":98,"value":390}," XP's media library was not a serious digital asset management system, but it was right there. Content Hub is a serious DAM, and it is a separate application with its own permissions, taxonomy, and publishing path. Authors who used to drag an image into a rich text field now work across two systems, and the connector between them has to be configured and maintained.",{"type":93,"tag":94,"props":392,"children":393},{},[394,399],{"type":93,"tag":374,"props":395,"children":396},{},[397],{"type":98,"value":398},"One upgrade.",{"type":98,"value":400}," This is the underrated one. Upgrading XP was painful, but it was one event with one release note. In a composable suite, each product versions on its own schedule, and the integrations between them are yours. There is no big upgrade any more. There is instead a permanent, low-grade integration maintenance obligation that never appears in a project plan because it is not a project.",{"type":93,"tag":94,"props":402,"children":403},{},[404],{"type":98,"value":405},"That last point is the one we most often end up making to a steering committee. Composable does not remove upgrade cost. It converts a large periodic cost into a continuous one, which is easier to absorb and much easier to under-resource.",{"type":93,"tag":111,"props":407,"children":409},{"id":408},"do-you-need-the-whole-composable-stack",[410],{"type":98,"value":411},"Do you need the whole composable stack?",{"type":93,"tag":94,"props":413,"children":414},{},[415],{"type":98,"value":416},"Almost certainly not, and Sitecore does not really claim you do. The most common healthy configuration we see is narrower than the sales deck:",{"type":93,"tag":418,"props":419,"children":420},"ul",{},[421,432,442,452],{"type":93,"tag":422,"props":423,"children":424},"li",{},[425,430],{"type":93,"tag":374,"props":426,"children":427},{},[428],{"type":98,"value":429},"XM Cloud alone",{"type":98,"value":431},", with the front end handling everything else. Appropriate when you need enterprise content governance and multi-site management but personalization is aspirational. This is a large share of real deployments and there is nothing wrong with it.",{"type":93,"tag":422,"props":433,"children":434},{},[435,440],{"type":93,"tag":374,"props":436,"children":437},{},[438],{"type":98,"value":439},"XM Cloud plus Search.",{"type":98,"value":441}," Site search is the capability most often underestimated in a headless move, because Solr came free with XP and self-operating a search index is genuinely unpleasant.",{"type":93,"tag":422,"props":443,"children":444},{},[445,450],{"type":93,"tag":374,"props":446,"children":447},{},[448],{"type":98,"value":449},"XM Cloud plus Content Hub.",{"type":98,"value":451}," Correct when brand assets are a real governance problem, typically at organizations with regulated claims, licensed imagery, or many regional teams.",{"type":93,"tag":422,"props":453,"children":454},{},[455,460],{"type":93,"tag":374,"props":456,"children":457},{},[458],{"type":98,"value":459},"The engagement products (CDP and Personalize)",{"type":98,"value":461}," only when there is an owner. Personalization without a named person accountable for the strategy produces expensive infrastructure serving one banner variant. We have seen this more than once.",{"type":93,"tag":94,"props":463,"children":464},{},[465],{"type":98,"value":466},"The discipline that helps: for each product, name the person who owns the outcome it produces, before it is licensed. If you cannot name them, you are buying capability you will not operate. That test has saved our clients more money than any architectural recommendation we have made.",{"type":93,"tag":111,"props":468,"children":470},{"id":469},"what-composable-costs-that-the-license-does-not-show",[471],{"type":98,"value":472},"What composable costs that the license does not show",{"type":93,"tag":94,"props":474,"children":475},{},[476],{"type":98,"value":477},"Four line items, consistently missing from early budgets.",{"type":93,"tag":94,"props":479,"children":480},{},[481,486],{"type":93,"tag":374,"props":482,"children":483},{},[484],{"type":98,"value":485},"Integration engineering.",{"type":98,"value":487}," Every seam between two products is code you own: authentication, data mapping, error handling, retries, and the monitoring that tells you when the seam broke. Budget it as real engineering, because a failed personalization call that silently renders the default experience is exactly the kind of bug that runs for months undetected.",{"type":93,"tag":94,"props":489,"children":490},{},[491,496,498,505],{"type":93,"tag":374,"props":492,"children":493},{},[494],{"type":98,"value":495},"Front-end responsibility.",{"type":98,"value":497}," Composable assumes a capable front end. Rendering, caching, metadata, and search visibility all become yours. We covered the general shape of this in ",{"type":93,"tag":499,"props":500,"children":502},"a",{"href":501},"\u002Fblog\u002Fenterprise-cms\u002Fheadless-cms-seo-complete-guide",[503],{"type":98,"value":504},"headless CMS SEO",{"type":98,"value":506},", and it is the most common source of post-launch traffic loss we get called about.",{"type":93,"tag":94,"props":508,"children":509},{},[510,515],{"type":93,"tag":374,"props":511,"children":512},{},[513],{"type":98,"value":514},"Author change management.",{"type":98,"value":516}," Two or three applications instead of one, with different permission models. Authors absorb this badly when it arrives as a surprise and well when it arrives as training. The cost is the same either way; only the goodwill differs.",{"type":93,"tag":94,"props":518,"children":519},{},[520,525],{"type":93,"tag":374,"props":521,"children":522},{},[523],{"type":98,"value":524},"Observability across products.",{"type":98,"value":526}," When a page renders wrong, the cause could be in XM Cloud, Edge, the CDP call, the Personalize decision, or your front end. In XP, it was in XP. Cross-product tracing is not optional at this architecture, and it is not included.",{"type":93,"tag":94,"props":528,"children":529},{},[530],{"type":98,"value":531},"None of this makes composable the wrong choice. It makes it a different choice than the license comparison implies, and the teams that go in knowing this do fine.",{"type":93,"tag":111,"props":533,"children":535},{"id":534},"in-what-order-should-you-adopt-composable-products",[536],{"type":98,"value":537},"In what order should you adopt composable products?",{"type":93,"tag":94,"props":539,"children":540},{},[541],{"type":98,"value":542},"Sequencing matters, and the order that works is not the order the products are usually presented in.",{"type":93,"tag":94,"props":544,"children":545},{},[546,551],{"type":93,"tag":374,"props":547,"children":548},{},[549],{"type":98,"value":550},"Content first, always.",{"type":98,"value":552}," XM Cloud (or whatever holds your content) before anything else. Everything downstream depends on the content model, and adopting engagement products on top of a model you are about to change means integrating twice.",{"type":93,"tag":94,"props":554,"children":555},{},[556,561],{"type":93,"tag":374,"props":557,"children":558},{},[559],{"type":98,"value":560},"Search next, if you need it.",{"type":98,"value":562}," It is the capability most commonly underestimated in a headless move, and it is largely independent of the engagement products, so it can proceed in parallel without creating coupling.",{"type":93,"tag":94,"props":564,"children":565},{},[566,571],{"type":93,"tag":374,"props":567,"children":568},{},[569],{"type":98,"value":570},"Assets when governance demands it, not before.",{"type":98,"value":572}," Content Hub is a platform in its own right. Adopt it when asset governance is a named problem with an owner, not as part of a bundle.",{"type":93,"tag":94,"props":574,"children":575},{},[576,581],{"type":93,"tag":374,"props":577,"children":578},{},[579],{"type":98,"value":580},"Customer data before personalization.",{"type":98,"value":582}," Sitecore Personalize on top of a customer data platform with no meaningful data in it produces rules firing on nothing. Get the data flowing, verify it is correct, then personalise on it. Teams that do this in the other order build sophisticated infrastructure that decides between two identical experiences.",{"type":93,"tag":94,"props":584,"children":585},{},[586,591],{"type":93,"tag":374,"props":587,"children":588},{},[589],{"type":98,"value":590},"Commerce on its own timeline.",{"type":98,"value":592}," It has its own stakeholders and its own risk profile, and coupling it to a content migration means one slip delays both.",{"type":93,"tag":94,"props":594,"children":595},{},[596],{"type":98,"value":597},"The general rule: adopt in dependency order, and let each product be genuinely in production before starting the next. Parallel adoption of three composable products is how organizations end up with three half-integrated systems and no working seam between any of them, which is materially worse than having adopted none of them.",{"type":93,"tag":111,"props":599,"children":601},{"id":600},"how-should-you-decide",[602],{"type":98,"value":603},"How should you decide?",{"type":93,"tag":94,"props":605,"children":606},{},[607],{"type":98,"value":608},"Work backwards from operations rather than forwards from capability.",{"type":93,"tag":94,"props":610,"children":611},{},[612,617],{"type":93,"tag":374,"props":613,"children":614},{},[615],{"type":98,"value":616},"Start with what you will actually run in two years.",{"type":98,"value":618}," Not what you would like to run. Personalization programs that nobody staffed are the most expensive shelfware in this category, because they carry both license and integration cost.",{"type":93,"tag":94,"props":620,"children":621},{},[622,627],{"type":93,"tag":374,"props":623,"children":624},{},[625],{"type":98,"value":626},"Then check who owns the seams.",{"type":98,"value":628}," Composable pushes integration ownership to you or your partner permanently. If your model is a systems integrator who builds and leaves, composable will degrade quietly after they go, because there is no longer a vendor whose job it is to make the pieces agree.",{"type":93,"tag":94,"props":630,"children":631},{},[632,637,639,645],{"type":93,"tag":374,"props":633,"children":634},{},[635],{"type":98,"value":636},"Then look at the content model.",{"type":98,"value":638}," Whether you go composable or stay on XP, the content model is the asset that outlives the decision. If it is a mess, moving it to a nicer platform makes it a mess on a nicer platform. The ",{"type":93,"tag":499,"props":640,"children":642},{"href":641},"\u002Fblog\u002Fenterprise-cms\u002Fsitecore-xp-technical-debt-audit",[643],{"type":98,"value":644},"Sitecore XP technical debt audit",{"type":98,"value":646}," is the version of this we run for clients before any platform decision, because platform choice made on top of an unmeasured content model is a guess.",{"type":93,"tag":94,"props":648,"children":649},{},[650,655],{"type":93,"tag":374,"props":651,"children":652},{},[653],{"type":98,"value":654},"Finally, price the do-nothing option honestly.",{"type":98,"value":656}," Staying on XP is a real option with real risk, and it deserves a number rather than a shrug. Running XP well for another three years is often cheaper than moving badly, and much cheaper than moving to a composable stack you do not staff.",{"type":93,"tag":94,"props":658,"children":659},{},[660],{"type":98,"value":661},"Composable is not hype and it is not a trap. It is an unbundling, and unbundling moves work rather than removing it. Sitecore made the products better and handed you the seams. Whether that trade works depends almost entirely on whether anyone owns them.",{"type":93,"tag":94,"props":663,"children":664},{},[665,667,674,676,682],{"type":98,"value":666},"If you are pricing a composable move, staring at a stack you already bought and have not integrated, or trying to decide what to license before committing, that is our work. We put senior specialists on the architecture and the integration seams, and our support hours never expire, so you can scale help to the phase you are actually in rather than to a retainer calendar. ",{"type":93,"tag":499,"props":668,"children":671},{"href":5,"rel":669},[670],"nofollow",[672],{"type":98,"value":673},"Book a call",{"type":98,"value":675},", or read about our ",{"type":93,"tag":499,"props":677,"children":679},{"href":678},"\u002Fservices\u002Fsitecore",[680],{"type":98,"value":681},"Sitecore development and support",{"type":98,"value":683}," practice.",{"type":93,"tag":111,"props":685,"children":687},{"id":686},"read-next",[688],{"type":98,"value":689},"Read next",{"type":93,"tag":418,"props":691,"children":692},{},[693,704,715,725,736],{"type":93,"tag":422,"props":694,"children":695},{},[696,702],{"type":93,"tag":499,"props":697,"children":699},{"href":698},"\u002Fblog\u002Fenterprise-cms\u002Fenterprise-cms-2026-platform-and-partner",[700],{"type":98,"value":701},"Enterprise CMS in 2026: How to Choose the Platform and the Partner",{"type":98,"value":703},": the cluster pillar and the wider platform decision.",{"type":93,"tag":422,"props":705,"children":706},{},[707,713],{"type":93,"tag":499,"props":708,"children":710},{"href":709},"\u002Fblog\u002Fenterprise-cms\u002Fis-sitecore-a-headless-cms",[711],{"type":98,"value":712},"Is Sitecore a Headless CMS?",{"type":98,"value":714},": what headless means inside Sitecore, and how XM Cloud and XP differ.",{"type":93,"tag":422,"props":716,"children":717},{},[718,723],{"type":93,"tag":499,"props":719,"children":720},{"href":641},[721],{"type":98,"value":722},"The Sitecore XP Technical Debt Audit",{"type":98,"value":724},": the six domains that decide what any move off XP costs.",{"type":93,"tag":422,"props":726,"children":727},{},[728,734],{"type":93,"tag":499,"props":729,"children":731},{"href":730},"\u002Fblog\u002Fenterprise-cms\u002Fenterprise-headless-cms-explained",[732],{"type":98,"value":733},"Enterprise Headless CMS, Explained",{"type":98,"value":735},": what the enterprise tier is actually buying.",{"type":93,"tag":422,"props":737,"children":738},{},[739,741,745,747,753],{"type":98,"value":740},"Work with us: ",{"type":93,"tag":499,"props":742,"children":743},{"href":678},[744],{"type":98,"value":681},{"type":98,"value":746},", or our ",{"type":93,"tag":499,"props":748,"children":750},{"href":749},"\u002Fservices\u002Fheadless-cms",[751],{"type":98,"value":752},"headless CMS agency",{"type":98,"value":683}]