Buyers talk about CMS cost in two registers: what the platform charges, and what it takes to build and run the sites on it. Buyers describe the first very differently by platform — Contentful charges tied to instances, spaces and content, large licences on AEM and Sitecore, and little or no licence on open source; the second — implementation partners, developers, agencies and hosting — can materially add to the first. Below are the seven mechanics buyers describe and how the cost shows up platform by platform; where buyers who left on price went is recorded on the Contentful, Sitecore and WordPress alternatives pages. The companion read is what headless CMS buyers wish they'd known (where the ratings live).
The list price is not the price
Across the interviews, buyers describe three kinds of CMS cost: the cost of structure (instances, spaces and the content model), the cost of operation (developers, agencies, partners and hosting), and the cost of change (upgrades, rewrites, migrations and even small site edits).
Contentful buyers describe pricing that grows with the content model
Contentful buyers describe charges tied to instances, spaces, components or content — a bill that grows as they structure more of it. One running several brands says “there's a cost to each Contentful bucket that I got to go in and create.” Another says “it gets absurdly expensive the more content that's on there,” and that “the prices have been just skyrocketing as we scaled.” A third describes the platform starting flat and then charging for each component added: “you are paying Contentful and you are paying your devs also.” The tier matters too — one buyer found “we need to have the enterprise thing to get what we need.” The online marketplace in the stories below pays per instance.
Named in this context: Contentful
AEM and Sitecore buyers count specialists alongside the licence
Buyers of Adobe Experience Manager and Sitecore describe a premium licence with specialists alongside it. One AEM buyer says it “can be expensive to maintain” because of “the amount of support that is required internally to continue to keep the platform current”; another, at a large company, says it is “very expensive for us. So we're at this point where we can't have this as a best-in-class solution for everybody,” and is deciding which countries and divisions get it. On Sitecore, one buyer says it is “not the cheapest CMS either” and that you need dedicated Sitecore developers; another finds its “price points are pretty high considering there are a lot of competitors in the market.”
Named in this context: Adobe Experience Manager · Sitecore
Unexpected costs can come from overages, upgrades and price increases
Some significant costs buyers describe were not in the original quote. A Sitecore buyer describes overage: “If they catch you accidentally going over plan even just a little bit, they'll be hit with a big bill.” On Kentico, one buyer says new functionality means paying to upgrade the hosted version, and that “it's so expensive to maintain and upgrade.” And on Contentful, one company moved when “Contentful was looking to raise their prices dramatically.” A vendor-required architectural change is a different kind of cost again: another Sitecore customer had to rewrite its sites, a major implementation expense beyond the licence (see the stories below).
Named in this context: Sitecore · Kentico · Contentful
Hosting can become a separate CMS cost
Buyers describe hosting as its own line, in several forms: managed WordPress hosting, a move between hosting providers, cloud-hosting fees and traffic overages. A WordPress VIP customer praises the pricing — “I think my bill this year will actually be lower than the year before from WordPress VIP” — while another buyer is moving from WP Engine to Kinsta for “both cost, value, what they offer.” A team rebuilding on Netlify says it “essentially eliminates our Azure hosting fees, which are pretty pricey.” Acquia buyers describe traffic in the contract: “You have a kind of quota assigned as part of your contract. If it exceeds, you get charged more.”
Named in this context: WordPress VIP · WP Engine · Netlify
Agencies and developers are part of the cost
Software price is not the cost of a working site, and buyers count who makes the changes. The credit union in the stories below left an agency-run CMS over the fees for small edits. A team moving from Kentico to Optimizely expects savings because the new platform is “easier to maintain, it's more low code, no code.” On AEM, one buyer describes migrating thousands of pages without “the right cost structure, capacity structure, and support,” and a bank choosing its next CMS is working out “how much time will it take and how much money will it cost” with implementation partners before settling the licence.
Named in this context: Kentico · Optimizely · Adobe Experience Manager
Suite agreements can change the incremental cost
Buyers in the Adobe stack describe the enterprise agreement changing what each additional tool costs them. One dropped a landing-page tool it rated well because “it was an extra cost for us where AEM was kind of part of this larger enterprise agreement.” A buyer comparing suites notes that buying more from one vendor “gives you better bargaining power when you are discussing licensing,” and another in the Adobe stack is weighing more of it because “a lot of efficiencies of scale are making it a natural choice.” The counterweight: “We're in with Adobe anyway. To me, it's a no-brainer. The problem is just it just costs so much.”
Named in this context: Adobe Experience Manager · Unbounce
Open source trades licence cost for costs the buyer carries
Buyers value free software and describe development, hosting, maintenance and, in some cases, security as costs or responsibilities they carry themselves. A WordPress user says “the price tag is close to nothing,” then adds “you need to develop it right from the get-go in the right way for it to be scalable and not to have tech debt over time.” A Drupal buyer's perception is that it is “more or less a free code, and it's not as secure as some other more expensive languages.” A Strapi user says “it's super cheap” but has taken “more wrangling than I would have wanted from a CMS,” and one company is moving its WordPress sites to AEM because “There's a lot of security risk with WordPress.”
Named in this context: WordPress · Drupal · Strapi
How the cost shows up, platform by platform
What the corpus does show for each platform is the satisfaction rating and the shape of the cost complaint. The headless platforms buyers move to on price sit near the top; Contentful and the enterprise suites draw the sharpest cost complaints. These are overall buyer satisfaction ratings, not ratings of value for money.
| Platform | Buyer rating | How the cost shows up |
|---|---|---|
| around 7.5 | A destination for a price-led move off Contentful, still under way. | |
| 7.3 | Charges tied to instances, spaces, components or content — a bill that grows as the content model does; the most common starting point for price-led moves here. | |
| 7.2 | A premium licence plus the specialists to keep it current; buyers call the product solid and the licence and upkeep expensive. | |
| 7.2 | Software that costs close to nothing; buyers pay instead for hosting, developers, maintenance and, for some, security. | |
| around 7 | A destination for a price-led move off Sitecore. | |
| 5.9 | Price points buyers call high for the market, overage bills, and a vendor-required rewrite one buyer calls long and expensive. |
Want this read against your own stack?
Get my read →The stories behind the mechanics
The counter-current: some buyers find the premium worth it
Not every buyer is trading down. One AEM user says “I don't have any real concerns around AEM,” and that with a licensed CMS “you have ongoing development, you have a support team.” Another calls it “very expensive” but adds “The product itself is very solid.” A buyer comparing Adobe and Sitecore rates Sitecore higher “because of pricing, I think Sitecore is sharper.” And the cheaper path has its own price: the Strapi team's “more wrangling,” and the WordPress buyer's warning about tech debt.
What this means for your CMS budget
In these interviews, CMS cost takes several forms. Contentful buyers describe charges that grow with instances, components or content. AEM and Sitecore buyers describe large licence costs alongside the specialists and partners needed to operate them. Buyers using open-source CMSs describe low software cost but expenses they carry elsewhere, including development, hosting, maintenance and sometimes security. Across platforms, implementation and the people who build and change the site can be as important to the budget as the licence itself. Our recommendation, not a practice buyers describe: before comparing CMS quotes, identify exactly what each vendor meters — instances, spaces, components, content, traffic or another unit — and model how that meter grows with your architecture; price the implementation partner and the people who will keep an enterprise suite current alongside the licence; on open source, price hosting, development and maintenance; and on any platform, ask what a vendor-required upgrade would cost.
Common questions
How is CMS software priced?
Different CMS architectures create different cost structures. Contentful buyers describe charges tied to instances, spaces, components or the amount of content; Adobe Experience Manager and Sitecore buyers describe large licences alongside implementation partners and specialists; and buyers of open-source platforms such as WordPress and Drupal describe low software cost but development, hosting, maintenance and sometimes security as costs they carry themselves.
Why is Contentful so expensive?
Buyers point to pricing that grows with the number of instances or brands they run, the content they store and the components they add, to an enterprise tier needed for some features, and to price increases. Cost comes up in most of the departures recorded on the Contentful alternatives page, and the price-led moves in these interviews went to Shopify's own content tools, Sanity and Payload.
Is Adobe Experience Manager worth the cost?
Buyers are split. Its critics call it overpriced for what they use and expensive to keep current, and one large company is rationing which countries and divisions get it because of the cost. Its defenders say the product itself is solid and that a licensed platform brings ongoing development and support a homegrown one does not.
Is WordPress really free?
The software is, and buyers value it for that. What buyers describe paying for is hosting, sometimes on managed services such as WordPress VIP or WP Engine, the developers who build and maintain the site, and for some, security. One buyer warns that it has to be built right from the start to avoid technical debt, and another company is moving its sites off WordPress for security.
Is Sitecore cheaper than Adobe Experience Manager?
One buyer comparing both found Sitecore sharper on price but needing three products where Adobe needs two, and found smaller, cheaper implementation partners for Sitecore. Others call Sitecore's price points high for the market, describe bills for going over plan, and describe a required platform rewrite that proved long and expensive.
Get this research made for your stack
Facing a CMS renewal, or pricing a move to a different platform? Do a 15-minute interview about your sites, your content model and who builds for you, and get this personalized — which cost mechanics drive your number, and where peers found the savings.
Get my personalized read — 15-min interviewNo password · your interview is anonymized before it ever informs a page like this one.