The DXP Scorecard logo
Independent Platform Evaluation
Scored on implementation experience
Not vendor briefings
← Dashboard
Statamic logo

Statamic

Traditional CMS
Visit Website ↗
Overall Capability
50/ 100
#41of 47overall#11of 14Traditional CMS

Statamic is a self-hosted CMS built on Laravel that stores content as Markdown and YAML files in your own Git repository, with an optional database driver.

Head-to-Head

Suite Capability50 : 55
Cost Efficiency70 : 70
Build Simplicity66 : 68
Operational Ease56 : 59

Craft CMS is Statamic's closest rival: both are PHP CMSs for agency-built marketing sites with flexible content models and perpetual licences, and Craft is moving to Laravel. Statamic wins on flat-file Git storage, a free commercial Core edition and real-time collaborative editing. Craft has the larger, longer-established community and enterprise track record.

Full Comparison →
Suite Capability50 : 56
Cost Efficiency70 : 76
Build Simplicity66 : 63
Operational Ease56 : 53

WordPress has a vastly larger talent pool, plugin library and block-based visual editor. Statamic offers a cleaner structured content model, Git-based content and a smaller, Laravel-based codebase that is easier to extend properly. Pick WordPress for ecosystem reach and Statamic for developer control and maintainability.

Full Comparison →
Suite Capability50 : 60
Cost Efficiency70 : 73
Build Simplicity66 : 54
Operational Ease56 : 50

Drupal brings content moderation workflows, granular access control and deep multi-site and intranet capability. Statamic is much simpler to learn, quicker to get running and cheaper to staff with a single Laravel developer. Choose Drupal for complex governance and Statamic for lean marketing sites.

Full Comparison →
Suite Capability50 : 54
Cost Efficiency70 : 79
Build Simplicity66 : 65
Operational Ease56 : 47

Payload CMS suits TypeScript and Next.js teams who want a code-first headless CMS with typed schemas and a write API. Statamic suits PHP and Laravel teams who want a full website CMS with templating, first-party SEO tooling and an addon marketplace. The choice usually follows the team's language.

Full Comparison →
Compare Statamic against any of 47 platforms →
Platform Alternatives · Analyst write-up
Looking for alternatives to Statamic?

Our analysts rate 8 platforms as replacements, with a recommendation for who should move and who should stay. Ratings updated Nov 5, 2026.

Read the write-up →

Use-Case Fit

Top Fit
Marketing
42#39 of 47
Commerce
36#28 of 47
Intranet
25#39 of 47
Multi-Brand
38#39 of 47
Ideal For
  • 88Laravel development shops and agencies building marketing sites
  • 82Small to mid-size organizations wanting a polished CMS at low cost
  • 85Developer teams that want content in Git
  • 72Multilingual sites that are variations of one brand
Look Elsewhere If
  • 20Enterprises that need certified vendors and accessibility documentation
  • 22Marketing teams wanting personalization and experimentation built in
  • 18Organizations building an employee intranet
  • 35JavaScript-only teams wanting a headless SaaS CMS

Strengths & Weaknesses

Strengths
  • +
    Content lives as files in your own Git repository

    By default every entry, blueprint and setting is a Markdown or YAML file versioned with the code, and Pro can commit each Control Panel change automatically. Sites on the database driver get first-party commands to export everything back to files. The whole CMS runs locally as a normal Laravel app, so developers work with real content and ship through ordinary Git pipelines. Leaving Statamic means rebuilding templates, not rescuing content.

    77.7
  • +
    Flexible, well-designed content modeling

    Blueprints and fieldsets offer more than 40 field types, conditional fields and reusable field groups, all stored as YAML in Git. Replicator and Bard sets let editors compose pages from typed blocks with unlimited nesting, and Bard stores rich text as portable structured JSON. Any Laravel validation rule can be applied per field. Content architects get structure without fighting the tool.

    78.5
  • +
    Low, published pricing you own outright

    Core is free for commercial work, and Pro costs $349 per production site with unlimited development sites and $99 a year for updates after the first year. Nothing is metered: no API, user, entry or bandwidth limits. Agencies running many sites can switch to a Platform plan at $12 per site per month, falling to $3.50 at volume. Lapsing the update plan stops updates, not the site.

    75.3
  • +
    Built on Laravel, so it extends without limits

    Statamic is a Laravel package, so any Laravel developer can work on it and use Blade templates instead of Statamic's own Antlers language. Addons can add field types, Control Panel pages, widgets, bulk actions and event listeners, and every Laravel package is available too. The Marketplace lists around 500 addons. One capable developer can build and ship a production site.

    72
  • +
    Fast, transparent release cadence

    Since Statamic 6 shipped in January 2026 the team has released a feature version almost every week, reaching 6.39 by late October, while still patching version 5. A public roadmap shows what is in progress, planned and shipped, linked to community ideas on GitHub. Release notes, a changelog and upgrade guides accompany every version.

    73.5
  • +
    Thorough first-party SEO tooling

    SEO Pro, Statamic's own paid addon, covers meta and Open Graph defaults, live Google and social previews, JSON-LD structured data and multi-site sitemaps. It also adds a redirects manager with automatic redirects on slug changes, 404 tracking and graded site reports. It is included in Platform plans.

    70
Weaknesses
  • −
    No personalization, segmentation or recommendations

    Statamic has no segment builder, visitor profiles, content variants or recommendation engine. Targeting means template conditionals on the logged-in user or user group, written by developers. A/B testing exists only as small third-party addons without significance reporting. Teams that need audience targeting must buy and integrate an external engine.

    18
  • −
    No compliance certifications or accessibility documentation

    Statamic, Inc. holds no SOC 2 or ISO 27001 certification, offers no HIPAA business associate agreement and publishes no data processing agreement. There is no VPAT (Voluntary Product Accessibility Template) or accessibility statement for the Control Panel. Because the software is self-hosted, every control comes from the buyer's own hosting and processes, which leaves procurement teams with little to file.

    24.6
  • −
    No editorial approval workflow

    Editors can save a working copy and roles can be denied the publish permission, but there are no custom workflow states, review routing, notifications or approval history. There are also no review dates or stale-content flags. Workflows remain a planned roadmap item, so regulated or multi-reviewer teams must build approvals themselves.

    28.3
  • −
    AI features depend entirely on third-party addons

    Statamic ships no first-party AI writing, auditing or governance. Addons such as Ghostwriter and Magic Actions add drafting, alt text and metadata with your own model keys, but there is no shared AI audit trail, usage reporting or policy layer. Each addon is configured and billed separately.

    22
  • −
    Heavy 2026 security patching on a yearly upgrade cycle

    The core package received more than 40 security advisories in 2026, including account takeover, remote code execution and an unauthenticated file write fixed in October. Fixes ship quickly to both supported versions, but the self-hosting team must apply every one. Each major version gets only about 18 months of security fixes, so an upgrade with new PHP and Laravel minimums comes every year.

    50
  • −
    You run all the infrastructure

    There is no vendor cloud, CDN, uptime SLA or status page. Hosting, CDN purging, monitoring and backups are the buyer's job, though Laravel tools like Forge, Ploi and Pulse make that manageable. Teams without in-house ops capacity will need a hosting partner.

    37.3

Deep Dive

Analyst Editorial

The analyst view on Statamic

DXP Scorecard Analyst Team
Statamic is a self-hosted CMS built on Laravel that stores content as Markdown and YAML files in your own Git repository, with an optional database driver. It offers a strong content model, low and transparent licence pricing and very little lock-in. It is not a DXP: personalization, experimentation, approval workflows and AI all come from third-party addons or custom code. It fits Laravel teams building marketing sites far better than enterprises with compliance checklists.
1Core Content Management62▼
Content Modeling
1.1.1
Content type flexibility
80

Blueprints and fieldsets define collections, taxonomies, globals, assets and users with dozens of first-party fieldtypes (Bard, Replicator, Grid, Group, Dictionary, Entries, Terms, Link, Code, Color, Info and more), conditional fields and reusable fieldset imports. Blueprints are YAML files kept in Git, so schema is genuinely versioned and deployable as code, and custom fieldtypes are Vue plus PHP. Not higher because there is no typed schema DSL or true union field outside Replicator sets.

1.1.2
Content relationships
66

Entries, Terms, Users and Assets fieldtypes create many-to-many references that can span several collections, and taxonomy terms resolve their related entries automatically. Not higher because relationships are stored one way as IDs on the source entry; reverse lookups need a query on the target side or an addon, and there are no declared inverse fields resolvable in one GraphQL selection.

1.1.3
Structured content & composition
80

Replicator and Bard sets let editors compose pages from typed blocks, sets can contain any fieldtype including further Replicators and Grids for unlimited nesting, and Statamic 6 added image previews when choosing sets. Bard stores rich text with embedded sets as a ProseMirror JSON document, a portable structured format. Not higher because there is no slot or region model and deep nesting has known Control Panel performance costs that the team is still working on.

1.1.4
Content validation
76

Any Laravel validation rule can be set per field in the blueprint UI or YAML (regex, min/max, dates, mimes, size, in), custom Rule classes are supported, cross-field rules work through required_if and the {this} placeholder inside Grid and Replicator rows, and UniqueEntryValue and UniqueTermValue rules ship in core. Not higher because the content APIs are read-only so there is no API-write validation path to speak of, and complex rules need PHP.

1.1.5
Versioning, history & rollback
58

With Pro and revisions enabled per collection, published entries get a separate working copy, every publish and unpublish creates a revision with author, timestamp and a note, and the history view previews and restores any revision; flat-file content in Git adds full repository history. Not higher because there is no field-level diff or compare view, no branching or releases, no trash for deleted entries, and revisions are off by default and Pro-only.

1.1.6
Taxonomy & metadata management
60

Taxonomies are first-class: each has its own blueprint, terms have URLs and fields, any taxonomy can be attached to any collection, terms are localizable and exposed through both the REST and GraphQL APIs, and per-taxonomy permissions control who can create terms. Not higher because taxonomies are flat; hierarchical taxonomies are still in progress on the roadmap, and there are no synonyms or bulk reclassification tools.

Authoring, Collaboration & Governance
1.2.1
Preview & in-context editing
62

Live Preview renders unsaved changes in the real templates beside the publish form with device sizes, multiple preview targets per collection and hot-reload in Statamic 6, and since v6.38 (October 2026) it also works while an entry is still being created; for headless frontends a token is appended so GraphQL or REST returns the draft, and postMessage events allow live updates without refresh. Not higher because there is no click-to-edit overlay on the frontend and no official preview SDK for Next.js or Nuxt, so headless preview is hand wired.

1.2.2
Rich text & embedded content
78

Bard is a Tiptap and ProseMirror editor with configurable buttons, links to entries and assets, embedded sets of any fields inline in the text, custom Tiptap extensions and marks, and output stored as a ProseMirror JSON document that can be rendered to HTML or processed elsewhere; a Markdown fieldtype exists for writers who prefer it. Not higher because rendering structured output outside PHP needs your own ProseMirror renderer and paste cleanup from Word is basic.

