contentbird vs Scompler

contentbird

The platform's modules include Strategy and Research & Planning, plans are metered in projects and workflows, campaign planning is named as a manager responsibility, and content sits in a pipeline with statuses. We found no public information on an editorial calendar view, briefs carrying goal, audience and keywords, or due-date and workload views per person, so the documented level is a list of content with statuses rather than a connected plan.

Scompler

Topic and story planning is well evidenced: an ideas area plus editorial and topic conference toggles carry stories into the review process, and briefings on topics, stories and pieces carry audience, personas, strategic requirements, deadlines, budget and working teams, shareable with external agencies in the TEAM and PRO versions, with administrators configuring target topics and per-group availability under Strategy. We found no public information on keywords inside briefs, per-person workload and deadline views, recurring formats scheduled as series, or coverage-gap and plan-versus-published reporting.

contentbird

Four standard roles (Admin, Manager, Author, Observer) plus custom roles separate writing from publishing — permissions cover visibility, read, edit, delete and publish, and can be assigned per project — while review runs on inline comment threads, outline comments, @mentions and a feedback loop that returns the task to the previous editor. Approvers and observers are plan features and a request-revision option exists, which gives roles, comments and a review step before release. We found no public information on configurable multi-step approvals with mandatory legal or brand reviewers, an audit log of every edit, approval and publish, or retention of the approval trail after the contract ends.

Scompler

A documented release-and-reject cycle exists — PRO users can reject approval with a reason, a revision task with deadline and assignee is created and notified by email — alongside version control that shows who changed what and when and restores earlier versions even across users, and a standard audit trail that records who performed an AI action and when. We found no public information on configurable multi-step approvals, mandatory reviewers such as legal or brand, inline suggested edits, freelancer access limited to assigned pieces, or scheduled publishing that waits for approval.

contentbird

Content carries custom fields and versions (copy last content version, copy custom element values), and translation runs on a duplication principle — a ticket is copied into a target language, translated against a reference view of the original, and filtered back to all its translations, with external tools used by copy-paste. We found no public information on a configurable content model with reusable components, locales managed side by side per entry, or a documented export of the repository in a format such as JSON, CSV or XML.

Scompler

Language variants are configured per project and multilingual posts are created within entries, a GraphQL API extracts data and content into external systems and data lakes, and content and briefings export to PDF with a 500-article limit per run, with DeepL named as a translation connector. The vendor's own security page refers to content models being sent to the AI assistant; we found no public information on a configurable content model with reusable components, field-level localisation with fallback languages, translation workflows with status per locale, or a documented machine-readable export of the whole repository with model and assets.

contentbird

An open API is documented at a public URL and the vendor names CMS integrations for WordPress, Drupal and TYPO3, ticket sync with Jira, Trello and Asana, automated translation workflows, a DeepL integration, and YouTube auto-upload via OAuth, with MCP and connectors on all plans. The captured pages give different access routes for the full API documentation — a public docs link in one place, support or the Customer Success Manager in another — and the terms state that uninterrupted availability is not guaranteed. We found no public information on webhooks, rate limits, SDKs, preview environments or a public status page.

Scompler

Publishing runs to seven named social channels plus press, intranet and asset connectors, the GraphQL API distributes publish-ready content outward and receives status updates back into workflows, and a marketplace lists apps by category with paid add-ons, 30-day trials and API tokens, with a public status page linked in the footer. We found no public information on published rate limits or SDKs, webhooks on publish and change, preview environments, or performance data per piece pulled back from analytics tools.

contentbird

The AI assistant's provider and models are named — OpenAI, with GPT-5.4 as default and GPT-4.1 available — and an administrator can switch the model system-wide, with providers beyond OpenAI planned, which is the model transparency I ask for. We found no public information on whether customer content or prompts are used to train the models, any opt-out, retention of prompts and outputs in days, where AI processing takes place, assignment of rights to generated output in the terms, or marking of generated text for EU AI Act transparency; the captured privacy policy governs the marketing website rather than the platform's AI features.

Scompler

This is unusually well governed: Amazon Nova and Anthropic Claude run via AWS Bedrock on EU-only inference profiles with Frankfurt storage, retention of prompts and outputs at the model provider is effectively zero days, AWS is named as the only AI sub-processor, customer content does not train models, web search is disabled by default and activated per project by an administrator with Linkup (EU) default and Brave (US) under standard contractual clauses, and AI usage is recorded in the audit trail without storing prompts. We found no public information on ownership of generated output being assigned to the customer in the contract terms, a per-feature mapping of model, provider and location, an audit trail of AI-made changes, or a marking feature for AI Act transparency beyond the stated reliance on the assistive-use exemption.

contentbird

The contracting side is clean and European: contentbird GmbH, Knesebeckstraße 59-61, 10719 Berlin, commercial register HRB 136392 B at Amtsgericht Charlottenburg, VAT ID DE 279084703, venue Berlin, and an external data protection officer (IITR Datenschutz GmbH, München). Beyond the entity, we found no public information naming the hosting region for the cloud service, its backups or AI prompts — the terms describe redundant servers and regular backups without a region — and no subprocessor list for the platform itself; the published subprocessors (Google Ireland, Meta, LinkedIn, Vimeo, WebProspector, Usercentrics with possible US transfer) concern the vendor's own marketing website.

Scompler

The entity is named in full and registered in Munich — Scompler Technologies GmbH, Balanstraße 55, Amtsgericht München HRB 240236, VAT DE317404836 — acting as the GDPR controller with an appointed data protection officer, EU standard contractual clauses for US transfers under the Data Privacy Framework, an ISO 27001-certified ISMS, encrypted multi-AZ AWS backups, AI processing in the EU, and a German server available for larger deployments. Sub-processors are disclosed with locations and purposes — AWS for inference, Linkup (EU) and optional Brave (US) for search, Gravatar (US) as CDN, HubSpot only for the newsletter — though AWS as a US-headquartered provider remains exposed to the US CLOUD Act, and we found no public information on ownership or a stated default hosting region for all content.

contentbird

Per-plan limits are public and precise — 3 users with 2 projects and 10 workflows, 5 users with 10 projects, 30 workflows and 10 observers and approvers, 15 users with unlimited projects, workflows, observers and approvers — with add-ons quoted at 50€ per additional project (max. 10 on the lowest plan) and 86€ per additional 1 million tokens, an annual saving of up to 20%, observers free of charge, and renewal, notice periods, prepayment and payment terms stated in the terms. We found no public information on the base plan prices themselves, SSO, audit logs, or API and bandwidth limits, so an annual total for a given team cannot be computed from the captured pages.

Scompler

All three plans are priced publicly with billing period and user limits — ONE at €0 for one user, ONE+ at €19 net per month including 2 users billed monthly by credit card, PRO at €199 net per user per month billed annually on invoice — plus a free tier pitched as the alternative to an Excel editorial plan, 30-day trials for paid marketplace apps, and admin-visible AI credit usage where free credits are consumed first. We found no public prices for the Scompler AI and Community Management add-ons or for additional AI credits, no published limits for locales, records or API usage, and no published statement of which plan unlocks SSO or audit features, though reasoned approval rejection is documented as a PRO feature.