Content Marketing
TYPO3
Provenance unknown Report an error0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by TYPO3 GmbH · typo3.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.
TYPO3 at a glance
- Vendor
- TYPO3 GmbH
- Headquarters
- Not stated on the vendor’s pages as of 3 Nov 2026
- Data hosting
- Not stated on the vendor’s pages as of 3 Nov 2026
- Free plan
- Not stated on the vendor’s pages as of 3 Nov 2026
- Panel verdict
- The AI panel rates TYPO3 2/5, the mean of 6 judges. TYPO3, an open-source content platform from TYPO3 GmbH of Düsseldorf, is presented as a central hub for brand presence, lead generation and campaign management. how scores are made
- As of
- Vendor pages captured 3 Nov 2026; evaluated by the panel 4 Nov 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
TYPO3, an open-source content platform from TYPO3 GmbH of Düsseldorf, is presented as a central hub for brand presence, lead generation and campaign management. Its strongest criterion is content model and reuse, minimum 6 and maximum 6, on reusable templates, side-by-side localized editing, source-linked translations with change tracking, and unlimited websites and languages from one installation — with no public information on a documented export. Editorial planning scores 1 to 2 — calendars, briefs, owners and due dates unevidenced — and approval steps, version restore and audit logs likewise (collaboration and approval, 3 to 4). AI and content rights spans 2 to 4: DeepL and Mittwald are named; models, training use, opt-outs and output rights are not. Sovereignty spans 4 to 6: the vendor is a German entity; its website runs at Hetzner with a data processing agreement; where customer content and AI prompts are processed goes unstated. The disagreement sits in pricing transparency, 0 to 3: judges crediting the no-license-fee open-source core scored above those weighing the absence of any price figure.
Speaks for it
- Content model and reuse scored a minimum of 6 and a maximum of 6, on reusable templates, side-by-side localized editing and connected translations with change tracking
- One installation publishes unlimited websites and languages, with translation workflows and a named DeepL translation extension
- Granular access rights assign roles for editors, teams and regions, with a preferred backend language per editor including right-to-left scripts
- The imprint establishes a European contracting entity — TYPO3 GmbH of Düsseldorf, registered at Amtsgericht Düsseldorf — with an appointed German data protection officer
- The platform core is open source and community-supported, presented as a Digital Public Good, with a public demo available
Held against it
- Editorial planning scores range from 1 to 2, with no public information on editorial calendars, briefs, owners or due dates
- No public information on approval steps before publishing, version history with restore, or an audit log recording who released which version
- AI and content rights scores range from 2 to 4, with no public information on underlying models, whether customer content trains them, opt-outs or rights to generated output
- No public information on a documented API, webhooks, SDKs or rate limits — integrations arrive through a curated program of technology partners on 24-month terms
- No public information on where customer content, assets and AI prompts are stored and processed for the product itself, or on a customer-facing data processing agreement
Best for
- You publish many websites and languages from one installation and want create-once content adapted per language and region without duplication
- Your regional teams localize content under a central brand strategy and need roles assignable per editor, team and region
- You prefer an open-source, community-supported core with a European contracting entity and delivery through agency partners
Avoid if
- You need planning built in — the captured pages document campaign and landing-page workflows rather than calendars, briefs or deadline views
- You publish legally sensitive content requiring gated approvals, version restore and an audit log before release — the pages document access roles, not release governance
- You build integrations yourself — the pages present a curated Official Integrations & Services program tied to 24-month technology partnerships rather than public API documentation
- You must close AI governance questions first — DeepL translations and the Mittwald Smart Extension Builder are named, with no public information on processing location, training use or output rights
The scores
| Criterion | Panel median |
|---|---|
| Planning, editorial calendar & briefs | 1 of 5 |
| Creation, review & approval | 1.5 of 5 |
| Structured content, localisation & export | 3 of 5 |
| Publishing, distribution & integrations | 2.5 of 5 |
| AI assistance & content rights | 1.5 of 5 |
| European sovereignty | 2.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 at all; the product only stores or renders content.
3 — A calendar or list view of content with publish dates and statuses.
5 — An editorial calendar across channels with owners, due dates and custom statuses, and content grouped by campaign, topic or channel.
8 — Strategy connected to the plan: briefs carrying goal, audience and keywords attached to each piece, 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 position the platform as a central marketing hub uniting brand presence, lead generation and campaign management, where marketing teams create, test and launch landing pages independently. I found no public information on an editorial calendar, briefs carrying goal and audience to the writer, owners and due dates, or any view of what is due, late or missing. 1 4
The SME Marketer
The captured pages position TYPO3 as a hub where marketing teams build landing pages and unite brand presence, lead generation and campaign management, but we found no public information on an editorial calendar, briefs carrying goal, audience and keywords, or views of what is due, late or missing. 4 1
The Localisation Lead
The captured campaign page positions TYPO3 as a central marketing hub for brand presence, lead generation and campaign management, with marketing teams creating, testing and launching landing pages independently and integrated forms feeding CRMs. We found no public information on an editorial calendar, briefs carrying goal, audience and keywords, or any view of what is due, late or missing. 4 1
The Web Engineer
The captured marketing use-case page positions TYPO3 as a central hub uniting brand presence, lead generation and campaign management, with landing pages created, tested and launched by marketing teams independently. That is campaign framing rather than a planning capability: we found no public information on an editorial calendar, briefs, owners, due dates or content statuses. 4
The Data Protection Officer
The captured marketing-campaign page frames the platform as a central hub for brand presence, lead generation and campaign management, where marketing teams create, test and launch landing pages themselves. We found no public information on an editorial calendar, briefs carrying goal, audience and keywords, per-person deadline views, or plan-versus-published reporting. 4
The Skeptic
The German marketing page sells the platform as a central hub uniting brand presence, lead generation and campaign management, and lets teams create, test and launch landing pages quickly and independently. Beyond that narrative we found no public information on an editorial calendar, briefs, owners, due dates, custom statuses or workload views. 4 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 — published content is a legal statement (UWG, Heilmittelwerbegesetz, the imprint duty).
0 — A single-user tool; content cannot be shared with or reviewed by others.
3 — Several users working on content, with comments or a version history.
5 — Roles and permissions that separate writing from publishing, comments on content, a version history with restore, and an approval or review status before publishing.
8 — Configurable multi-step approval per content type or market, mandatory reviewers (legal, product, brand), inline suggested edits, guest or freelancer access limited to assigned pieces, 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
Granular access rights let me assign roles for editors, teams and regions, each editor works in their own backend language, and translations linked to their source carry automatic change tracking. But I found no public information on comments or inline suggested edits, a version history with restore, an approval status that gates publishing, or an audit log recording who released which version. 1 5
The SME Marketer
Role assignment for editors, teams and regions is documented, and translations can be linked to their source with automatic change tracking; we found no public information on approval steps before publishing, reviewer comments, version restore or an audit trail of who released which version. 5 1
The Localisation Lead
Granular access rights with roles assignable for editors, teams and regions are documented, and each editor can set a preferred backend language, with strict access controls named as a design principle. We found no public information on comments on content, version history with restore, approval steps before publishing, or an audit log recording who released which version. 5 1
The Web Engineer
Assignable roles for editors, teams and regions, with regional teams localizing under a central brand strategy, evidence several people working on the same content with permission separation. We found no public information on comments, version history with restore, approval steps or an audit log — and for published content that approval trail is exactly what I would insist on before calling it release-ready. 1 5 6
The Data Protection Officer
Granular access rights let roles be assigned for editors, teams and regions, alongside vendor statements on strict access controls and dedicated security teams. We found no public information on approval or review statuses before publishing, version history with restore, or an audit log recording who released which version — for content that is a legal statement, that is the part I sign off on. 1 5
The Skeptic
Granular access rights with roles for editors, teams and regions, plus translations linked to their source with automatic change tracking, are documented alongside strict access controls. We found no public information on comments, version restore, approval steps, mandatory reviewers or an audit log recording who released which version — the part that matters when published content is a legal statement. 5 1
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 — Not a content store; the product keeps no content of its own (for example a pure scheduling or analytics tool).
3 — Templates or custom fields for content, a media library, and content in several languages.
5 — A configurable content model or content types with reusable components, locales managed side by side for each entry, and an export of entries in JSON, CSV, XML or a similar documented format.
8 — References between entries, field-level localisation with fallback languages, variants per market or audience, translation workflows with status per locale and named translation-service connectors, 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
Templates, content elements and features are reusable across sites, the localized content overview shows locales side by side while editing, translations link to their source with automatic change tracking, and translation workflows come with a named DeepL connector — a create-once structure adapted for languages and regions without duplication. I found no public information on a documented export of the whole repository, on field-level fallback languages, or on market-specific variants. 1 5 6
The SME Marketer
Create-once content adapted per language and region, reusable templates and content elements across sites, a side-by-side localized overview, Connected and Copy translation modes with workflow support for unlimited languages, and a named DeepL translation extension cover my German-plus-second-language case well; we found no public information on a documented export format for entries or field-level fallback languages. 5 6 1
The Localisation Lead
This is the heart of my brief, and much of it is there: reusable templates and content elements across sites, a localized content overview showing languages side by side in columns, connected translations linked to the source with automatic change tracking, a named DeepL translation extension, and unlimited sites and languages from one installation. What the captured pages do not show is a documented export of content, model, locales and assets, so portability — my test of whether a repository is an asset or a hostage — stays unevidenced. 5 6 1
The Web Engineer
Localisation is the strongest part of the captured pages: content viewed side by side per language, translations linked to the source with automatic change tracking, translation workflows, a named DeepL connector, reusable templates and content elements across sites, and domain modelling through the extension tooling. The open question is portability: we found no public information on a documented, self-service export of content, model, locales and assets, and that is where a repository proves itself to me. 1 5 6 8
The Data Protection Officer
Templates, content elements and features are reusable across unlimited sites, translations link to their source with automatic change tracking, a localized overview shows locales side by side in columns, and translation workflows plus a named DeepL extension are documented. We found no public information on field-level localisation with fallback languages, per-locale translation status, or a documented self-service export of content, model, locales and assets. 1 5 6
The Skeptic
Content is documented as reusable structure: shared templates and content elements across sites, a localized overview showing languages side by side in columns, copy and connected translation modes with change tracking, and a named DeepL connector across unlimited sites and languages. For the exit I found no public information on a documented export of content, model, locales and history — the only portability statement captured is the privacy-policy right to personal data in a commonly used, machine-readable format, which is not a content export. 5 6 1 3
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 — A closed tool; content leaves only by copy and paste.
3 — Publishing to one website or CMS, and a few named integrations.
5 — Publishing to websites and several channels from one place, a publicly documented API or webhooks, and integrations named for common CMS, CRM or analytics tools.
8 — A versioned API with published rate limits and SDKs, webhooks on publish and change, 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
All websites and languages publish from a single installation across a multi-domain page tree, ERP and CRM integration is claimed for enterprise setups, and named connections exist — DeepL translations, a cookieless analytics extension built into the backend, and SOLR, KeyCloak and UserCentrics add-ons — alongside a curated Official Integrations & Services program whose listings require a 24-month technology partnership. I found no public information on a documented API, webhooks or SDKs. 1 4 5 8
The SME Marketer
Unlimited websites and languages from a single installation, claims of seamless ERP and CRM integration, a curated Official Integrations and Services program delivered by technology partners, and cookieless TYPO3 Analytics bringing performance data into the backend are documented; we found no public information on a publicly documented API or webhooks. 1 4 8 5
The Localisation Lead
Publishing covers unlimited websites, microsites and landing pages from a single installation, and a curated Official Integrations and Services program delivered by technology partners on 24-month terms names pieces such as DeepL translations and TYPO3 Analytics, alongside stated ERP and CRM integration. We found no public information on a documented API, webhooks, SDKs or rate limits. 5 8 1 4
The Web Engineer
Unlimited websites and languages published from a single installation, a curated Official Integrations & Services program with named partners such as the toujou website builder, a cookieless analytics extension with AI guidance, and stated integration with ERP and CRM systems — that is real reach. But the captured pages give me nothing on the delivery surface itself: we found no public information on API documentation, webhooks, rate limits, SDKs or preview environments, and I read a content platform's promises through its API first. 1 4 5 8
The Data Protection Officer
Publishing covers unlimited websites and microsites from a single installation, integrations are named for ERP and CRM systems and analytics platforms, and a curated Official Integrations & Services program delivers maintained connectors through technology partners on 24-month terms. We found no public information on a documented API, webhooks, published rate limits, or a status page. 1 4 5 8
The Skeptic
One installation publishing unlimited sites and languages is documented, with named connections such as DeepL, SOLR, KeyCloak and UserCentrics, cookieless analytics with AI guidance in the backend, and claimed seamless ERP/CRM integration. We found no public information on a documented API, webhooks, rate limits, SDKs or a status page, and the Official Integrations & Services listing is a curated 24-month technology partnership rather than an open directory. 1 5 8 4
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 under the EU AI Act, and who holds the rights to output.
0 — The vendor states that customer content trains its models with no opt-out, or reserves the rights to AI output for itself.
3 — AI writing features described with what they do, and a general statement on how content is handled by them.
5 — The AI model provider named, a statement that customer content does not train models, and AI features that an admin can switch off.
8 — Model providers listed as subprocessors, EU processing for AI features stated or selectable, retention of prompts and outputs given in days, ownership of generated output assigned to the customer in the terms, generated content markable for EU AI Act transparency, and brand voice or terminology rules applied without training 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 that is documented does concrete things: an open-source Smart Extension Builder generates extension code and connects to coding assistants via MCP, the analytics extension offers AI-powered guidance, and DeepL handles translations in the system. I found no public information on the underlying models or where they run, whether customer content trains them, any opt-out, retention of prompts and outputs, EU AI Act labelling, or who holds the rights to generated output. 5 8
The SME Marketer
Named AI capabilities exist — DeepL translations inside the CMS, an open-source Smart Extension Builder from Mittwald, and AI guidance in TYPO3 Analytics — but we found no public information on how content is handled by them, whether customer content trains models, output ownership, admin off-switches or EU AI Act labelling, which is exactly what I need answered before letting an assistant near my drafts. 5 8
The Localisation Lead
AI assistance is described concretely — DeepL translations directly in the CMS, an open-source Smart Extension Builder from Mittwald connecting to coding assistants via MCP, and AI-powered guidance inside TYPO3 Analytics. We found no public information on the models and providers behind these features, where prompts are processed, whether customer content trains anything, opt-outs, EU AI Act labelling, or the rights to generated output. 8 5
The Web Engineer
The AI features are described concretely and providers are named — DeepL for translations directly in the CMS, Mittwald behind the open-source Smart Extension Builder, and AI-powered guidance inside the privacy-first analytics extension. We found no public information on whether customer content trains any model, on admin switch-off, retention of prompts and outputs, or on who holds the rights to generated output. 5 8
The Data Protection Officer
AI features are described concretely: an open-source Smart Extension Builder from Mittwald CM Service GmbH generating extension code and connecting via MCP, AI-powered guidance inside the cookieless TYPO3 Analytics, and DeepL translations. We found no public information on which models process content, whether customer content trains them, any opt-out, retention of prompts and outputs, where AI processing runs, or how output rights are assigned in the terms. 5 8
The Skeptic
AI features are described only by what they do: generating extension code (Smart Extension Builder, an open-source tool from Mittwald, connectable via MCP), AI-powered DeepL translation, and AI guidance inside analytics. We found no public information on the underlying models, where AI processing runs, whether customer content trains them, any opt-out, EU AI Act labelling of generated text, or who holds the rights to output. 8 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; dimensions the evidence does not establish are unknown, not non-European.
0 — Vendor, contracting entity and hosting all shown to be outside the EU, with no data processing agreement offered.
3 — A privacy policy and a data processing agreement offered, with hosting or the contracting entity outside the EU or not established.
5 — EU hosting stated for content and assets, with a data processing agreement offered.
8 — EU contracting entity, content, assets and backups stored in the EU on named infrastructure, subprocessor list published with locations and purposes, and AI processing location stated.
10 — Sovereign end to end and evidenced: European ownership, EU entity, every hosting, CDN, AI and support subprocessor European or optional, self-hosting or a European cloud offered, and certifications published.
The Head of Content
The contracting entity is firmly European: TYPO3 GmbH of Düsseldorf, registered at Amtsgericht Düsseldorf, with a German data protection officer, the vendor's own site hosted by Hetzner Online GmbH in Gunzenhausen under a data processing agreement, and a German partner in Fürth delivering a SaaS website builder. I found no public information on where customers' content and AI prompts are processed or on a subprocessor list for the product itself; the vendor's own website does name US-domiciled tools with transfers based on EU standard contractual clauses. 2 3 8
The SME Marketer
The imprint names TYPO3 GmbH in Düsseldorf with a Handelsregister entry, German VAT ID, named representatives and a German data protection officer, the vendor's own site is hosted at Hetzner in Gunzenhausen with a data processing agreement concluded, and the platform is open source with a global community; we found no public information on where customer content, backups or AI prompts are processed, or on a subprocessor list for the product itself. 2 3 5
The Localisation Lead
The contracting entity is TYPO3 GmbH, registered at the district court in Düsseldorf, the vendor's site runs on Hetzner in Gunzenhausen with a data processing agreement and a German data protection officer, and the platform is presented as open source and a Digital Public Good. We found no public information on where customer content, assets and AI prompts are stored and processed for the product itself, and the privacy policy states that tools of companies domiciled in the United States are used on the website. 2 3 6
The Web Engineer
The contracting entity is TYPO3 GmbH in Düsseldorf with a commercial register entry and a German VAT number, the vendor's own site runs on Hetzner in Gunzenhausen under a data processing agreement, a data protection officer is appointed, and the privacy policy names its subprocessors with addresses, flagging US transfers under standard contractual clauses. The open gaps concern the product's own footprint: we found no public information on where customer content is processed in TYPO3 deployments, and no stated processing location for the AI features. 2 3 6
The Data Protection Officer
The imprint establishes a German contracting entity in full — TYPO3 GmbH, Düsseldorf, register court and number, VAT IDs, supervisory board — and the privacy policy names Hetzner Online GmbH in Gunzenhausen as host with a concluded data processing agreement and an appointed data protection officer; the platform is open source and a German website builder from DFAU GmbH in Fürth sits in the partner program. Those captures concern the vendor's own website, however, and we found no public information on where customer content and AI prompts are processed by the product, a customer-facing processing agreement, a product subprocessor list, or published certifications. 2 3 8
The Skeptic
The contracting entity is solidly European: TYPO3 GmbH of Düsseldorf, registered at Amtsgericht Düsseldorf with a German VAT ID, a German data protection officer, and a German host (Hetzner) named for the vendor's own website. For the product itself we found no public information on where customer content, assets or AI prompts are stored and processed, or on a data processing agreement offered to customers; the privacy policy's processor list, including US-based Gravatar and Vimeo, covers the vendor's website, not customer projects. 2 3
Pricing transparency
not rated — the vendor publishes no price
panel disagrees
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 public "from" price, a free tier, or one priced plan, with the rest on request.
5 — Prices for each plan public with the billing period (per month or per year) and the seats or main limits each includes.
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 core is public: the platform is open source, community-supported and presented as a Digital Public Good, so the software itself carries no license price. Everything an enterprise buys around it — Extended Long Term Support, certifications, official integrations and services, training — is named without prices on the captured pages, delivery runs through a partner-matching service proposing three to five agencies, and I found no public information on seats, limits, or what any paid offering costs. 1 5 6 8
The SME Marketer not rated — no public information
We found no public information on pricing transparency: the captured pages list Extended Long Term Support, certifications, official integrations, TYPO3 Analytics and training as offerings and mention encrypted payment methods, but no plan price, seat, locale or guest-editor cost appears, so the annual cost for my team, a second language and agency guests cannot be computed from what was captured. 1 3 8
The Localisation Lead
The captured pages name commercial services — Extended Long Term Support, certifications, TYPO3 Analytics, official integrations tied to a 24-month partnership — alongside a free demo, but no price figure appears anywhere. We found no public information on plan prices, seats, limits, overages, or which plan unlocks capabilities such as approval workflows or single sign-on. 1 8
The Web Engineer not rated — no public information
We found no public information on pricing in any captured page: Extended Long Term Support, certifications, official integrations and services, the analytics extension and the toujou website builder are all described without a single figure, so a buyer cannot compute an annual cost from public pages. The open-source nature of the platform core is stated, but the commercial offerings around it carry no public prices. 1 6 8
The Data Protection Officer
The core platform is open source, supported by a global community, with a public demo and no license fee shown, which functions as the free tier. Extended long-term support, certifications, official integrations, TYPO3 Analytics and training are named without prices, and delivery runs through an agency-matching service and 24-month technology partnerships, so an annual cost cannot be computed from the captured pages. 1 5
The Skeptic
The captured pages name what money buys — Extended Long Term Support, Certifications, Official Integrations & Services, TYPO3 Analytics, Official Training, and matching with three to five agencies — but we found no public price, plan, billing period, seat, locale or usage limit on any captured page. What the invoice does when a third locale or an API overage arrives is therefore not computable from these pages. 1 8
European sovereignty — proven facts
0 of 6 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 |
|---|---|---|---|
| Hosting location | Not determined ⚠ unverified | — | uncited Report an error |
| Hosting options | Not determined | — | uncited Report an error |
| Open source | Not determined | — | uncited Report an error |
| Data processing agreement | Not determined | — | uncited Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about TYPO3
Is TYPO3 European?
Not determined: the vendor’s pages as captured do not say where TYPO3 is based.
Where does TYPO3 store data?
Not stated on the vendor’s pages as of 3 Nov 2026.
Does TYPO3 have a free plan?
Not stated on the vendor’s pages as of 3 Nov 2026.
What are the best alternatives to TYPO3?
As of 4 Nov 2026, the panel rates StoryChief (3/5), Kontent.ai (3/5) and Scompler (3/5) highest among the other 23 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 StoryChief (EU-Made). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: TYPO3 alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 3 Nov 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Hosting location, 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.
- We found no public information on pricing on the pages we read (typo3.com, typo3.com/legal-notice, typo3.com/privacy-policy, typo3.com/de/loesungen/anwendungsfaelle/marketing-kampagne, typo3.com/typo3-cms/why-typo3/multisite-multilingual, typo3.com/solutions/use-case/internationalization-localization and 2 more). If the vendor publishes it somewhere else, send us the page. Know more? Tell us
- 13 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
- 2 legal facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 2 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
- 1 hosting 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
- 2 sovereignty dimensions could not be confirmed on the vendor’s own pages and are shown as unknown. Know more? Tell us
Sources (8)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor page typo3.com Checked 3 Nov 2026 Details →
- 2 Imprint — found from the homepage typo3.com Checked 3 Nov 2026 Details →
- 3 Privacy policy — found from the homepage typo3.com Checked 3 Nov 2026 Details →
- 4 Planning, editorial calendar & briefs — found from sitemap typo3.com Checked 3 Nov 2026 Details →
- 5 Structured content, localisation & export — found from sitemap typo3.com Checked 3 Nov 2026 Details →
- 6 Structured content, localisation & export — found from sitemap typo3.com Checked 3 Nov 2026 Details →
- 7 Publishing, distribution & integrations — found from sitemap typo3.com Checked 3 Nov 2026 Details →
- 8 Publishing, distribution & integrations — found from sitemap typo3.com Checked 3 Nov 2026 Details →