1.2.3
Media library & image handling
70

Asset containers on local disk or S3-compatible storage carry blueprints for alt text and metadata, a focal point and zoom picker, and native image cropping (February 2026); Glide performs on-the-fly resize, crop, fit and format conversion with presets, and hybrid Glide caching shipped September 2026. Not higher because there is no built-in asset usage tracking, asset metadata cannot yet vary per site, and transforms run on your own server.

1.2.4
Real-time collaboration
60

The free first-party Collaboration addon shows presence avatars when several people open the same entry, locks a field while someone has it focused and syncs field values to everyone in real time over Laravel Reverb or Pusher. Not higher because there is no commenting, mentions or suggestion mode, and it requires running a WebSockets server; cursors, chat and comments are only planned for Collaboration 3.0.

1.2.5
Editorial workflow & approvals
32

Natively an editor can save a working copy on a published entry and roles can be denied the publish permission, which separates authoring from going live. Not higher because there are no custom workflow states, assignments, review routing, notifications or approval audit trail; Workflows remain a planned roadmap item after Statamic 6.

1.2.6
Scheduling, releases & publishing control
52

Dated collections can treat future dates as private, so an entry publishes at its date and time, entries get computed scheduled and expired statuses, and Statamic 6 adds a collection calendar view with better timezone support. Not higher because expiry is a collection-wide past-date behavior rather than a per-entry unpublish date, there are no release bundles or scheduled changes to a live entry, and cache refresh at publish time needs the Laravel scheduler running.

1.2.7
Localization model
70

Multi-site (Pro) defines sites per locale on domains, subdomains or paths, managed in the Control Panel since Statamic 5; each field is marked localizable or not, and a localized entry inherits every field it does not override from its origin entry, giving field-level localization with fallback. Per-site permissions, locale-aware text direction, per-site Live Preview and site-filtered API queries are included. Not higher because fallback follows the origin entry rather than a configurable locale chain and asset metadata is not yet localizable.

1.2.8
Roles, permissions & content governance
50

