Progress Sitefinity vs TYPO3
Progress Sitefinity 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 10.
- Progress Sitefinity Enterprise DXP · Closed source · 22 of 28 built in
- TYPO3 Traditional · Open source · 20 of 28 built in
Sources checked: Progress Sitefinity 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 | Progress's .NET CMS and DXP for websites, run self-hosted or on the Sitefinity Cloud PaaS, with ASP.NET Core and Next.js renderers. | 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. | Sitefinity CMS 15.4 DX edition, self-hosted or on Sitefinity Cloud Version 15.4.8639, released 29 Sept 2026 | TYPO3 v14 LTS, version 14.3, open source Version 14.3.7, released 8 Sept 2026 |
| Vendor | Progress Software progress.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 and Next.js renderers | 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. DX and DX+Enterprise editions, self-hosted or on Sitefinity Cloud. | 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 Export for deployment writes module and field changes to files for source control. 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 Module Builder. | 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 editor widgets. | 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 Multilingual content per 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 Resize through URL parameters and thumbnail profiles. 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. | Built in OData REST web services. 5 | 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 GraphQL on the web services layer. 6 | Not available |
| Webhooks The CMS can call an external URL when content is created, changed or published. | Built in Service hooks with a webhook action, available on all licences. 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, Next.js or legacy MVC renderers. 1 | 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 Scheduled publish and unpublish per item. 9 | 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 Revision history. | 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 Page editor with widgets. | 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 One or two approval levels, or a custom workflow. 8 | Built in Custom stages in Workspaces. 5 |
| Content releases Editors group changes across several entries and publish them together as one release. | Not available Publishing and scheduling work per item. 9 | 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 Pages lock while another user edits them. 10 | Not available |
| Access and governance | ||
| Custom roles Admins define their own roles with granular permissions instead of picking from a fixed set. | Built in 11 | Built in Backend user groups. 9 |
| Field-level permissions Admins can restrict access to single fields, on top of content types and entries. | Limited Module Builder types only, in the classic editing UI. Built-in content types have none. 12 | 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 and external providers such as Azure AD. 13 | 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. | Paid tier DX + Enterprise includes Audit Trail. Progress sells it as an add-on for DX. 142 | 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 Multisite with shared content and per-site permissions. 15 | 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 fields, widgets and AdminApp extensions. | Built in Backend modules and custom form elements. |
| Plugin marketplace The vendor runs an official directory or marketplace of installable extensions. | Built in Sitefinity integrations directory. 16 | Built in TYPO3 Extension Repository. 16 |
| Form builder Editors can build and publish forms and collect submissions without code. | Built in Forms module with a drag-and-drop 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 Front-end users with registration and login widgets. | 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. | Plugin or add-on Sitefinity AI subscription for text generation and agents. 17 | 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. | Plugin or add-on Sitefinity MCP Server, 15.4.8633 or later, needs a Sitefinity AI subscription. 18 | Not available Third-party only, e.g. hauptsache.net's TYPO3 MCP Server. 15 |
Progress Sitefinity sources
Checked 29 Sept 2026. Sitefinity CMS 15.4 DX edition, self-hosted or on Sitefinity Cloud.
- Sitefinity CMS 15.4.8639 release notes
- Sitefinity packaging and deployment options
- Export and deploy database changes
- Resize images through the URL
- Set up a web service
- Use GraphQL protocol
- Service hooks
- Content lifecycle and workflow
- Manage scheduled tasks
- Unlock pages
- Permissions
- Progress knowledge base: How to set up field permissions in Sitefinity
- Authentication
- Sitefinity Audit Trail
- Multisite
- Sitefinity integrations directory
- Sitefinity AI
- Sitefinity MCP Server
- Sitefinity release history
- Sitefinity Cloud documentation
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 Progress Sitefinity and TYPO3 with the rest of your shortlist in the CMS comparison tool.
Where they differ
Progress Sitefinity and TYPO3 get a different status on 10 of the 28 features and the same status on 18. Progress Sitefinity has 22 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
- Progress Sitefinity is closed source (Proprietary). TYPO3 is open source (GPL-2.0-or-later).
- Vendor cloud
- Progress Sitefinity has a vendor-run cloud. TYPO3 has no vendor-run cloud.
- Free option
- Progress Sitefinity has no free option. TYPO3 has a free option.
Built in on Progress Sitefinity, a different answer on TYPO3 5
- Content model in the UI Progress Sitefinity: Built in. TYPO3: Plugin or add-on.
- REST API Progress Sitefinity: Built in. TYPO3: Plugin or add-on.
- GraphQL API Progress Sitefinity: Built in. TYPO3: Not available.
- Visual editing Progress Sitefinity: Built in. TYPO3: Plugin or add-on.
- Single sign-on Progress Sitefinity: Built in. TYPO3: Plugin or add-on.
Built in on TYPO3, a different answer on Progress Sitefinity 3
- Content releases Progress Sitefinity: Not available. TYPO3: Built in.
- Field-level permissions Progress Sitefinity: Limited. TYPO3: Built in.
- Audit log Progress Sitefinity: Paid tier. TYPO3: Built in.
Built in on neither, with different answers 2
- AI writing assistant Progress Sitefinity: Plugin or add-on. TYPO3: Not available.
- Official MCP server Progress Sitefinity: Plugin or add-on. TYPO3: Not available.
More comparisons
Progress Sitefinity against other platforms
- Adobe Experience Manager vs Progress Sitefinity
- Contentful vs Progress Sitefinity
- Contentstack vs Progress Sitefinity
- CoreMedia Content Cloud vs Progress Sitefinity
- Craft CMS vs Progress Sitefinity
- DatoCMS vs Progress Sitefinity
- Decap CMS vs Progress Sitefinity
- Directus vs Progress Sitefinity
- Drupal vs Progress Sitefinity
- EmDash vs Progress Sitefinity
- FirstSpirit vs Progress Sitefinity
- Framer vs Progress Sitefinity
- Ghost vs Progress Sitefinity
- HubSpot CMS vs Progress Sitefinity
- Hygraph vs Progress Sitefinity
- Instatic vs Progress Sitefinity
- Joomla vs Progress Sitefinity
- Keystone vs Progress Sitefinity
- Kirby vs Progress Sitefinity
- Liferay DXP vs Progress Sitefinity
- Optimizely CMS vs Progress Sitefinity
- Progress Sitefinity vs Payload
- Prismic vs Progress Sitefinity
- Sanity vs Progress Sitefinity
- Sitecore vs Progress Sitefinity
- Progress Sitefinity vs Squarespace
- Progress Sitefinity vs Statamic
- Progress Sitefinity vs Storyblok
- Progress Sitefinity vs Strapi
- Progress Sitefinity vs Umbraco
- Progress Sitefinity vs Wagtail
- Progress Sitefinity vs Webflow
- Progress Sitefinity vs Wix
- Progress Sitefinity vs WordPress
- Xperience by Kentico vs Progress Sitefinity
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
- 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
- Xperience by Kentico vs TYPO3
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.