Content Marketing
Scompler
EU-Made Report an error0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Scompler Technologies GmbH · scompler.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.
Scompler at a glance
- Vendor
- Scompler Technologies 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
- Yes, per the vendor’s own page source, captured 13 Oct 2026
- Panel verdict
- The AI panel rates Scompler 2.5/5, the mean of 6 judges. Scompler Technologies GmbH of Munich builds a content strategy and planning platform for DACH communications teams; the vendor cites more than 450 organisations and 25,000 users worldwide. 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
Scompler Technologies GmbH of Munich builds a content strategy and planning platform for DACH communications teams; the vendor cites more than 450 organisations and 25,000 users worldwide. The bench scores it highest on AI and content rights, 7 to 8: models are named as Amazon Nova and Anthropic Claude on AWS Bedrock with EU-only inference, provider retention of prompts and outputs is effectively zero days, customer data is excluded from training, and AI actions land in the audit trail — though we found no public information on ownership of generated output or EU AI Act marking. Pricing transparency scores 1 to 2 — no monetary price is published and paid plans route through an individual offer — and sovereignty 3 to 4, with a German server tied to large content volumes and more complex organisations and no public information on default content hosting, subprocessors or a data processing agreement. Editorial planning and distribution sit at 6 to 7. Persona-weighted totals run from 4.8 to 5.9; every criterion spans a single point and the flagged split check reports none.
Speaks for it
- Names its AI models — Amazon Nova and Anthropic Claude on AWS Bedrock — with EU-only inference and provider retention of prompts and outputs effectively zero days.
- Excludes customer data from AI training, presents AI outputs as drafts, and records AI actions in the product audit trail.
- Runs briefings at topic, story and piece level carrying audience, personas, deadlines, budget and working teams, shareable with agencies.
- Turns approval rejections into revision tasks with a stated reason, deadline and assignee, on version control that shows who changed what and restores earlier versions.
- Offers a documented GraphQL API for distributing publish-ready content plus a marketplace naming seven social networks, Staffbase, Presspage and DeepL.
Held against it
- Publishes no monetary price for any paid plan, which is reached through an individual offer.
- Meters AI usage in credits that the two AI modes consume differently, with no public pricing for credits or seat and usage limits.
- We found no public information on the default hosting region for content and backups, a subprocessor list with locations, or a published data processing agreement.
- Ties the German server to organisations with a lot of content and more complex setups.
- Shows a PDF export of a customised view as the documented in-product export, with no public information on reusable components or fallback languages.
Best for
- You are a blogger, creator or small team replacing a spreadsheet editorial plan and want to start on the free ONE plan.
- You plan communications as topics, stories and pieces and need briefings with audience, personas, deadlines, budget and working teams shared across departments or with an agency.
- You want AI assistance where the models, provider, EU-only inference location and audit trail are publicly documented.
- You distribute publish-ready content to seven social networks, an intranet via Staffbase, or press via Presspage through a documented GraphQL API.
Avoid if
- You need to compute an annual cost from public prices before talking to sales, since paid plans are presented through an individual offer.
- You need German hosting on a smaller or simpler setup, as the German server is offered for large content volumes and more complex organisations.
- You depend on a structured export of entries, model and assets together, as the documented in-product export is a PDF of a customised view.
- Your policy bars any US-linked processing, since the AI web search option includes a US provider (Brave Search) and newsletter sending uses HubSpot.
The scores
| Criterion | Panel median |
|---|---|
| Planning, editorial calendar & briefs | 3.5 of 5 |
| Creation, review & approval | 3 of 5 |
| Structured content, localisation & export | 2.5 of 5 |
| Publishing, distribution & integrations | 3 of 5 |
| AI assistance & content rights | 4 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 briefs are real: topic, story and piece cards carry audience, personas, strategic guidelines, deadlines, budget and working teams, and can be shared with agencies, while strategy-level topics and the editorial and topic conference stages turn ideas into stories for scheduled work. What I cannot find is the calendar discipline I run on — per-person workload and deadline views, visibility of what is late, and recurring formats — so I stop between the mid and high anchors. 5 6 1 2
The SME Marketer
Planning is genuinely built around strategy: briefs exist on topic, story and article level carrying audience, personas, deadlines, budget and working teams, stories are grouped under topics and pushed through topic and editorial conference views, and admins pin target topics per user group in the strategy area. We found no public information on workload or deadline views per person or recurring formats scheduled as series, so I stop short of the top band. 5 6 1
The Localisation Lead
Briefings run at topic, story and piece level carrying audience, strategic requirements, personas, deadlines, budget and working teams, with an ideas area and editorial and topic conferences that turn ideas into scheduled stories. I found no public information on custom statuses, per-person workload views or recurring formats scheduled as series. 1 5 6
The Web Engineer
The strategy is genuinely connected to the plan: topic plans, story cards and an ideas area feed editorial and topic conferences, admins define target topics under Strategy, and briefings carry audience, strategic requirements, personas, deadlines, budget and work teams, exportable and shareable with agencies. Approval rejections spawn workflow tasks with owners and deadlines, but we found no public information on workload or deadline views per person, custom statuses, or recurring formats scheduled as series. 1 5 6 7 10
The Data Protection Officer
Briefings exist at topic, story and piece level carrying audience, strategic requirements, personas, deadlines, budget and working teams, admins configure target topics per user group, and editorial and topic conferences with an ideas area turn communication ideas into reviewable stories. The platform is positioned around real-time editorial planning, but we found no public information on per-person workload or deadline views, custom statuses, or recurring formats scheduled as series. 1 2 5 6
The Skeptic
Work is grouped as topics, stories and contributions under a strategy, with briefings that carry audience, strategic requirements, personas, deadlines, budget and working teams, and an ideas area feeding the editorial and topic conferences — that is a genuine strategy-to-plan connection. We found no public information on workload or deadline views per person, recurring formats scheduled as series, or any plan-versus-published reporting. 1 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
Rejection with a written reason, a revision deadline, a named owner and an email notification, a repeatable release cycle, and versioning that shows who changed what and when with restore — that is most of the release trail I answer for, and a product audit trail exists that records who acted and when. I found no public information on inline comments and suggested edits, freelancer access limited to assigned pieces, or scheduled publishing that waits for approval, which keeps it below the higher anchor. 7 8 14 9
The SME Marketer
Approval is a real workflow, not a status anyone can set: approvers can reject with a reason, the rejection creates a revision task with its own deadline and assignee, the cycle is repeatable, and version control shows who changed what when and restores earlier versions across users, while briefs and content can be shared with agencies and external users. We found no public information on inline comments or suggested edits, guest access limited to assigned pieces, or configurable multi-step approval with mandatory reviewers, which keeps me in the middle. 6 7 8
The Localisation Lead
The release function supports approval, rejection with a reason, a revision deadline and task assignment to a person or team, and version control shows who changed what and restores earlier versions. I found no public information on roles separating writing from publishing, inline suggested edits, multi-step approval per content type, or how long the audit trail is retained. 7 8 9 14
The Web Engineer
The release function is a real loop — rejection with a stated reason, a revision task assigned to a person or team with its own deadline, email notification, repeatable cycles — and version control shows who changed what and restores earlier versions, though the captured documentation covers social media posts specifically. We found no public information on inline comments or suggested edits, on roles separating writing from publishing, or on guest access limited to assigned pieces; an audit trail is confirmed for AI actions with user and timestamp, but we found no public information on a full edit-approval-publish audit trail. 6 7 8 9 14
The Data Protection Officer
The approval workflow records reasoned rejections that create revision tasks with deadlines and named assignees, version control shows who changed what and when with restore across users, and AI actions land in the standard product audit trail with user and timestamp. We found no public information on role-based publishing permissions, inline comments and suggested edits, mandatory reviewers, or a stated retention period for the audit trail. 7 8 14
The Skeptic
Approval is a real gate: reasoned rejection with a revision deadline, task assigned to a person or team, a repeatable cycle, on top of a version history that shows who changed what and restores earlier versions across users; an audit trail is referenced for AI actions. We found no public information on inline comments or suggested edits, guest access limited to assigned pieces, configurable multi-step approval, or scheduled publishing that waits for approval. 7 8 14
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
Language variants are configured per piece, DeepL is available as an integration, and a documented GraphQL API can extract content outward and mirror asset structures from external DAMs. But I found no public information on reusable components, field-level localisation with fallback languages, or a documented bulk export of entries, model and assets — the in-product export shown is a PDF of a customised view. 9 10 11 12
The SME Marketer
Language variants are configured once under strategy and then used within posts, which is what I would need for a second language, DeepL is listed for translation, and content leaves through a documented GraphQL API plus PDF export rather than copy-and-paste. We found no public information on reusable components, field-level fallback languages, or a self-service export of content and model together. 9 10 11 12
The Localisation Lead
Language variants are configured once per project and multilingual pieces created, so locales sit on the contribution rather than on copies, and a DeepL connector plus a GraphQL API for extracting data and content exist. But the documented structured export I insist on is not evidenced: the knowledge base shows a PDF export of a custom view, and while a data export before termination is confirmed, no format is named. I found no public information on per-locale translation status, fallback languages, reusable components, or a self-service export of content, model, locales and assets. 9 10 11 12 14
The Web Engineer
Language variants are configured per project and posts can be multilingual, DeepL is available as a connector, and content is extractable through the GraphQL API or exportable as a PDF of a customised view, with export available before termination. We found no public information on reusable components, field-level localisation with fallback languages, or a documented self-service export of entries, model and assets together — and no migration tooling is evidenced. 9 10 11 12 14
The Data Protection Officer
Language variants are configured per workspace and multilingual pieces are created side by side, DeepL is offered as an integration, and a documented GraphQL API extracts content and asset structures to external systems while the in-product export produces PDFs of the customised view. We found no public information on reusable components, fallback languages, a media library with alt text, or a documented export of the full repository together with its model. 9 10 11 12
The Skeptic
Multilingual posts are configured as language variants within a contribution rather than by duplicating entries, and a GraphQL API extracts content into external systems — but the only export format documented on the captured pages is a PDF of the current view. We found no public information on reusable components, field-level localisation with fallback languages, or translation workflow status per locale; DeepL is named as a connector. 9 10 11 12
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
A GraphQL API moves publish-ready content such as press releases and website texts to external systems in both directions and feeds data lakes and dashboards, and the marketplace names connectors for seven social networks, asset systems, Staffbase, Presspage and DeepL, with a public status page for the platform. I found no public information on webhooks, published rate limits or SDKs, and no named CRM or analytics connector beyond category headings. 11 12 1
The SME Marketer
Distribution is broad and named: seven social channels, press via Presspage, intranet via Staffbase, asset systems via Canto, Celum and Frontify, and a documented GraphQL API that pushes publish-ready content out and lets external systems write workflow status back. The marketplace is a real integration directory and a public status page exists for the SaaS platform, but we found no public information on webhooks, published rate limits or SDKs, or a CRM connector. 1 11 12
The Localisation Lead
A marketplace with named connectors across social channels, asset management, analytics, intranet and press, a GraphQL API publicly described for distributing publish-ready content to external systems and receiving updates back, and a public SaaS status page. I found no public information on webhooks on publish and change, SDKs, published rate limits, or per-piece performance data pulled back from analytics. 1 11 12
The Web Engineer
A publicly documented GraphQL API distributes publish-ready content to external systems and accepts write-back that updates workflows, and a marketplace names maintained connectors for seven social networks, several DAM and cloud-drive services, Staffbase, Presspage and DeepL, with a SaaS status page linked from the homepage. We found no public information on webhooks on publish or change, published rate limits, an API versioning or deprecation policy, SDKs, or preview environments — all of which I would need before building delivery on this. 1 11 12
The Data Protection Officer
A publicly documented GraphQL API carries publish-ready content out to external, CMS and intranet systems and takes status back into workflows, a marketplace names connectors across social, asset management, press and intranet categories, and a SaaS status page is linked from the site. We found no public information on webhooks, published rate limits or SDKs, or named CRM and analytics connectors. 1 11 12
The Skeptic
A marketplace names seven social networks plus asset-management systems, Staffbase, Presspage and DeepL, a public status page exists, and the GraphQL API pushes publish-ready content to external systems and receives data back to update workflows. We found no public information on webhooks, published rate limits, SDKs, or preview environments. 1 11 12
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
This is unusually well documented for my purposes: the foundation models are named as Amazon Nova and Anthropic Claude on AWS Bedrock, inference stays in the EU, the provider stores and logs nothing, customer data is stated never to be used for training, web search is off by default and activated per project by an administrator, and AI use lands in the audit trail with tenant-level permission scoping. What I found no public information on is ownership of generated output, EU AI Act transparency marking, or any contractual indemnity — the first thing legal will ask me. 13 14 5
The SME Marketer
This is what I scrutinise hardest and it holds up: models and providers are named (Amazon Nova and Anthropic Claude via AWS Bedrock), inference runs entirely in the EU, customer data is stated never to train models, provider-side retention of prompts and outputs is effectively zero days, web research is off by default until an admin enables it per project, and AI usage lands in the audit trail with who, when and which function. The assistant grounds its answers in my own strategy, personas and project data instead of a shared trained model. We found no public information on who owns the generated output or on EU AI Act labelling of AI-generated text, which is the first thing my legal review asks. 13 14
The Localisation Lead
Models are named (Amazon Nova, Anthropic Claude) and run EU-only on AWS Bedrock with provider-side retention of effectively zero days, customer data excluded from training, AI usage events recorded in the audit trail, outputs kept as drafts under human review, and web search off by default with an EU provider as the default. I found no public information on ownership of generated output, EU AI Act labelling of generated text, or a per-workspace admin switch for the AI features. 2 13 14
The Web Engineer
The AI documentation is unusually concrete: models named as Amazon Nova and Anthropic Claude on AWS Bedrock with EU-only inference, no training on customer data, prompts not stored at the provider, conversation history held in Frankfurt until the parent entity is deleted, tenant-scoped permissions, web search off by default with its processing location selectable, and AI actions recorded in the audit trail. We found no public information on marking generated text for EU AI Act transparency or on output rights and indemnity written into contract terms. 2 13 14
The Data Protection Officer
The models, provider and location are named — Amazon Nova and Anthropic Claude on AWS Bedrock with EU-only inference — prompts and outputs are not stored at the provider, effectively zero days, training on customer content is excluded, and AI actions are recorded in the audit trail with web search off by default and administrator-activated. The training exclusion sits in a knowledge-base security page rather than evidenced contract terms, and we found no public information on ownership of generated output, EU AI Act transparency marking, or an indemnity written into the terms. 2 13 14
The Skeptic
The AI governance disclosure is the strongest thing here: models named as Amazon Nova and Anthropic Claude on AWS Bedrock, EU-only inference, provider retention of prompts and outputs effectively zero days, customer data excluded from training, web search off by default with an EU processor, outputs only as drafts, and AI actions recorded in the audit trail. We found no public information on who owns generated output, on labelling for EU AI Act transparency, or on any indemnity written into the terms. 13 14
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
AI processing is stated to run entirely in the EU on AWS Bedrock with conversation history stored in Frankfurt, and a German server is offered for large content volumes and more complex organisations; the newsletter names Hubspot as a processor. I found no public information confirming where platform content is hosted by default, the contracting entity on the vendor's own pages, or a published subprocessor list with locations and purposes. 2 14 3 1
The SME Marketer
AI processing is stated to run entirely in the EU with conversation history stored in Frankfurt, and a German server is offered, though the wording ties it to organisations with a lot of content and more complex setups. We found no public information on where the main content hosting runs by default, on a published subprocessor list with locations and purposes, or on a DPA, and the contracting entity's jurisdiction is not confirmed on the vendor's own captured pages, so I can only credit the AI-location clarity. 2 14
The Localisation Lead
AI processing is stated to run entirely in the EU (Frankfurt, AWS Bedrock with EU-only inference profiles), which is the transparency I want on the AI chain. However, a German server is offered only in connection with larger or more complex organisations, and I found no public information confirming the contracting entity's jurisdiction, a general statement on where content and assets are hosted, or a subprocessor list with locations and purposes. 2 14
The Web Engineer
The captured pages point to German operation — a German server available for larger setups, AI processing entirely within the EU on AWS Bedrock with Frankfurt storage for conversation history, and Hubspot named as an Article 28 processor for the newsletter. Beyond that we found no public information on the contracting entity's jurisdiction or on the hosting location for content, assets and backups on the vendor's own pages, and no public information on a published subprocessor list with locations and purposes. 2 3 4 14
The Data Protection Officer
The vendor is recorded as a Munich GmbH offering a German server for larger setups, AI processing is stated to run entirely in the EU on AWS Bedrock with conversation history stored in Frankfurt. We found no public information on the default hosting region for content and backups, the ownership structure, a published data processing agreement, or a subprocessor list with locations and purposes; the newsletter names HubSpot as a processor and web search optionally routes queries through a US provider. 2 3 4 14
The Skeptic
A German server is available "Für viel Content und komplexere Organisationen", which reads as the higher tier only, and AI processing is stated to run entirely in the EU on AWS Bedrock with conversation history stored in Frankfurt. We found no public information on the contracting entity's jurisdiction from the captured pages, on where content is hosted for the standard plans, on a published subprocessor list, or on a data processing agreement; the privacy policy names Hubspot as processor for the newsletter. 2 3 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 names a free plan and tiers aimed at small teams through to corporations, plus paid add-ons for Scompler AI and community management, and AI usage is metered in credits — but the paid plans are presented through an individual quote. I found no public information on actual prices for the paid plans, seat counts, locale or record limits, or credit rates, so I cannot compute a year's cost from what is published. 2 6 13 7
The SME Marketer
For my concrete question — what the plan costs with a second language, an agency as guests and AI credits — the public pages give no answer: a free ONE plan, further tiers with named target audiences, and paid add-ons like Scompler AI and Community Management are described, but we found no public information on euro figures per seat, per-locale or guest pricing, AI credit prices, or the limits that drive the real cost, with larger needs routed to a custom offer. The free tier and the named plan structure keep this above nothing, but I cannot compute an annual cost from what is public. 2 12 13
The Localisation Lead
Plan tiers are named with their target audiences, a free ONE plan exists, AI and Community Management are paid add-ons and custom licensing is a sales conversation — but the captured pages show no price figures, no seat or usage limits, and no pricing for AI credits even though the two AI modes consume them differently. I found no public information on any numeric price or on which plan unlocks approval workflows. 2 12 13
The Web Engineer
The pricing page shows a free ONE plan and plan tiers by team size, but the only stated path for paid plans is an individual offer, and Scompler AI and Community Management are paid add-ons with no published prices even though AI features consume credits. We found no public information on seat prices, seat, locale, record or API limits, AI credit pricing, or which plan unlocks which approval or access features beyond the release function being tied to PRO — so an annual cost cannot be derived from public pages. 2 6 7 13
The Data Protection Officer
The pricing page names a free plan, tiers by team size, and paid add-ons for Scompler AI and Community Management, and knowledge-base pages place briefings in TEAM and reasoned approval rejection in PRO. We found no public information on any monetary price, on seat, locale or usage limits, or on AI credit pricing; the path shown for paid plans is an individual offer, even though the AI modes are described as consuming credits at different rates. 2 6 7 13
The Skeptic
The pricing page names plans — ONE free, ONEPLUS, PRO — with target audiences and directs buyers to an individual offer with flexible licence packages, but we found no public prices for any paid plan, no seat or limit figures, and AI credits are referenced in the AI FAQ without a price. An annual cost is not computable from these pages; the paid tiers are a sales conversation. 2 13
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 | — | uncited Report an error |
| Data residency | Not determined ⚠ unverified | — | uncited Report an error |
| Subprocessors | Not determined ⚠ unverified | — | uncited Report an error |
Questions about Scompler
Is Scompler European?
Yes. whats-best.ai classifies Scompler as EU-Made.
Where does Scompler store data?
Not stated on the vendor’s pages as of 13 Oct 2026.
Does Scompler have a free plan?
Yes. Scompler has a free plan, per the vendor’s page captured 13 Oct 2026.
What are the best alternatives to Scompler?
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: Scompler 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 — 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.
- 8 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
- 8 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 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
- 2 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
- 1 data fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 1 integrations fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 1 legal fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 3 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 (14)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage scompler.com Checked 13 Oct 2026 Details →
- 2 Pricing page scompler.com Checked 13 Oct 2026 Details →
- 3 Privacy policy scompler.com Checked 13 Oct 2026 Details →
- 4 Legal notice scompler.com Checked 13 Oct 2026 Details →
- 5 Planning, editorial calendar & briefs — found from sitemap kb.scompler.com Checked 13 Oct 2026 Details →
- 6 Planning, editorial calendar & briefs — found from sitemap kb.scompler.com Checked 13 Oct 2026 Details →
- 7 Creation, review & approval — found from sitemap kb.scompler.com Checked 13 Oct 2026 Details →
- 8 Creation, review & approval — found from sitemap kb.scompler.com Checked 13 Oct 2026 Details →
- 9 Structured content, localisation & export — found from sitemap kb.scompler.com Checked 13 Oct 2026 Details →
- 10 Structured content, localisation & export — found from sitemap kb.scompler.com Checked 13 Oct 2026 Details →
- 11 Publishing, distribution & integrations — found from sitemap scompler.com Checked 13 Oct 2026 Details →
- 12 Publishing, distribution & integrations — found from sitemap kb.scompler.com Checked 13 Oct 2026 Details →
- 13 AI assistance & content rights — found from sitemap kb.scompler.com Checked 13 Oct 2026 Details →
- 14 AI assistance & content rights — found from sitemap kb.scompler.com Checked 13 Oct 2026 Details →