Pro adds custom roles and user groups with permissions per collection (view, edit, create, publish, delete, others' entries), per taxonomy, asset container, global set, navigation and site, plus impersonation for testing; Statamic 6 added core two-factor authentication, passkeys and elevated sessions, and OAuth login comes through Laravel Socialite. Not higher because there are no role-based field permissions, SAML SSO needs a third-party package and there is no SCIM provisioning.

Content Delivery
1.3.1
API delivery model
72

Both a REST Content API and a first-party GraphQL API cover entries, collections, trees, taxonomies, terms, assets, globals, navs and users, with opt-in filters, multi-field sorting, field selection, pagination, per-site queries, GraphiQL in the Control Panel and REST authentication added in Statamic 6; the REST API became self-describing in September 2026. Not higher because both APIs are read-only for content with no management API or GraphQL mutations, and filtering must be allow-listed per resource.

1.3.2
CDN and edge delivery
40

Statamic has no vendor-run hosting or CDN; delivery speed comes from built-in half and full static caching with invalidation rules, background re-caching in Statamic 6 and Glide image caching, which can sit behind any CDN the team configures. Not higher because CDN setup and purge integration are the buyer's job with no first-party edge or purge service.

1.3.3
Webhooks & events
40

Core dispatches a broad set of Laravel events (EntrySaving, EntrySaved, EntryDeleted, TermSaved, AssetUploaded, BlueprintSaved and more) that developers can listen to and queue, and Marketplace addons add configurable outbound webhooks with retries and auth headers. Not higher because there is no native webhook UI, no signed payloads in core and no dedicated publish event, so every integration is PHP code or a third-party addon.

1.3.4
Multi-channel output
58

Statamic can run headless or hybrid through REST and GraphQL, and rich text is stored as ProseMirror JSON, so non-web channels are not forced to parse HTML. Not higher because it is a coupled Laravel CMS first, with no official client SDKs in any language and API output shaped around the web templating model.

2Additional Platform Capabilities (DXP Features)44▼
Personalization & Experimentation
2.1.1
Audience segmentation & customer data
20

Statamic has no segment builder, visitor profiles or CDP connector; the only audience concept is front-end user accounts with groups and roles, which developers can branch on in Antlers or Blade. No Segment, mParticle or Tealium addon turned up on the Marketplace. Not higher because any behavioral segmentation means building it in Laravel or running an external engine end to end.

2.1.2
Content personalization
28

There are no content variants per audience and no audience preview in the Control Panel; personalization is template conditionals on the authenticated user, group or request data, or an external decision engine wired in by developers. Not higher because nothing ships or is sold as a personalization feature.

2.1.3
Experimentation (A/B, MVT)
40

Two Marketplace addons add server-side testing: Thoughtco's AB Tester (paid) runs experiments on entries, and Frank Lambregts' Statamic A/B Testing (1.0 stable August 2026) adds sticky weighted variants, conversion tracking and a results view under Tools in the Control Panel. Not higher because nothing comes from Statamic itself and neither addon offers significance reporting comparable to a dedicated tool.

2.1.4
Recommendations
12

No recommendation engine exists in core or as a first-party addon; related content is curated by editors with the Entries fieldtype or queried by taxonomy in templates. Scored in the manual-curation band.

Search & Discovery
2.2.1
Site search & discovery
62

Core ships a search system with multiple configurable indexes, field selection and a search results tag, using the local Comb driver (JSON indexes) or the bundled Algolia driver with index sync on save; Rad Pack drivers add Meilisearch and Typesense. Not higher because the local driver has no faceting, merchandising or search analytics, and richer relevance tuning lives in the external service.

Commerce
2.3.1
Native commerce
42

Statamic has no commerce in core; carts, checkout, orders, discounts and payment gateways come from Duncan McClean's Cargo addon, which replaced Simple Commerce (Simple Commerce 8 supports Statamic 6 but will not be updated for Statamic 7). Scored as an integration because it is a separately sold Marketplace addon rather than part of the product, and it suits small to mid-size stores.

2.3.2
Commerce platform integration
52

The Rad Pack Shopify addon (v7.12.1, September 2026) imports products, variants and images into Statamic entries and keeps stock and products in sync through Shopify webhooks, with Antlers tags for the storefront. Not higher because there are no maintained connectors for commercetools, BigCommerce, Salesforce Commerce Cloud or SAP Commerce.

Analytics & Insights
2.4.1
Built-in experience analytics
25

Core has no content or page performance analytics; the Control Panel dashboard shows widgets such as recent entries and form submissions, and SEO Pro adds SEO report scores and recent 404s. Engagement data only appears through third-party GA4 widget addons, so built-in analytics sits in the operational band.

2.4.2
Analytics & tag integration
48

Analytics tags are added in templates, and third-party addons such as ISAPP's GA4 widgets and the GA Dashboard Widget pull GA4 data into the Control Panel. Not higher because Statamic maintains no analytics integration of its own and there are no event helpers for Segment, Adobe Analytics or Amplitude.

Multi-site & Global Operations
2.5.1
Multi-site management
60

Statamic Pro's multi-site runs several sites on domains, subdomains or subdirectories from one install, with localized entries that inherit from an origin entry and per-site collections and permissions. Not higher because the vendor positions it for variations of one site and says it is not intended for multi-tenant setups, so truly independent sites usually mean separate installs.

2.5.3
Translation management
40

Editors translate inside the Control Panel by localizing entries side by side with the origin, and Marketplace addons add machine translation: Magic Translator (October 2026, LLMs and DeepL, bulk and staleness detection) and Apps with love's DeepL and Google one-click translation. Not higher because there are no Phrase, Smartling, Lokalise or Crowdin connectors and no translation memory or batch export to a TMS.

2.5.4
Multi-brand governance
25

Beyond per-site permissions inside one multi-site install there is no brand-level governance: no shared component library with brand overrides, cross-brand approvals or policy enforcement. Multiple brands typically run as separate installs sharing a code base built by the agency.

Digital Asset Management
2.6.1
Enterprise DAM
40

Asset containers on local disk or S3 carry blueprint-defined metadata, folders, focal points and permissions, but there are no rights or expiry fields, approvals, usage tracking or versioning. Enterprise DAM comes only through Marketplace or community addons such as Fairu and 21st Digital's Cloudinary addon, and no Bynder or Aprimo connector was found.

2.6.3
Video & rich media
30

Video files can be uploaded as assets and the core Video fieldtype embeds YouTube, Vimeo and, since Statamic 6.38 (October 2026), Cloudflare Stream, which brings adaptive streaming from Cloudflare's paid service. Statamic itself does no transcoding, captions or player, so video is still hosted outside the product and embedded.

Page Building & Site Delivery
2.7.1
Visual page builder & layout composition
50

Developers build page builders from Replicator and Bard sets with set previews and fly-out pickers, and editors see the result in Live Preview, so marketers assemble pages from an approved block palette. Statamic 6 ships no visual or drag-on-canvas editing; click-to-edit and on-page editing come only from third-party addons such as Fine Builder. Scored in the structured block editor band.

2.7.5
Managed site delivery & front-end hosting
50

Statamic renders the full site with Antlers or Blade templates, routing and static caching or full static generation, but the vendor runs no hosting; the customer deploys to Laravel Forge, Vapor, Ploi or any PHP host following the deployment docs. Scored in the renders natively, customer hosts band.

Marketing & Engagement
2.8.1
Forms & data capture
52

Core forms are defined by blueprints with validation rules, conditional fields, file uploads, honeypot spam protection, stored submissions with CSV and JSON export, email notifications and a Control Panel area for reports. Not higher because there is no multi-step builder, progressive profiling or lead routing, and push to other systems needs events or addons.

2.8.2
Email marketing & ESP integration
42

The Rad Pack Mailchimp addon subscribes users on form submission or registration with interests and marketing permissions, and other Marketplace addons connect forms to Mailchimp and similar services. Not higher because there is no content push or triggered sends from CMS events and no HubSpot, Marketo or Salesforce Marketing Cloud connector from Statamic.

2.8.3
Marketing automation
30

There is no marketing automation in Statamic; a third-party addon suite for Statamic 6 adds CRM, campaigns and automations, but it is a small independent offering. Most sites hand leads to an external automation tool through form addons or custom code.

2.8.5
SEO tooling
72

SEO Pro, Statamic's own paid addon, covers cascading meta and Open Graph, live Google and social previews, JSON-LD structured data with custom types, sitemaps with hreflang across multi-site, a redirects manager with wildcards and automatic redirects on slug changes, 404 tracking, robots controls, GraphQL fields and graded site reports. Close to the add-on ceiling; not higher only because it is a separate purchase rather than core.

2.8.6
AI search visibility
42

Mity Digital's llms.txt for Statamic addon generates a curated llms.txt, SEO Pro handles robots controls and JSON-LD, and Statamic adopted llms.txt and AI crawler rules for its own documentation in August 2026. Not higher because there are no per-page Markdown endpoints, per-bot crawler controls or AI citation reporting in the product.

Platform Services
2.9.1
App marketplace & connectors
66

The Statamic Marketplace lists around 500 addons plus starter kits from the core team, the Rad Pack and third parties, installed with one Composer command and licensed per site, and every Laravel package is also available. Not higher because many addons are small single-developer projects and first-party integrations with enterprise systems are few.

2.9.5
Customer identity & authenticated experiences
60

Core supports front-end users with login, registration and password reset tags, content protection per page, collection or site using auth or password schemes, user groups and roles, and OAuth login through Laravel Socialite with 100+ community providers. Not higher because built-in protection checks only login rather than role, there is no portal or consent layer, and CIAM federation such as Auth0 or Azure AD B2C is custom Socialite wiring.

3Technical Architecture60▼
API & Integration
3.1.1
API design quality
66

Statamic ships a first-party read-only Content REST API and a read-only GraphQL API with GraphiQL inside the Control Panel, with opt-in per-resource filters (field:condition syntax), multi-field and nested sorting, and paginated responses with links and meta. Recent releases added self-describing ping and sites endpoints, collection and taxonomy metadata, a fields parameter and slug resolution. Not higher because both APIs are read-only (no write or mutation API), filtering must be allow-listed per resource, and both are Pro-licence features.

3.1.2
API performance
58

API responses are cached by default with automatic invalidation on content change and a pluggable cacher class, and full-measure static caching serves pre-rendered HTML straight from Nginx or Apache. Not higher because there is no vendor CDN or managed edge, no published throughput figures or rate limits, and real delivery performance depends entirely on how the customer hosts and caches the Laravel app.

3.1.3
SDK ecosystem
40

Statamic is itself a PHP/Laravel package, so server-side development uses its PHP facades and Laravel directly, but there are no official delivery SDKs for JavaScript, Python, .NET or mobile. Headless front ends consume the REST or GraphQL endpoints with generic clients or community packages. Not lower because the PHP API surface is rich and first-party; not higher because no official TypeScript client exists.

3.1.4
Integration marketplace
66

The Statamic Marketplace lists roughly 500 addons and starter kits from the core team, the Rad Pack and third parties, browsable inside the Control Panel, with paid licensing and checkout handled by Statamic. Any Composer package in the Laravel ecosystem can also be used. Not higher because most integrations are small third-party addons of varying maintenance, and there are few vendor-certified connectors for enterprise DAM, translation or commerce systems.

3.1.5
Extensibility model
82

Addons can register custom fieldtypes with Vue components, Control Panel navigation items, pages and dashboard widgets, bulk actions, Antlers tags and modifiers, event listeners, custom routes and controllers, and replace repositories (for example the Eloquent driver). Because Statamic runs inside a full Laravel app, server-side extension has no sandbox limits. Not higher because the extension surface requires PHP and Vue development and Statamic 6 forced addon authors to update for its redesigned Control Panel.

Security & Compliance
3.2.1
Authentication
68

Statamic 6 made two-factor authentication, passkeys and elevated sessions for sensitive actions core features for Control Panel and front-end users, and OAuth login is built in via Laravel Socialite with over 100 community providers. Not higher because there is no native SAML 2.0; enterprise SSO needs a Socialite provider or community addon, and API token management for the REST API is left to Laravel middleware.

3.2.2
Authorization model
66

Roles are named sets of granular permissions assigned to users or user groups, scoped per collection, taxonomy, navigation, global set, asset container and site, including permissions to edit or publish other authors' entries. Not higher because there are no field-level permissions and no arbitrary per-entry access rules without custom policies; super users bypass everything.

3.2.3
Compliance certifications
35

Statamic is licensed self-hosted software with no vendor-run cloud, so there is no SOC 2, ISO 27001 or HIPAA attestation from the vendor; compliance is inherited from whatever host and processes the customer chooses. Not lower because data residency is fully under customer control.

3.2.4
Security track record
48

Statamic handles disclosure well, with a clear SECURITY.md, private GitHub reporting, prompt patched releases on both the 6.x and still-maintained 5.x lines, and published GitHub advisories, but 2026 brought 43 advisories against the core package (1 critical, 13 high) versus one in 2025, including an account takeover via password reset link injection, remote code execution through Antlers-enabled Control Panel inputs, data destruction via unsafe method invocation, and an October unauthenticated path traversal allowing YAML file writes and user record overwrites. Not higher because the volume and severity of 2026 findings is heavy for a project this size and there is no paid bug bounty; not lower because fixes ship quickly and are clearly communicated, with no known mass exploitation.

Infrastructure & Reliability
3.3.1
Hosting model
70

Statamic runs anywhere Laravel runs (Forge, Vapor, Laravel Cloud, Ploi, any PHP host), with flat-file or database storage and full static site generation as further options, so private and regulated hosting is straightforward. Not higher because there is no vendor-managed hosting option at all, so every buyer must run their own infrastructure.

3.3.2
SLA and uptime
30

As self-hosted software there is no vendor uptime SLA or product status page; availability is whatever the customer's host provides. Not lower because static caching or static site generation make high availability achievable with commodity hosting.

3.3.3
Scalability architecture
55

Full-measure static caching and Redis-backed Stache handle high read traffic well, and the Eloquent driver moves content to a database for large entry counts and multi-server setups. Not higher because flat-file content complicates load-balanced deployments (files must be synchronised or edited on a single CMS server), large flat-file sites slow the Stache rebuild, and there are no documented scale limits or enterprise benchmarks.

3.3.4
Disaster recovery
48

Because content, blueprints and config are files in Git by default, and Pro's Git automation commits and pushes every Control Panel change, a full versioned off-site copy of the site exists as a side effect, and the Stache can be rebuilt from files at any time. Not higher because there is no vendor backup service, RTO/RPO, or failover; assets and database-driver installs need customer-run backups.

Developer Experience
3.4.1
Local development
85

The full CMS runs locally as a normal Laravel app (Herd, Valet, Sail, Docker), installed with the Statamic CLI and managed with php please commands, and with flat-file storage the local site carries real content without a database dump. Not higher only because headless JavaScript teams still need a PHP environment.

3.4.2
CI/CD integration
68

Blueprints, fieldsets, collections and config are YAML files versioned with the code, so schema changes flow through normal Git branches, pull requests and Laravel deploy pipelines (Forge, Envoyer, GitHub Actions), and Git automation can commit editor changes back to the repo. Not higher because there is no environment management or content sync tooling between staging and production, and mixing editor commits with developer branches needs care.

3.4.3
Documentation quality
76

statamic.dev is versioned (v5 and v6 sites), well written, searchable and full of copyable examples covering templating, the REST and GraphQL APIs, caching, extending and deployment, and the docs were redesigned alongside Statamic 6. Not higher because there is no interactive API playground outside the in-CP GraphiQL, and headless framework guides (Next.js, Nuxt, Astro) are thin.

3.4.4
TypeScript support
40

There is no official TypeScript SDK and no type generation from blueprints; headless teams can run generic GraphQL codegen against the schema. Not lower because the GraphQL schema is introspectable, which gives codegen tools something to work with.

4Platform Velocity & Health62▼
Release Cadence
4.1.1
Release frequency
82

Statamic 6 went stable on January 28, 2026 and has since shipped a feature minor roughly every week, moving from 6.12.0 in April to 6.39.0 on October 29. These releases carry real features: Laravel 13 support, content model discovery for headless tools in 6.31, hybrid Glide image caching, and Live Preview before the first save plus keyboard reordering in 6.36 to 6.38. Version 5 still gets security patches (5.74.7 on October 22). Not higher because Forms 2.0, the largest item on the roadmap, is still in progress after a preview in August.

4.1.2
Changelog quality
74

statamic.com hosts a paginated Release Notes page for every tagged core version, the repository keeps a per-version CHANGELOG.md, and each addon has its own release notes. Each major version comes with an upgrade guide; the 5-to-6 guide separates high-impact changes (Vue 3 Control Panel, UTC date handling, PHP 8.3 and Laravel 12 minimums) from changes that only affect addons. Monthly blog roundups explain the notable changes. Not higher because the release notes are raw lists rather than curated summaries, and there are no machine-readable migration manifests.

4.1.3
Roadmap transparency
72

The public roadmap at statamic.com/roadmap is split into In Progress (Forms 2.0, Control Panel performance, groupable collections, multi-site improvements, hierarchical taxonomies), Planned (workflows, dashboard widgets, Collaboration 3.0) and a dated Shipped log. Each item links to the matching requests in the public statamic/ideas GitHub repository, where the community proposes and discusses features. Not higher because the roadmap gives no target dates and the ideas repository has no formal voting ranking.

4.1.4
Breaking change handling
66

Statamic follows semver, finished its v6 breaking changes before the beta, and says most sites upgrade from 5 to 6 by bumping the Composer constraint. It publishes a release and support policy: v5 active support ended March 31, 2026 and security support ends December 31, 2026, about 11 months after v6 shipped. Each major raises the PHP and Laravel floor (v6 needs PHP 8.3 and Laravel 12) and the Vue 3 move forced addon authors to rework Control Panel code. Not higher because the support window is far shorter than the multi-year LTS some peers offer.

Ecosystem & Community
4.2.1
Community size
53

The statamic/cms core repository has about 4.9K GitHub stars and 652 forks, with roughly 4.4M total Packagist downloads, and the vendor cites a Discord of about 5,300 developers. That sits just under the 5K-star band, with steady growth through 2026. It is a solid niche community that also draws on the much larger Laravel ecosystem, but it is small in absolute terms.

4.2.2
Community engagement
68

Engagement is strong for the community's size. Monthly release roundups credit outside contributors by name, the core team is active in Discord, and Marketplace submissions grew enough that the vendor introduced a review process in September. Statamic Summit, a dedicated multi-day conference with talks and workshops, is set for February 2027, following the earlier Flat Camp meetups. Not higher because the core team of about six people limits how much community input it can absorb.

4.2.3
Partner ecosystem
56

A formal paid partner program has freelancer and agency tiers, plus certified levels that require minimum project counts and client references. The public 'Hire a Statamic Expert' directory lists about 90 partners. Not higher because the roster is entirely boutique agencies and freelancers, with no global systems integrators and no certification exam for individual developers.

4.2.4
Third-party content
56

Laracasts carries a Statamic video course and Laravel News covers each major release and launch (v6, Sidecar), giving Statamic reach across the Laravel audience. Laravel Daily, independent instructors and Laracon talks add material, and community tooling such as the Antlers Toolbox for PhpStorm keeps appearing. Not higher because independent content is thin outside Laravel media and we found few recent dated third-party courses.

Market Signals
4.3.1
Talent availability
52

Statamic-specific job listings are sparse: a handful of aggregator results, a few roles on European developer boards, and some remote postings. Toptal and the partner directory offer freelance supply. Not lower because Statamic is a Laravel package, so any Laravel developer can become productive quickly, which makes the real talent pool far larger than the Statamic job count suggests.

4.3.2
Customer momentum
60

Momentum signals strengthened in 2026: a flagship site in the Laravel ecosystem moved to Statamic in August, the vendor raised Pro pricing to $349 per site from May without visible backlash, and it launched Sherpa, a free Mac app that takes non-developers from starter kit to deployed site without a terminal. Packagist downloads also grew by over a million this year. Not higher because Statamic publishes no customer counts, licence growth or revenue figures, and its independent review footprint is barely growing.

4.3.3
Funding and stability
52

Statamic is bootstrapped and independent, funded by Pro licences and renewals with no venture capital, and has shipped continuously since 2012. The founder reported over $1.5M in revenue as early as 2021, and the new opt-in automatic renewals for Pro and addons make that income more predictable. Not higher because the core team is about six people maintaining the CMS, its first-party addons, the Marketplace and new tools like Sherpa, a real key-person and capacity risk for enterprise buyers. Not lower because there are no layoffs or distress signals.

4.3.4
Competitive positioning
58

Statamic's positioning is clear and defensible: the Laravel-native CMS with flat-file Git storage by default and an optional database driver. Sidecar extends it to teams running static-site generators, and the vendor now argues directly against WordPress on total cost. Not higher because it has no Gartner or Forrester recognition, and Craft CMS porting to Laravel puts a well-known competitor directly into Statamic's niche.

4.3.5
Customer sentiment
50

G2 shows 4.8 out of 5 but from only 3 reviews, and TrustRadius shows 7.3 out of 10 from 7 ratings. Reviewers praise ease of use and predictable licensing compared with WordPress, but the volume is far below the 100-review threshold, so these ratings cannot support a confident score. Developer sentiment in Laravel channels is warm, which keeps it from falling lower.

5Total Cost of Ownership70▼
Licensing
5.1.1
Pricing transparency
76

Statamic publishes dollar figures for almost every way to buy it: Core free, Pro $349 per site with $99 a year for updates after the first year, a $1,500 Master License for five Pro sites plus 25% off further licences for a year, and a Platform plan at $12 per site per month with a published volume curve. The FAQ also states the 20% nonprofit and education discount and PPP pricing on request. Not higher because Enterprise, which carries SSO, audit logging and the support SLA, is contact-only with no indicative price.

5.1.2
Pricing model fit
79

A Pro licence is a one-time, per-production-site purchase with unlimited development sites, no metering of API calls, users, entries or bandwidth, and only an update fee after year one; the vendor's own Platform page says buyers 'still own those licenses in perpetuity'. Agencies and SaaS builders who run many sites get a usage-based alternative ($12 per site per month falling to $3.50) with no renewal fees, so the model scales both ways. Not higher because the licence is per site, so a portfolio multiplies the cost, and paid Marketplace addons are a separate line on top.

5.1.3
Feature gating
62

Core keeps the whole content model (all 40+ fieldtypes, unlimited collections and taxonomies, assets, Live Preview), and Statamic 6 made two-factor authentication and passkeys part of the product rather than a paid extra. Against that, the REST and GraphQL APIs, roles and permissions, revisions and drafts, and multi-site all require Pro, so any headless or multi-editor build is a paid build, though Pro is inexpensive. Not higher because SSO and audit logging sit only in the sales-gated Enterprise tier, the gating the rubric flags as problematic.

5.1.4
Contract flexibility
76

There is no subscription to escape on the standard path: Pro is bought per site and kept, it can be run free in Trial Mode for as long as a site stays on a non-public domain, purchases carry a 14-day refund, and licences can be transferred from an agency to the client. Automatic Renewals for the $99 update plan, added in September 2026, are opt-in and off by default, so lapsing only stops updates. Not higher because there is no startup programme and Enterprise terms are negotiated privately.

5.1.5
Free / Hobby Tier
68

Statamic Core is free forever and permitted for commercial and client work, not a trial, with unlimited collections and taxonomies, every fieldtype, asset management, Live Preview and the full front-end feature set. The hard limits are tight for anything beyond one person: a single admin account, a single form, and no API, revisions or multi-site. Not higher because the one-admin cap and the missing headless API push most team or client projects onto Pro.

Implementation Cost Signals
5.2.1
Time-to-first-value
77

Sherpa, a free native Mac app launched in August 2026, takes a newcomer from nothing to a running Control Panel without a terminal, Composer or a PHP install: pick a starter kit, preview on a local .test domain, and publish to Laravel Cloud or as static HTML to Netlify or Cloudflare Pages. Developers still have `statamic new`, Laravel Herd and one-click Forge or Ploi installs, and flat-file storage means no database has to be provisioned first. Not higher because the no-terminal path is macOS on Apple silicon only and there is no hosted sandbox to click into.

5.2.2
Typical implementation timeline
68

Statamic's sweet spot is the small to mid-size marketing site built by a Laravel shop, where a templated build from a starter kit or static HTML typically lands within the rubric's two to six week band, and its flat-file content and Blueprint modelling remove the schema and migration work a database CMS adds. As with Craft, there is no theme ecosystem, so every site is a bespoke build, and larger multi-site or integration-heavy projects scale with Laravel development effort. Confidence is INFERRED because no independent timeline data could be retrieved for this run.

5.2.3
Specialist cost premium
70

Statamic is a Composer package on Laravel, so any Laravel developer can work on it, and templates can be written in Laravel's own Blade instead of Statamic's Antlers; the Control Panel extends with Vue 3, Inertia and Tailwind, all mainstream tools. That points to a small premium over generalist PHP rates rather than a specialist one. Not higher because Statamic-specific experience is a much smaller pool than WordPress or plain Laravel, and this run could not retrieve rate data to confirm the premium.

Operational Cost Signals
5.3.1
Hosting costs
55

There is no vendor cloud, so hosting is always a separate line from the licence, run on Forge, Ploi, Laravel Cloud, Fortrabbit, Kinsta or a plain VPS. The bill sits at the cheap end of self-hosting: flat-file storage needs no database server, static caching can serve pages without booting PHP, and the static site generator can publish to Netlify or Vercel. Not higher because a server, backups and a CDN are still the buyer's to buy and run on every path.

5.3.2
Ops team requirements
55

A typical Statamic site needs part of one developer's time rather than a dedicated ops role, and Git-based content (with Pro's Git automation) makes backup and rollback simple. The buyer still owns PHP, Laravel and Statamic patching on a fast cadence (v6.0.0 in January 2026 to v6.39.0 at the end of October, with 5.x patch releases still shipping alongside), plus major upgrades: Statamic 6 raised the floor to PHP 8.3 and Laravel 12 and moved custom Control Panel code from Vue 2 to Vue 3. Not higher because nothing is managed by the vendor; not lower because the stack is small and conventional.

