DatoCMS vs Progress Sitefinity
DatoCMS is a closed-source headless CMS that runs on the vendor's cloud. Progress Sitefinity is a closed-source enterprise DXP that you can host yourself or run on the vendor's cloud. The table below sets them side by side on 28 features. They get a different status on 10.
- DatoCMS Headless · Closed source · 16 of 28 built in
- Progress Sitefinity Enterprise DXP · Closed source · 22 of 28 built in
Sources checked: DatoCMS on 29 Sept 2026, Progress Sitefinity 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 | Hosted headless CMS run by DatoCMS. It delivers content over a GraphQL API, with a REST API for content management. | 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. |
| Edition compared The product and release each column describes. | DatoCMS SaaS, Free, Professional and Enterprise plans SaaS, continuously updated | Sitefinity CMS 15.4 DX edition, self-hosted or on Sitefinity Cloud Version 15.4.8639, released 29 Sept 2026 |
| Vendor | DatoCMS datocms.com | Progress Software progress.com |
| Licence | Closed source Proprietary | Closed source Proprietary |
| Hosting | No self-hosting Vendor cloud | Self-hosting Vendor cloud |
| Built with | Hosted SaaS with GraphQL delivery and REST management APIs, TypeScript client | .NET, ASP.NET Core and Next.js renderers |
| Database | Managed by DatoCMS | Microsoft SQL Server |
| Pricing Public list prices only. Hosting and implementation are extra everywhere. | Free to start Free plan. Professional €149 per month billed annually, or €199 monthly. Enterprise on request. | No free option Pricing on request. DX and DX+Enterprise editions, self-hosted or on Sitefinity Cloud. |
| 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. | Limited Migration scripts run by the DatoCMS CLI, auto-generated from environment diffs. 12 | Built in Export for deployment writes module and field changes to files for source control. 3 |
| Content model in the UI Admins can create and change content types and fields in the admin interface without writing code. | Built in 1 | Built in Module Builder. |
| Reusable blocks Editors compose pages from reusable, typed components or blocks, and can reorder them. | Built in Block library used in modular content and Structured Text fields. 1 | Built in Page editor widgets. |
| Localization Editors translate content per locale inside the CMS, by field or by entry, without a separate site for each language. | Built in Field-level locales, 5 included and up to 10 with paid add-ons. 1 | Built in Multilingual content per item. |
| Image transformations The CMS resizes, crops or converts images on request, through URL parameters or generated sizes, with no external service. | Built in Images API with imgix URL parameters. 3 | Built in Resize through URL parameters and thumbnail profiles. 4 |
| APIs and delivery | ||
| REST API A documented REST or JSON HTTP API returns content. | Built in REST Content Management API reads records. Delivery is GraphQL. 111 | Built in OData REST web services. 5 |
| GraphQL API The vendor or an official module provides a GraphQL API for content. | Built in 1 | Built in GraphQL on the web services layer. 6 |
| Webhooks The CMS can call an external URL when content is created, changed or published. | Built in 1 | Built in Service hooks with a webhook action, available on all licences. 7 |
| Renders the website The CMS itself renders and serves the public pages through themes or templates. Headless-only products answer no. | Not available | Built in ASP.NET Core, Next.js or legacy MVC renderers. 1 |
| Editorial workflow | ||
| Drafts Editors save changes as a draft and publish them later. The live version stays untouched until then. | Built in 1 | Built in |
| Scheduled publishing An editor can set a future date and time for content to publish or unpublish. | Built in 1 | Built in Scheduled publish and unpublish per item. 9 |
| Version history The CMS keeps earlier versions of an entry, and editors can compare or restore them. | Limited History kept 3 days on Free, 60 days on Professional. 1 | Built in Revision history. |
| Preview Editors can see unpublished content rendered as it will appear on the site before publishing. | Built in 17 | Built in |
| Visual editing Editors can click on the rendered page and edit content in place or in a side panel next to it. | Built in Click-to-edit overlays on the site in draft mode. 17 | Built in Page editor with widgets. |
| Approval workflows Content moves through review stages you configure, such as draft, review and approved, with permissions per stage. | Paid tier Editorial workflows with stage permissions on Enterprise. 16 | Built in One or two approval levels, or a custom workflow. 8 |
| Content releases Editors group changes across several entries and publish them together as one release. | Limited Publishing a record can also publish its linked records. No standalone releases. 1 | Not available Publishing and scheduling work per item. 9 |
| 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 Presence and live updates, but a record locks while one editor edits it. 4 | Not available Pages lock while another user edits them. 10 |
| Access and governance | ||
| Custom roles Admins define their own roles with granular permissions instead of picking from a fixed set. | Built in Projects include Admin and Editor roles and can create additional roles. The Free plan is limited to 2 editor seats. 15 | Built in 11 |
| Field-level permissions Admins can restrict access to single fields, on top of content types and entries. | Not available Rules apply per model, creator, locale and workflow stage. Locale rules need Enterprise. 5 | Limited Module Builder types only, in the classic editing UI. Built-in content types have none. 12 |
| Single sign-on Editors can sign in through SAML or OpenID Connect against a company identity provider. | Paid tier Enterprise, with SCIM provisioning. 1 | Built in OpenID Connect and external providers such as Azure AD. 13 |
| Audit log The CMS logs who changed what and when across the whole installation, and admins can review the log. | Paid tier Enterprise. 1 | Paid tier DX + Enterprise includes Audit Trail. Progress sells it as an add-on for DX. 142 |
| Platform and extensibility | ||
| Multiple sites One installation or account can manage several separate websites or brands with shared users. | Built in Separate projects per site. 3 on Free, extra projects €39 a month on Professional. 1 | Built in Multisite with shared content and per-site permissions. 15 |
| Extensible admin UI Developers can add their own components, views or fields to the editing interface. | Built in Plugin SDK for field editors, sidebars and custom pages. 1 | Built in Custom fields, widgets and AdminApp extensions. |
| Plugin marketplace The vendor runs an official directory or marketplace of installable extensions. | Built in DatoCMS Marketplace. 19 | Built in Sitefinity integrations directory. 16 |
| Form builder Editors can build and publish forms and collect submissions without code. | Not available | Built in Forms module with a drag-and-drop builder. |
| Site member accounts The platform handles sign-up and login for public site users or members, separate from editors. | Not available | Built in Front-end users with registration and login widgets. |
| AI writing assistant A first-party AI feature in the editing interface generates, rewrites or translates content. | Plugin or add-on Official AI Translations plugin with your own OpenAI, Gemini, Claude or DeepL key. 89 | Plugin or add-on Sitefinity AI subscription for text generation and agents. 17 |
| Official MCP server The vendor publishes a Model Context Protocol server so AI agents can read or write content. | Built in Remote MCP server at mcp.datocms.com. 10 | Plugin or add-on Sitefinity MCP Server, 15.4.8633 or later, needs a Sitefinity AI subscription. 18 |
DatoCMS sources
Checked 29 Sept 2026. DatoCMS SaaS, Free, Professional and Enterprise plans.
- DatoCMS pricing
- DatoCMS docs: Write and test migration scripts
- DatoCMS docs: Images API
- DatoCMS docs: Record-level collaboration, presence and locking
- DatoCMS docs: Project collaborators, roles and permissions
- DatoCMS docs: Workflows
- DatoCMS docs: Visual Editing
- DatoCMS docs: Translating content with AI
- DatoCMS Marketplace: AI Translations plugin
- DatoCMS docs: MCP Server
- DatoCMS Content Management API: Record
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
Considering more platforms? Compare DatoCMS and Progress Sitefinity with the rest of your shortlist in the CMS comparison tool.
Where they differ
DatoCMS and Progress Sitefinity get a different status on 10 of the 28 features and the same status on 18. DatoCMS has 16 built in on its baseline edition, Progress Sitefinity has 22. Two matching statuses can still name different paid tiers or limits, so read the notes in the table before treating a row as equal.
- Self-hosting
- DatoCMS cannot be self-hosted. Progress Sitefinity can be self-hosted.
- Free option
- DatoCMS has a free option. Progress Sitefinity has no free option.
Built in on DatoCMS, a different answer on Progress Sitefinity 1
- Official MCP server DatoCMS: Built in. Progress Sitefinity: Plugin or add-on.
Built in on Progress Sitefinity, a different answer on DatoCMS 7
- Content model in code DatoCMS: Limited. Progress Sitefinity: Built in.
- Renders the website DatoCMS: Not available. Progress Sitefinity: Built in.
- Version history DatoCMS: Limited. Progress Sitefinity: Built in.
- Approval workflows DatoCMS: Paid tier. Progress Sitefinity: Built in.
- Single sign-on DatoCMS: Paid tier. Progress Sitefinity: Built in.
- Form builder DatoCMS: Not available. Progress Sitefinity: Built in.
- Site member accounts DatoCMS: Not available. Progress Sitefinity: Built in.
Built in on neither, with different answers 2
- Content releases DatoCMS: Limited. Progress Sitefinity: Not available.
- Field-level permissions DatoCMS: Not available. Progress Sitefinity: Limited.
More comparisons
Full write-ups with worked examples and costs: DatoCMS vs Payload.
DatoCMS against other platforms
- Adobe Experience Manager vs DatoCMS
- Contentful vs DatoCMS
- Contentstack vs DatoCMS
- CoreMedia Content Cloud vs DatoCMS
- Craft CMS vs DatoCMS
- DatoCMS vs Decap CMS
- DatoCMS vs Directus
- DatoCMS vs Drupal
- DatoCMS vs EmDash
- DatoCMS vs FirstSpirit
- DatoCMS vs Framer
- DatoCMS vs Ghost
- DatoCMS vs HubSpot CMS
- DatoCMS vs Hygraph
- DatoCMS vs Instatic
- DatoCMS vs Joomla
- DatoCMS vs Keystone
- DatoCMS vs Kirby
- DatoCMS vs Liferay DXP
- DatoCMS vs Optimizely CMS
- DatoCMS vs Payload
- DatoCMS vs Prismic
- DatoCMS vs Sanity
- DatoCMS vs Sitecore
- DatoCMS vs Squarespace
- DatoCMS vs Statamic
- DatoCMS vs Storyblok
- DatoCMS vs Strapi
- DatoCMS vs TYPO3
- DatoCMS vs Umbraco
- DatoCMS vs Wagtail
- DatoCMS vs Webflow
- DatoCMS vs Wix
- DatoCMS vs WordPress
- DatoCMS vs Xperience by Kentico
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
- 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 TYPO3
- 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
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.