contentbird vs Scompler

contentbird

The platform sells Strategy and Research & Planning as modules, the plans meter workflows, and content items carry statuses from which publications can be triggered — so planning exists. But the captured pages never document an editorial calendar with owners and due dates, briefs carrying goal, audience and keywords, or any workload view per person.

Scompler

Briefings on topics, stories and individual posts carry audience, strategic requirements, personas, deadlines, budget and teams, and can be shared with external partners like agencies; the ideas area plus the editorial and topic conferences turn ideas into scheduled stories, and admins assign target topics per user group. That is strategy wired into the plan — we found no public information on recurring formats scheduled as series or workload and deadline views per person.

contentbird

Permissions are properly engineered: standard Admin, Manager, Author and Observer roles plus custom roles with read, edit, delete and publish actions, per-project assignment, secondary permissions, and free unlimited observers and approvers, alongside inline comment threads with mentions and a revision-request loop that returns work to the previous editor. What I don't find is a version history with restore or any audit log recording who released which version — for content that is a legal statement, that trail is the part I'd insist on.

Scompler

PRO users can reject a piece with a reason, set a revision deadline and assign the task to a person or team in a repeatable cycle, and version control records who changed what and when with restore of earlier versions across users. AI usage lands in the standard product audit trail with user and timestamp; we found no public information on inline suggested edits, guest access limited to assigned pieces, or retention of the approval record beyond the stated deletion of all customer data within 30 days of contract end or export handover.

contentbird

Custom fields exist (duplicating a ticket can transfer their values) and localisation works by copying a content ticket into a target language with the original shown alongside in reference mode and filters to find all translations — a real workflow, but duplication-based rather than field-level locales. We found no public information on reusable components, references between entries, or a documented export format; the only data movement shown is outbound through the API.

Scompler

Content sits in a topic–story–post structure, posts can be multilingual with language variants configured per project, and DeepL appears as a named translation connector. Export is documented as a PDF of the current view (max 500 articles) plus the GraphQL API for extracting content and data to external systems; we found no public information on field-level localisation with fallback languages, translation status per locale, or a documented self-service export of content and model together.

contentbird

An open API with a public documentation URL that can push content to CMS, DAM and PIM systems, trigger status changes and publications, and sync tickets with Jira or Trello, plus named connections for WordPress, Drupal, TYPO3, Asana and DeepL, YouTube auto-upload via OAuth and MCP connectors in every plan. The captured pages give different signals on documentation access — a public URL alongside guidance to obtain keys and the full documentation through support — and we found no public information on webhooks, rate limits, SDKs or a status page, while the terms explicitly state no guarantee that the software is available at all times.

Scompler

A GraphQL API page documents extracting content and data to external systems, distributing publish-ready pieces, and letting systems like an intranet or CMS push status back to update workflows, and the Marketplace names connectors across social channels, DAM, intranet and press with a public status page for the SaaS platform. From the integration side, though, we found no public information on API versioning, published rate limits, webhooks on publish or SDKs, and custom marketplace apps with API access are subject to a fee.

contentbird

The assistant runs OpenAI GPT-5.4 by default with GPT-4.1 selectable in a system-wide admin setting that takes effect immediately, further providers are planned, and additional tokens are priced at 86€ per million. On everything that decides rights and risk — whether customer content trains models, opt-out, retention of prompts and outputs, ownership of generated text, EU processing and AI-Act labelling — we found no public information.

Scompler

The AI names its models (Amazon Nova, Anthropic Claude via AWS Bedrock), runs on EU-only inference profiles with conversation history in Frankfurt, provider-level retention of prompts and outputs is effectively zero days, customer data does not train models, and AI actions are recorded in the audit trail with user and timestamp — though prompts and outputs are not included. Web search is off by default and activated per project by an administrator, with Linkup (EU) as default and Brave (US) optional under Standard Contractual Clauses; we found no public information on ownership of generated output being assigned to the customer in the terms.

contentbird

The contracting entity is proven European: contentbird GmbH at Knesebeckstraße 59-61, Berlin, registered at Amtsgericht Charlottenburg under HRB 136392 B with German VAT ID DE 279084703, Berlin as venue, and an external data protection officer in Munich. The captured pages state no hosting location for customer content or backups, no data processing agreement, and no subprocessor list for the service itself — the named subprocessors are marketing tools on the vendor's own website.

Scompler

The contracting entity is Scompler Technologies GmbH in Munich (Amtsgericht München, HRB 240236), a German server is available for larger deployments, AI processing runs EU-only on AWS Bedrock in Frankfurt, and the AI sub-processors are published with locations, purposes and retention — AWS as the only one for inference, Linkup (EU) default and Brave (US) optional. We found no public information on the default hosting region for the main platform's content and backups or a full platform sub-processor list, and AWS as a US-headquartered provider remains exposed to the US CLOUD Act.

contentbird

Per-plan limits are fully public — three, five or fifteen users with projects, workflows, and observer counts per tier — and add-ons are priced exactly: 50€ per additional project and 86€ per additional million tokens, annual billing saving up to 20 percent, with the terms publishing auto-renewal, notice periods and payment terms. But we found no public information giving a price figure for the plans themselves, so an annual total cannot be computed from the captured pages alone.

Scompler

All three plans are public with billing period and seat counts: ONE at € 0 limited to one user, ONE+ at € 19 pro Monat inkl. 2 Nutzer billed monthly by credit card, and PRO at € 199 pro Nutzer / Monat billed annually by invoice, plus custom licensing and named paid add-ons (Scompler AI, Community Management) with 30-day trials for paid marketplace apps. AI credit usage is visible to administrators and additional credits are requested rather than bought at a published price, and we found no public information on prices for add-ons, locales, records or API limits, so an annual cost is not computable from public pages.