Statamic for publishers: a flat-file Laravel CMS with a Pro tier

What is Statamic?

Statamic is a content management system built as a Laravel package. Its repository calls it the core Laravel CMS Composer package, a flat-first, Git-powered CMS that is installed into a Laravel application. The company, Statamic, LLC, shows a copyright range from 2012 on its site and describes the product as a flat-file CMS that scales to database mode.

In practice that means pages, collections and settings are stored as files, which suits version control, and a developer who already knows Laravel can extend it with familiar tools.

Who is Statamic best for?

Statamic works for small and mid-sized publications built by developers who like Laravel: a niche magazine, a local news site, a publisher’s microsite. Content in Git means changes are reviewable and deployments repeatable, and the static caching options suit sites with mostly anonymous readers.

It is less suitable for a large newsroom that wants a mature plugin market, publishers without a Laravel developer, and anyone who needs the CMS licence to be open source. Our CMS directory lists alternatives in each of those situations.

Picture a small digital magazine with a developer on retainer and three editors. Content in files means the developer can branch, review and deploy structural changes the way they do code, and editors work in the control panel. Where a publisher expects non-technical staff to run hosting, plugins and upgrades alone, the Composer and Laravel stack becomes a burden.

A useful question is who will own updates. A Laravel package is updated through Composer, so the answer must be a person or retainer, not a button.

How does Statamic handle editorial workflow?

Two key features sit behind Pro. The documentation states that Revisions, its publishing workflow with published, unpublished, working copy and revision states, is a Pro feature. It also marks access control, meaning permissions, roles and groups, as a Pro feature. Access then works as a stack: permissions are collected into roles and roles are assigned to users or groups, with super admin accounts able to do everything.

Core includes one super admin account, according to the pricing page, so any site with more than one editor effectively needs Pro. The pricing page says Pro adds multi-user capabilities. We did not find scheduling or comment workflows described in the pages we opened, so check the documentation if you need them.

Git integration is documented too. It is switched on with a setting in the environment file, and it fits a workflow where content changes are committed and deployed like code.

SEO, structured data and feeds

The documentation index we read did not list pages on SEO, sitemaps or feeds, so this profile makes no claims about built-in sitemaps, meta fields or RSS. Statamic has a redirect tag that sends a visitor to another URL when rendered, but that is template-level logic, not a redirect manager.

Treat SEO output as something a developer builds in templates or adds through an add-on, and verify the specifics before committing. Structured data guidance should come from Google’s documentation, not from a CMS vendor.

Media, multilingual and performance

Multi-site is how Statamic handles variations of a site. The documentation says it manages variations of a single site, or sections of one site across domains or subdomains, such as translations or country versions. It says explicitly that it is not intended for multi-tenant applications running completely separate sites.

For speed, Statamic documents two static caching strategies. The application driver serves pre-rendered data from Laravel’s cache but still runs a full Statamic instance. The file driver writes static HTML files that the web server delivers without running PHP, at the cost of rewrite rules in your server configuration.

Hosting and requirements

Statamic needs PHP 8.3 or above and Composer. The documentation lists the BCMath, Ctype, Exif, JSON, Mbstring, OpenSSL, PDO, Tokenizer and XML extensions, plus GD or ImageMagick for image work. It runs as a Laravel package, so a Laravel-capable host is needed; the requirements page does not name a Laravel version.

Because content is flat files by default, you can start without a database server. The vendor says Statamic scales to database mode, and we have not verified how that is configured. Compare the effort with our self-hosted guide.

Extending Statamic

Statamic is a Laravel package, so the Laravel ecosystem is available to developers. For front ends, it has a read-only REST API and a read-only GraphQL API. The documentation says both are disabled by default, and each resource such as a collection or taxonomy must be enabled explicitly.

The pricing page lists API access among Pro features, while the API pages we read do not mention a Pro requirement. Confirm which applies to your edition before you build on it. We have not verified the number of add-ons available.

What does Statamic cost?

The licence has no cost for Core, which includes one super admin user. Pro is listed at US$349 per site, with the first year of updates included and US$99 a year for updates afterwards, and can be trialled free during development. Enterprise has custom pricing and includes premium support, according to the pricing page. Non-profits and educational institutions get 20% off.

Under the licence, a copy may be actively installed in one production environment at a time, so each production site needs its own. Add hosting and developer time. See our cost guide for the other cost lines a CMS carries.

For budgeting, assume Pro for any site with more than one editor, because the free edition has a single super admin and the documentation places revisions and role-based access in Pro. That puts the real entry cost at the Pro price per site, then the yearly update fee from the second year if you want continued updates, plus hosting and development.

Where does Statamic fall short?

• Pro gates workflow. Revisions and role-based access are Pro features, so the free edition is a one-person tool.
• Proprietary licence. Source is visible but not free software, and updates after year one cost money.
• Developer-run. It is a Laravel package, not a hosted app with a panel, so someone must maintain PHP, Composer and updates.
• Unverified areas. We could not confirm built-in SEO output, feeds, scheduling or add-on counts from the pages we opened.

The verdict for publishers

Statamic is a fine choice for a small publication that already has Laravel skills. Content in Git and optional static caching make for a tidy, fast site, and the pricing is clear.

If you need many editors on a budget, an open-source licence or a deep plugin ecosystem, look elsewhere. This profile is based on the vendor’s documentation and not on a test install; see how we test.