Craft CMS
Provenance unknown Report an errorPanel rating · 6 judges · How to read the stars
Category median
Sovereignty: 4 of 6 dimensions proven
0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Pixel & Tonic, Inc. · craftcms.com
Report an error on this page Is this your product? →
Link to this page
Add ?theme=dark to the image address for dark backgrounds.
The badge shows the category and the month of the latest evaluation, and EU-Made where
that is the product’s provenance. It never shows a score.
Craft CMS at a glance
- Vendor
- Pixel & Tonic, Inc.
- Headquarters
- Incorporated in the United States source, captured 10 Nov 2026
- Data hosting
- Outside the EU by default source, captured 10 Nov 2026
- Free plan
- Not stated on the vendor’s pages as of 10 Nov 2026
- Panel verdict
- The AI panel rates Craft CMS 2/5, the mean of 6 judges. Craft CMS, from Pixel & Tonic, Inc., is a template-based content platform the bench scored strongest on content model and reuse and distribution and integrations: unlimited sites, languages and locales, per-volume field layouts, a documented GraphQL API with scoped, expiring tokens, and named connectors for Salesforce, Mailchimp and Hubspot. how scores are made
- As of
- Vendor pages captured 10 Nov 2026; evaluated by the panel 11 Nov 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Craft CMS, from Pixel & Tonic, Inc., is a template-based content platform the bench scored strongest on content model and reuse and distribution and integrations: unlimited sites, languages and locales, per-volume field layouts, a documented GraphQL API with scoped, expiring tokens, and named connectors for Salesforce, Mailchimp and Hubspot. It is weakest at editorial planning, where the captured pages describe site architecture rather than calendars, briefs or deadline views, and the AI and content rights criterion stands at 0 with no public information on models, training use or output rights. Collaboration and approval scores at 3-4 on granular, 403-enforced permissions, though no public information covers comments, version history with restore, approval steps or an audit trail. Sovereignty scores at 3-4: a US entity storing personal information in the United States per its privacy policy, with a data processing addendum for EU customers and documented self-managed deployment as the counterweight. Beyond a free Craft Cloud trial the captured pages show no plan prices. No disagreements were flagged; weighted verdicts run from 3.2 to 5.3.
Speaks for it
- Content model and reuse scores at 5-7, covering unlimited sites, languages and locales with per-volume field layouts.
- Granular permissions — custom, nested and per-volume, enforced with a 403 — separate who writes from who publishes.
- A documented GraphQL API moves content out through scoped, expiring tokens and mutations.
- Named connectors cover Salesforce, Mailchimp and Hubspot, alongside first-party storage plugins for Amazon S3, Google Cloud Storage and Rackspace.
- Documented self-managed deployment keeps site content on the customer's own servers.
Held against it
- Editorial planning scores at 0-2, with no public information on calendars, briefs, campaigns or deadline views.
- The AI and content rights criterion stands at 0, with no public information on models, training use or output rights.
- No public information covers comments, version history with restore, approval steps or an audit trail behind the permissions.
- No documented self-service export of content, model, locales and assets appears on the captured pages.
- Named subprocessors are listed with purposes but no locations.
Best for
- You build template-based sites with a development team and model content across unlimited sites, languages and locales.
- You distribute content through a documented GraphQL API with scoped tokens and connect Salesforce, Mailchimp or Hubspot.
- You want to self-manage deployment and keep site content on your own infrastructure.
Avoid if
- You need an editorial calendar, briefs and per-person deadline views inside the tool.
- Your release process runs on approval gates, version restore and an audit trail rather than developer-configured permissions.
- You need a vendor under EU jurisdiction with a stated EU hosting location for the managed platform.
- Your exit plan depends on a self-service export of content, model and locales rather than the GraphQL API.
The scores
| Criterion | Panel median |
|---|---|
| Planning, editorial calendar & briefs | 0.5 of 5 |
| Creation, review & approval | 2 of 5 |
| Structured content, localisation & export | 3 of 5 |
| Publishing, distribution & integrations | 3 of 5 |
| European sovereignty | 1.5 of 5 |
Planning, editorial calendar & briefs
Show reasoningHide reasoning
How this is scored
Turning a content strategy into scheduled work: topics and campaigns, an editorial calendar across channels, briefs that carry the goal, audience and keywords to the writer, and a view of what is due, late or missing.
0 — No planning at all; the product only stores or renders content.
3 — A calendar or list view of content with publish dates and statuses.
5 — An editorial calendar across channels with owners, due dates and custom statuses, and content grouped by campaign, topic or channel.
8 — Strategy connected to the plan: briefs carrying goal, audience and keywords attached to each piece, topics or personas defined once and assigned to pieces, configurable workflows per content type, workload and deadline views per person, and recurring formats scheduled as series.
10 — The plan is accountable: every published piece traces back to its brief, topic and campaign, gaps in coverage per topic or funnel stage are reported, and plan-versus-published is visible over time without a spreadsheet.
The Head of Content
The captured planning material is about site structure and static templates, and it advises modeling content on paper or outside the tool first. I found no public information on an editorial calendar, briefs carrying goal and audience to the writer, campaign grouping, or a view of what is due or late. 4 5
The SME Marketer
The captured planning guide is about site architecture — thinking in static templates and modelling content before build — not editorial work. I found no calendar, campaign, brief, owner or deadline view on any page I read, so this reads as a content store rather than a planning tool. 4 5
The Localisation Lead
The planning documentation captured here is about planning a site as static HTML templates and modelling content before you build it, not about editorial work — I found no public information on an editorial calendar, briefs, campaign or topic grouping, or workload and deadline views. The captured planning pages also cover a version the vendor itself states is no longer supported. 4 5
The Web Engineer
The planning documentation I read is site architecture, not editorial work: content modeling sketched on paper first and static HTML templates implemented in Craft. We found no public information on an editorial calendar, briefs, campaigns, owners or deadline views in the captured pages. 4 5
The Data Protection Officer
The captured planning pages describe planning a site around static HTML templates and advise working out the content model on paper or outside of Craft first. We found no public information on an editorial calendar, campaigns, briefs, owners, due dates or per-person workload views. 4 5
The Skeptic
The captured planning pages are about building the site, not running an editorial operation: they advise modeling content on paper or outside the product first and treating the site as static templates. We found no public information on an editorial calendar, briefs carrying goal and audience, campaign grouping, or per-person deadline views. 4 5
Creation, review & approval
Show reasoningHide reasoning
How this is scored
Writing and reviewing content together: editing with comments and suggestions, roles and permissions for internal and external contributors, and an approval trail that records who released which version — published content is a legal statement (UWG, Heilmittelwerbegesetz, the imprint duty).
0 — A single-user tool; content cannot be shared with or reviewed by others.
3 — Several users working on content, with comments or a version history.
5 — Roles and permissions that separate writing from publishing, comments on content, a version history with restore, and an approval or review status before publishing.
8 — Configurable multi-step approval per content type or market, mandatory reviewers (legal, product, brand), inline suggested edits, guest or freelancer access limited to assigned pieces, scheduled publishing that waits for approval, and an audit log of every edit, approval and publish with user and timestamp.
10 — Approval is evidence: the exact version each approver released is preserved and exportable, permissions reach down to field and locale level, and the audit trail is retained for a stated period and available after the contract ends.
The Head of Content
Permissions are documented in depth, including developer-registered custom permissions, checks in templates and controllers, and 403 enforcement, which can separate who publishes from who writes. But I found no public information on comments, suggested edits, version history with restore, or an approval trail recording which version was released. 6 7
The SME Marketer
Granular user permissions are well documented — custom permissions, nesting, and per-volume rules enforced with a 403 — so writing and publishing can genuinely be separated by role. But I found no public information on comments, version history with restore, approval steps before publishing, guest or freelancer access, or an audit trail, which is exactly what I need before legal releases a piece. 6 7 9
The Localisation Lead
A genuinely granular permission system is documented — custom permissions registered by modules, nested permissions, per-volume permissions, and checks enforced in controllers and templates with a 403 on denial — which separates duties well. But I found no public information on comments, version history with restore, approval steps, mandatory reviewers, or an audit log recording who released which version, and for German publishing that trail is not optional. 6 7 9
The Web Engineer
A genuinely granular permission system is documented — permission checks in templates, controllers and PHP, custom permissions registered via events, nested permissions, and per-volume permissions returning 403 when denied — so writing and publishing can be separated. We found no public information on comments, version history with restore, approval steps or an audit trail in the captured pages. 6 7 9
The Data Protection Officer
The developer documentation shows a granular permission system — permission checks for logged-in users, permissions registered by modules and plugins, nested permissions, and asset volumes that each carry their own permission configuration — with a 403 response when a permission is missing. We found no public information on comments, version history with restore, review or approval states before publishing, or an audit log. 6 7 9
The Skeptic
What the captured documentation evidences is a permission system — permission checks in templates and controllers returning a 403, and custom permissions that modules and plugins can register. We found no public information on comments, a version history with restore, approval steps before publishing, or any audit trail recording who released which version — the part that makes published content defensible. 6 7
Structured content, localisation & export
Show reasoningHide reasoning
How this is scored
Whether content is stored as reusable structure rather than pages: a content model, components shared across channels, German and other locales managed side by side, and the whole repository exportable in a documented format.
0 — Not a content store; the product keeps no content of its own (for example a pure scheduling or analytics tool).
3 — Templates or custom fields for content, a media library, and content in several languages.
5 — A configurable content model or content types with reusable components, locales managed side by side for each entry, and an export of entries in JSON, CSV, XML or a similar documented format.
8 — References between entries, field-level localisation with fallback languages, variants per market or audience, translation workflows with status per locale and named translation-service connectors, and a full export of content, model, locales and assets documented and self-service.
10 — The repository is portable by design: model and content exportable together and re-importable, migration tooling or a CLI documented in both directions, version history included in the export, and no feature that only works while the content stays.
The Head of Content
Content is real structure: a configurable model, volumes each with their own field layout, relations between entries, categories and tags, and unlimited sites, languages and locales side by side. Content is reachable as documented JSON through the GraphQL API with schema-scoped tokens, and Crowdin is named for translation work alongside services like Gengo; I found no public information on a self-service full export of content, model and assets together. 1 4 8 9 10
The SME Marketer
A configurable content model, asset volumes with their own field layouts, unlimited sites, languages and locales managed side by side, and named translation services via Crowdin (Alconost, Gengo, Acclaro) make this a good fit for my German and English rollout. Content leaves through a documented GraphQL API rather than a self-service full export of model, locales and assets, and I found no public information on field-level fallback languages or translation status per locale. 1 4 8 9 10
The Localisation Lead
Native multi-site architecture with unlimited sites, languages and locales, a configurable content model with per-volume field layouts, relation arguments between elements, and a translation workflow via Crowdin connecting Alconost, Gengo and Acclaro — this is the core of what I ship every day. But the Crowdin workflow shown covers static interface messages rather than per-entry translation status per locale, field-level localisation and fallbacks are not shown, and I found no documented export of content, model and locales on any captured page; a CLI exists, yet no export or migration command appears, and a repository that cannot leave is a hostage. 1 8 9 4
The Web Engineer
Content modeling with per-volume custom field layouts, relation arguments linking entries to entries, assets, users, categories and tags in GraphQL, and unlimited sites, languages and locales with a Crowdin workflow and named translation services (Alconost, Gengo, Acclaro). Content leaves through a documented GraphQL API with scoped, expiring tokens and mutations rather than a one-shot repository export; we found no public information on field-level locale fallback or re-import tooling. 1 4 8 9 10
The Data Protection Officer
Content modeling is documented as a first-class activity, assets sit in volumes each with its own custom field layout, and localization for an unlimited number of sites, languages and locales is offered, with a Crowdin workflow named for translations and GraphQL queries that traverse relations between entries, assets, users, categories and tags. We found no public information on field-level localization with fallback languages, per-market variants, or a documented self-service export of content, model and assets together. 1 4 8 9 10
The Skeptic
Content modeling is documented, sites, languages and locales are unlimited and managed side by side, relations between entries are queryable through the API, and a translation path exists via Crowdin with named professional services such as Gengo and Acclaro. We found no public information on field-level localisation with fallback languages or a documented, self-service export of content, model, locales and assets; portability rests on self-managed deployment and the command-line interface. 1 3 4 8 10
Publishing, distribution & integrations
Show reasoningHide reasoning
How this is scored
Getting approved content to where it is read: publishing to websites and channels, a documented API and webhooks, and named connections to the CMS, CRM, analytics, SEO and translation tools a marketing stack already runs.
0 — A closed tool; content leaves only by copy and paste.
3 — Publishing to one website or CMS, and a few named integrations.
5 — Publishing to websites and several channels from one place, a publicly documented API or webhooks, and integrations named for common CMS, CRM or analytics tools.
8 — A versioned API with published rate limits and SDKs, webhooks on publish and change, preview environments, a marketplace or integration directory with maintained connectors, performance data per piece pulled back from analytics, and a public status page.
10 — The platform is a dependable source for every channel: API deprecation policy published, CDN and delivery SLA stated, scheduled and event-driven publishing documented end to end, and content performance attributed per channel without a separate tool.
The Head of Content
Craft publishes its own templated sites and exposes content through a documented GraphQL API with public and token-protected schemas, mutations and configurable origins; named connections cover Salesforce, Mailchimp and Hubspot plus first-party storage plugins for Amazon S3 and Google Cloud. I found no public information on webhooks, published rate limits, or per-piece performance data pulled back from analytics. 1 4 9 10
The SME Marketer
Sites are rendered from templates with multi-site support across subdomains, there is a documented GraphQL API with schemas and access tokens, a built-in plugin store, first-party storage connectors like Amazon S3, and named marketing integrations (Salesforce, Mailchimp, HubSpot). I found no public information on webhooks, published rate limits, per-piece performance data or a status page. 1 8 9 10
The Localisation Lead
Content leaves through a documented GraphQL API with public and private token-scoped schemas, expiration dates and token regeneration, plus a built-in plugin store and named connectors for Salesforce, Mailchimp and Hubspot as well as first-party remote storage for Amazon S3 and Google Cloud. The captured API pages cover version 3.x, however, and I found no public information on webhooks, rate limits, SDKs, a delivery SLA or a status page. 1 9 10
The Web Engineer
A documented GraphQL API with public and private schemas, token scoping, expiration and regeneration, write mutations, CORS control and a built-in GraphiQL, plus named marketing connectors (Salesforce, Mailchimp, Hubspot), a plugin store with first-party S3, Google Cloud Storage and Rackspace filesystem plugins, and a first-party hosting platform with a free trial. We found no public information on webhooks, published rate limits or SDKs, and the GraphQL docs captured cover older, unsupported major versions. 1 9 10 11
The Data Protection Officer
A publicly documented GraphQL API with public and private schemas, tokens with expiry dates, mutations and configurable origins is offered, alongside a built-in Plugin Store, named marketing connections to Salesforce, Mailchimp and Hubspot, first-party storage plugins for Amazon S3, Google Cloud Storage and Rackspace, and a first-party hosting platform. We found no public information on API rate limits, SDKs, webhooks, a public status page, or performance data pulled back per piece. 1 3 9 10
The Skeptic
A publicly documented GraphQL API with token-scoped schemas, expiration dates and mutations is evidenced, alongside named connections to Salesforce, Mailchimp and Hubspot and first-party remote-storage connectors for Amazon S3, Google Cloud Storage and Rackspace. We found no public information on rate limits, webhooks, a maintained integration directory or a status page, and the captured GraphQL pages cover different product versions. 1 9 10
AI assistance & content rights
n/r
n/r
n/r
n/r
n/r
n/r
Show reasoningHide reasoning
How this is scored
What the platform's AI does with the customer's content and what the customer may do with the AI's: the models and where they run, whether content trains them, opt-out, labelling of generated text under the EU AI Act, and who holds the rights to output.
0 — The vendor states that customer content trains its models with no opt-out, or reserves the rights to AI output for itself.
3 — AI writing features described with what they do, and a general statement on how content is handled by them.
5 — The AI model provider named, a statement that customer content does not train models, and AI features that an admin can switch off.
8 — Model providers listed as subprocessors, EU processing for AI features stated or selectable, retention of prompts and outputs given in days, ownership of generated output assigned to the customer in the terms, generated content markable for EU AI Act transparency, and brand voice or terminology rules applied without training a shared model.
10 — AI is governed and documented: per-feature list of model, provider and processing location, admin controls per role and content type, an audit trail of AI-generated changes, and the output rights and any indemnity written into the contract terms.
The Head of Content not rated — no public information
I found no public information on AI writing features, what any model does with customer content, or who holds rights to generated output; neither the vendor page nor the privacy statement addresses it. 1 2
The SME Marketer not rated — no public information
I found no public information on AI writing features, which models run where, whether my drafts train them, opt-out, EU AI Act labelling, or who owns generated output — nothing on the captured homepage or in the privacy statement. For someone who writes half her content with an AI assistant, that is a blank page. 1 2
The Localisation Lead not rated — no public information
We found no public information on AI assistance, where any models run, whether content trains them, EU AI Act labelling, or rights to generated output on the homepage and privacy policy pages I read. Nothing on this evidence lets me score it either way. 1 2
The Web Engineer not rated — no public information
We found no public information on AI writing features, model providers or processing locations, whether content trains models, opt-outs, or rights to generated output in the captured pages. 1 2
The Data Protection Officer not rated — no public information
We found no public information on AI writing features, the models behind them, where they run, whether customer content trains them, or who holds the rights to generated output. Neither the captured homepage nor the privacy policy mentions AI. 1 2
The Skeptic not rated — no public information
We found no public information on AI assistance — no models named, no statement on where they run, nothing on whether customer content trains them, and nothing on labelling or output rights. The captured homepage, privacy policy and documentation pages describe hosting, licensing and content management only. 1 2
European sovereignty
panel opinion
Show reasoningHide reasoning
How this is scored
Who the contracting entity is, where content, assets and AI prompts are stored and processed, and which subprocessors touch them. Independently sourced by the sovereignty pipeline; dimensions the evidence does not establish are unknown, not non-European.
0 — Vendor, contracting entity and hosting all shown to be outside the EU, with no data processing agreement offered.
3 — A privacy policy and a data processing agreement offered, with hosting or the contracting entity outside the EU or not established.
5 — EU hosting stated for content and assets, with a data processing agreement offered.
8 — EU contracting entity, content, assets and backups stored in the EU on named infrastructure, subprocessor list published with locations and purposes, and AI processing location stated.
10 — Sovereign end to end and evidenced: European ownership, EU entity, every hosting, CDN, AI and support subprocessor European or optional, self-hosting or a European cloud offered, and certifications published.
The Head of Content
The contracting entity is Pixel & Tonic, Inc. in Oregon, and the privacy statement says personal information is collected and stored in the United States, with a data processing addendum offered to EU customers; subprocessors are named with purposes but no locations. Self-managed deployment is documented, so a customer's own content can sit on their own servers, but I found no public information on EU hosting for the vendor's platform. 2 3
The SME Marketer
The contracting entity is a US company in Bend, Oregon, and the privacy statement says personal information is stored in the United States; a data processing addendum is offered and the excerpt restricts it to EU customers. Self-managed installation means our site content can stay on our own servers, which is the one real sovereignty lever, though the named subprocessors (Stripe, Front App, Google Analytics, plugin developers) are listed with purposes but no locations. 2 3
The Localisation Lead
The contracting entity is Pixel & Tonic, Inc. of Bend, Oregon, personal information is stored in the United States, and subprocessors (Stripe, Front App, Google Analytics, plugin developers) are named with purposes but no locations; a data processing addendum is offered to EU customers. The one sovereign path is documented self-managed deployment with a local-first workflow, so site content can stay on the customer's own infrastructure — but EU hosting is not stated for the first-party platform. 2 3 1
The Web Engineer
The contracting entity is a US company, personal data storage is stated as the United States, and a privacy policy with GDPR rights plus a self-serve data processing addendum for EU customers is offered; subprocessors are named (Stripe, Front, Google Analytics, plugin developers) without locations. Self-managed installs keep site content on your own infrastructure, but we found no public information on where the first-party hosting platform stores content. 2 3
The Data Protection Officer
The contracting entity is Pixel & Tonic, Inc. of Bend, Oregon, and the privacy policy states that personal information is collected and stored in the United States, with a data processing addendum referenced for EU customers and a subprocessor list naming Stripe, Front App, Google Analytics and plugin store developers published with purposes but no locations. Self-managed installation on the customer's own infrastructure is documented, which keeps site content under the customer's control, while the hosting location of the first-party Craft Cloud platform is not stated; the policy itself was last updated in January 2020. 1 2 3
The Skeptic
The contracting entity is Pixel & Tonic, Inc. of Bend, Oregon, and the privacy policy — last updated January 2020 — states collection and storage of personal information in the United States, while linking a data processing addendum restricted to EU customers. Self-managed deployment is documented, so content can sit on the customer's own servers, but no EU hosting statement is given; named subprocessors such as Stripe, Front App and Google Analytics appear with purposes but no locations, and the AI processing location is unknown. 2 3
Pricing transparency
not rated — the vendor publishes no price
Show reasoningHide reasoning
How this is scored
Whether a buyer can compute the annual cost for their team, locales and traffic from public pages alone — seats and contributor roles, locales, content records, API calls and bandwidth, AI credits, and the plan where approval workflows or SSO begin.
0 — No public prices at all; every plan is a sales conversation.
3 — A public "from" price, a free tier, or one priced plan, with the rest on request.
5 — Prices for each plan public with the billing period (per month or per year) and the seats or main limits each includes.
8 — Every plan priced with seats, locales, records, API and bandwidth limits and overage rates stated, AI usage priced or included explicitly, and the plan that unlocks approval workflows, SSO and audit logs named.
10 — Complete cost computability: annual cost derivable for a given team, locale count and traffic, every add-on and overage priced publicly, contract term and renewal conditions stated, and the cost of exporting or leaving the platform zero or published.
The Head of Content
A free trial of Craft Cloud is offered and installing the software binds you to a license, with support plans and SLAs available, but the captured pages state no plan prices, billing periods, or seat and content limits. I cannot compute an annual cost for a team of six plus freelancers from public information. 1 3
The SME Marketer
The captured pages show a free trial and a licence that binds on installation, but no plan prices, seat definitions, locale or content limits anywhere. I cannot compute what a second language and the agency as additional users would cost from public pages alone. 1 3
The Localisation Lead
The captured pages show only a free trial for the first-party hosting platform and a licence that binds on install — we found no public information on plan prices, billing periods, seat or locale limits, or the plan where approval workflows and SSO begin. A buyer cannot compute an annual cost from these pages. 1 3
The Web Engineer
The captured pages show a free trial for the hosting platform and a license that binds on download or install, with support plans and SLAs available on request. We found no public information on plan prices, seat counts, content or usage limits, so an annual cost cannot be computed from the pages alone. 1 3
The Data Protection Officer
The homepage offers a free trial for Craft Cloud and states that support plans and SLAs are available, and the installation documentation warns that downloading or installing Craft binds you to its license. We found no public prices for any plan on the captured pages, so an annual cost for a given team cannot be computed from what is published. 1 3
The Skeptic
The captured pages show a free Craft Cloud trial and support plans and SLAs "available when needed" — with no figures anywhere. We found no public prices for licenses, plans, seats, locales or usage limits, while the installation documentation states that downloading or installing the product by any means binds you to its license; the annual cost is not computable from these pages. 1 3
European sovereignty — proven facts
4 of 6 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity |
Incorporated in US
unverified
Why unverified?Jurisdiction is derived from a postal address block and a storage statement naming the United States; no commercial register entry is cited. |
0/2 pts | 2 Report an error |
|---|---|---|---|
| Hosting location |
Outside the EU
unverified
Why unverified?This covers personal information collected through Pixel & Tonic's website and services; self-hosted Craft CMS deployments store site content on the customer's own servers. |
0/4 pts | 2 Report an error |
| Hosting options |
Self-hostable
unverified
Why unverified?The page never uses the term "self-hosted", and a first-party hosted platform (Craft Cloud) is offered alongside self-managed deployment. |
1/1 pts | 3 Report an error |
| Open source | Not determined | — | uncited Report an error |
| Data processing agreement |
Published, self-serve
unverified
Why unverified?The excerpt only references a link to the addendum and restricts it to EU customers, so the agreement text itself is not shown here. |
1/1 pts | 2 Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about Craft CMS
Is Craft CMS European?
Not determined: the vendor’s pages as captured do not say where Craft CMS is based. Its vendor, Pixel & Tonic, Inc., is incorporated in the United States, per the vendor’s page captured 10 Nov 2026.
Where does Craft CMS store data?
Craft CMS stores customer data outside the EU by default, per the vendor’s page captured 10 Nov 2026.
Does Craft CMS have a free plan?
Not stated on the vendor’s pages as of 10 Nov 2026.
What are the best alternatives to Craft CMS?
As of 19 Nov 2026, the panel rates Kontent.ai (3.5/5), StoryChief (3.5/5) and Scompler (3/5) highest among the other 30 Content Marketing products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is Kontent.ai (EU-Made, Czechia). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: Craft CMS alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 10 Nov 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Data processing agreement. The excerpt only references a link to the addendum and restricts it to EU customers, so the agreement text itself is not shown here.
- Weak sourcing — Legal entity. Jurisdiction is derived from a postal address block and a storage statement naming the United States; no commercial register entry is cited.
- Weak sourcing — Hosting location. This covers personal information collected through Pixel & Tonic's website and services; self-hosted Craft CMS deployments store site content on the customer's own servers.
- Weak sourcing — Hosting options. The page never uses the term "self-hosted", and a first-party hosted platform (Craft Cloud) is offered alongside self-managed deployment.
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
What we left out
A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.
- 28 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 18 integrations facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 1 pricing fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
Sources (11)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor page craftcms.com Checked 10 Nov 2026 Details →
- 2 Privacy policy — found from the homepage craftcms.com Checked 10 Nov 2026 Details →
- 3 Self-hosting / on-premises installation docs — found from the homepage craftcms.com Checked 10 Nov 2026 Details →
- 4 Planning, editorial calendar & briefs — found from sitemap craftcms.com Checked 10 Nov 2026 Details →
- 5 Planning, editorial calendar & briefs — found from sitemap craftcms.com Checked 10 Nov 2026 Details →
- 6 Creation, review & approval — found from sitemap craftcms.com Checked 10 Nov 2026 Details →
- 7 Creation, review & approval — found from sitemap craftcms.com Checked 10 Nov 2026 Details →
- 8 Structured content, localisation & export — found from sitemap craftcms.com Checked 10 Nov 2026 Details →
- 9 Structured content, localisation & export — found from sitemap craftcms.com Checked 10 Nov 2026 Details →
- 10 Publishing, distribution & integrations — found from sitemap craftcms.com Checked 10 Nov 2026 Details →
- 11 Publishing, distribution & integrations — found from sitemap craftcms.com Checked 10 Nov 2026 Details →