Now booking enterprise content platform builds for 2026. Contact us

CMS comparison Liferay DXP vs TYPO3

Liferay DXP vs TYPO3

Liferay DXP is a closed-source enterprise DXP that you can host yourself or run on the vendor's cloud. TYPO3 is an open-source traditional CMS that you host yourself. The table below sets them side by side on 28 features. They get a different status on 8.

  • Liferay DXP Enterprise DXP · Closed source · 26 of 28 built in
  • TYPO3 Traditional · Open source · 20 of 28 built in

Sources checked: Liferay DXP on 29 Sept 2026, TYPO3 on 29 Sept 2026. Plans and releases can change after those dates.

WAYF is an official Payload partner and top contributor. Every platform in the table is classified by the same published definitions, and each answer lists the vendor page it came from.


Feature comparison

Built inPaid tierPlugin or add-onLimitedNot available
Liferay DXP vs TYPO3 feature comparison. Columns are the two platforms. Rows are features, grouped by area.
Platform
Liferay DXP Enterprise DXP
TYPO3 Traditional
Overview
What it is Java platform for websites, portals and commerce, with a new object-based CMS. Self-hosted or run by Liferay as PaaS or SaaS.Open-source PHP CMS for multi-site, multilingual websites, with workspaces and granular backend permissions. Self-hosted, often run by agencies.
Edition compared The product and release each column describes. Liferay DXP 2026.Q3, Enterprise Subscription. The Free Tier replaced Liferay Portal CE from 2026.Q1. Version 2026.q3.5, released 25 Sept 2026 TYPO3 v14 LTS, version 14.3, open source Version 14.3.7, released 8 Sept 2026
Vendor Liferay, Inc. liferay.com TYPO3 Association (project); TYPO3 GmbH sells support and extended LTS typo3.org
Licence Closed source Proprietary, under the Liferay EULA. Free Tier activation key at no cost Open source GPL-2.0-or-later
Hosting Self-hosting Vendor cloud Free Tier suits smaller-scale use and gets no security patches, SAML or AI Hub. Self-hosting No vendor cloud No vendor SaaS. TYPO3 agencies and hosts run managed installations.
Built with Java, OSGi, ReactPHP, Symfony components, Fluid
Database MySQL, MariaDB, PostgreSQL, Oracle, SQL Server, IBM Db2MySQL, MariaDB, PostgreSQL, SQLite
Pricing Public list prices only. Hosting and implementation are extra everywhere. Free to start Free Tier at no cost for smaller-scale use. Enterprise Subscription per server instance, price on request. Free to start Free and open source. Commercial support and extended LTS are sold separately.
Content modelling
Content model in code You define content types in files in your repository, review them like any other code and apply them from there. Imperative migration scripts alone count as limited. Built in Definitions export to JSON and deploy from the repo as batch client extensions. 7 Built in TCA in PHP. The Content Blocks extension adds YAML definitions. 11
Content model in the UI Admins can create and change content types and fields in the admin interface without writing code. Built in Objects and web content structures. 6 Plugin or add-on Mask extension builds content elements in the backend. 12
Reusable blocks Editors compose pages from reusable, typed components or blocks, and can reorder them. Built in Fragments on content pages. 11 Built in Content elements on pages, reordered by drag and drop.
Localization Editors translate content per locale inside the CMS, by field or by entry, without a separate site for each language. Built in Built in Page and record translations. Guided translation wizard in v14. 2
Image transformations The CMS resizes, crops or converts images on request, through URL parameters or generated sizes, with no external service. Built in Adaptive Media generates set image resolutions. 8 Built in Server-side image processing with crop variants. 10
APIs and delivery
REST API A documented REST or JSON HTTP API returns content. Built in Headless REST APIs. 9 Plugin or add-on EXT:headless outputs pages as JSON. Core has no content API. 13
GraphQL API The vendor or an official module provides a GraphQL API for content. Built in 9 Not available
Webhooks The CMS can call an external URL when content is created, changed or published. Built in Object actions call a webhook on add, update or delete. 10 Built in Webhooks system extension, in core since v12. 6
Renders the website The CMS itself renders and serves the public pages through themes or templates. Headless-only products answer no. Built in Built in Fluid templates. Camino default theme in v14. 2
Editorial workflow
Drafts Editors save changes as a draft and publish them later. The live version stays untouched until then. Built in Built in Via the Workspaces system extension. 5
Scheduled publishing An editor can set a future date and time for content to publish or unpublish. Built in Display and expiration dates. Built in Start and stop dates on pages and content.
Version history The CMS keeps earlier versions of an entry, and editors can compare or restore them. Built in Built in Record history with diff and undo.
Preview Editors can see unpublished content rendered as it will appear on the site before publishing. Built in Built in Workspace preview links. 5
Visual editing Editors can click on the rendered page and edit content in place or in a side panel next to it. Built in Inline editing in the content page editor. 11 Plugin or add-on Visual Editor extension from Friends of TYPO3. TYPO3 plans core support for v15. 3
Approval workflows Content moves through review stages you configure, such as draft, review and approved, with permissions per stage. Built in Kaleo workflow, also included in the Free Tier. 3 Built in Custom stages in Workspaces. 5
Content releases Editors group changes across several entries and publish them together as one release. Built in Publications group changes and publish them together. 12 Built in Workspaces publish staged changes together. 5
Real-time co-editing Two or more editors can work on the same entry at once and see each other's changes live. Not available A page locks while one editor has it open. 13 Not available
Access and governance
Custom roles Admins define their own roles with granular permissions instead of picking from a fixed set. Built in Built in Backend user groups. 9
Field-level permissions Admins can restrict access to single fields, on top of content types and entries. Not available Permissions apply per object, entry or asset. 14 Built in Exclude fields per backend group. 9
Single sign-on Editors can sign in through SAML or OpenID Connect against a company identity provider. Built in SAML and OpenID Connect. The Free Tier lacks SAML. 315 Plugin or add-on OpenID Connect extensions such as causal/oidc. 14
Audit log The CMS logs who changed what and when across the whole installation, and admins can review the log. Built in Audit framework with search and export of events. 16 Built in Log module records backend changes by user.
Platform and extensibility
Multiple sites One installation or account can manage several separate websites or brands with shared users. Built in Built in Several site configurations in one installation.
Extensible admin UI Developers can add their own components, views or fields to the editing interface. Built in Client extensions. 7 Built in Backend modules and custom form elements.
Plugin marketplace The vendor runs an official directory or marketplace of installable extensions. Built in Liferay Marketplace. 17 Built in TYPO3 Extension Repository. 16
Form builder Editors can build and publish forms and collect submissions without code. Built in Liferay Forms. Built in Form Framework with a backend form editor. 7
Site member accounts The platform handles sign-up and login for public site users or members, separate from editors. Built in Built in Frontend users and the felogin extension. 8
AI writing assistant A first-party AI feature in the editing interface generates, rewrites or translates content. Built in AI Hub writing tools in the new CMS. Not in the Free Tier. 418 Not available Core ships AI integration points only. Third-party extensions such as AI Suite. 417
Official MCP server The vendor publishes a Model Context Protocol server so AI agents can read or write content. Built in Built-in MCP server released in 2026.Q3, switched on by feature flag. 19 Not available Third-party only, e.g. hauptsache.net's TYPO3 MCP Server. 15