5.3.3
Vendor lock-in and exit cost
80

By default every entry, Blueprint and setting is a Markdown or YAML file in the buyer's own Git repository, about the most portable storage any CMS offers, and sites on the Eloquent driver sit in a standard Laravel database with first-party commands to export each repository back to flat files. The code runs on the buyer's infrastructure with no SaaS dependency beyond hourly licence validation, and offline validation is available on Enterprise. Not higher because Antlers templates and Bard or Replicator field structures do not carry over to another CMS, so leaving still means rebuilding the front end.

6Build Simplicity66▼
Learning Curve
6.1.1
Concept complexity
68

The core vocabulary (Collections, Blueprints, Fieldsets, Taxonomies, Globals, Navigation, Asset Containers) maps to ordinary content-model thinking, every definition is a readable YAML file, and the platform sits on standard Laravel routing, config and views. The vendor's own high-level build approach is 'static HTML, then views, then collections and routes, then blueprints', which is a mainstream web-dev mental model. Not 75+ because a developer still has to learn the Stache (the flat-file index and cache), the flat-file versus Eloquent storage split, and Antlers' tag semantics, which the docs describe as combining the roles of Blade templates and controllers.

6.1.2
Onboarding resources
66

Statamic ships a narrative Quick Start Guide that builds a complete small site from scratch in an estimated 20 to 30 minutes, an install hub with per-environment paths (Laravel Herd recommended, CLI, existing Laravel app, Sail/Docker, Forge and Ploi one-click), and points newcomers to a Laracasts video series. The `statamic new` CLI wizard walks starter-kit choice, first super user and git init. Not higher because there is no in-app interactive tour, no structured certification path and no framework-specific headless tutorials of the kind headless vendors publish.

6.1.3
Framework familiarity
64

Statamic is a Laravel package, so Laravel developers use Composer, Artisan, Eloquent-style queries and Blade templates they already know, and Statamic 6 rebuilt the Control Panel on Vue 3, Inertia and Tailwind 4. Headless teams get a first-party GraphQL API (with GraphiQL in the Control Panel) and a REST Content API. Held in the mid-60s because the default and documented-first templating path is the proprietary Antlers language, and there is no first-class React or Next.js support, so JavaScript-only teams work against generic APIs with no vendor SDK.

Implementation Complexity
6.2.1
Boilerplate and starter quality
60

Starter Kits are a first-class install path (`statamic new site vendor/kit`) and can carry their own content model, example content and design; the vendor maintains several free Antlers and Tailwind kits, and the widely used Peak kit adds a page builder, deploy scripts for Forge and Ploi, a production .env example, Nginx caching config and an optional GitHub workflow for dependency-update PRs. The Marketplace also lists many paid vertical kits. Capped at 60 because the vendor-built kits are small blog and portfolio demos, the most complete kit is third-party, and there are no official Next.js, Nuxt or Astro headless starters.

6.2.2
Configuration complexity
68

With Laravel Herd supplying PHP, Composer and a local server, `statamic new` produces a running site and Control Panel with no database to provision, because content is flat files and the default database connection is SQLite. Enabling GraphQL is one env var plus switching on resources, and Pro features can be enabled for development with a single config flag. Not 70+ because self-hosting still means owning a PHP 8.3+ runtime, extensions, Composer and a production server, and headless setups add per-resource API config that is disabled by default.

6.2.3
Data modeling constraints
66

Blueprints and fieldsets are YAML files versioned in Git alongside the code, there are no field-count caps, and on flat-file storage adding or renaming fields needs no database migration. Moving content into a database is a single `php please install:eloquent-driver` command that can move repositories selectively, and documented export commands move each one back to flat files. Not higher because there is no schema-migration tooling to transform existing content when a field changes type or handle, flat-file storage pushes very large content sets toward the database driver, and blueprint changes made in production on a Git-backed site must be reconciled with the repository. The new fieldtype inspection commands make valid blueprint settings discoverable from the CLI but do not migrate existing content.

6.2.4
Preview and editing integration
64

