Your client wants a fast marketing site with an editor they can actually use. You want version control, a clean codebase and no database to babysit. Most CMS options make you pick one side. So, what is Statamic? Statamic is a content management system built on Laravel that saves your content as plain files by default and gives editors a polished Control Panel on top.
That combination is unusual. If you have used Laravel before, Statamic will feel familiar, and our beginner’s guide to Laravel covers the framework underneath. If you are still choosing a platform, our guide on how to choose the right CMS gives the wider view.
In this guide, you will learn how Statamic stores content, how the Git workflow works and what the Control Panel offers. You will also see the difference between Core and Pro and how it compares with WordPress, Craft CMS and Kirby. Finally, you will see the easiest ways to host it.
TL;DR: Statamic in 60 Seconds
Short on time? Here is the whole guide in a few lines:
- Statamic is a flat-first CMS built on Laravel. Content lives in Markdown and YAML files, not in a database, unless you choose one.
- Content and code can share one Git repository. You review, branch and roll back content the same way you handle code.
- Editors get a visual Control Panel at
/cpwith collections, blueprints, fieldsets, assets and forms. - Templates use Antlers or Blade, so Laravel developers can work in the language they already know.
- Core is free for one administrator and one content form. Pro adds teams, revisions, APIs, multi-site and Git automation.
- Statamic 6 shipped in January 2026. Statamic 5 receives security fixes until December 2026.
- It is not open source. The code is public, but the license has conditions worth reading.
What Is Statamic?
Statamic is a “flat-first” CMS: a Laravel package that stores content as files on disk and adds a visual admin panel for editors. The project started in 2012. Since version 3 (June 2020), it installs into any Laravel app as a Composer package.
Think of it like a well-organized filing cabinet with a front desk. The cabinet is your folder of Markdown and YAML files. The front desk is the Control Panel, where editors ask for a page, change it and put it back without ever opening a drawer.
A few things worth knowing:
- No database is required. Entries, users and settings are files by default. You can still move content into a database later.
- It is a real Laravel app. Routes, controllers, middleware and Composer packages all work the way Laravel developers expect.
- The license is commercial. The source code is on GitHub, but it is not an open-source license.
- Free does not mean unlimited. The free Core edition covers one administrator and one content form.
| Detail | Statamic |
|---|---|
| Type | Flat-file CMS (database optional) |
| Built on | Laravel (PHP); Statamic 6 works with Laravel 12 and 13 |
| Default storage | Markdown and YAML files on disk |
| Optional database | Official Eloquent driver for Laravel-supported databases |
| Templating | Antlers or Laravel Blade |
| Editions | Core (free) and Pro (paid, per site) |
| First released | 2012; rebuilt as a Laravel package in v3 (2020) |
| Current major version | Statamic 6 (released January 28, 2026) |
| License | Commercial license, source code public |
| Small-site floor | 1 GB RAM, 1 CPU core, 5 GB disk (xCloud template) |
How Statamic Works: Flat Files, Git and the Database Option
Here is the part that sets Statamic apart from most CMS platforms. Your content is just files. A blog post is a Markdown file with YAML front matter inside a content/collections folder. Settings, navigation and user accounts are YAML files too.
To keep things fast, Statamic builds an index of those files, which it calls the Stache. You edit a file, and Statamic picks up the change. There is no database server to install, patch or back up separately.
The Git Workflow
Because content is files, it fits naturally into Git. Developers commit content changes next to template changes. A new landing page can go through a branch, a pull request and a review before it reaches production.
Rolling back a bad edit becomes a normal Git revert. On Pro, Statamic’s Git automation can commit and push changes that editors make in the Control Panel, so their work lands in the same history.
When You Outgrow Flat Files
Flat files are not the right fit for every site. A site with tens of thousands of entries, or content written by many users at once, can strain a file-based setup. For that case, the official Eloquent driver moves entries, collections, assets and other data into a database.
The trade-off is simple. You gain database scale, but you lose the “content in Git” workflow for whatever you move. Treat the database as an option you reach for, not the starting point.
Key Features of Statamic
Statamic packs a lot into the Core edition. These are the features that shape daily work.
1. The Control Panel
The Control Panel lives at /cp on your site. Editors create entries, upload images, manage navigation and read form submissions there. It includes Live Preview, so editors see a page as visitors will before they publish.
Statamic 6 rebuilt the Control Panel on Vue 3. It added a command palette, two-factor authentication and passkeys for sign-in.
2. Collections, Blueprints and Fieldsets
These three ideas form the content model:
- Collections group similar entries, such as pages, blog posts, case studies or team members.
- Blueprints define the fields an entry has, such as a title, a hero image and a summary.
- Fieldsets are reusable groups of fields you can drop into many blueprints, such as an SEO block.
You build blueprints in the Control Panel with a drag-and-drop editor, and Statamic saves them as YAML files. Taxonomies, globals and navigation trees round out the model.
3. Flexible Fieldtypes
Statamic ships with dozens of fieldtypes. Bard is a rich-text editor that can hold custom blocks, and Replicator lets editors stack page sections in any order.
4. Antlers and Blade Templates
Statamic supports two template languages. Antlers is its own tag-based language, built for short content loops like “list the last five posts”. Blade is Laravel’s standard template engine.
If you only remember one line: Laravel developers can skip Antlers entirely and still use every Statamic feature from Blade.
5. Built-In Asset Management
Upload, browse and organize images and files from the Control Panel. Assets can carry their own fields, such as alt text.
6. Static Caching and Static Site Generation
Statamic offers two static caching strategies. Half measure stores rendered pages in Laravel’s cache, so PHP returns them without rebuilding the page. Full measure writes plain HTML files that the web server sends before PHP even runs.
For sites that never change between deploys, the official SSG package exports the whole site as static HTML. You can then upload it to any static host.
Statamic Core vs Pro: What You Get for Free
Core is free and covers a surprising amount, including a form builder. Pro adds what teams and larger sites need.
| Feature | Core (free) | Pro (paid, per site) |
|---|---|---|
| Control Panel administrators | One | Unlimited users with roles and permissions |
| Content forms | One | Unlimited |
| Collections, blueprints, assets | ✅ | ✅ |
| Static caching and Antlers/Blade | ✅ | ✅ |
| Revisions | ❌ | ✅ |
| REST and GraphQL APIs | ❌ | ✅ |
| Multi-site | ❌ | ✅ |
| Git automation | ❌ | ✅ |
On price, Pro is a paid license per site. Confirm the current price and renewal terms on statamic.com/pricing before you quote a client.
Statamic Versions: v5 vs v6
Statamic 5 launched in May 2024. Its bug fixes ended in March 2026, and security fixes run until December 2026. If you still run v5, plan the upgrade now.
Statamic 6 launched on January 28, 2026. The headline change is the rebuilt Control Panel. It works with Laravel 12 and 13, so read the release notes before each upgrade.
Who Should Use Statamic? Top Use Cases
Marketing and Brochure Sites
A company site with a few dozen pages is the sweet spot: fast pages, a friendly editor and no database to patch.
Agency Client Sites
Developers own the code and content model in Git. Clients edit content in the Control Panel without touching templates.
Laravel Teams Adding Content
Already running a Laravel app? Statamic installs as a package, so you can add a blog, docs or marketing pages to the same codebase.
Documentation and Content That Needs Review
Docs teams can treat content like code: write in Markdown, review in a pull request and publish on merge.
Trying a CMS Before Committing
Core is free for one administrator. You can build a full site and decide later whether Pro features are worth paying for.
Statamic vs WordPress vs Craft CMS vs Kirby
Every one of these platforms is a sound choice for the right team. The differences come down to storage, stack and licensing.
| Statamic | WordPress | Craft CMS | Kirby | |
|---|---|---|---|---|
| Content storage | Flat files (database optional) | MySQL or MariaDB database | MySQL or PostgreSQL database | Flat files |
| Built on | Laravel | Its own PHP core | Yii (PHP) | Its own PHP core |
| Templating | Antlers or Blade | PHP themes and blocks | Twig | PHP templates |
| Free option | Core: one admin, one form | Free and open source | Solo edition: one admin | Free to try locally |
| Paid license | Pro, per site | None (plugins may cost) | Team or Pro, per project | Required per site |
| Best for | Laravel teams, Git workflows | Blogs, stores, plugin-heavy sites | Complex content models | Small designer-built sites |
WordPress has earned its reach. Its plugin and theme catalog is far larger than any other option here, and it is free for any number of users. Statamic wins when you want content in Git and a codebase without a database. Our WordPress hosting page covers the other side if you stay there.
Craft CMS is the closest match in spirit: an editor-friendly, developer-first CMS with a free single-admin edition. The main difference is storage. Craft keeps content in a database, while Statamic defaults to files and adds a database only if you ask.
Kirby is also flat-file and much loved by designers. It does not run on Laravel, and production sites need a paid license. Statamic suits teams that already live in the Laravel ecosystem. For another flat-file option, see Grav hosting on xCloud.
How to Run Statamic: DIY vs One-Click
Statamic is light. The xCloud template lists 1 GB of RAM, 1 CPU core and 5 GB of disk as a conservative floor for a small site. Traffic and image uploads push that number up.
The DIY Path
Install PHP, Composer and a web server. Create the Laravel app, add Statamic, set an APP_KEY, point a domain at the server and issue an SSL certificate. Then set up backups that capture the content files and the app key together.
None of it is hard for a Laravel developer. The catch worth knowing: your time is the hidden cost. Security updates, certificate renewals and the occasional 3 a.m. “why is the disk full” check are all yours. Our guide to self-managed vs managed hosting breaks down that trade-off.
The Managed One-Click Path
A one-click deploy handles the server, the domain and HTTPS, so you start in the Control Panel instead of a terminal. You trade some low-level control for fewer chores.
If you want Statamic inside your own Laravel project instead, treat it like any Laravel app. Our Laravel hosting page and the guide to deploy Laravel applications cover that route.
Pros and Cons of Statamic
| Pros | Cons |
|---|---|
| ✅ No database needed by default | ❌ Not open source; license has conditions |
| ✅ Content and code in one Git repository | ❌ Core is limited to one admin and one form |
| ✅ Polished Control Panel for editors | ❌ Smaller add-on catalog than WordPress |
| ✅ Antlers or Blade, on a real Laravel app | ❌ Very large or busy sites may need the Eloquent driver |
| ✅ Static caching and a static site export | ❌ Team features need a paid Pro license per site |
Launch Statamic on xCloud in a Few Clicks
xCloud lists Statamic in its One Click Apps catalog. The template runs Statamic Core 6.33.0 in one container with no separate database. Your content, users, blueprints, config and assets live on one persistent data volume.
Here is how the deploy works:
- From the xCloud dashboard, click New Site, open One Click Apps and select Statamic.
- Choose Deploy on a new server or Select an existing server that runs NGINX. For an existing server, the wizard recommends at least 4 GB of RAM, 1 vCPU and 5 GB of disk.
- Enter a Site Title and pick a domain mode. Demo Site gives you a temporary
x-cloud.appsubdomain, while Go Live uses your own domain. - Enter the Administrator email and click Next to start provisioning.
- When the site is ready, open
/cpover HTTPS and sign in with the generated administrator account.
xCloud generates the first administrator password and a stable APP_KEY, and serves the site over HTTPS on your domain. The Cloud VPS plans also include automatic server backups, security updates and more than 30 server locations. A 6 GB Cloud VPS starts at $24.99 per month.
Here is our honest take on the limits. The template ships Core only, so Pro features stay off. It logs email instead of sending it, so password resets and form notifications need your own SMTP setup. The image is pinned to one version and does not upgrade itself, and it is independently maintained packaging rather than an official Statamic image.
Back up the whole data volume together with your APP_KEY. 👉 See how backups work in xCloud.
Ready to publish without building the server first? Deploy Statamic hosting on xCloud and sign in to your Control Panel in minutes.
👉 Follow the step-by-step guide to deploy Statamic with xCloud.
Pick Statamic If Your Content Belongs in Git
Statamic answers one question well: what if a CMS treated content like code? You get files in Git, a Laravel codebase and an editor that clients enjoy. In return, you accept a commercial license and a free tier sized for one administrator.
This week, spin up a Demo Site and build one collection with a blueprint. Write a page in the Control Panel, then open the file it created. If that workflow clicks, Statamic is likely your CMS.
If you have found this blog helpful, feel free to subscribe to our blogs for valuable tutorials, guides, knowledge and tips on web hosting and server management. You can also join our Facebook community to share insights and engage in discussions.
Frequently asked questions
What is Statamic used for?
Statamic is used to build and manage websites such as marketing sites, documentation, blogs and agency client sites. Editors work in a visual Control Panel, while developers shape the content model and templates in a Laravel codebase. Content is saved as files by default, so it can live in Git next to the code.
Is Statamic free?
Statamic Core is free for one administrator and one content form. Features such as multiple users and roles, revisions, the REST and GraphQL APIs, multi-site and Git automation need a paid Pro license. Pro is licensed per site, so check statamic.com/pricing for the current price before you buy.
Is Statamic open source?
No. The source code is public on GitHub, but its license is a commercial one with conditions, such as one production environment per licensed copy. Read the LICENSE file before you rely on it for a project.
Does Statamic need a database?
No. By default, entries, users and settings are saved as Markdown and YAML files on disk. If a site outgrows flat files, the official Eloquent driver moves content into a database that Laravel supports.
Is Statamic better than WordPress?
It depends on the project. Statamic suits developers who want content in Git, a Laravel codebase and fewer moving parts. WordPress wins when you need a very large plugin catalog, a large hiring pool or a free multi-user setup.
I already know Laravel. Do I need to learn Antlers?
No. Statamic supports Laravel Blade templates as well as its own Antlers language. Many Laravel developers start with Blade and pick up Antlers later for quick content loops.
How much RAM does Statamic need?
Not much for a small site. The xCloud template lists 1 GB of RAM, 1 CPU core and 5 GB of disk as a conservative floor. For an existing server, the xCloud wizard recommends at least 4 GB of RAM so the site has room to grow.