What Craft CMS really costs to own

Most teams looking at Craft ask one question first. What does it cost? The honest answer is that the licence is a small line item in a bigger picture and the bigger picture is what decides whether Craft pays for itself or quietly drains the budget.

I have built and maintained Craft sites for years for clients ranging from one-person studios to teams of fifty. The cost structure is consistent enough that I can describe it as a model. What follows is that model, with the components in the order they tend to surprise people.

The licence is the smallest piece

Craft offers tiered editions. Solo is free and indefinite, capped to a single admin account. Team adds a small group of editors with shared permissions. Pro removes those caps and adds features around previewing, user accounts and SSO. Enterprise covers larger organisations with custom licence agreements and premium support. Craft Cloud, the first-party hosting product, bundles the editions for sites hosted on it.

You pay once per Craft installation, then optionally renew each year for updates and continued support. If you skip the renewal, the site keeps running on the last version you had access to. That structure is unusual in the CMS world and worth understanding because it changes how the cost compounds.

In a five-year cost model, the licence and renewals are rarely the largest component. They are the most visible, which is why they get the focus, but they are not the part that decides the budget.

Plugin and module licences are the second invoice

A typical Craft site uses somewhere between five and fifteen commercial plugins. The Craft plugin ecosystem follows the same renewal pattern as Craft itself. Buy once, renew annually for updates. Each plugin sits in a price bracket that ranges from a small one-off cost for utilities to a larger annual figure for the more involved ones like Solspace Freeform, SEOmatic, Commerce or Sprig.

The total plugin spend is usually larger than the Craft licence itself. That is not a bad thing. The Craft plugin market is small enough that the plugins on it tend to be high quality and actively maintained. The cost reflects that.

Two things to plan for. First, plugin renewals lapse and the site keeps working, but you stop getting updates. Plan a renewal review once a year and decide consciously which renewals matter. Second, some sites need bespoke modules built in code rather than plugins bought off the shelf. That sits in the build budget, not the licensing budget, but it is part of the same conversation.

The build is where most of the money goes

A new Craft build sits anywhere from a few weeks of senior developer time for a small marketing site to several months for something with custom content modelling, multilingual content and integrations. The shape of the build cost is similar to any other modern web project. Design, front-end, content modelling, back-end work, content migration, testing.

What is specific to Craft is that the content modelling phase tends to be a larger share of the project than it is on WordPress. Craft rewards thoughtful content architecture and penalises sloppy modelling. A team that invests two extra days at the start saves weeks of editor friction over the life of the site.

The build budget also has to absorb the difference between an off-the-shelf theme and a bespoke design. Craft has no theme marketplace in the WordPress sense. Sites are built bespoke or from internal agency templates. The starting line is higher than WordPress, but the ceiling is too.

Hosting sits in a narrower bracket than WordPress

Craft will run on most modern PHP hosts, but the hosts that actually understand Craft are a small list. Servd, Craft Cloud, Cloudways with a proper PHP stack, a managed VPS at someone like DigitalOcean or Hetzner with a developer who knows the stack. The bracket sits higher than the cheapest WordPress hosts and below dedicated enterprise hosting.

The trade-off is that the floor of Craft hosting is higher than the floor of WordPress hosting. The ceiling is similar. You cannot run a serious Craft site on a five-pound-a-month shared host and you should not want to. Budget hosting that actually fits the platform.

Maintenance is the line that gets cut first and missed most

Every Craft site needs ongoing attention. Craft minor versions ship regularly with security and bug fixes. Plugins update. PHP versions on the host move forwards. Major Craft versions land every few years and require a planned upgrade rather than a one-click button.

For a typical marketing site, that maintenance lands somewhere around a half day to a day of senior developer time each month, plus a project-shaped piece of work every few years for the major version upgrade. Some sites need more. Sites with heavy integrations, custom modules or unusual content models tend to need closer attention.

The teams who cut this line do not avoid the cost. They postpone it. The bill arrives later as an emergency upgrade or a security incident and it is always larger than the maintenance retainer would have been. I have written about how I structure ongoing support if you want to see what that looks like in practice.

Content production does not get cheaper because of the CMS

Whatever CMS you pick, somebody still has to write the words, take the photos, edit the video and publish the entries. That cost is independent of the platform. What changes between platforms is how much friction sits between the editor and the publish button.

On Craft, the editor experience is one of the better ones in the market. Field groups are clearly labelled. Matrix blocks each have their own field layout. Live preview shows the page as it will look. The control panel is opinionated about content architecture in a way that helps editors think clearly about structure.

The cost question here is the opportunity cost of bad editor experience. A team that abandons a blog post halfway through, or asks the developer to update a homepage banner because the CMS is confusing, is paying a friction tax. That tax does not appear on any invoice, but it is real.

Training is small but often skipped

A two-hour walkthrough of the control panel, plus a one-page reference sheet, is enough for most editors to be productive in Craft. Teams that skip this expect editors to figure it out on the job, which works for the technically curious and leaves everyone else frustrated.

Budget a half day of training per editor as part of the build, with a follow-up session a few weeks in once the team has hit real questions. The cost is small. The payoff in editor confidence and content velocity is large.

A simple model for estimating your own number

When I help teams estimate the five-year cost of a Craft site, the model has the same components in the same order.

• One-off build cost. Design, content modelling, development, content migration, training. The largest single number.

• Craft licence. Once-off purchase at the edition you need, plus optional annual renewal. Smaller than people expect.

• Plugin licences and renewals. Five to fifteen plugins, mostly with annual renewals. Larger than the Craft licence.

• Hosting. Annual or monthly cost on a host that fits the platform.

• Maintenance retainer. Half a day to a day of senior developer time per month, plus a project-shaped upgrade every few years.

• Content production. Whatever it already costs you. The CMS does not change this number directly but it changes how much friction the team feels.

Add those up over five years. The total is usually larger than the build budget alone by a factor of two or three. Teams that plan the full picture from the start make sensible decisions. Teams that only budget the build make panicked decisions in year two.

Where Craft tends to pay for itself

Craft is not the cheapest CMS to own in raw line items. It pays for itself in the things that are harder to measure. Lower editor friction, fewer security incidents, a content model that does not collapse under its own weight, a smaller pile of plugins that each do one job well and a maintenance posture where minor updates do not break the site.

For teams who care about content quality and have a developer available to take advantage of the platform, the maths usually works out. For teams who want a site that runs itself with no developer attention, Craft is the wrong tool. I would point them at Squarespace or a managed WordPress host instead.

What to do next

If you are sizing up a Craft project and want a realistic five-year number, the practical move is to work through the model above with whoever is going to deliver and support the build. Pick the licence edition that fits your team. List the plugins you will need. Decide on a host. Lock in a maintenance retainer. Then add the build estimate on top.

If you want help putting that number together, see what Craft CMS development looks like as a senior freelance engagement, or read how to choose a Craft CMS agency in the UK if you are weighing studios against freelancers.