Content Marketing
Contentstack
Rest of world Report an error0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Contentstack Inc. · www.contentstack.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.
Contentstack at a glance
- Vendor
- Contentstack Inc.
- Headquarters
- Not stated on the vendor’s pages as of 13 Oct 2026
- Data hosting
- Not stated on the vendor’s pages as of 13 Oct 2026
- Free plan
- Yes, per the vendor’s own page source, captured 1 Oct 2026
- Panel verdict
- The AI panel rates Contentstack 2/5, the mean of 6 judges. Contentstack, an enterprise headless CMS from Contentstack Inc. how scores are made
- As of
- Vendor pages captured 1 Oct 2026 to 13 Oct 2026; evaluated by the panel 15 Oct 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Contentstack, an enterprise headless CMS from Contentstack Inc. of Austin, Texas, scores highest on collaboration and approval at 6-7: judges cite workflows with named stages such as Draft, Review and Publish, publishing approval rules, a two-distinct-reviewer rule, an audit log recording who moved each entry and when, and five user roles with permissions to entry, field and asset level. It scores lowest on editorial planning and pricing transparency, both 2: beyond workflow stages and a tasks page, judges found no public information on an editorial calendar, briefs or campaign grouping, and none on price figures for the free, Build and Enterprise tiers. Content model and reuse at 5-6 pairs genuine structure with a schema-only export path; distribution and integrations at 5-6 rests on deeply documented GraphQL delivery; AI and content rights sits at 4, sovereignty at 3. The widest spread is one point: the single 6 on collaboration turns on guest access for external writers; the 5s on content model and distribution weigh a schema-only export and the finding of no public information on webhooks more heavily.
Speaks for it
- Workflows add named stages, publishing approval rules and a two-distinct-reviewer minimum, with every transition captured in an audit log.
- Permissions across five user roles reach entry, field and asset level.
- The GraphQL Content Delivery API is publicly documented in depth, with a default rate limit of 80 requests per second per organization, rate-limit headers and endpoints across AWS, Azure and GCP.
- Content types export as a JSON schema from the UI or the Content Management API and re-import with edits retained.
- Entries carry a fallback locale, and multiple locales can be fetched in a single query.
Held against it
- We found no public information on an editorial calendar, briefs, campaigns or due dates.
- We found no public information on price figures, seat or locale limits, overage rates or AI-credit pricing.
- The documented export path covers the content-type schema only; we found no public information on exporting entries, assets or locale data.
- We found no public information on webhooks, SDKs or named connectors to CRM, analytics or translation tools.
- AI products default to Contentstack's Managed LLM, and we found no public information on where prompts are processed, whether customer content trains models, or who owns generated output.
Best for
- You need governed approval — multi-stage workflows, restricted publishers, a two-reviewer rule and a full audit trail earn the highest scores here.
- Your engineers deliver content through a documented GraphQL API with published rate limits and regional endpoints across AWS, Azure and GCP.
- You run multilingual content from one repository, relying on fallback locales and multi-locale queries in a single request.
Avoid if
- Your team plans by editorial calendar, briefs and campaign grouping — the captured pages show workflow stages and a tasks page, and we found no public information on planning views.
- You must compute an annual cost before talking to sales — we found no public information on prices, limits or overage rates.
- You need EEA storage without exceptions — ask the vendor: the public pages we read do not show it
- Your legal review must clear AI use up front — AI products default to Contentstack's Managed LLM, and we found no public information on where prompts are processed or who owns generated output.
The scores
| Criterion | Panel median |
|---|---|
| Planning, editorial calendar & briefs | 1 of 5 |
| Creation, review & approval | 3.5 of 5 |
| Structured content, localisation & export | 3 of 5 |
| Publishing, distribution & integrations | 3 of 5 |
| AI assistance & content rights | 2 of 5 |
| European sovereignty | 1.5 of 5 |
| Pricing transparency | 1 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 features; content is created as standalone entries with no calendar, status or owner.
3 — A shared calendar with publish dates and simple statuses, but no briefs, no campaigns or topics to group work under, and no notion of who owns a piece.
5 — An editorial calendar across channels with owners, due dates and custom statuses, briefs attached to each piece, and content grouped by campaign or topic cluster.
8 — Strategy is connected to the plan: 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 workflow documentation gives me named stages like Draft, Review and Publish, a Tasks page for pending actions, and user-and-role assignments that clarify ownership — a real sense of who owns what. We found no public information on an editorial calendar, briefs that carry goal and audience to the writer, campaigns or topic clusters, or views of what is due or late, so a strategy has nothing scheduled to hang on. 5 6
The SME Marketer
Workflow stages with named owners and a tasks page give us statuses and accountability for pending work, which is more than nothing. But I found no public information on an editorial calendar, briefs that carry goal and audience to the writer, or any grouping of pieces into campaigns or topic clusters — for a team that plans by quarter, the plan would still live in a spreadsheet. 5 6
The Localisation Lead
Workflows can name stages like Draft, Review and Publish and a Tasks page shows pending actions with assigned users, which is the only planning-adjacent evidence I found. We found no public information on an editorial calendar, briefs, campaigns or due dates, so my German and French editors would still run the plan in a spreadsheet. 5
The Web Engineer
The workflow engine gives entries stages like Draft, Review and Publish, a Tasks page for pending actions, and users or roles assigned to stages, which is status and ownership but not planning. I found no public information on an editorial calendar, briefs, campaigns or topic clusters, due dates, or per-person workload and deadline views. 5 6
The Data Protection Officer
We found no public information on an editorial calendar, briefs, or grouping of work under campaigns and topics. What the captured documentation shows is review machinery — named workflow stages such as Draft, Review and Publish, plus a tasks page where assigned users move entries between stages — with no view of what is due, late or missing across channels. 5 6
The Skeptic
The workflow documentation gives teams named stages, a tasks page for pending actions and users assigned per stage, which is more than standalone entries with no status or owner. But we found no public information on an editorial calendar with publish dates, briefs that carry goals and keywords to the writer, or campaigns and topics to group work under, so turning strategy into a schedule is not evidenced. 5 6
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.
0 — Single-user editing with no comments, no roles beyond admin, and no record of changes.
3 — Comments and a version history exist, but every user can publish, external writers need a full seat, and approval is a status anyone can set.
5 — Roles that separate writing from publishing, inline comments and suggested edits, a version history with restore, and guest or freelancer access limited to assigned pieces.
8 — Configurable multi-step approval per content type or market, mandatory reviewers (legal, product, brand), 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
This is the part I answer for, and it holds up: configurable multi-step workflows with named stages, approval rules so only authorized users can approve or publish, a two-distinct-reviewer rule against self-advancement, custom permissions down to entry, field and asset level, and an audit log capturing who moved an entry and when. We found no public information on inline comments and suggested edits, freelancer access limited to assigned pieces, scheduled publishing that waits for approval, or preservation of the exact version each approver released, which is what legal would need in a dispute. 5 6
The SME Marketer
Multi-step workflows with publishing approval rules, a two-distinct-reviewer rule, and an audit log recording who moved each entry and when are exactly what our legal reviewer needs, and permissions reach down to entry, field and asset level with five roles. But I found no public information on inline comments, version restore, or guest access for the agency, so my external-writer question stays open. 5 6
The Localisation Lead
Approval is engineered seriously: multiple workflows per content type, approval rules restricting who may publish, a two-distinct-reviewer rule, and an audit log recording who moved an entry and when, with custom roles reaching entry and field level. We found no public information on inline comments, suggested edits, freelancer access or scheduled publishing that waits for approval, and the only stated post-termination treatment is deletion of content within 180 days rather than a retained, exportable approval record. 5 6 3
The Web Engineer
Workflows are configurable per content type and per branch, with approval rules restricting who may publish, a rule requiring at least two distinct reviewers before content advances, and an audit log recording who moved an entry and when; permissions reach entry, field and asset level across five roles. I found no public information on scheduled publishing that waits for approval, guest access for external writers, or restore from version history, which keeps this short of the top of the scale. 5 6
The Data Protection Officer
Approval is governed, which is what I sign off on: workflows add named stages, publishing approval rules restrict who may approve or publish, at least two distinct reviewers can be required before content advances, and every stage transition is captured in an audit log showing who moved the entry and when. Five user roles with permissions assignable down to entry, field and asset level separate duties. We found no public information on inline comments, suggested edits, version history with restore, or guest and freelancer access limited to assigned pieces. 5 6
The Skeptic
Workflows are configurable per content type with approval rules that restrict who may approve or publish, a requirement for at least two distinct reviewers, and an audit log recording who moved an entry and when, while custom roles reach down to entry, field and asset level. We found no public information on scheduled publishing that waits for approval, preservation and export of the exact version each approver released, or audit-trail retention beyond the stated 180-day deletion of content after termination. 3 5 6
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 — Content stored as formatted pages with no structure, one language per entry, and no export beyond copy and paste.
3 — Custom fields or templates exist, but localisation means duplicating entries, assets live elsewhere, and the only export is HTML or a CSV of titles.
5 — A configurable content model with reusable components, field-level localisation with fallback languages, a media library with alt text, and an export of entries and assets in JSON or a similar documented format.
8 — References between entries, variants per market or audience, translation workflows with status per locale and connectors to translation services named, 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
The model is genuine structure — content types with Reference and JSON custom fields, reusable Global fields, group fields, fallback locales, multi-locale queries and early-access entry variants. Export stops at the model: the documented path covers the JSON schema of a content type, editable and re-importable with changes retained, while we found no public information on exporting entries, assets and locales together, on translation workflow connectors, or on a media library with alt text. 7 8 10
The SME Marketer
The model fits our German/English set-up: reusable global fields, reference datatypes, a fallback-locale argument and multi-locale queries in one request, with variants available in early access. Export, however, is evidenced only for the content-type JSON schema — re-importable with edits retained — and I found no public information on exporting entries, assets or locales, nor a named translation connector. 8 10
The Localisation Lead
Global fields, group fields, JSON rich text and entry references give genuinely reusable structure, and locales sit on entries with a fallback locale and multi-locale queries rather than duplicated copies — the part I care about most. The documented export, however, covers only the content type schema: we found no public information on exporting entries, assets or locale data, on translation status per locale, or on connectors to translation services, and entry variants are offered only as an early access program. 10 7 8
The Web Engineer
The content model is real and partly portable: content types export as JSON from the UI and the management API, edits to the exported file are retained on re-import, and the delivery API exposes references, global fields, fallback locales, multi-locale queries and early-access variants. I found no public information on a documented export of entries and assets themselves or on translation-service connectors, so portability is evidenced for the model more than for the content. 7 8 10
The Data Protection Officer
Structure is genuinely present: global and group fields, reference and JSON field types, a fallback locale, multi-locale fetching in a single query, and entry variants — the latter only in an early access program. The JSON schema of any content type exports from the UI or the Content Management API and re-imports with edits retained. We found no public information on exporting entries and assets themselves in a documented format, on translation workflow status per locale, or on connectors to named translation services. 7 8 10
The Skeptic
The repository is genuine structure — global and group fields, references, JSON rich text, fallback locales, multi-locale queries in one request, and early-access variants per audience — and the model exports as JSON from the UI or API with edits retained on reimport, a real round trip. But the captured pages document export of the model only: we found no public information on exporting the entries and assets themselves, version history included in that export, or connectors to translation services. 7 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 — Content leaves only by copy and paste; no API, no webhooks and no named integrations.
3 — Publishing to one CMS through a plugin, a handful of named integrations, and an API that is mentioned but not publicly documented.
5 — Publishing to websites and several channels from one place, a publicly documented REST or GraphQL API, webhooks on publish and change, and integrations named for at least the common CMS, CRM and analytics tools.
8 — A versioned API with published rate limits and SDKs, 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
The GraphQL Content Delivery API is documented publicly to real depth — default rate limits with plan dependency, rate-limit headers, HTTP 429 semantics, regional endpoints across AWS, Azure and GCP, a GraphiQL explorer and a Postman collection — and Launch hosts projects with live preview. We found no public information on webhooks on publish and change, named connections to the CMS, CRM, analytics or translation tools a marketing stack already runs, SDKs, an integration marketplace or a public status page. 9 10 2
The SME Marketer
The GraphQL delivery API is publicly documented down to rate limits, response headers, error semantics, regions across three clouds and live preview, with Launch to host the project — that is a genuinely deep delivery story. But I found no public information on webhooks, SDKs, or a single named connector for the CRM, analytics or SEO tools our stack already runs. 9 2
The Localisation Lead
The GraphQL delivery API is publicly documented in real depth — a default rate limit of 80 requests per second per organization with rate limit headers and HTTP 429 semantics, seven regional endpoints across AWS, Azure and GCP, dedicated infrastructure, live preview, and a Launch module to host projects. We found no public information on webhooks, SDKs, a connector directory naming CMS, CRM, analytics or translation tools, or a public status page. 9 2
The Web Engineer
The GraphQL Content Delivery API is publicly documented with published rate limits of 80 requests per second per organization by default, plan-dependent, rate-limit response headers, HTTP 429 semantics, read-only delivery tokens, dedicated endpoints across seven regions on AWS, Azure and GCP, live preview with branch headers, and Launch to host the project. I found no public information on webhooks, SDKs, a maintained integration directory, per-piece performance data from analytics or a status page — and webhooks on publish are half of what headless promises. 9 10 2
The Data Protection Officer
The GraphQL Content Delivery API is publicly documented in depth: endpoints across AWS, Azure and GCP in North America, Europe and Australia, a default origin rate limit of 80 requests per second per organization with rate-limit headers and 429 semantics, GraphiQL and a Postman collection, live preview, and a Launch module that hosts the project. We found no public information on webhooks on publish and change, on named connections to CRM, analytics or translation tools, on SDKs, or on a public status page. 9 10 2
The Skeptic
The GraphQL delivery API is publicly documented in depth — authentication, a default 80 requests per second per organization with rate-limit headers and 429 semantics, endpoints across AWS, Azure and GCP regions, a dedicated-infrastructure option, GraphiQL, a Postman collection and live preview, plus a Launch hosting module. We found no public information on webhooks, SDKs, a directory of maintained connectors to the common CMS, CRM and analytics tools, or a public status page. 9 10 2
AI assistance & content rights
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, and who holds the rights to output.
0 — AI writing features with no statement on which model is used, where content is sent, or whether it is used for training.
3 — An AI page that names a provider but leaves open whether customer content trains models, where prompts are processed, or whether the features can be switched off.
5 — The model providers named as subprocessors, customer content excluded from training stated in the terms, AI features switchable per workspace by an admin, and ownership of generated output assigned to the customer.
8 — EU processing for AI features stated or selectable, retention of prompts and outputs given in days, generated or AI-edited content markable for EU AI Act transparency, and brand voice or terminology rules applied without uploading content to train 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
Global AI Settings let an Owner or Admin switch AI on or off per product, credit consumption is documented, Agent OS advertises LLM choice with a stated default of Contentstack's Managed LLM, and first use requires accepting AI Terms of Service. Beyond a homepage reference tying source openness to the EU AI Act's transparency article, we found no public information on the underlying model providers and where prompts are processed, whether customer content trains the models, retention of prompts and outputs, labelling of generated text, or who owns the generated output — the questions my legal review starts with. 1 11 12 2
The SME Marketer
An admin can switch each AI product on or off centrally with per-product toggles, there is LLM choice with a Contentstack Managed LLM as default, and credits are only consumed when enabled — real admin control. But I found no public information on whether my drafts train the models, where prompts are processed, or who owns the generated output; the AI Terms of Service must be accepted, yet the captured pages do not show what those terms say about rights, and the only EU AI Act reference concerns ranking sources for transparency, not labelling of generated text. 1 11 12 2
The Localisation Lead
Global AI Settings let an admin switch each AI product off, credits are consumed only while enabled, a Managed LLM is the stated default with LLM choice advertised, and first use requires accepting separate AI terms. Beyond that governance scaffolding we found no public information on whether customer content trains models, where prompts are processed or retained, or who holds rights to generated output; the EU AI Act reference concerns third-party answers that the Canoe product monitors, not labelling of the platform's own output. 12 11 1
The Web Engineer
AI is administratively controllable: a global settings page with per-product toggles and an Enable All link, credits consumed only by enabled products, first-time acceptance of AI Terms of Service, a managed LLM by default and LLM choice in Agent OS. I found no public information on whether customer content trains the models, where prompts are processed, retention of prompts and outputs in days, or who holds the rights to generated output. 1 11 12 2
The Data Protection Officer
An Owner or Admin can switch AI on or off per product, disabled products consume no credits, and first use requires accepting Contentstack's AI Terms of Service — real governance levers, with a homepage reference to the EU AI Act beside them. But the default is an unnamed Contentstack Managed LLM, and I found no public information naming the underlying model providers as subprocessors, stating where prompts are processed or retained in days, excluding customer content from training in the terms, or assigning rights to generated output. 1 11 12 2
The Skeptic
AI is at least governable: a Global AI Settings page with per-product toggles an Owner or Admin can switch off so disabled products consume no credits, a first-use terms acceptance, and a mention of LLM choice under Agent OS. But the default is a "Contentstack Managed LLM" that names no provider, and we found no public information on whether customer content trains models, where prompts are processed, retention periods, labelling of generated text, or who holds rights to the output. 11 12 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.
0 — Non-EU contracting entity, no statement on where content is hosted, and subprocessors unnamed.
3 — Content hosted in the EU on request or on a higher plan only, or the subprocessor list is absent, or AI and analytics features send content outside the EU without an explained safeguard.
5 — EU hosting stated for content and assets, a DPA available, but the contracting entity or significant parts of the chain (CDN, AI, support) are non-EU without a stated safeguard.
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 Contentstack Inc. of Austin, Texas, storage defaults to the United States, and the privacy policy describes an EEA instance holding European customers' data in Ireland and Germany — while stating that data shared with subprocessors located outside the EEA still leaves it. Enterprise buyers can choose an AWS, Azure or GCP data center, but we found no public information on a published subprocessor list with locations and purposes or on where AI prompts are processed. 3 2
The SME Marketer
European customers' data is stated to be stored in Ireland and Germany, with all other customers in the United States, and the EEA instance explicitly excludes data shared with subprocessors located outside the EEA — a carve-out that touches content without naming anyone. I found no public information on a subprocessor list, a data processing agreement, or where the Managed LLM processes our prompts, and enterprise cloud choice across AWS, Azure and GCP does not say who is behind it. 3 12 2
The Localisation Lead
The privacy policy states an EEA instance storing European customers' data in Ireland and Germany while all other customers' data is stored in the United States, and the same sentence excepts data shared with subprocessors located outside the EEA. The contracting company is American, and we found no public information on a published subprocessor list, a data processing agreement, or where AI prompts are processed. 3 9 2
The Web Engineer
The privacy policy states an EEA instance stores European customers' data in Ireland and Germany while all other customers' data is stored in the United States, and the same text acknowledges data shared with subprocessors located outside the EEA. Enterprise buyers can choose AWS, Azure or GCP, but I found no published subprocessor list with locations and purposes on the captured pages and no statement on where AI prompts are processed. 3 9 2
The Data Protection Officer
The privacy policy states an EEA instance stores European customers' data in Ireland and Germany while all other customers' data is stored in the United States, and the EEA instance itself carves out data shared with subprocessors located outside the EEA. The captured pages leave the contracting entity's jurisdiction unconfirmed, though the vendor presents itself as a US company, and the enterprise tier offers a choice of AWS, Azure or GCP data centers. We found no public information on a published subprocessor list with locations and purposes, on European ownership, or on where AI prompts are stored and processed — my sign-off questions go unanswered. 3 2
The Skeptic
The privacy policy states an EEA instance storing European customers' data in Ireland and Germany, with all other customers' data in the United States, and enterprise choice of AWS, Azure or GCP. The contracting entity is Contentstack Inc. of Austin, Texas, the EEA statement itself carves out data shared with subprocessors outside the EEA, the captured pages publish no subprocessor list with locations, and we found no public information on where AI prompts are processed. 3 2
Pricing transparency
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 starting price per month, but what it includes is vague and the limits that drive the real cost (locales, records, API calls, AI credits) are unstated.
5 — Plans priced per seat with their main limits listed, but at least one commonly incurred cost (extra locales, overage on records or API calls, AI credits, guest contributors) is missing or "on request".
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
The captured pricing pages name tiers — a free one including Content Cloud and Agent OS with no credit card, a Build tier with pay-as-you-go overages, and an Enterprise tier that shows a free-trial invitation rather than a price — but we found no public information on price figures, seat counts, locale or record limits, API and bandwidth quotas, AI-credit pricing, or the plan where approval workflows, SSO and audit logs begin. I could not begin to compute an annual cost for my team of six plus freelancers from these pages. 2 12 2
The SME Marketer
Tier names, a free tier with its contents listed and pay-as-you-go overages are named, but no price figure for any plan, seat, locale or AI credit appears anywhere — I cannot compute what a second language and the agency as guests would cost. The GraphQL rate limit 'depends on your plan' with the plan-dependent figures unstated, and AI credits require an active subscription whose price I found no public information on. 2 9 12 2
The Localisation Lead
The tiers name what they include — the free tier lists the headless CMS, Brand Kit and Agent OS with no credit card required, every tier includes Agent OS, and Build advertises pay-as-you-go overages — but we found no public information on price figures or on the limits that drive cost for seats, locales, records, API calls or AI credits. I cannot compute an annual price for a trilingual team from the public pages. 2 2 11
The Web Engineer
The pricing page names the tiers — a free one requiring no credit card, Build with pay-as-you-go overages, and Enterprise behind a free trial — but the captured pages show no figures for any paid tier, and nothing quantifies seats, locales, records, API limits or AI credits. An AI Credits administration page exists, yet no cost terms for credits appear in the captured material. 2 11 2
The Data Protection Officer
The captured pricing pages name a free tier, a Build tier with pay-as-you-go overages and an Enterprise tier with a free trial, and state that every tier includes Agent OS — but we found no public information on prices for any tier, on seat, locale, record, API or bandwidth limits, on AI credit pricing, or on overage rates. No annual cost can be computed from public pages alone. 2 12 2
The Skeptic
The pricing page names a free tier with the headless CMS, Brand Kit and Agent OS, a Build tier with pay-as-you-go overages, and an Enterprise tier with trial and a success manager, but no public price figure for any tier appears anywhere in the captures. We found no public information on seat counts, locale or record limits, overage rates, or AI-credit pricing, so a buyer cannot compute a year's cost for a given team, locale count and traffic. 2 11 2
European sovereignty — proven facts
0 of 4 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 | Not determined | — | uncited Report an error |
|---|---|---|---|
| Ownership | Not determined | — | uncited Report an error |
| Data residency | Not determined | — | uncited Report an error |
| Subprocessors | Not determined ⚠ unverified | — | uncited Report an error |
Questions about Contentstack
Is Contentstack European?
No. whats-best.ai classifies Contentstack as Rest of world.
Where does Contentstack store data?
Not stated on the vendor’s pages as of 13 Oct 2026.
Does Contentstack have a free plan?
Yes. Contentstack has a free plan, per the vendor’s page captured 1 Oct 2026.
What are the best alternatives to Contentstack?
As of 15 Oct 2026, the panel rates CoreMedia (3/5), Storyblok (2.5/5) and Contently (2.5/5) highest among the other 14 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 CoreMedia (EU origin, foreign-owned). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: Contentstack alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 1 Oct 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Subprocessors. Not confirmed on the vendor’s own pages as captured.
- 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.
- 21 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
- 9 subprocessors 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
- 4 compliance 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
- 4 support 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
- 3 data 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
- 3 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
- 2 legal 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 sovereignty dimension could not be confirmed on the vendor’s own pages and is shown as unknown. Know more? Tell us
- 6 of the readings below were written against an earlier fact sheet — a fact has been corrected, added or pulled since. Until the panel next runs on this product you are reading the older judgement. Know more? Tell us
Sources (12)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage www.contentstack.com Checked 13 Oct 2026 Details →
- 2 Pricing page www.contentstack.com Checked 13 Oct 2026 +1 earlier capture: 1 Oct 2026 Details →
- 3 Privacy policy www.contentstack.com Checked 13 Oct 2026 Details →
- 4 Terms of service www.contentstack.com Checked 13 Oct 2026 +1 earlier capture: 1 Oct 2026 Details →
- 5 Creation, review & approval — found from sitemap www.contentstack.com Checked 13 Oct 2026 Details →
- 6 Creation, review & approval — found from sitemap www.contentstack.com Checked 13 Oct 2026 Details →
- 7 Structured content, localisation & export — found from sitemap www.contentstack.com Checked 13 Oct 2026 Details →
- 8 Structured content, localisation & export — found from sitemap www.contentstack.com Checked 13 Oct 2026 Details →
- 9 Publishing, distribution & integrations — found from sitemap www.contentstack.com Checked 13 Oct 2026 Details →
- 10 Publishing, distribution & integrations — found from sitemap www.contentstack.com Checked 13 Oct 2026 Details →
- 11 AI assistance & content rights — found from sitemap www.contentstack.com Checked 13 Oct 2026 Details →
- 12 AI assistance & content rights — found from sitemap www.contentstack.com Checked 13 Oct 2026 Details →