Content Marketing
contentbird
EU-Made Report an error0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by contentbird GmbH · www.contentbird.io
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.
contentbird at a glance
- Vendor
- contentbird GmbH
- 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
- Not stated on the vendor’s pages as of 13 Oct 2026
- Panel verdict
- The AI panel rates contentbird 1.5/5, the mean of 6 judges. contentbird, an AI content operations platform from contentbird GmbH, Berlin, scores highest on collaboration and approval at 4 to 5 and distribution and integrations at 4 to 5, crediting four standard roles with publishing as a separately grantable action, custom and per-project permissions, inline and outline comments with notifications, an open API, named WordPress, Drupal and TYPO3 connections, Jira, Trello and Asana sync, DeepL and OAuth YouTube upload. how scores are made
- As of
- Vendor pages captured 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
contentbird, an AI content operations platform from contentbird GmbH, Berlin, scores highest on collaboration and approval at 4 to 5 and distribution and integrations at 4 to 5, crediting four standard roles with publishing as a separately grantable action, custom and per-project permissions, inline and outline comments with notifications, an open API, named WordPress, Drupal and TYPO3 connections, Jira, Trello and Asana sync, DeepL and OAuth YouTube upload. The lowest marks go to pricing transparency at 1 to 1 — the pricing page compares three plans by features with no price, seat count or limit published — and sovereignty at 0 to 2, where legal entity jurisdiction, ownership, data residency and subprocessor exposure are all listed as unknown and the AI assistant runs OpenAI models with no stated processing location. Editorial planning splits between 2 and 4: some credit the planning modules and role-based campaign duties, others the undocumented calendar, briefs and deadline views. Content model and reuse holds at 3 to 3 on duplication-based translation; AI and content rights runs 3 to 4, models named but retention and ownership open.
Speaks for it
- Four standard roles — Admin, Manager, Author, Observer — separate writing from publishing, extended by custom roles and per-project secondary permissions
- Inline and outline comment threads, mentions with email notifications and a change-request loop back to the previous editor are documented
- An open API supports pushing content to CMS, DAM or PIM, triggering publications and syncing tickets with Jira or Trello
- Named integrations include WordPress, Drupal and TYPO3, Asana, DeepL and automatic YouTube upload via OAuth, with MCP connectors on every plan
- Translation by duplication pairs with reference mode, translation filters and carry-over of custom field values
Held against it
- The pricing page compares three plans by features, with no public information on prices, seat counts or limits
- All four sovereignty attributes — legal entity jurisdiction, ownership, data residency and subprocessor exposure — are listed as unknown, with hosting described only as a cloud solution on redundant servers with regular backups
- The AI assistant runs OpenAI models with no public information on prompt or output retention, training on customer content, processing location or ownership of generated output
- Localisation rests on copying whole tickets rather than field-level locales, and the captured data-export article yields no export format
- We found no public information on version history with restore, configurable multi-step approval or an audit log of who released which version
Best for
- You need a review workflow where writing and publishing are separate permissions, backed by custom and per-project roles
- Your team pushes content into WordPress, Drupal or TYPO3 and syncs tickets with Jira, Trello or Asana over an open API
- Your second language can live as deliberate copies of each ticket, translated in reference mode with DeepL named
Avoid if
- You must compute an annual cost from public prices, seat counts or limits before a sales conversation
- Your contract sign-off requires a stated hosting region, subprocessor list or data processing agreement in public materials
- You run the content year on an editorial calendar with due dates, briefs and per-person workload views
- Your AI policy requires answers on prompt retention, training on customer content or output ownership before any assistant touches drafts
The scores
| Criterion | Panel median |
|---|---|
| Planning, editorial calendar & briefs | 1.5 of 5 |
| Creation, review & approval | 2.5 of 5 |
| Structured content, localisation & export | 1.5 of 5 |
| Publishing, distribution & integrations | 2 of 5 |
| AI assistance & content rights | 1.5 of 5 |
| European sovereignty | 1 of 5 |
| Pricing transparency | 0.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 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 captured pages name Strategy and Research & Planning as modules and show task-based feedback loops plus a Manager role responsible for campaign planning, but I found no public information on an editorial calendar, briefs, due-date or late views, or work grouped under campaigns and topics. 2 8 9
The SME Marketer
The platform is sold with strategy, research and planning modules, and the role pages describe campaign planning, executing briefings and a feedback loop that returns work to the responsible editor, with statuses on every content ticket. We found no public information on an editorial calendar with due dates, deadline or workload views per person, or recurring formats scheduled as series — the scheduling layer I would run my content year on is simply not described. 2 8 9 13
The Localisation Lead
A research-and-planning module, campaign planning as a named manager responsibility and briefings that authors execute give evidence of owners and brief-attached work, with feedback loops that reassign a task to the responsible person. We found no public information on a calendar view, due dates, custom statuses or campaign grouping, so the cadence side of the plan stays in the dark. 2 8 9
The Web Engineer
The platform is presented as modules including Strategy and Research & Planning, and the Manager role lists campaign planning among its responsibilities, but the captured pages show no calendar with publish dates, no briefs and no campaign or topic grouping. What is evidenced is task-level structure — authors work only on assigned content and tasks, and feedback is sent back to the previous editor — and status changes can be triggered through the API. We found no public information captured on deadlines or workload views per person, or on an editorial calendar. 2 8 9 13
The Data Protection Officer
The captured pages show a Strategy and a Research & Planning module, campaign planning listed among manager duties, briefings executed by authors, and content tickets with statuses and automatically reassigned responsible persons. What is missing is the backbone: I found no public information on a calendar view, due dates, custom statuses or workload views per person, so the plan is implied by roles rather than evidenced as a scheduling surface. 2 8 9 13
The Skeptic
What the captured pages show are module names, task statuses implied by the API, and passing references to campaign planning and executing briefings inside the role descriptions. The dedicated planning and editorial-calendar pages in the evidence set yielded no confirmed calendar, brief or deadline features. We found no public information on a calendar across channels, briefs carrying goal and audience, per-person workload views, or grouping under campaigns and topics. 2 9 13
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
Inline comment threads, mentions with notifications, a feedback loop that returns work to the previous editor, and roles where publishing is a separately grantable action give me a real review workflow. I found no public information on a version history with restore, suggested edits, freelancer access limited to assigned pieces, or an approval trail recording who released which version. 8 9 5
The SME Marketer
Four standard roles separate writing from publishing, custom roles and per-project permissions control visibility, actions and projects, and inline comment threads, mentions with email notifications and change requests are documented in detail. We found no public information on version history with restore, external guest access for my agency, configurable multi-step approvals or an audit trail recording who released which version, so it earns the middle ground but not more. 5 8 9
The Localisation Lead
Four standard roles plus custom roles spanning visibility, actions (including publish) and projects separate writing from releasing, and comments come in inline and outline form with mention notifications and a revision-request option. We found no public information on version history with restore, suggested edits, guest access limited to assigned pieces, or any audit trail of who released which version. 5 8 9
The Web Engineer
Inline comments tied to selected text, outline comments, mentions with email notifications and a feedback-and-change-request loop are documented, and the role model genuinely separates writing from publishing — Admin, Manager, Author and Observer, plus custom roles where publish is an action granted or withheld per visibility area and project. We found no public information on suggested edits, a version history with restore, guest or freelancer access limited to assigned pieces, multi-step approval with mandatory reviewers, or an audit log recording who released which version. The terms do show a request-revision option in the interface, but no approval trail with user and timestamp is captured. 5 8 9
The Data Protection Officer
Four standard roles separate authoring from publishing, extendable through custom roles with visibility, action and project-level permissions plus secondary permissions per project, and inline comment threads, mentions, email notification and a change-request loop back to the previous editor are documented. I found no public information on version history with restore, configurable multi-step approval or an audit log of who released which version with a timestamp, which for a tool holding campaign drafts and author profiles is the part I would refuse to sign off unseen. 5 8 9
The Skeptic
Inline comments tied to text, outline comments, @mentions with notification, feedback routed back to the previous editor and a revision-request option are confirmed, alongside four standard roles where publishing is a separate permission, custom roles, per-project roles and secondary permissions. We found no public information on version history with restore, guest or freelancer access without a full seat, configurable multi-step approval, or an audit log of edits and releases. 8 9 5
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
Translation runs on the duplication principle — a ticket is copied and edited in another language with reference mode and filters to find translations, and custom field values can be carried over — which is managing locales by duplicating entries rather than field-level localisation. DeepL is named and the API mentions translation workflows, but I found no public information on reusable components or a documented export format. 11 13
The SME Marketer
Translation rests on the duplication principle — an existing content ticket is copied, a target language and optionally another project chosen, and the original displayed alongside the editor — supported by translation filters, carry-over of custom field values and a named DeepL integration. Localisation by copying entries is the entry-level pattern for exactly my second-language use case, and we found no public information on a documented export format for entries and assets, a media library, or field-level language fallback, even though a data-export help page exists among the captured pages. 10 11
The Localisation Lead
Translation rests on the duplication principle — a content ticket is copied and edited in another language — so locales live on copies of the entry, managed by hand with reference mode, translation counts and filters, and custom element values can be carried over on duplication. The captured data-export help page gives no export format, so we found no public information on a documented export of content, model or locales. 10 11
The Web Engineer
Custom fields exist — the duplicate dialog transfers values from custom fields — but translation is explicitly built on the duplication principle: an existing content ticket is copied and edited in another language, managed with reference mode, filters and translation counts, while external translation tools are used by copy and paste; DeepL is named as an integration. A help article on data export exists in the captured material, but its contents were not captured, so we found no public information on a documented export format for entries, model and assets. Field-level localisation with fallbacks, reusable components and a media library are likewise not evidenced, which places this at duplication-based localisation with named custom fields. 10 11 13
The Data Protection Officer
Localisation rests on an explicit duplication principle — copy the ticket, choose a target language, translate in reference mode, with custom field values optionally carried over — which is manual duplication rather than field-level locale management. A help article on data export was captured but yielded no confirmed export format, and I found no public information on a configurable content model, reusable components or a media library. 10 11
The Skeptic
Localisation is confirmed as duplication: an existing content ticket is copied and edited in another language, with reference mode, filters and a translation count to keep the copies findable, and custom fields exist as values carried over on duplicate. A DeepL integration is named and external translation tools work by copy and paste. We found no public information on a documented export format, a media library, reusable components, or field-level localisation with fallbacks — the data-export help page in the evidence set carried no captured content. 11
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
Named CMS connections for WordPress, Drupal and TYPO3, YouTube auto-upload via OAuth, and an open API cover more than a single plugin. The captured pages give different pictures of documentation access — one publishes the API documentation address, the other says the full documentation comes via support or the customer success manager — and I found no public information on webhooks, CRM or analytics connectors, or rate limits. 12 13 3
The SME Marketer
An open API with a public documentation address is described, along with named connections for WordPress, Drupal and TYPO3, project tools such as Asana, Jira and Trello, MCP connectors on every plan, automated translation workflows and automatic YouTube uploads via OAuth. The help pages give two routes to the full documentation — the public address and access via support or the Customer Success Manager — and we found no public information on webhooks, CRM or analytics connections, rate limits, SDKs or a public status page. 2 3 12 13
The Localisation Lead
Named connections cover WordPress, Drupal and TYPO3, Asana alongside Jira and Trello sync, DeepL and an oAuth YouTube auto-upload, with MCP and connectors on every plan, and the API is described with capabilities from triggering publications to pushing content into CMS, DAM and PIM. The captured pages give different routes to the full documentation — a public URL versus access through support or the Customer Success Manager — and we found no public information on webhooks, rate limits, SDKs, a CRM connection or a status page. 2 3 12 13
The Web Engineer
The API is documented at a public URL with a version selector, and its stated capabilities are real distribution plumbing — push content to CMS, DAM and PIM, trigger status changes and publications automatically, sync tickets with Jira, Trello and Asana, and create content in the platform from external systems; WordPress, Drupal and TYPO3 are named alongside YouTube upload over OAuth, DeepL, and MCP connectors on every plan. The captured pages give different pictures of documentation access — one publishes the docs URL, the other routes the full documentation and the API key through support or the Customer Success Manager. We found no public information on webhooks on publish or change, published rate limits, SDKs, preview environments, named CRM or analytics connectors, or a status page, which keeps this below the middle of the scale. 2 3 12 13
The Data Protection Officer
API documentation is published at a public URL and the open API covers transferring content to CMS, DAM or PIM systems, triggering statuses and publications, and syncing tickets with Jira or Trello, with WordPress, Drupal, TYPO3 and Asana named and YouTube videos auto-uploaded via oAuth. No webhooks, rate limits, SDKs, status page or CRM and analytics connectors were captured, and full documentation access runs through support or the customer success manager rather than self-service. 3 12 13
The Skeptic
An open API with a public documentation URL is confirmed, plus named WordPress, Drupal and TYPO3 CMS integrations, Asana, Jira and Trello ticket sync, DeepL, and automatic YouTube upload via OAuth. We found no public information on webhooks on publish and change, any named CRM or analytics connector, published rate limits, SDKs, preview environments or a status page, which is what would move this up. 13 12 3 11
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
The AI assistant names OpenAI with GPT-5.4 as default and GPT-4.1 available, and an admin switches the model system-wide with immediate effect. I found no public information on whether customer content trains the models, where prompts are processed, retention of prompts and outputs, labelling of generated text, or who owns the output. 14 4
The SME Marketer
The models are named — GPT-5.4 by OpenAI as the default, GPT-4.1 available, further providers planned — and an admin can switch the model system-wide. But every question that decides whether my team lets the assistant near our drafts is open: we found no public information on whether customer content trains the models, where prompts are processed or how long they are retained, whether the features can be switched off, labelling of generated text, or who holds the rights to the output. 9 14
The Localisation Lead
The assistant's provider is named — OpenAI, GPT-5.4 as default with GPT-4.1 — switchable system-wide in admin settings with immediate effect, and additional providers beyond OpenAI are planned. We found no public information on whether customer content trains the models, where prompts are processed or retained, an admin off-switch for the features, labelling of generated text, or who holds the rights to the output. 9 14
The Web Engineer
The AI assistant is concrete about models — GPT-5.4 by OpenAI as default, GPT-4.1 available, switchable system-wide by an admin with immediate effect, and further providers beyond OpenAI planned — but a model picker is not an off switch, and the AI Assistant and Trusted Content modules are named without captured detail on what they govern. We found no public information on whether customer content trains the models, where prompts are processed, retention of prompts and outputs, labelling of generated text, or who holds the rights to the output. A named provider with the rights questions left open is where this sits. 4 9 14
The Data Protection Officer
OpenAI is named as the provider with GPT-5.4 as default and GPT-4.1 available, selectable by an admin in system settings — model choice, not governance. I found no public information on prompt or output retention in days, on whether customer content trains the models, on processing location, or on ownership of generated output; none of this appears in the terms, which is where I need the training exclusion to sit. 5 14
The Skeptic
The AI page names OpenAI as provider with GPT-5.4 as default and GPT-4.1 available, switchable system-wide by an admin. It leaves open whether customer content trains models, where prompts are processed, whether the features can be switched off, and who owns generated output, and the captured terms say nothing on any of these. We found no public information on EU processing for AI, prompt retention periods, or labelling of generated text for transparency rules. 14 5
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 terms describe cloud hosting on redundant servers with regular backups, but I found no public information on the contracting entity's jurisdiction, ownership, where content is hosted, or any subprocessor list — while the AI assistant defaults to OpenAI with no stated processing location. 5 14
The SME Marketer
The terms describe cloud hosting on redundant servers with regular backups but state no location, the AI assistant runs OpenAI models with no processing location stated, and we found no public information on the contracting entity, ownership, data residency or a subprocessor list on any captured page, including the legal notice and privacy policy. For a German Mittelstand team, that is a blank exactly where our GDPR comfort needs to stand. 3 4 5 14
The Localisation Lead
The vendor header naming a Berlin GmbH is the only European signal; hosting is described as a cloud solution with redundancy and regular backups but with no location, and the captured privacy policy gives none either. We found no public information on where content, assets or AI prompts are stored and processed, and no subprocessor list, while the AI default runs on OpenAI with no processing location stated. 3 5 14
The Web Engineer
The vendor line presents contentbird GmbH in Berlin, and the terms describe a cloud solution on redundant servers with regular backups, but the captured pages confirm neither the contracting jurisdiction nor any hosting location — the sovereignty attributes for entity, ownership, data residency and subprocessor exposure are all listed as unconfirmed. The one named processor in the chain is OpenAI for the AI assistant, with no statement of where that processing happens or any safeguard for it. We found no public information on EU hosting for content and assets, a data processing agreement, or a published subprocessor list with locations and purposes. 3 5 14
The Data Protection Officer
The terms describe cloud hosting with regular backups on redundant servers, but no hosting region is stated, no subprocessor list exists in the captures, and no data processing agreement was found; the AI assistant runs on OpenAI models with no processing location or safeguard explained. The company carries Berlin provenance, yet the captured legal notice yielded no contracting-entity details, so almost nothing in the chain — hosting, CDN, AI, support — is publicly evidenced. 4 5 14
The Skeptic
The terms describe a cloud service on redundant servers with regular backups but never say where it runs; we found no public information on data residency, a subprocessor list, a DPA, or a contracting entity confirmed on the vendor's own captured pages. The AI assistant is confirmed to run OpenAI models with no statement of processing location. 5 14
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 pricing page compares plans by features, with the multilingual interface and MCP connectors shown on all three, but I found no public information on any price: no per-seat figures, no locale, record or API limits, and no indication of which plan unlocks approval workflows or SSO. 2
The SME Marketer
The public pricing page shows a plan comparison — connectors and the German-English interface marked for every plan — but we found no public information on actual prices, seat counts, or the limits that drive our real cost: additional languages, guest seats for the agency, content records, API calls or AI credits. I cannot begin to compute what a second language plus agency contributors would cost us per year, and the terms only speak of credit card or direct debit for ordered texts. 2 5
The Localisation Lead
The pricing page compares three plans and shows the German/English interface and MCP connectors on each, but the captured pages show no price figures — nothing on seats, locale or record limits, API usage or overages. We found no public information on which plan unlocks approval workflows, SSO or audit logs, and the only pricing-adjacent detail anywhere is text orders billed via credit card or direct debit. 2 5
The Web Engineer
The captured pricing page compares three plans by features — multilingual interface and MCP & connectors on all of them — but no prices, seat counts, locale, content-record, API or bandwidth limits, overage rates or AI credit pricing were captured. We found no public information naming which plan unlocks approval workflows, SSO or audit logs, or on contract term and renewal conditions. An annual cost for a given team and locale count cannot be computed from what was captured. 2
The Data Protection Officer
The captured pricing page compares plans on features — connectors and a German/English interface in every plan — but not a single price figure, seat count, locale limit, record or API limit, or AI credit allowance was captured. From these pages a buyer cannot compute even a starting annual cost; the only pricing-adjacent fact is that marketplace text orders are paid by credit card or direct debit, with the costs unstated. 2 5
The Skeptic
The captured pricing page shows a three-column plan comparison and a multilingual-interface row but no prices, seat counts, locale or record limits, API or AI credit costs. Texts can be ordered in the interface and paid by credit card or direct debit, again with no figure. We found no public information on what any plan costs or on overage rates, so the captured pages do not let a buyer compute an annual cost. 2 5
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 ⚠ unverified | — | uncited Report an error |
|---|---|---|---|
| Ownership | Not determined ⚠ unverified | — | uncited Report an error |
| Data residency | Not determined ⚠ unverified | — | uncited Report an error |
| Subprocessors | Not determined ⚠ unverified | — | uncited Report an error |
Questions about contentbird
Is contentbird European?
Yes. whats-best.ai classifies contentbird as EU-Made.
Where does contentbird store data?
Not stated on the vendor’s pages as of 13 Oct 2026.
Does contentbird have a free plan?
Not stated on the vendor’s pages as of 13 Oct 2026.
What are the best alternatives to contentbird?
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: contentbird alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 13 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 — Ownership, Data residency, Subprocessors, Legal entity. 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.
- 108 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
- 11 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
- 9 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
- 7 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
- 6 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
- 5 pricing 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 hosting 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 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
- 2 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
- 4 sovereignty dimensions could not be confirmed on the vendor’s own pages and are 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 (15)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage www.contentbird.io Checked 13 Oct 2026 Details →
- 2 Pricing page www.contentbird.io Checked 13 Oct 2026 Details →
- 3 Privacy policy www.contentbird.io Checked 13 Oct 2026 Details →
- 4 Legal notice www.contentbird.io Checked 13 Oct 2026 Details →
- 5 Terms of service www.contentbird.io Checked 13 Oct 2026 Details →
- 6 Planning, editorial calendar & briefs — found from sitemap www.contentbird.io Checked 13 Oct 2026 Details →
- 7 Planning, editorial calendar & briefs — found from sitemap www.contentbird.io Checked 13 Oct 2026 Details →
- 8 Creation, review & approval — found from sitemap help.contentbird.io Checked 13 Oct 2026 Details →
- 9 Creation, review & approval — found from sitemap help.contentbird.io Checked 13 Oct 2026 Details →
- 10 Structured content, localisation & export — found from sitemap help.contentbird.io Checked 13 Oct 2026 Details →
- 11 Structured content, localisation & export — found from sitemap help.contentbird.io Checked 13 Oct 2026 Details →
- 12 Publishing, distribution & integrations — found from sitemap help.contentbird.io Checked 13 Oct 2026 Details →
- 13 Publishing, distribution & integrations — found from sitemap help.contentbird.io Checked 13 Oct 2026 Details →
- 14 AI assistance & content rights — found from sitemap help.contentbird.io Checked 13 Oct 2026 Details →
- 15 AI assistance & content rights — found from sitemap www.contentbird.io Checked 13 Oct 2026 Details →