On the templated front end Live Preview is plug-and-play: it renders unsaved content with the current template, switches devices and templates, uses Alpine or Livewire morphing to update without reloads, collections can define several preview targets in YAML, and since v6.38 it also works on brand-new entries before their first save. Headless preview is documented but needs frontend work: a preview target points at the external app, Statamic appends a token that the app must pass back on GraphQL or REST calls, and live updates require a postMessage listener. Held to the mid-60s because there is no vendor SDK or reference Next.js/Nuxt implementation for the headless path.

Team & Talent
6.3.1
Required specialization
64

There is no certification and no partner-gated skill set: a Laravel or general PHP developer is productive quickly, Blade is a supported alternative to Antlers, and headless consumers need only GraphQL or REST. Moderate platform knowledge is still needed for Antlers, Stache behaviour, blueprint conventions and the addon API, and the Statamic-specific talent pool is small compared with WordPress or the JavaScript headless platforms, so buyers usually hire Laravel developers and train them.

6.3.2
Team size requirements
76

Statamic is built for small teams: one Laravel-capable developer can install, model, template and ship a production site, and the docs list one-click installs on Forge and Ploi that remove most server setup. Flat-file content in Git means no separate database administration for typical sites, and there is no mandatory partner or solution-architect model. Crosses 75 because the minimum viable team is genuinely one person, though that person owns hosting, updates and backups since there is no vendor-run cloud.

6.3.3
Cross-functional complexity
67

After launch, editors create and edit entries, pages, navigation and assets, use Live Preview, and assemble pages from developer-defined Replicator and Bard sets, which is how Peak and Marketplace page-builder kits give marketers block-based layouts without tickets; Statamic 6 added a command palette, keyboard set reordering and select-all bulk actions. Capped below 70 because new blueprints, fields, templates and block types need a developer and a Git deploy, the vendor explicitly says it is not trying to become a page builder, and on Git-backed sites editor changes flow through the repository.

7Operational Ease56▼
Upgrade & Patching
7.1.1
Upgrade difficulty
58

Statamic upgrades are Composer constraint bumps (^5.0 to ^6.0, then `composer update statamic/cms --with-dependencies`) with a published per-major upgrade guide, and flat-file installs have no database schema migrations to run. Majors still carry real breaking changes: Statamic 6 (released 28 January 2026) raised the floor to PHP 8.3 and Laravel 12, moved the Control Panel from Vue 2 to Vue 3 (forcing rework of custom fieldtypes and addons with Vue components), and changed date handling so API dates return in UTC. Not higher because each annual major drags a Laravel/PHP bump and addon compatibility checks with it; not lower because majors are not rewrites and vendor and community reports describe v3 to v5 as smooth.

7.1.2
Security patching
46

Statamic publishes GitHub security advisories with CVEs and back-ports fixes to both supported lines in ordinary patch releases (CVE-2026-64665 OAuth account takeover fixed in 5.74.1 and 6.24.0; CVE-2026-71435 stored XSS fixed in 5.74.3 and 6.24.2), and applying a patch is a routine `composer update`. But the 2026 advisory count has kept climbing (Packagist now lists 44 for statamic/cms, up from 31 earlier in the year, including HIGH-severity account takeover and data-destruction issues), CVE-2026-41175's fix was incomplete and needed CVE-2026-49287, and the 6.x two-factor recovery-code advisory CVE-2026-71293 (published 5 August 2026) still lists no first patched version. Not higher because the cadence is heavy and the self-hosting team owns every rollout with no auto-update; not lower because most issues need an authenticated Control Panel user and fixes usually reach both lines within days.

7.1.3
Vendor-forced migrations
56

Statamic ships one major a year (around Q1) and supports each for only one year of bug fixes and 18 months of security fixes: Statamic 5 stopped receiving bug fixes in March 2026 and loses security fixes in December 2026, and Statamic 7 is already scheduled for Q1 2027 on Laravel 13-14 and PHP 8.4+. Every major is coupled to Laravel's own support window, so teams follow an annual upgrade treadmill. Not higher because that window is short against the 12+ month deprecation benchmark and there is no LTS line; not lower because the content format (Markdown/YAML) and APIs are stable across majors and the vendor has avoided platform rewrites.

7.1.4
Dependency management
62

The default flat-file install needs only PHP, Composer and a web server: no database, no separate search service (the built-in local search driver works out of the box) and no mandatory cache server, which is a much shorter dependency list than most self-hosted CMSs. The trade-off is the Laravel framework's full Composer graph plus a Vue 3 Control Panel, and teams that move to the Eloquent driver, Redis queues or Algolia add those services back. Not higher because Laravel and PHP version floors move every year and transitive Composer packages must be audited by the operator; not lower because the graph is conventional, legible and patchable with standard tooling.

Operational Overhead
7.2.1
Monitoring requirements
42

Statamic itself ships no monitoring: no health dashboard, no APM, no status page (there is no vendor cloud to report on), so uptime, queue, error and server monitoring all fall to the operator. The Laravel ecosystem softens this considerably (Pulse, Telescope, Nightwatch, Forge/Ploi server monitoring all apply unchanged), and Marketplace addons such as Healthchecks add application checks. Not higher because none of this is first-party Statamic tooling; not lower because the Laravel monitoring tools drop in with little effort.

7.2.2
Content operations burden
47

Content lives in Git by default, so every change is diffable and recoverable, and Pro adds revisions and Git automation; Statamic also updates asset references across content automatically when an asset is moved or renamed, and dated collections can hide past-dated entries. The automated hygiene layer is addon territory: broken-link checking (Link Checker, Linkwise), orphaned-asset detection (Unused Assets, Clear Assets, Asset Atlas) and content-usage reports are all third-party, several not yet confirmed for v6, and there is no native scheduled-unpublish workflow. Not higher because 60+ requires native automated hygiene tooling; not lower because Git history and reference updating remove a meaningful share of manual cleanup.

7.2.3
Performance management
56

Static caching is built in: half measure serves pre-rendered responses through the application, full measure writes static HTML served before PHP runs, with automatic invalidation and `static:warm` warming, and Statamic 5 reworked the flat-file query layer to read only the files it needs (vendor claims 50 to 600 percent gains on large sites). Operators still own CDN setup, cache warming and invalidation strategy, and flat files slow down on sorting and filtering across very large collections, which pushes big sites to the Eloquent driver. Full-measure caching also only invalidates on the instance that handled the change, so multi-server setups need extra configuration. Not higher because none of this is managed for the customer; not lower because a single server with full-measure caching performs very well with little tuning.

Support & Resolution
7.3.1
Support tier quality
56

Pro licences include Basic Developer Support, so vendor help is not locked behind Enterprise, and Capterra reviewers rate customer support 4.7/5. But no response-time commitment attaches below Enterprise: the pricing page answers Basic Developer Support questions by email 'within 2-3 business days' and steers anyone needing guaranteed response times to premium support, while SLA support, a dedicated chat channel and a two-hour response on VIP sit in Enterprise. Not higher because mid-tier support carries no SLA from a small vendor team; not lower because reviewers consistently report good support quality.

7.3.2
Community support quality
70

The official Discord is large and busy for a CMS of this size (Statamic cites several thousand developers in live chat) with core team participation, backed by GitHub Discussions, a weekly community newsletter and the wider Laravel community, which answers most framework-level questions. Not higher because the community is far smaller than WordPress's or Drupal's and Stack Overflow coverage is thin; not lower because response quality and team presence are consistently praised.

7.3.3
Issue resolution velocity
66

Release velocity stays high: GitHub shows a 6.x release almost every week (6.31.0 on 1 September through 6.39.0 on 29 October 2026) while 5.x keeps receiving back-ported patches (5.74.5 to 5.74.7 in October), and security fixes land on both lines in the same release window. Not higher because the incomplete CVE-2026-41175 fix needed a second advisory, one 6.x advisory still records no patched version, and self-hosted teams add their own lag after a fix ships; not lower because bug turnaround from a small core team is visibly fast and transparent, with about 120 open issues on the core repo.

8Use-Case Fit35▼
Marketing Sites
8.1.1
Landing page tooling
48

Marketers can assemble pages from developer-defined Replicator and Bard sets (Page Builder pattern in Peak and most starter kits) and see them in Live Preview, so new pages are possible without a developer once the block library exists. There is no drag-and-drop or visual canvas editor; new layouts and block types still need a developer.

8.1.2
Campaign management
32

Campaign support is limited to scheduled publishing through collection date behaviours (future entries private until their date) and revisions. No content calendar, campaign object, multi-channel coordination or campaign analytics.

8.1.3
SEO tooling
68

The first-party SEO Pro addon covers meta, Open Graph and X card fields with cascading defaults, live Google and social previews on every entry, XML sitemaps, JSON-LD structured data, a redirects manager with wildcards, automatic redirects when slugs change, 404 tracking with one-click redirects, and graded site reports that flag title length, missing meta and broken links. It is an addon rather than core, but it is first-party and included in Platform plans.

8.1.4
Performance marketing
40

Native forms with blueprints, honeypot, email notifications, submission storage and CSV export, plus a FormSubmitted event for routing leads. No CTA management, conversion tracking or UTM handling; those come from tag managers and addons. Forms 2.0, aimed at funnel pages and marketing data capture, is in progress on the public roadmap but has not shipped.

8.1.5
Personalization and targeting
20

No personalization engine or audience segmentation. Targeting is template conditionals on the logged-in user and user groups, written by developers.

8.1.6
A/B testing and experimentation
32

No native experimentation. Small third-party marketplace addons provide weighted variants with conversion counts and a Control Panel dashboard, without statistical significance or auto-winner selection. External tools are the usual route.

8.1.7
Content velocity
56

Fast authoring once the block library exists: entry duplication, Bard and Replicator sets, Live Preview, bulk actions in listings, the Statamic 6 command palette, and Git-backed flat files that developers can edit in bulk. Revisions add a publish step without approval routing.

8.1.8
Multi-channel publishing
46

Web-first, with structured content exposed through the native REST Content API and first-party GraphQL (Pro), so apps and other channels can consume it. No channel-specific renditions or native email, social or push delivery.

8.1.9
Marketing analytics integration
33

No built-in analytics. GA4 dashboard widgets exist as paid third-party addons; SEO Pro adds SEO report and 404 widgets. Content performance metrics otherwise live in external tools.

8.1.10
Brand and design consistency
40

Consistency comes from developers defining the only available Replicator sets, Bard buttons and field validation in blueprints, so editors cannot break layouts. No design token management or brand guardrail tooling in the Control Panel.

8.1.11
Social and sharing integration
42

SEO Pro manages Open Graph and X card fields with images run through Glide, cascade defaults, and live Facebook and X previews in the entry editor. No push-to-social or social scheduling.

8.1.12
Marketing asset management
48

Asset containers on local or S3 storage with blueprints for metadata, focal points, and on-the-fly Glide image transforms. No tagging taxonomy, rights management or usage tracking at DAM level; Cloudinary and Fairu addons extend it.

