Statamic cost in 2026: licence, build, maintenance

From statamic.com/pricing, checked on 30 October 2026. These are paid to Statamic, not to us. Older articles quote lower Pro prices, and this is the current one.

Most business sites need Pro, for one simple reason. Core has a single admin account, and Statamic’s own page advises against sharing it. As soon as two people edit the site, or you want drafts and revisions, you are on Pro.

Verified non-profits, schools and universities get 20% off first-party products, including renewals, through Statamic’s support team. Statamic also mentions volume pricing and regional discounts, which aren’t in these tables because you have to request them.

Statamic’s page lists two-factor sign-in under Enterprise too. If security policy makes that a must for your editors, ask Statamic what applies to your plan and version before you budget.

You don’t need to buy Pro at the start of a project. Statamic’s licensing docs describe a trial mode for non-public addresses, such as localhost or a staging subdomain, with no time limit. A public launch needs the licence, with its key added to the site’s configuration. So the first year of updates is best started close to launch, not months earlier while the site is being built.

Ask who buys it. If your agency buys the licence, make sure the quote says the site will be transferred to your Statamic account afterwards. The transfer has to be approved by the recipient, so someone on your side needs an account by launch day, and the renewal invoices then come to you.

This assumes you keep updates on and today’s prices hold, which nobody can promise. It covers the licence and updates and nothing else. For a live business site it is a small number next to the build, which is why we don’t think the licence should decide between platforms.

Licences are per site, so the sums scale in a straight line unless you get a volume price. A group running three sites for five years would pay 3 × $349 = $1,047 up front, then 3 × $99 × 4 years = $1,188 in updates, or $2,235 altogether at list price. Multi-site on one install is a different arrangement from three separate sites, and that choice is worth raising early. Check how Statamic would license your setup before you plan around it.

The licence figures come from Statamic’s price list. Everything else is yours, from quotes you hold. We leave those blank deliberately, because a default number would look like an estimate, and it wouldn’t be one. Nothing you type leaves your browser.

It leaves out your staff’s time, content writing, design if you’re buying it separately, and any volume discount. Adding those is worthwhile if they are big for you.

The drivers matter more than any average, because they tell you which parts of your own project are expensive.

• Number of content types. Each page type, its fields and who edits it become collections and blueprints. Mistakes here are the costly ones to fix later, so this work comes before design.
• Design. A starter kit from the Marketplace and a design made from scratch are different projects. Check what a kit costs on its own listing, since prices aren’t on the main pricing page.
• Languages and sites. Multi-site is a Pro feature and it affects the content model, the templates and the redirects, so settle it early.
• Integrations. Each CRM, payment or search connection is its own small project with its own failure cases.
• Migration. Moving from another CMS is separate work. It has its own guide: what drives WordPress to Statamic migration cost.
• Headless or not. Feeding a separate Next.js front end over the REST or GraphQL APIs means building two things, and you lose what templates give you for free.
• Addons or custom code. The Marketplace covers a lot. Whatever it doesn’t cover becomes custom addon work, and you then have to maintain that across releases.

We don’t publish a price band for Statamic builds. We quote a fixed price after seeing your content model and designs, and our developers start from $20/h, invoiced in USD, GBP, EUR or INR. If you are building with your own team, dedicated developers are ~$2,200 (junior), ~$3,250 (mid) or ~$5,400 (senior) for 160 h per month, retainer discount. Those are our published rates, not a Statamic build estimate.

A major upgrade most years

Statamic’s release policy plans a major release roughly every year, with one year of bug fixes and 18 months of security fixes each. Statamic 5 security fixes end in December 2026. Statamic 6 gets them until December 2027, and Statamic 7 is planned for Q1 2027. That makes upgrades a recurring cost, and it’s the line older “set and forget” comparisons leave out.

Laravel and PHP move too

The current Statamic package requires Laravel 12.40 or 13, and Statamic’s docs ask for PHP 8.3 or above. If Statamic sits inside your Laravel application, a Statamic upgrade can pull a framework upgrade behind it, and that belongs on the plan. Our Laravel upgrade prices are published if that applies to you.

Paid addons

Marketplace addons and starter kits are priced separately on their own listings. Total them for the ones you actually need before comparing against WordPress plugin costs.

Hosting that fits

Statamic needs a server that can run PHP 8.3 and Composer, so the cheapest shared plan may not qualify. We don’t quote hosting prices here, because they change and depend on traffic. Get a figure from the host you’d really use. Statamic hosting requirements lists what to check.

A Statamic site needs framework and CMS updates, security releases, tested backups and someone who owns Git and deployment. We don’t publish a Statamic maintenance plan. Our USD 99/month plan is published for Laravel applications, and our WordPress care plans are for WordPress, so neither is a price for your Statamic site. CMS work is quoted once we know the scope, so ask us if you want a figure.

Quotes for the same Statamic site can look far apart because they cover different things. Before comparing totals, line them up against these questions:

• Is the Statamic licence included, or is it a separate payment to Statamic?
• Are paid addons and any starter kit included, and whose account holds them?
• Who enters content? Moving it across, rewriting it and checking it are three different jobs.
• Does the migration price include a redirect for every old URL?
• Is setting up hosting and deployment in scope, or is that assumed to be yours?
• What does the first major upgrade cost, and is it mentioned at all?
• What happens to the site if the supplier stops working with you?

The last two tell you the most, because they are about year two. Our guide to choosing a Statamic agency has more to ask. If you’re comparing Statamic with staying on WordPress, run the same three-year sums for both, using plugin renewals and hosting from your own invoices. Statamic vs WordPress covers everything that isn’t price.

1. List your page types, your editors and your languages.
2. List integrations and any WordPress plugins you rely on today.
3. Get quotes for the build and for hosting, then put them in the calculator with a three-year view.
4. If you want ours, send that list.

More on what we do is on our Statamic development page. We have no public Statamic case study on this site. Most of our work is delivered under NDA, so many projects cannot be named. The projects below are our UK engagements on Laravel, the framework Statamic is built on. They are not Statamic sites.