Considering more platforms? Compare Liferay DXP and TYPO3 with the rest of your shortlist in the CMS comparison tool.


Where they differ

Liferay DXP and TYPO3 get a different status on 8 of the 28 features and the same status on 20. Liferay DXP has 26 built in on its baseline edition, TYPO3 has 20. Two matching statuses can still name different paid tiers or limits, so read the notes in the table before treating a row as equal.

Licence
Liferay DXP is closed source (Proprietary, under the Liferay EULA. Free Tier activation key at no cost). TYPO3 is open source (GPL-2.0-or-later).
Vendor cloud
Liferay DXP has a vendor-run cloud. TYPO3 has no vendor-run cloud.

Built in on Liferay DXP, a different answer on TYPO3 7

  • Content model in the UI Liferay DXP: Built in. TYPO3: Plugin or add-on.
  • REST API Liferay DXP: Built in. TYPO3: Plugin or add-on.
  • GraphQL API Liferay DXP: Built in. TYPO3: Not available.
  • Visual editing Liferay DXP: Built in. TYPO3: Plugin or add-on.
  • Single sign-on Liferay DXP: Built in. TYPO3: Plugin or add-on.
  • AI writing assistant Liferay DXP: Built in. TYPO3: Not available.
  • Official MCP server Liferay DXP: Built in. TYPO3: Not available.

Built in on TYPO3, a different answer on Liferay DXP 1

  • Field-level permissions Liferay DXP: Not available. TYPO3: Built in.

More comparisons

Open the CMS comparison tool to put up to six platforms in one table.


We're booking content platform
engagements for 2026.

Twenty-five minutes to walk through the work and decide if we're the right team for it. Scoping and a fixed price come after.