What is Statamic? How the CMS works, what it costs and who it suits

If you want to know what Statamic is, the page you're reading is a fair example. It's served by Statamic 6, and every word of it sits in a text file inside a Git repository, next to the code that displays it. There's no content database behind it.

Statamic is the content management system (CMS) I build every client site on, and I've written two addons for it. This post explains what it is in plain English, how it works, what it costs, and where it isn't the right fit.

What is Statamic?

Statamic is a CMS: the software your team logs into to edit pages, publish posts and upload images. It is built on Laravel, a popular framework for building web applications in PHP (the programming language that runs a large share of the web).

Its main difference from WordPress and most other CMSs is where the content lives. By default, Statamic stores it as files on disk rather than in a database. The current major version is Statamic 6, released in January 2026. I covered what changed in Statamic 6: what's new and why it matters.

Content lives in files, not a database

Each page, post or case study is a single file. The settings for that entry sit at the top in YAML, a plain-text format for structured data, and the body follows. This is the top of the file for this post:

# content/collections/blog/2023-04-25-0000.the-power-of-statamic-cms-speed-security-and-flexibility.md
---
id: 6068cf9b-87ae-480d-92d9-65d8db62a838
blueprint: blog
title: 'What is Statamic? How the CMS works, what it costs and who it suits'
categories:
  - statamic
  - web-development

The user accounts are files too. My login for this site is a YAML file in a users folder.

Because it's all files, the content goes into Git, the version control tool developers use to track changes to code. The first commit to this site's content folder was in March 2022, and more than 700 commits have touched it since. I can see what any page said on any date, who changed it, and put it back if an edit goes wrong. Content and templates move from my machine to a test copy of the site and then to the live site together, so a new page doesn't arrive before the template that displays it.

Every change to this site's content since March 2022 is in its Git history, right next to the code that displays it.

Files don't make it slow

A fair question is whether reading files on every visit is slow. Statamic doesn't do that. It reads the content files into an index it calls the Stache, held in Laravel's cache, and answers requests from that. When a file changes, it updates the parts of the index that changed.

On top of that sits static caching. The lighter option keeps each finished page in the cache so Statamic can skip rebuilding it. The heavier option writes each page out as a plain HyperText Markup Language (HTML) file that the web server hands over without running Statamic at all. That is as fast as a page can be served, but anything that needs the server to respond, such as a form that checks its fields before sending, needs extra work.

Caching needs setting up with care. On one site I look after, tracking parameters from paid ads filled the cache with around 25,000 extra copies of the same few pages. It grew to 2.3GB and took the site offline. The fix was a few lines of config.

What your team sees: the Control Panel

Editors never touch the files. They log into the Control Panel (CP), Statamic's admin area, and fill in forms. Each type of content, such as news, case studies or events, gets its own collection, and each collection gets a blueprint: the exact set of fields that content type needs. A case study might have a client name, a quote and a gallery. A news post might have a date and a category. Nobody has to remember a layout rule or paste in code.

When I moved Vocal from Perch to Statamic, I set up seven collections so their team could publish case studies, blog posts, resources and opportunities from clearly separate areas. Annie Keane at Vocal said afterwards that "the new Statamic system is a significant improvement on our old setup and is much more user-friendly."

On the L.B. Foster global site, I built the editing experience in the Control Panel first. Their marketing team could enter content while I was still developing the templates, and they already knew the CMS by launch day.

What developers work with

Templates are written in Antlers, Statamic's own template language, or in Blade, the one that comes with Laravel. Both are plain HTML with tags that pull content in. Because Statamic is a Laravel application underneath, any Laravel developer can work on a Statamic site, and anything Laravel can do, a Statamic site can do. That matters if you ever change developer.

Addons are installed through Composer, the package manager for PHP. I maintain two on the Statamic marketplace. Sentinel checks a site's Statamic, PHP and package versions against public vulnerability data and shows the results in the CP. Tracer adds a field that builds campaign tracking links for each entry, so editors can copy them without leaving the post they are publishing.

When you need a database

Flat files suit most business websites, but not every site. For the others, Statamic has an official Eloquent driver that moves entries, users, forms and other content into a database, while the site's configuration can stay in files. There are commands to move content back to files if you change your mind.

The usual reasons to use it are a large number of entries, content that visitors create rather than your team, or data another system needs to query directly. If your site is mostly pages, posts and case studies edited by a marketing team, files are simpler and you lose nothing.

What Statamic costs

Statamic Core is free. It has everything you need to build a site, but it allows one admin user and one form. That's fine for a personal site and too tight for most businesses.

Statamic Pro is $349 (US dollars) per site, with a year of updates included, then $99 a year to keep receiving updates. It is free to use while a site is in development. Pro adds unlimited users and roles, revisions and drafts, multi-site and multilingual sites, Git automation in the CP, and access through an application programming interface (API) or GraphQL, for builds where another app or website displays the content. Those are the figures on Statamic's pricing page as of September 2026.

If more than one person will log in, or you want to see and restore earlier versions of a page, budget for Pro.

Who Statamic suits, and who it doesn't

Statamic suits an in-house marketing team that wants a site built around their content, with editing screens that match it and no plugins to juggle. It suits organisations that want every change recorded, and sites where speed and fewer moving parts for an attacker to target matter more than a long list of off-the-shelf features.

It is a poorer fit in a few cases:

• You want to buy a theme and add features yourself without a developer. Statamic has no theme store in that sense, and its marketplace lists around 500 addons against WordPress's tens of thousands of plugins.

• You need several people editing and the Pro licence is a real obstacle to the budget.

• You want a developer who already knows the platform on short notice. There are far fewer Statamic specialists than WordPress developers, although any Laravel developer can pick it up.

• Most of your content is generated by visitors or other systems. You can do it with the Eloquent driver, but a flat-file setup is the wrong starting point.

Statamic also needs looking after like any other CMS. It runs on PHP, which has its own support dates, and pulls in dozens of Composer and npm packages (ready-made code libraries the site is built from), each with its own security fixes. This site moved from Statamic 5 to 6 in March 2026, two months after 6 came out. If you'd rather someone else kept track of that, that's what my Statamic maintenance plans cover.

If you're weighing up Statamic for your next site, my page on Statamic websites explains how I design and build them, what is included, and what a project typically costs.