8.1.13
Marketing localization
48

Pro multi-site gives per-locale sites with entry localizations that inherit from an origin entry and can override fields, plus per-site permissions. No transcreation workflow or market-level campaign scheduling beyond per-entry dates; translation is via third-party addons.

8.1.14
MarTech ecosystem connectivity
38

First-party Rad Pack Mailchimp addon, third-party form-to-CRM connectors and a small CRM and automation addon suite, plus Laravel events and webhooks for anything else. No prebuilt Salesforce, Marketo or CDP connectors of note.

Commerce
8.2.1
Product content depth
55

Blueprints with 40+ fieldtypes, Replicator, Grid and taxonomies model products, variants and attributes well as generic content. Cargo (successor to Simple Commerce) adds product and variant types for smaller stores, but there is no purpose-built PIM layer.

8.2.2
Merchandising tools
22

No merchandising tooling. Cross-sell and spotlights are manual Entries relationship fields; category ordering uses structured collections.

8.2.3
Commerce platform synergy
45

The Rad Pack Shopify addon imports products and keeps them in sync by webhook, making Shopify products available as entries. No equivalent for commercetools, SFCC or BigCommerce beyond custom Laravel integration.

8.2.4
Content-driven storytelling
45

Bard sets and Entries fields let editors drop product references into editorial pages when products live as entries (Shopify import or Cargo). Shoppable layouts and purchase CTAs are template work rather than a native authoring pattern.

8.2.5
Checkout and cart content
32

With Cargo, cart and checkout templates are Statamic views so CMS-managed globals can be placed there; with Shopify the checkout stays on Shopify. No injection of CMS content into external commerce flows.

8.2.6
Post-purchase content
25

Cargo order emails and confirmation pages can be templated; nothing ties CMS content to order events for external commerce platforms.

8.2.7
B2B commerce content
32

Front-end protection schemes (logged in, IP, password, custom drivers) and user groups can gate spec sheets and catalogs, but there is no account-based pricing or quote flow.

8.2.8
Search and discovery content
40

Native search indexes with the Comb driver or Algolia, configurable searchables across collections, so content and imported products can be searched together. Faceting, synonyms and search landing pages are built in Algolia or templates.

8.2.9
Promotional content management
33

Promo banners can be scheduled with date behaviours or globals; Cargo adds discounts. No time-windowed activation with end dates or channel targeting out of the box.

8.2.10
Multi-storefront content
45

Pro multi-site can run regional or brand storefronts from one install with shared entries localized per site and site-specific legal content. The vendor positions it for variations of one site, not independent storefronts.

8.2.11
Visual commerce and media
30

Asset galleries with Glide transforms and YouTube or Vimeo video embeds. No 360, AR or hotspot support natively; Cloudinary addon helps.

8.2.12
Marketplace and seller content
20

Front-end user registration and forms could collect seller content, but there are no seller profiles, moderation queues or review aggregation.

8.2.13
Commerce content localization
45

Product entries localize per site like any content, with origin inheritance. No currency-aware blocks or regulatory content tooling beyond what Cargo or Shopify provide.

8.2.14
Commerce conversion analytics
20

No connection between content engagement and revenue inside the CMS; attribution lives in GA4 or the commerce platform.

Intranet & Internal
8.3.1
Access control depth
45

Control Panel access uses roles, permissions and user groups (Pro) with per-collection and per-site permissions. Front-end protection is per entry or collection by auth, IP or password, and the auth scheme ignores roles, so department-level audience visibility needs a custom driver. SSO via Laravel Socialite or Enterprise plan.

8.3.2
Knowledge management
38

Taxonomies, structured collections, native search and full revision history with notes support a knowledge base. No review dates, expiry or approval routing for knowledge updates.

8.3.3
Employee experience
24

Members-only areas with front-end login, registration and profile forms can be built, and Laravel makes custom portal features practical. There is no news feed, directory, notifications or social layer; any portal is a custom build.

8.3.4
Internal communications
22

News can be published to protected collections, but there is no audience targeting, read receipts or acknowledgment tracking.

8.3.5
People directory and org chart
20

User blueprints can hold bios and fields, so a basic directory is buildable, but there is no org chart or HR system integration.

8.3.6
Policy and document management
30

Revisions give versioned policy pages with history and restore, and Git storage adds a full audit trail of content files. No acknowledgment tracking or review reminders.

8.3.7
Onboarding content delivery
18

Onboarding pages can be modelled as a protected collection; no role-specific paths, progressive disclosure or HR triggers.

8.3.8
Enterprise search quality
30

Comb or Algolia search covers Statamic content only. No federation with SharePoint, Confluence or Drive and no search analytics.

8.3.9
Mobile and frontline access
30

Responsive front ends and a responsive Control Panel; no native app, offline support or push notifications.

8.3.10
Learning and training integration
12

No LMS integration or learning features; training content would just be pages.

8.3.11
Social and collaboration features
15

No comments, reactions, forums or polls in core; forms could approximate polls and idea submission.

8.3.12
Workplace tool integration
18

No Teams, Slack or Google Workspace integrations; notifications would be custom Laravel listeners on Statamic events.

8.3.13
Content lifecycle and archival
28

Unpublish with revision history and date-driven visibility exist, but there are no review dates, stale content flags, ownership reminders or archival workflow. Editorial Workflows are still only listed as planned on the roadmap.

8.3.14
Internal analytics and engagement
15

No internal analytics, failed-search reporting or adoption dashboards.

Multi-Brand / Multi-Tenant
8.4.1
Tenant isolation
52

Multi-site shares one content store, users and blueprints, so it is not tenant isolation. Genuine isolation means a separate install per brand, which Statamic now supports commercially through Platform licensing and its Sites API.

8.4.2
Shared component library
48

Within one multi-site install, blueprints, fieldsets, partials and globals are shared across all sites. Across separate installs sharing is code-level through Composer packages or starter kits.

8.4.3
Governance model
40

Central roles and per-site permissions in one install, plus Enterprise audit logging. No cross-brand content standards or approval workflows.

8.4.4
Scale economics
70

Multi-site brands share one perpetual Pro licence and one host. For separate installs, Platform pricing starts at $240 a month for 20 sites and drops to $3.50 per site at volume, and a Master License covers volume purchase. Self-hosting keeps infrastructure cost shared.

8.4.5
Brand theming and style isolation
40

Each site can carry custom attributes (for example a theme key) used by templates to switch styling, and separate sites can have their own templates. Theming is a developer pattern, not a platform feature.

8.4.6
Localized content governance
30

Per-site permissions control who edits each locale, but translation workflow is shared and addon-driven with no brand-aware approval.

8.4.7
Cross-brand analytics
15

No portfolio or per-brand analytics.

8.4.8
Brand-specific workflows
25

Revisions can be switched on per collection, which allows some variation, but there are no configurable approval chains per brand.

8.4.9
Content syndication and sharing
50

Within multi-site, entries can be localized into other sites from an origin and inherit unchanged fields, so origin edits flow to child sites while overrides stay local. Globals can be shared. Nothing syndicates across separate installs.

8.4.10
Regional compliance controls
20

No per-brand compliance rules or publishing guardrails; consent and accessibility are template and addon concerns.

8.4.11
Design system management
28

Shared partials, components and fieldsets can be versioned in Git or packaged with Composer, but there is no design system management in the platform.

8.4.12
Cross-brand user management
45

One user base with central super admins and per-site roles in a multi-site install; SSO through Socialite or Enterprise. Separate installs have separate user stores.

8.4.13
Multi-brand content modeling
42

Collections can use several blueprints and share fieldsets, so a base model can be extended per brand by composing fieldsets, though blueprints are not per-site.

8.4.14
Portfolio-level reporting
15

No executive or portfolio reporting.

9Regulatory Readiness & Trust36▼
Data Privacy & Regulatory
9.1.1
GDPR & EU data protection
38

Statamic is self-hosted software with no vendor-run cloud, so the vendor never processes a customer's site content and GDPR compliance for the installation sits with the customer; the privacy policy says so directly ('there is nothing we can do to make your Statamic installation 100% compliant'). What the vendor does process (statamic.com accounts and licence validation, which phones home hourly with domain and IP while the Control Panel is in use) is covered only by a 2022 privacy policy: no DPA, no SCCs, no formal sub-processor page, and data subject requests go by email. A named list of third-party services in the policy and the fact that content never leaves the customer's infrastructure keep it above the floor; the missing DPA keeps it below 55.

9.1.2
HIPAA & healthcare compliance
22

No BAA, no HIPAA statement and no healthcare guidance exist anywhere in Statamic's documentation or legal pages. Because the software is self-hosted, a buyer could in principle deploy it on HIPAA-eligible infrastructure under their own BAA with a hosting provider, but the default flat-file storage writes content, form submissions and user records as plain YAML files on disk, so every safeguard is the customer's to build. Low end of the 20 to 35 band.

9.1.3
Regional & industry regulations
22

The privacy policy addresses only EU GDPR rights in a generic paragraph. There is no CCPA or California disclosure, no UK GDPR or IDTA addendum, no PIPEDA or LGPD statement, and no FedRAMP, IRAP, C5, PCI DSS or HITRUST coverage. As with every self-hosted CMS, regional compliance is inherited entirely from how the customer deploys and operates it.

Security Certifications
9.2.1
SOC 2 Type II
22

Statamic, Inc. holds no SOC 2 attestation of any type, publishes no trust center and announces no plan to pursue one. With no vendor-hosted service there is little for a SOC 2 report to scope beyond the licensing server and marketplace, so buyers carry the whole control environment through their own hosting provider. Low in the no-SOC-2 band, in line with other self-hosted open-source platforms.

9.2.2
ISO 27001 / ISO 27018
22

No ISO 27001 or ISO 27018 certification is held or claimed for Statamic, Inc. The privacy policy's 'we follow industry standards on information security management' is a statement, not a certificate with a registrar, scope or surveillance cadence. Any ISO coverage a buyer gets comes from their chosen host, not from the product.

9.2.3
Additional certifications
20

There are no additional certifications: no CSA STAR, PCI DSS, Cyber Essentials, ISO 42001 or government authorization. Statamic does run an active, transparent security process (a published SECURITY.md with scope, private reporting through GitHub, and frequent GitHub Security Advisories with affected and patched versions, several published in October 2026 alone), plus a documented security-fix window per major version. That is good practice but none of it is third-party attested, and there is no bug bounty.

Data Governance
9.3.1
Data residency & sovereignty
78

Residency is entirely in the customer's hands: Statamic runs wherever Laravel runs, content lives as flat files or in the customer's own database, and the vendor stores no site content, so any region or on-premises location is possible. The one data flow that leaves the customer's infrastructure is licence validation, which sends the licence key, domain, IP address and PHP version to the vendor's US-based Outpost every hour the Control Panel is in use; air-gapped installs require contacting support. Scores just under self-hosted peers for that call-home dependency, and there is no contractual guarantee because there is no hosted service to guarantee.

