Website builder versus CMS, explained

A website builder is software a company runs for you. A content management system, in the sense the term is usually used for WordPress, is software you run yourself. Every comparison between named platforms in this section is really a comparison of where each one sits on that one line, and it is worth stating directly rather than leaving implicit, because it is the single fact that predicts most of what a platform will cost a business over time.

Where “who runs it” actually shows up: a website builder versus a CMS

A website builder — Wix, Squarespace, Webflow, and Shopify for commerce specifically — owns the server, applies its own software updates, issues its own certificates and, largely, defends its own infrastructure and storage. None of that appears as a line item you manage, because it is bundled into the subscription as a fully managed service. What you cannot do is take the software elsewhere; it does not exist independently of the company that built it.

A self-hosted CMS — WordPress being the dominant example — is software installed on hosting you choose. Nobody updates it for you unless you arrange that separately, or pay for managed hosting that includes it, which is why what WordPress actually is spends so much of its length on maintenance rather than features. In exchange, the software is genuinely yours: it can move to any competent host, be modified without asking anyone’s permission, and outlive any single vendor’s business decisions.

The trade is not “better” and “worse” — it is “paid how”

A builder’s subscription fee is, in large part, a maintenance fee wearing a different name. You are paying the company to do the things a self-hosted CMS otherwise leaves to you or to whoever you hire. That is not a criticism of either model; it is a description of where the same underlying cost has been moved.

This is the clearest way to compare a builder’s monthly price against a self-hosted stack’s apparently lower software cost: the self-hosted option is not actually free, it has simply not billed you yet for the maintenance obligation it has quietly assigned. A fair comparison prices hosting, updates, backups and security handling for the self-hosted option, and only then compares it to the builder’s all-in fee — comparing a builder’s total price to a self-hosted platform’s software price alone is comparing two different things.

Flexibility runs the other way for a self-hosted CMS

Builders trade convenience for boundaries. A self-hosted CMS trades convenience away in exchange for having, in principle, no functional ceiling — anything can be built, given enough development time and budget. That is genuinely true, and it is also why “self-hosted CMS” and “unlimited budget for custom development” are not the same claim; a small business on WordPress with no development budget hits a practical ceiling too, just a different one, set by which plugins exist rather than by the platform’s own template rules.

The question that actually decides website builder versus CMS

Not “which is more powerful” — a self-hosted CMS almost always wins that question and it is rarely the right one to ask. The question that predicts satisfaction is: who, specifically, is going to do the ongoing maintenance, and is that arrangement funded for as long as the site exists? If the honest answer is “nobody, indefinitely,” a builder is very often the better decision regardless of how the feature comparison reads, because an unmaintained self-hosted site is a well-documented security exposure, covered in why small-business websites get compromised.

If the honest answer is “yes, there is a funded maintenance relationship, now or planned,” the self-hosted route’s flexibility becomes available without the risk that makes it a bad idea in the first case.

Why this distinction is often blurred in a sales conversation

A supplier proposing a self-hosted CMS build has a natural incentive to emphasise its flexibility over its maintenance obligation, because flexibility is the more appealing pitch; a supplier proposing a hosted builder has the reverse incentive, emphasising simplicity over the functional ceiling it imposes. Neither framing is dishonest exactly, but neither is complete, and a buyer who only hears one half of the trade from whichever supplier they are speaking to should ask the question directly rather than accept the framing offered.

A genuinely useful test question to ask any supplier

“If I stop paying you next month, what happens to my site?” On a hosted builder, the honest answer is generally that the site keeps running under the same subscription regardless of who manages it, though editing may pause. On a self-hosted CMS with no maintenance arrangement, the honest answer is that nothing changes immediately, but nobody is applying updates from that point on — which is a materially different kind of exposure, and a supplier’s answer to this one question reveals a great deal about how clearly they understand, and are willing to state, the model they are actually selling.

Where to go from here

Choosing a platform for your business turns this single distinction into a fuller set of questions across all six named options. What a CMS actually does covers the mechanics of content-and-presentation separation that sits underneath both models. And what website maintenance actually does is the honest answer to what a self-hosted CMS is quietly asking you to fund.

Whichever model a build lands on, the point where this actually gets priced is website design services — a quote that does not distinguish between building on a hosted platform and building self-hosted software is a quote that has not yet decided who is doing the maintaining.