Statamic vs Filament: a ready-made CMS or a custom one

Statamic and Filament are not competitors. Statamic is a finished content management system. Filament is a toolkit for building your own administration panel in Laravel. Choose Statamic when the job is publishing content: pages, articles, landing pages. Choose Filament when the job is managing data and processes that no CMS was designed for: orders, bookings, members, approvals. Many projects need both.
At CNJ we use both. Most websites we build run on Statamic, usually in headless mode. Sometimes a project needs a custom CMS or back office, and we usually build that with Filament. Clients often ask why we do not use one tool for everything. This article is the answer.
What each one is
Statamic is a CMS built on Laravel. You install it and get a control panel with pages, collections, a block editor, an asset library, forms, languages, drafts and content APIs. The Pro edition costs $349 per site with one year of updates, then $99 a year.
Filament describes itself as an open-source framework for building business software with Laravel. It is free, under the MIT licence, and currently at version 5. You install it and get nothing to edit yet. A developer defines the screens: tables, forms, filters, actions, dashboards.
That is the real difference. Statamic starts full and you configure it. Filament starts empty and you build it.
What you get out of the box
With Statamic, on day one:
content types with fields defined in configuration, no database work
a block-based editor and an asset library with image handling
several languages, drafts, revisions, roles and permissions
live preview, also for a separate front end
a read-only REST API and GraphQL for headless sites
With Filament, on day one:
a login and a panel layout
building blocks for tables with search, sorting and filters
building blocks for forms with validation and many field types
actions, notifications, dashboard widgets and charts
support for separating data by customer or organisation
What Filament does not give you is anything specific to content: no pages, no preview, no content API, no revisions. All of that can be built, and that is the point to notice. Building it is the cost.
Signs you need a CMS
The content is pages, articles, case studies and landing pages.
A marketing team wants to publish without calling a developer.
You need several languages, SEO fields and a preview before publishing.
The structure of the content is similar to what other websites have.
In this case a custom admin panel means paying to rebuild what Statamic already does, and getting a less polished editor at the end.
Signs you need a custom back office
The data is records and transactions, not articles: orders, bookings, applications, stock.
There are business rules: statuses, approvals, calculations, deadlines.
Different users must see different records, not just different sections.
The system exchanges data with others: accounting, payments, a warehouse, a CRM.
You need reports and exports, not page layouts.
In this case a CMS gets in the way. You end up bending content types into something they were not designed for, and every new rule is a workaround.
What each one costs
Filament is free and Statamic Pro is not, but the licence is the wrong number to compare.
With Statamic you pay a small licence and a developer configures content types. With Filament you pay nothing for the software and a developer builds every screen. For content, Statamic is cheaper by a wide margin, because the work is already done. For a business process, Filament is cheaper, because forcing a CMS to do it takes longer and the result is harder to maintain.
A useful rule: if you can describe the system as "a website with content", start with a CMS. If you describe it as "an application with a few pages", start with a custom panel.
Using both together
Because both run on Laravel, they combine well. A typical project of this kind looks like this:
Statamic manages the public content: pages, news, help articles, translations.
Filament manages the business side: customers, orders, bookings, reports.
One front end reads content from Statamic and data from the application.
Editors work in a tool made for content. Staff work in a tool made for their process. Neither group sees screens meant for the other.
There is a middle ground as well. If a content site needs to manage one or two simple database tables, Statamic can handle that with an add-on, and a second tool is not worth it. Once the tables come with rules and workflows, Filament is the better home for them.
How we decide
We ask three questions.
What is being managed? Content or records.
Who works in the system? Editors who publish, or staff who process.
What will change in two years? New pages and languages, or new rules and integrations.
If the answers are mixed, the project gets both tools, each for its part.
How to start
Describe what you want to manage and who will use it. We tell you whether a CMS is enough, whether you need a custom back office, or both, and what that means for the budget. Get in touch or see the Build & Launch package.
Frequently asked questions
Is Filament a CMS?
No. Filament is a toolkit for building administration panels in Laravel. A developer can build a CMS with it, but it does not come with pages, a content editor or content APIs.
Can Filament replace Statamic?
Technically yes, at the cost of building what Statamic already includes: content types, block editing, preview, revisions, languages and APIs. It rarely pays off for a content website.
Is Filament free?
Yes. It is open source under the MIT licence. The cost of a Filament project is development time, not the software.
Can Statamic and Filament be used in the same project?
Yes. Both are built on Laravel. A common setup uses Statamic for public content and Filament for the business side, with one front end reading from both.
When is a custom CMS better than a ready-made one?
When the system manages data and processes specific to your business, such as orders, bookings or approvals. For pages and articles a ready-made CMS is cheaper and better for editors.
Do we need Statamic Pro for a headless site?
Yes. The REST API and GraphQL are part of the Pro edition, as are roles, revisions and multilingual sites.
We write about it. We also build it.
Let's talk about your project
A 30-minute call to understand what you're building and how cvan we help. No brief required.
Prefer email?
info@cnj.si