9.3.2
Data lifecycle & deletion
48

Content portability is unusually strong: by default every entry, user, form submission and setting is a Markdown or YAML file on disk, versionable in Git (the Pro Git automation commits changes as they happen), so a complete export is simply a copy of the repository with no proprietary format. Erasure, though, has no tooling: there is no data subject request workflow, no retention policy engine and no anonymisation feature, so deleting a person's data across entries, users, form submissions, revisions and Git history is a manual developer task, and Git history in particular retains deleted content unless rewritten. No vendor retention period applies because the vendor holds no content.

9.3.3
Audit logging & compliance reporting
42

Core Statamic has no audit log. Accountability comes from two Pro features: Revisions, whose history view records publish, unpublish and restore events with author and timestamp, and Git automation, which commits each content change under the authenticated user's name, giving a tamper-evident trail outside the application. Dedicated audit trails require marketplace addons (the paid Logger for Statamic from a Certified Partner, or the free Statamic Logbook), and there is no native SIEM push, configurable log retention or compliance reporting beyond standard Laravel logging channels.

Platform Accessibility
9.4.1
Authoring UI accessibility
40

Statamic publishes no accessibility statement or WCAG conformance target for the Control Panel. There is visible, recent remediation work, but it lands on the 6.x branch: in September and October 2026 the core team merged fixes for keyboard reordering of replicator sets, duplicate ARIA ids, heading order, modal focus handling, unlabelled search and table headers, and form-control contrast below 3:1. That demonstrates real attention, but buyers on Statamic 5 do not receive these fixes and there is no audited baseline to measure against, so it sits at the top of the no-documented-commitment band.

9.4.2
Accessibility documentation
22

There is no VPAT, ACR, Section 508 statement, ATAG assessment or accessibility page for Statamic. Accessibility in the Control Panel is visible only through individual GitHub issues and pull requests, which a procurement office cannot file. The only accessibility-specific tooling is third-party, such as a paid marketplace addon for editor-time WCAG checks on content, which concerns the delivered site rather than the authoring UI.

10AI Enablement30▼
AI Content Creation
10.1.1
AI text generation & editing
42

Statamic still ships no first-party generative AI, but the addon field now includes brand voice controls: Ghostwriter (1994, v1.3.0 Oct 2026, Statamic 6.30+) reads published entries to write an editable voice guide, drafts from a structured brief into the collection's own Replicator sets, edits existing entries, and never publishes for the editor. Statamic AI Writer (muench-dev), Scout (v0.1.3) and Bard Assist cover rewrite, summarise and translate in Bard. Above the plugin-only band because a maintained option has voice and review controls; held below 55 because none of it is first-party.

10.1.2
AI image & media generation
32

No media AI in core beyond manual focal point cropping and Glide manipulation, but addons now cover most of the asset workflow: Darkroom (D3 Creative, Oct 2026) generates images with Google's Nano Banana models straight into the asset library, Ghostwriter makes or sources matching images, and Magic Actions and AIDA generate alt text and captions, with Magic Actions also transcribing audio. Top of the no-native band; not higher because every piece is third-party and several are very new with little adoption.

10.1.3
AI translation assistance
36

No machine translation in core, but the marketplace has several maintained MT addons that work with Statamic Pro multi-site: AI Translator (Option5) bulk-translates whole entries through DeepL, One-click Content Translation (Apps with Love, commercial, Statamic 6 compatible) adds DeepL or Google buttons to fields including alt text, and Magic Translator (el-schneider, Apr 2026) translates Bard, Replicator and Grid fields through DeepL or LLMs via Prism. Top of the no-native band because bulk MT is genuinely available; not higher because there is no quality scoring or brand voice preservation and all of it is third-party.

10.1.4
AI metadata & SEO automation
34

SEO Pro, the first-party SEO addon, generates nothing with AI. Automation comes from Magic Actions (el-schneider, v0.2.2 Aug 2026), which proposes SEO titles, writes meta descriptions, extracts taxonomy tags and generates alt text, per field or in bulk from listing views and a CLI batch command, with AIDA and AI Alt as alt text options. No on-page AI scoring, and all of it is third-party, so it stays near the top of the no-automation band.

AI Workflow Automation
10.2.1
AI-assisted content operations
32

Core workflow tooling (revisions, scheduling) is rule-based, but Magic Actions now runs AI tag extraction, titles, teasers and alt text as queued background jobs across many entries or assets at once, and Dexter (BoldMinded) adds AI enrichment while indexing content into Algolia or Meilisearch. These are real bulk enrichment assists, but they are third-party and editor-triggered rather than woven into routing or lifecycle automation.

10.2.2
Agentic workflow automation
24

Statamic Inc. has no agent product. Third-party options remain early: Secretary (v0.1 beta) turns emailed or Control Panel requests into draft content for review, the Agentic starter kit adds guardrails, validation and a reviewed publish flow for an external content agent, and Scout describes itself as a write pipeline at version 0.1. External agents can also drive content through the community MCP servers. Early, third-party and beta, so it stays in the no-agentic band.

10.2.3
Content intelligence & insights
22

There is still no content intelligence dashboard in core; analytics come from external tools or the Mini Metrics addon. The one AI gap analysis is Ghostwriter's content plan, which reads what each collection holds and suggests what is missing, with a one-click brief for each idea. A single addon feature with no performance scoring, topic clustering or stale content detection keeps it below the basic band.

10.2.4
AI content auditing & quality
18

No AI quality, brand voice or compliance auditing at site scale. The audit-style addons that exist are rule-based (A11y Gate blocks publishing an entry that fails accessibility checks) or narrow and barely adopted (a greenwashing copy checker for EU rules), and Ghostwriter's publish block on unfilled facts applies only to its own drafts.

AI Search & Personalization
10.3.1
AI/semantic search
25

Core search uses a local index or Algolia, with community drivers for Meilisearch, Typesense and Elasticsearch, and no embeddings or vector index ship with the platform. The byte5 AI Entry Embeddings addon (v0.2.0, Apr 2026) now generates vector embeddings from entry content, with a companion assistant built on them, and Dexter adds AI enrichment to Algolia or Meilisearch indexing. Semantic search is therefore reachable through early addons and external engines, which stays in the custom-integration band.

10.3.2
AI-powered personalization
10

Statamic has no personalization engine, rule-based or ML. The new Statamic A/B Testing addon offers weighted entry variants with conversion tracking, which is experimentation rather than AI personalization; any audience targeting is built in Laravel or delegated to an external service.

AI Platform & Extensibility
10.4.1
MCP server availability
55

There is no official Statamic MCP server, but the community one has matured: cboxdk/statamic-mcp (v3.5.0, 29 Oct 2026, about 54,000 installs) is listed on the Marketplace with read and write tools for blueprints, entries, collections, assets and users, authenticated by Control Panel tokens. A second Marketplace server, Statamic MCP by Daniel (Aug 2026), is built on Laravel's MCP package and works under Statamic's permission system, and statamic-boost adds read-only tools to Laravel Boost. Scored as a well-supported community server; not higher because Statamic Inc. does not maintain one.

10.4.2
Bring your own AI model/key (BYOM/BYOK)
45

Every AI feature is an addon and every one is BYOK: Ghostwriter runs on Anthropic, OpenAI or Google keys or OpenRouter, with a gateway or proxy configurable per provider and keys kept on the site; Magic Actions reaches OpenAI, Anthropic, Gemini and Mistral through Prism; AI Writer takes any OpenAI-compatible endpoint, and self-hosting keeps content under the customer's control. Held at the top of the partial band because there is no platform-level model setting shared across features.

10.4.3
AI developer extensibility & agent APIs
55

Statamic has added first-party agent tooling in 2026: Statamic 6 ships Laravel Boost guidelines, the docs were made agent-ready with an llms.txt index and a Markdown version of every page, and Statamic 6.31 lets tools discover a site's collections, taxonomies, navs, asset containers and locales from the REST API, with slug lookups and field selection. GraphQL, Laravel events and flat-file content in Git round it out. No dedicated AI SDK or RAG endpoint, so it stays in the good-tooling band.

10.4.4
AI governance, safety & audit trails
20

There is no platform AI governance layer: no AI audit trail, indemnification or shared prompt policy. Controls exist only inside addons; Ghostwriter is the most complete, never publishing for the editor, blocking publication while a draft holds an unfilled fact or preview image, keeping prompts as overridable files in the project, and showing who sent each message. Secretary and the Agentic starter kit add review-before-publish gates, and MCP access is scoped by Control Panel tokens and permissions.

10.4.5
AI observability & usage analytics
8

No AI usage, cost or quality reporting exists in the Control Panel. Usage is billed to and visible only in each provider's own dashboard for the keys configured in each addon; Ghostwriter's dashboard widget tracks drafts in progress, not consumption.

Score History

How composite scores (0–100) have changed over time. Click legend items to show/hide metrics.

+0.7 capability
analyst note

Recent Updates

October 202621 score changes▼

Statamic is broadly stable, with a modest lift in Platform Velocity (60.7 to 61.7) and Cost Efficiency (70.3) offset by a slight slip in Operational Ease (55.6), while Suite Capability, Build Simplicity and Compliance & Trust hold steady. The upward movement comes almost entirely from the addon ecosystem filling AI gaps: Magic Actions now handles AI tagging, titles and metadata, and community addons cover more media and asset work, though core Statamic still ships no native AI, content intelligence dashboard or AI-driven SEO. Practitioners should weigh that addon-dependent AI story against a weaker security track record, where recent advisories pulled the picture down despite Statamic's well-run disclosure and prompt patching on both supported release lines.

Score Changes

AI image & media generation24 → 32(+8)

No media AI in core beyond manual focal point cropping and Glide manipulation, but addons now cover most of the asset workflow: Darkroom (D3 Creative, Oct 2026) generates images with Google's Nano Banana models straight into the asset library, Ghostwriter makes or sources matching images, and Magic Actions and AIDA generate alt text and captions, with Magic Actions also transcribing audio. Top of the no-native band; not higher because every piece is third-party and several are very new with little adoption.

AI-assisted content operations25 → 32(+7)

Core workflow tooling (revisions, scheduling) is rule-based, but Magic Actions now runs AI tag extraction, titles, teasers and alt text as queued background jobs across many entries or assets at once, and Dexter (BoldMinded) adds AI enrichment while indexing content into Algolia or Meilisearch. These are real bulk enrichment assists, but they are third-party and editor-triggered rather than woven into routing or lifecycle automation.

Content intelligence & insights15 → 22(+7)

There is still no content intelligence dashboard in core; analytics come from external tools or the Mini Metrics addon. The one AI gap analysis is Ghostwriter's content plan, which reads what each collection holds and suggests what is missing, with a one-click brief for each idea. A single addon feature with no performance scoring, topic clustering or stale content detection keeps it below the basic band.

Security track record55 → 48(-7)

