Xperience by Kentico vs TYPO3
Xperience by Kentico 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 12.
- Xperience by Kentico Enterprise DXP · Closed source · 19 of 28 built in
- TYPO3 Traditional · Open source · 20 of 28 built in
Sources checked: Xperience by Kentico 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
| Platform | | |
|---|---|---|
| Overview | ||
| What it is | Kentico's .NET digital experience platform for websites, email and headless channels, sold as Kentico-hosted SaaS or a private-cloud licence. | 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. | Xperience by Kentico Version 31.9.0, released 24 Sept 2026 | TYPO3 v14 LTS, version 14.3, open source Version 14.3.7, released 8 Sept 2026 |
| Vendor | Kentico kentico.com | TYPO3 Association (project); TYPO3 GmbH sells support and extended LTS typo3.org |
| Licence | Closed source Proprietary | Open source GPL-2.0-or-later |
| Hosting | Self-hosting Vendor cloud | Self-hosting No vendor cloud No vendor SaaS. TYPO3 agencies and hosts run managed installations. |
| Built with | .NET, ASP.NET Core | PHP, Symfony components, Fluid |
| Database | Microsoft SQL Server | MySQL, MariaDB, PostgreSQL, SQLite |
| Pricing Public list prices only. Hosting and implementation are extra everywhere. | No free option Pricing on request. Licensed per channel in Standard and Advanced tiers, plus AIRA credit packages. | 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 Continuous Integration serializes content types to files in the repository. 3 | 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 Field editor in the Content types application. | 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 Page Builder widgets and sections, plus reusable content items. | 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 Language variants per page and content item. | 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 Image variants with configured crops and sizes. 4 | Built in Server-side image processing with crop variants. 10 |
| APIs and delivery | ||
| REST API A documented REST or JSON HTTP API returns content. | Limited The Management REST API is for local development only. Headless delivery is GraphQL. 56 | 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. | Paid tier Headless channels need the Advanced tier. 6 | Not available |
| Webhooks The CMS can call an external URL when content is created, changed or published. | Not available No outgoing webhooks. Content events need custom handler code. 7 | 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 ASP.NET Core website channels. | 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 8 | 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 Schedule publish and unpublish. 8 | 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 View and restore previously published versions. 9 | 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 Preview mode and shareable preview URLs. | 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 Page Builder. | 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 Custom workflow steps with role permissions. 10 | Built in Custom stages in Workspaces. 5 |
| Content releases Editors group changes across several entries and publish them together as one release. | Limited Cascade publishing sends linked items with the parent. No standalone release bundles. 11 | 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 Content locking lets one user edit an item at a time. 12 | Not available |
| Access and governance | ||
| Custom roles Admins define their own roles with granular permissions instead of picking from a fixed set. | Built in Roles with application, workspace and page permissions. 13 | 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 stop at application, workspace and page level. 13 | 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 OpenID Connect for the administration, for example Microsoft Entra ID. 14 | 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. | Limited Event log records system events. Version history shows who changed versioned items. 159 | 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. | Paid tier Several main website channels need the Advanced tier. Standard adds only microchannels. 2 | 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 Custom React UI pages and form components. 16 | Built in Backend modules and custom form elements. |
| Plugin marketplace The vendor runs an official directory or marketplace of installable extensions. | Built in Integrations directory on the Kentico Community portal. 17 | Built in TYPO3 Extension Repository. 16 |
| Form builder Editors can build and publish forms and collect submissions without code. | Built in Form Builder. | 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 Members with registration, login and member roles. 18 | 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 AIRA text generation and translation on both tiers. Licences include 200,000 credits a year. 219 | 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. | Limited Management MCP server works on local development instances only. 205 | Not available Third-party only, e.g. hauptsache.net's TYPO3 MCP Server. 15 |
Xperience by Kentico sources
Checked 29 Sept 2026. Xperience by Kentico.
- Xperience by Kentico changelog (Refresh 31.9.0, 24 September 2026)
- How to buy Xperience by Kentico
- Continuous Integration
- Content item assets and image variants
- Configure the Management MCP and management API
- Headless channel management
- Handle content events
- Edit and publish pages
- Content versioning
- Workflows
- Content items and cascade publishing
- Content locking configuration
- Role management
- Administration external authentication
- Event log
- Extend the administration interface
- Kentico Community integrations
- Registration and authentication for members
- AIRA pricing, usage and policies
- Management MCP server
TYPO3 sources
Checked 29 Sept 2026. TYPO3 v14 LTS, version 14.3, open source.
- get.typo3.org: latest TYPO3 14 release
- TYPO3 Releases v14 LTS (press release)
- Changing the Playing Field: Visual Editing in TYPO3 v14
- TYPO3 v14: Building a System for Community-Driven AI Integrations
- TYPO3 Workspaces documentation
- TYPO3 Webhooks documentation
- TYPO3 Form documentation
- TYPO3 Frontend Login documentation
- Access control options (TYPO3 Explained)
- Crop variants for images (TYPO3 Explained)
- TYPO3 Content Blocks documentation
- Mask extension (TER)
- EXT:headless documentation
- OpenID Connect integration for TYPO3
- hauptsacheNet/typo3-mcp-server on GitHub
- How to find extensions (Getting Started)
- AI Suite extension (TER)
Considering more platforms? Compare Xperience by Kentico and TYPO3 with the rest of your shortlist in the CMS comparison tool.
Where they differ
Xperience by Kentico and TYPO3 get a different status on 12 of the 28 features and the same status on 16. Xperience by Kentico has 19 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
- Xperience by Kentico is closed source (Proprietary). TYPO3 is open source (GPL-2.0-or-later).
- Vendor cloud
- Xperience by Kentico has a vendor-run cloud. TYPO3 has no vendor-run cloud.
- Free option
- Xperience by Kentico has no free option. TYPO3 has a free option.
Built in on Xperience by Kentico, a different answer on TYPO3 4
- Content model in the UI Xperience by Kentico: Built in. TYPO3: Plugin or add-on.
- Visual editing Xperience by Kentico: Built in. TYPO3: Plugin or add-on.
- Single sign-on Xperience by Kentico: Built in. TYPO3: Plugin or add-on.
- AI writing assistant Xperience by Kentico: Built in. TYPO3: Not available.
Built in on TYPO3, a different answer on Xperience by Kentico 5
- Webhooks Xperience by Kentico: Not available. TYPO3: Built in.
- Content releases Xperience by Kentico: Limited. TYPO3: Built in.
- Field-level permissions Xperience by Kentico: Not available. TYPO3: Built in.
- Audit log Xperience by Kentico: Limited. TYPO3: Built in.
- Multiple sites Xperience by Kentico: Paid tier. TYPO3: Built in.
Built in on neither, with different answers 3
- REST API Xperience by Kentico: Limited. TYPO3: Plugin or add-on.
- GraphQL API Xperience by Kentico: Paid tier. TYPO3: Not available.
- Official MCP server Xperience by Kentico: Limited. TYPO3: Not available.
More comparisons
Xperience by Kentico against other platforms
- Adobe Experience Manager vs Xperience by Kentico
- Contentful vs Xperience by Kentico
- Contentstack vs Xperience by Kentico
- CoreMedia Content Cloud vs Xperience by Kentico
- Craft CMS vs Xperience by Kentico
- DatoCMS vs Xperience by Kentico
- Decap CMS vs Xperience by Kentico
- Directus vs Xperience by Kentico
- Drupal vs Xperience by Kentico
- EmDash vs Xperience by Kentico
- FirstSpirit vs Xperience by Kentico
- Framer vs Xperience by Kentico
- Ghost vs Xperience by Kentico
- HubSpot CMS vs Xperience by Kentico
- Hygraph vs Xperience by Kentico
- Instatic vs Xperience by Kentico
- Joomla vs Xperience by Kentico
- Xperience by Kentico vs Keystone
- Xperience by Kentico vs Kirby
- Xperience by Kentico vs Liferay DXP
- Xperience by Kentico vs Optimizely CMS
- Xperience by Kentico vs Payload
- Xperience by Kentico vs Prismic
- Xperience by Kentico vs Progress Sitefinity
- Xperience by Kentico vs Sanity
- Xperience by Kentico vs Sitecore
- Xperience by Kentico vs Squarespace
- Xperience by Kentico vs Statamic
- Xperience by Kentico vs Storyblok
- Xperience by Kentico vs Strapi
- Xperience by Kentico vs Umbraco
- Xperience by Kentico vs Wagtail
- Xperience by Kentico vs Webflow
- Xperience by Kentico vs Wix
- Xperience by Kentico vs WordPress
TYPO3 against other platforms
- Adobe Experience Manager vs TYPO3
- Contentful vs TYPO3
- Contentstack vs TYPO3
- CoreMedia Content Cloud vs TYPO3
- Craft CMS vs TYPO3
- DatoCMS vs TYPO3
- Decap CMS vs TYPO3
- Directus vs TYPO3
- Drupal vs TYPO3
- EmDash vs TYPO3
- FirstSpirit vs TYPO3
- Framer vs TYPO3
- Ghost vs TYPO3
- HubSpot CMS vs TYPO3
- Hygraph vs TYPO3
- Instatic vs TYPO3
- Joomla vs TYPO3
- Keystone vs TYPO3
- Kirby vs TYPO3
- Liferay DXP vs TYPO3
- Optimizely CMS vs TYPO3
- TYPO3 vs Payload
- Prismic vs TYPO3
- Progress Sitefinity vs TYPO3
- Sanity vs TYPO3
- Sitecore vs TYPO3
- Squarespace vs TYPO3
- Statamic vs TYPO3
- Storyblok vs TYPO3
- Strapi vs TYPO3
- TYPO3 vs Umbraco
- TYPO3 vs Wagtail
- TYPO3 vs Webflow
- TYPO3 vs Wix
- TYPO3 vs WordPress
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.