CoreMedia Content Cloud vs Instatic
CoreMedia Content Cloud is a closed-source enterprise DXP that you can host yourself or run on the vendor's cloud. Instatic is an open-source site builder that you host yourself. The table below sets them side by side on 28 features. They get a different status on 15.
- CoreMedia Content Cloud Enterprise DXP · Closed source · 18 of 28 built in
- Instatic Site builder · Open source · 15 of 28 built in
Sources checked: CoreMedia Content Cloud on 29 Sept 2026, Instatic on 30 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 | Java-based enterprise CMS with a Studio editor, a template engine and a GraphQL headless server. Runs on-premises or as CoreMedia's cloud service. | Open-source, self-hosted CMS with a visual canvas editor. One Bun server runs the editor, content store and publisher, and publishing writes plain HTML files to disk. |
| Edition compared The product and release each column describes. | CoreMedia Content Cloud v13, or CMCC 13 Version 2512.1.1, released 10 Aug 2026 | Instatic 0.0.20, open source Version 0.0.20, released 13 Sept 2026 |
| Vendor | CoreMedia GmbH coremedia.com | CoreBunch instatic.com |
| Licence | Closed source Proprietary | Open source MIT |
| Hosting | Self-hosting Vendor cloud Event Hub webhooks are an add-on for the CoreMedia cloud service only. | Self-hosting No vendor cloud No managed hosting. You deploy the Docker image to your own server, or use the Railway and Render templates. |
| Built with | Java, Spring Boot, TypeScript for Studio | TypeScript, Bun, React admin |
| Database | Relational database: PostgreSQL, MySQL, Oracle, SQL Server | SQLite, PostgreSQL |
| Pricing Public list prices only. Hosting and implementation are extra everywhere. | No free option Pricing on request. | Free to start Free and open source, with no paid tiers. You pay only for hosting. |
| 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 XML files in the project workspace define content types. 3 | Not available Tables and fields live in the database and change in the Data workspace. Plugins can create tables through the SDK. 610 |
| Content model in the UI Admins can create and change content types and fields in the admin interface without writing code. | Not available Content type changes need a developer and a deployment. 3 | Built in Custom post types and data tables in the Data workspace. 616 |
| Reusable blocks Editors compose pages from reusable, typed components or blocks, and can reorder them. | Built in Page grid placements hold reusable content items. 4 | Built in Visual Components with typed parameters and named slots, placed and reordered on the canvas. 72 |
| Localization Editors translate content per locale inside the CMS, by field or by entry, without a separate site for each language. | Limited Each locale is a derived site linked to a master site, with a translation workflow. 5 | Not available One site-wide language setting. No per-locale fields or entries. 21 |
| Image transformations The CMS resizes, crops or converts images on request, through URL parameters or generated sizes, with no external service. | Built in Named image variants and crops in the CAE and Headless Server. 6 | Built in Uploads get a set of WebP sizes, and the publisher writes srcset and sizes from the layout. 81 |
| APIs and delivery | ||
| REST API A documented REST or JSON HTTP API returns content. | Built in REST endpoints mapped from persisted GraphQL queries. 7 | Limited The JSON API under /admin/api/cms serves the admin behind a session cookie. No token-based content API outside MCP. 920 |
| GraphQL API The vendor or an official module provides a GraphQL API for content. | Built in Headless Server. 7 | Not available |
| Webhooks The CMS can call an external URL when content is created, changed or published. | Plugin or add-on Event Hub add-on service for cloud service subscribers. 89 | Not available No built-in webhooks. A plugin with network access can call a URL from content hooks. 10 |
| Renders the website The CMS itself renders and serves the public pages through themes or templates. Headless-only products answer no. | Built in Content Application Engine with FreeMarker templates. 1 | Built in Publishing renders every page to static HTML on the server's disk. 11 |
| Editorial workflow | ||
| Drafts Editors save changes as a draft and publish them later. The live version stays untouched until then. | Built in | Built in 51 |
| Scheduled publishing An editor can set a future date and time for content to publish or unpublish. | Built in Valid-from and valid-to dates plus a scheduled publication workflow. 11 | Built in Per page and per post-type entry. 5 |
| Version history The CMS keeps earlier versions of an entry, and editors can compare or restore them. | Built in | Built in Published versions of pages and entries, restorable into the draft. Added in 0.0.20. 124 |
| Preview Editors can see unpublished content rendered as it will appear on the site before publishing. | Built in | Built in The canvas renders drafts in the site design. Branch preview links work without an account. 122 |
| Visual editing Editors can click on the rendered page and edit content in place or in a side panel next to it. | Built in In-preview editing in Studio, also for headless frontends. 10 | Built in Editing happens on the rendered page canvas, with a live mode for the full-size page. 214 |
| Approval workflows Content moves through review stages you configure, such as draft, review and approved, with permissions per stage. | Built in Workflow Server with configurable publication workflows. 1113 | Limited Branch merge requests with a review page and comments. No configurable review stages. 12 |
| Content releases Editors group changes across several entries and publish them together as one release. | Limited Projects group content. A publication set carries linked items along. 1213 | Limited Publish ships all draft pages at once. Branches group edits across pages and entries, but entries still publish one by one. 125 |
| 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 | Limited Live co-editing of pages, components and layouts in the Site editor. Content workspace entries save separately. 13144 |
| Access and governance | ||
| Custom roles Admins define their own roles with granular permissions instead of picking from a fixed set. | Built in Rights rules per group, folder and content type. 14 | Built in The Owner builds roles from a fixed list of capabilities. 1516 |
| Field-level permissions Admins can restrict access to single fields, on top of content types and entries. | Not available Rights apply per folder and content type. 14 | Not available Capabilities apply per table type and edit category, not per field. 16 |
| Single sign-on Editors can sign in through SAML or OpenID Connect against a company identity provider. | Built in Studio login runs on Spring Security. A project swaps in a redirect-based SSO provider. 1516 | Not available Email and password with optional TOTP two-factor. 15 |
| Audit log The CMS logs who changed what and when across the whole installation, and admins can review the log. | Built in Records who changed what and when; supports reversions. Retention, export and edition limits are not public: confirm in the contract. 16 | Built in Append-only log of logins, content changes, role edits and plugin actions. 17 |
| Platform and extensibility | ||
| Multiple sites One installation or account can manage several separate websites or brands with shared users. | Built in | Not available One site per installation. 2 |
| Extensible admin UI Developers can add their own components, views or fields to the editing interface. | Built in Studio plugins. | Built in Plugins add admin pages, editor extensions, dashboard widgets and canvas modules. 10 |
| Plugin marketplace The vendor runs an official directory or marketplace of installable extensions. | Built in CoreMedia Marketplace. 17 | Not available Plugins install as uploaded zip packages. No official directory. 10 |
| Form builder Editors can build and publish forms and collect submissions without code. | Plugin or add-on Formcentric for CoreMedia, a partner product from the Marketplace. 18 | Built in Forms are built on the canvas and submissions land in a data table. 18 |
| Site member accounts The platform handles sign-up and login for public site users or members, separate from editors. | Plugin or add-on Elastic Social module manages site users and comments. 19 | Not available |
| AI writing assistant A first-party AI feature in the editing interface generates, rewrites or translates content. | Plugin or add-on KIO Co-Pilot needs a licence with KIO enabled. 20 | Built in Built-in agent in the Site and Content workspaces, with your own Claude, OpenAI, OpenRouter or Ollama key. 19 |
| Official MCP server The vendor publishes a Model Context Protocol server so AI agents can read or write content. | Not available None for content. The only official MCP server covers Engagement Cloud analytics. 20 | Built in Built in at /_instatic/mcp, with OAuth or scoped personal access tokens. 20 |
CoreMedia Content Cloud sources
Checked 29 Sept 2026. CoreMedia Content Cloud v13, or CMCC 13.
- CoreMedia release notes: 2512.1.1
- CoreMedia Content Management System
- Content Server Manual: Structure of content type definitions
- Studio User Manual: Editing a page grid
- Studio User Manual: Translation to derived sites
- CAE Developer Manual: Image Transformation API
- Headless Server Developer Manual: Mapping REST access
- Introduction to the Event Hub Service
- Service description: Event Hub
- Introducing in-preview editing for CoreMedia Content Cloud
- Scheduled publication workflow
- How to use projects in Studio (CMCC 13)
- Publication steps and best practices
- Studio User Manual: Permissions and rights
- Studio Developer Manual 2512.1: Single Sign On Integration
- CoreMedia: security, access control and audit trails
- CoreMedia Marketplace
- Formcentric Form Manager on CoreMedia Marketplace
- Studio User Manual 2512.0: Elastic Social
- Introduction to KIO Co-Pilot
Instatic sources
Checked 30 Sept 2026. Instatic 0.0.20, open source.
- Instatic homepage
- Instatic repository on GitHub
- Instatic 0.0.20 release
- Instatic changelog
- Instatic docs: Content storage
- Instatic docs: Data workspace
- Instatic docs: Visual Components
- Instatic docs: Media
- Instatic docs: Server
- Instatic docs: Plugin system
- Instatic docs: Publisher
- Instatic docs: Site branches
- Instatic docs: Site shell and real-time co-editing
- Instatic docs: Content workspace
- Instatic docs: Auth and access
- Instatic docs: Capabilities
- Instatic docs: Audit log
- Instatic docs: CMS-native forms
- Instatic docs: AI agent
- Instatic docs: MCP connectors
- Instatic docs: Editor
Considering more platforms? Compare CoreMedia Content Cloud and Instatic with the rest of your shortlist in the CMS comparison tool.
Where they differ
CoreMedia Content Cloud and Instatic get a different status on 15 of the 28 features and the same status on 13. CoreMedia Content Cloud has 18 built in on its baseline edition, Instatic has 15. 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
- CoreMedia Content Cloud is closed source (Proprietary). Instatic is open source (MIT).
- Vendor cloud
- CoreMedia Content Cloud has a vendor-run cloud. Instatic has no vendor-run cloud.
- Free option
- CoreMedia Content Cloud has no free option. Instatic has a free option.
Built in on CoreMedia Content Cloud, a different answer on Instatic 7
- Content model in code CoreMedia Content Cloud: Built in. Instatic: Not available.
- REST API CoreMedia Content Cloud: Built in. Instatic: Limited.
- GraphQL API CoreMedia Content Cloud: Built in. Instatic: Not available.
- Approval workflows CoreMedia Content Cloud: Built in. Instatic: Limited.
- Single sign-on CoreMedia Content Cloud: Built in. Instatic: Not available.
- Multiple sites CoreMedia Content Cloud: Built in. Instatic: Not available.
- Plugin marketplace CoreMedia Content Cloud: Built in. Instatic: Not available.
Built in on Instatic, a different answer on CoreMedia Content Cloud 4
- Content model in the UI CoreMedia Content Cloud: Not available. Instatic: Built in.
- Form builder CoreMedia Content Cloud: Plugin or add-on. Instatic: Built in.
- AI writing assistant CoreMedia Content Cloud: Plugin or add-on. Instatic: Built in.
- Official MCP server CoreMedia Content Cloud: Not available. Instatic: Built in.
Built in on neither, with different answers 4
- Localization CoreMedia Content Cloud: Limited. Instatic: Not available.
- Webhooks CoreMedia Content Cloud: Plugin or add-on. Instatic: Not available.
- Real-time co-editing CoreMedia Content Cloud: Not available. Instatic: Limited.
- Site member accounts CoreMedia Content Cloud: Plugin or add-on. Instatic: Not available.
More comparisons
CoreMedia Content Cloud against other platforms
- Adobe Experience Manager vs CoreMedia Content Cloud
- Contentful vs CoreMedia Content Cloud
- Contentstack vs CoreMedia Content Cloud
- CoreMedia Content Cloud vs Craft CMS
- CoreMedia Content Cloud vs DatoCMS
- CoreMedia Content Cloud vs Decap CMS
- CoreMedia Content Cloud vs Directus
- CoreMedia Content Cloud vs Drupal
- CoreMedia Content Cloud vs EmDash
- CoreMedia Content Cloud vs FirstSpirit
- CoreMedia Content Cloud vs Framer
- CoreMedia Content Cloud vs Ghost
- CoreMedia Content Cloud vs HubSpot CMS
- CoreMedia Content Cloud vs Hygraph
- CoreMedia Content Cloud vs Joomla
- CoreMedia Content Cloud vs Keystone
- CoreMedia Content Cloud vs Kirby
- CoreMedia Content Cloud vs Liferay DXP
- CoreMedia Content Cloud vs Optimizely CMS
- CoreMedia Content Cloud vs Payload
- CoreMedia Content Cloud vs Prismic
- CoreMedia Content Cloud vs Progress Sitefinity
- CoreMedia Content Cloud vs Sanity
- CoreMedia Content Cloud vs Sitecore
- CoreMedia Content Cloud vs Squarespace
- CoreMedia Content Cloud vs Statamic
- CoreMedia Content Cloud vs Storyblok
- CoreMedia Content Cloud vs Strapi
- CoreMedia Content Cloud vs TYPO3
- CoreMedia Content Cloud vs Umbraco
- CoreMedia Content Cloud vs Wagtail
- CoreMedia Content Cloud vs Webflow
- CoreMedia Content Cloud vs Wix
- CoreMedia Content Cloud vs WordPress
- CoreMedia Content Cloud vs Xperience by Kentico
Instatic against other platforms
- Adobe Experience Manager vs Instatic
- Contentful vs Instatic
- Contentstack vs Instatic
- Craft CMS vs Instatic
- DatoCMS vs Instatic
- Decap CMS vs Instatic
- Directus vs Instatic
- Drupal vs Instatic
- EmDash vs Instatic
- FirstSpirit vs Instatic
- Framer vs Instatic
- Ghost vs Instatic
- HubSpot CMS vs Instatic
- Hygraph vs Instatic
- Instatic vs Joomla
- Instatic vs Keystone
- Instatic vs Kirby
- Instatic vs Liferay DXP
- Instatic vs Optimizely CMS
- Instatic vs Payload
- Instatic vs Prismic
- Instatic vs Progress Sitefinity
- Instatic vs Sanity
- Instatic vs Sitecore
- Instatic vs Squarespace
- Instatic vs Statamic
- Instatic vs Storyblok
- Instatic vs Strapi
- Instatic vs TYPO3
- Instatic vs Umbraco
- Instatic vs Wagtail
- Instatic vs Webflow
- Instatic vs Wix
- Instatic vs WordPress
- Instatic vs Xperience by Kentico
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.