Statamic handles disclosure well, with a clear SECURITY.md, private GitHub reporting, prompt patched releases on both the 6.x and still-maintained 5.x lines, and published GitHub advisories, but 2026 brought 43 advisories against the core package (1 critical, 13 high) versus one in 2025, including an account takeover via password reset link injection, remote code execution through Antlers-enabled Control Panel inputs, data destruction via unsafe method invocation, and an October unauthenticated path traversal allowing YAML file writes and user record overwrites. Not higher because the volume and severity of 2026 findings is heavy for a project this size and there is no paid bug bounty; not lower because fixes ship quickly and are clearly communicated, with no known mass exploitation.

AI metadata & SEO automation28 → 34(+6)

SEO Pro, the first-party SEO addon, generates nothing with AI. Automation comes from Magic Actions (el-schneider, v0.2.2 Aug 2026), which proposes SEO titles, writes meta descriptions, extracts taxonomy tags and generates alt text, per field or in bulk from listing views and a CLI batch command, with AIDA and AI Alt as alt text options. No on-page AI scoring, and all of it is third-party, so it stays near the top of the no-automation band.

AI/semantic search20 → 25(+5)

Core search uses a local index or Algolia, with community drivers for Meilisearch, Typesense and Elasticsearch, and no embeddings or vector index ship with the platform. The byte5 AI Entry Embeddings addon (v0.2.0, Apr 2026) now generates vector embeddings from entry content, with a companion assistant built on them, and Dexter adds AI enrichment to Algolia or Meilisearch indexing. Semantic search is therefore reachable through early addons and external engines, which stays in the custom-integration band.

AI developer extensibility & agent APIs50 → 55(+5)

Statamic has added first-party agent tooling in 2026: Statamic 6 ships Laravel Boost guidelines, the docs were made agent-ready with an llms.txt index and a Markdown version of every page, and Statamic 6.31 lets tools discover a site's collections, taxonomies, navs, asset containers and locales from the REST API, with slug lookups and field selection. GraphQL, Laravel events and flat-file content in Git round it out. No dedicated AI SDK or RAG endpoint, so it stays in the good-tooling band.

AI governance, safety & audit trails15 → 20(+5)

There is no platform AI governance layer: no AI audit trail, indemnification or shared prompt policy. Controls exist only inside addons; Ghostwriter is the most complete, never publishing for the editor, blocking publication while a draft holds an unfilled fact or preview image, keeping prompts as overridable files in the project, and showing who sent each message. Secretary and the Agentic starter kit add review-before-publish gates, and MCP access is scoped by Control Panel tokens and permissions.

AI text generation & editing38 → 42(+4)

Statamic still ships no first-party generative AI, but the addon field now includes brand voice controls: Ghostwriter (1994, v1.3.0 Oct 2026, Statamic 6.30+) reads published entries to write an editable voice guide, drafts from a structured brief into the collection's own Replicator sets, edits existing entries, and never publishes for the editor. Statamic AI Writer (muench-dev), Scout (v0.1.3) and Bard Assist cover rewrite, summarise and translate in Bard. Above the plugin-only band because a maintained option has voice and review controls; held below 55 because none of it is first-party.

Release frequency78 → 82(+4)

Statamic 6 went stable on January 28, 2026 and has since shipped a feature minor roughly every week, moving from 6.12.0 in April to 6.39.0 on October 29. These releases carry real features: Laravel 13 support, content model discovery for headless tools in 6.31, hybrid Glide image caching, and Live Preview before the first save plus keyboard reordering in 6.36 to 6.38. Version 5 still gets security patches (5.74.7 on October 22). Not higher because Forms 2.0, the largest item on the roadmap, is still in progress after a preview in August.

Roadmap transparency68 → 72(+4)

The public roadmap at statamic.com/roadmap is split into In Progress (Forms 2.0, Control Panel performance, groupable collections, multi-site improvements, hierarchical taxonomies), Planned (workflows, dashboard widgets, Collaboration 3.0) and a dated Shipped log. Each item links to the matching requests in the public statamic/ideas GitHub repository, where the community proposes and discusses features. Not higher because the roadmap gives no target dates and the ideas repository has no formal voting ranking.

MCP server availability52 → 55(+3)

There is no official Statamic MCP server, but the community one has matured: cboxdk/statamic-mcp (v3.5.0, 29 Oct 2026, about 54,000 installs) is listed on the Marketplace with read and write tools for blueprints, entries, collections, assets and users, authenticated by Control Panel tokens. A second Marketplace server, Statamic MCP by Daniel (Aug 2026), is built on Laravel's MCP package and works under Statamic's permission system, and statamic-boost adds read-only tools to Laravel Boost. Scored as a well-supported community server; not higher because Statamic Inc. does not maintain one.

Bring your own AI model/key (BYOM/BYOK)42 → 45(+3)

Every AI feature is an addon and every one is BYOK: Ghostwriter runs on Anthropic, OpenAI or Google keys or OpenRouter, with a gateway or proxy configurable per provider and keys kept on the site; Magic Actions reaches OpenAI, Anthropic, Gemini and Mistral through Prism; AI Writer takes any OpenAI-compatible endpoint, and self-hosting keeps content under the customer's control. Held at the top of the partial band because there is no platform-level model setting shared across features.

Time-to-first-value74 → 77(+3)

Sherpa, a free native Mac app launched in August 2026, takes a newcomer from nothing to a running Control Panel without a terminal, Composer or a PHP install: pick a starter kit, preview on a local .test domain, and publish to Laravel Cloud or as static HTML to Netlify or Cloudflare Pages. Developers still have `statamic new`, Laravel Herd and one-click Forge or Ploi installs, and flat-file storage means no database has to be provisioned first. Not higher because the no-terminal path is macOS on Apple silicon only and there is no hosted sandbox to click into.

Security patching49 → 46(-3)

Statamic publishes GitHub security advisories with CVEs and back-ports fixes to both supported lines in ordinary patch releases (CVE-2026-64665 OAuth account takeover fixed in 5.74.1 and 6.24.0; CVE-2026-71435 stored XSS fixed in 5.74.3 and 6.24.2), and applying a patch is a routine `composer update`. But the 2026 advisory count has kept climbing (Packagist now lists 44 for statamic/cms, up from 31 earlier in the year, including HIGH-severity account takeover and data-destruction issues), CVE-2026-41175's fix was incomplete and needed CVE-2026-49287, and the 6.x two-factor recovery-code advisory CVE-2026-71293 (published 5 August 2026) still lists no first patched version. Not higher because the cadence is heavy and the self-hosting team owns every rollout with no auto-update; not lower because most issues need an authenticated Control Panel user and fixes usually reach both lines within days.

Video & rich media28 → 30(+2)

Video files can be uploaded as assets and the core Video fieldtype embeds YouTube, Vimeo and, since Statamic 6.38 (October 2026), Cloudflare Stream, which brings adaptive streaming from Cloudflare's paid service. Statamic itself does no transcoding, captions or player, so video is still hosted outside the product and embedded.

Community engagement66 → 68(+2)

Engagement is strong for the community's size. Monthly release roundups credit outside contributors by name, the core team is active in Discord, and Marketplace submissions grew enough that the vendor introduced a review process in September. Statamic Summit, a dedicated multi-day conference with talks and workshops, is set for February 2027, following the earlier Flat Camp meetups. Not higher because the core team of about six people limits how much community input it can absorb.

Customer momentum58 → 60(+2)

Momentum signals strengthened in 2026: a flagship site in the Laravel ecosystem moved to Statamic in August, the vendor raised Pro pricing to $349 per site from May without visible backlash, and it launched Sherpa, a free Mac app that takes non-developers from starter kit to deployed site without a terminal. Packagist downloads also grew by over a million this year. Not higher because Statamic publishes no customer counts, licence growth or revenue figures, and its independent review footprint is barely growing.

SEO tooling66 → 68(+2)

The first-party SEO Pro addon covers meta, Open Graph and X card fields with cascading defaults, live Google and social previews on every entry, XML sitemaps, JSON-LD structured data, a redirects manager with wildcards, automatic redirects when slugs change, 404 tracking with one-click redirects, and graded site reports that flag title length, missing meta and broken links. It is an addon rather than core, but it is first-party and included in Platform plans.

Social and sharing integration40 → 42(+2)

SEO Pro manages Open Graph and X card fields with images run through Glide, cascade defaults, and live Facebook and X previews in the entry editor. No push-to-social or social scheduling.

Community size52 → 53(+1)

The statamic/cms core repository has about 4.9K GitHub stars and 652 forks, with roughly 4.4M total Packagist downloads, and the vendor cites a Discord of about 5,300 developers. That sits just under the 5K-star band, with steady growth through 2026. It is a solid niche community that also draws on the much larger Laravel ecosystem, but it is small in absolute terms.

Frequently Asked Questions

What do current customers say is their favorite thing about being on Statamic?

Reviewers most often praise Statamic for ease of use and predictable licensing compared with WordPress. Developers also value its Laravel foundation and an active Discord where the core team answers questions, and Capterra reviewers rate support 4.7 out of 5.

What is the 5 year TCO of Statamic?

Statamic's five year licence cost is small: Pro costs $349 per site plus $99 a year for updates after year one, about $745 per site over five years. Hosting, paid addons and developer time for upgrades and security patches usually cost more.

Verify with the vendor: Statamic Pricing ↗ · Statamic Licensing ↗

What are the best alternatives to Statamic?

The closest alternatives to Statamic are Craft CMS, WordPress, Drupal and Payload CMS. Craft is the nearest PHP peer, WordPress has a far larger ecosystem, Drupal adds stronger editorial workflow, and Payload suits TypeScript teams wanting a code-first headless CMS.

Does Statamic have built-in AI features?

Statamic has no first-party AI features. AI drafting, translation, alt text and image generation come from bring-your-own-key Marketplace addons such as Ghostwriter and Magic Actions, and community Model Context Protocol (MCP) servers let external AI agents read and edit content.

How hard is Statamic to implement and maintain?

Statamic is easy to implement for a Laravel developer: one person can build and ship a small marketing site, and flat-file content needs no database. Maintenance is steady work, with frequent 2026 security patches and a major upgrade every year.

What are some of the biggest criticisms of Statamic from current customers?

Reviewers and developers mostly criticise Statamic for what it leaves out: no editorial approval workflow, no visual page editing and no first-party AI. Developers also flag the yearly major upgrade cycle and a heavy wave of security advisories in 2026.

Independent
We don't implement these platforms. Our trusted partner community does. Do you need help getting started?

Looking for a Statamic partner?

Agencies, dev shops, and systems integrators vary wildly in how well they deliver on Statamic. We don't take on implementation work ourselves.

Tell us what you're building and we'll come back with a shortlist of firms with a genuine track record on this platform.

How does Statamic stack up against your shortlist?
Side-by-side scoring across all 10 categories and every criterion.
Compare head to head →