Statamic at a glance
- Type
- Laravel CMS, with a free Solo edition
- Built with
- PHP and Laravel, content in files or a database
- Hosting
- Self-hosted, on any Laravel-ready host
- Best for
- Marketing sites built by Laravel developers
How Statamic works
Content in Statamic lives in collections of entries, each shaped by a blueprint of fields. Bard fields mix rich text with sets of blocks, Replicator fields hold repeating blocks, taxonomies group entries, and navigation, globals and assets in containers are built in. Content is saved as Markdown and YAML files, or in a database for larger sites.
What Statamic does well
Content in Git
Flat files keep content versioned with the code, with no database needed.
Built on Laravel
Developers extend it with the framework they already know.
Blocks inside rich text
Bard lets editors drop sets of blocks between paragraphs.
Fast by default
Static caching serves pages without running PHP for each visit.
What to weigh before you move
No CMS fits every team. These are the points that come up most when people plan to leave Statamic, or to make it their next home.
- Pro for teams and APIsThe free Solo edition has one user; Pro adds users, roles and the content APIs.
- Read-only APIsIts REST and GraphQL APIs read content; writing in needs files or an add-on.
- Large sites need careVery large flat-file sites usually move to the database driver.
Who uses Statamic
Laravel developers and agencies use Statamic for marketing sites, blogs and documentation, often for clients who want simple editing without a database to look after. Some sites outgrow flat files or move to another platform as their teams grow.
What a Statamic migration covers
When the connector is ready, Reloque will scan your Statamic content first and map each field before anything moves. These are the kinds of content a migration has to account for.
- Collections and entries
- Blueprints and fields
- Bard and Replicator sets
- Taxonomies
- Assets
- Navigation
- Globals
- Users
Planning a move from Statamic
A Statamic move centres on the collections, their blueprints and the sets inside Bard and Replicator fields.
- List the collections, their blueprints and the taxonomies each one uses
- Note Bard and Replicator sets, and fields from add-ons
- Check whether content sits in files or a database, and which asset containers it uses
- Keep the old addresses, since each collection sets its own route, and plan redirects
Where Statamic content could go
The Statamic connector is planned, and connectors are built in the order people ask for them. These ten work today, in every direction, and Statamic will join them both ways.
Moving to Statamic
Moving to Statamic means creating a collection and blueprint for each content type, then filling the entries, terms and assets.
Statamic questions
What is Statamic?
Statamic is a CMS built on Laravel that keeps content in plain files by default, so a site's content can live in Git alongside its code. Blueprints shape the content, and Antlers or Blade templates show it.
Who uses Statamic?
Laravel developers and agencies use Statamic for marketing sites, blogs and documentation, often for clients who want simple editing without a database to look after. Some sites outgrow flat files or move to another platform as their teams grow.
What content can be migrated to or from Statamic?
A migration with Statamic typically covers collections and their entries, blueprints and fields, Bard and Replicator sets, taxonomies, assets, navigation, globals and users. Reloque scans your site first and shows what it found before anything moves.
What should I prepare before a Statamic migration?
A Statamic move centres on the collections, their blueprints and the sets inside Bard and Replicator fields. Four checks help most: (1) list the collections, their blueprints and the taxonomies each one uses; (2) note Bard and Replicator sets, and fields from add-ons; (3) check whether content sits in files or a database, and which asset containers it uses; (4) keep the old addresses, since each collection sets its own route, and plan redirects.
Can Reloque migrate Statamic today?
Not yet. The Statamic connector is planned, in both directions with every CMS Reloque supports. Reloque moves WordPress, Payload, Strapi, Ghost, Umbraco, Drupal, Contentful, Sanity, Storyblok and Webflow today. Tell us your route when you start a free assessment.