Now booking enterprise content platform builds for 2026. Contact us

Join us
Contact us

What we build

Who it's for

How we engage

Case studies

Industries

Partnerships

About

Writing

Tools

For startups Join us
Contact us
CMS comparison Adobe Experience Manager vs Instatic

Adobe Experience Manager vs Instatic

Adobe Experience Manager is a closed-source enterprise DXP that runs 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 12.

Book a call
  • Adobe Experience Manager Enterprise DXP · Closed source · 25 of 28 built in
  • Instatic Site builder · Open source · 15 of 28 built in

Sources checked: Adobe Experience Manager 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

Built inPaid tierPlugin or add-onLimitedNot available
Adobe Experience Manager vs Instatic feature comparison. Columns are the two platforms. Rows are features, grouped by area.
Platform
Adobe Experience Manager Enterprise DXP
Instatic Site builder
Overview
What it is Adobe's enterprise CMS for websites and headless content, run by Adobe as a cloud service with page, fragment and document-based authoring.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. Adobe Experience Manager Sites as a Cloud Service Version 2026.9.0, released 24 Sept 2026 Instatic 0.0.20, open source Version 0.0.20, released 13 Sept 2026
Vendor Adobe business.adobe.com CoreBunch instatic.com
Licence Closed source Proprietary Open source MIT
Hosting No self-hosting Vendor cloud Cloud Service runs only on Adobe's cloud. AEM 6.5 LTS is the separate self-hosted edition. 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, Apache Sling, OSGi, HTLTypeScript, Bun, React admin
Database Apache Jackrabbit Oak repository, managed by AdobeSQLite, 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 Components, dialogs and Universal Editor models live in the project repository. 2 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. Built in Content Fragment Model editor. 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 29 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. Built in Language copies with translation projects and connectors. 4 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 Web-optimized image delivery resizes, crops and converts DAM images to WebP. 5 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 Content Fragment Delivery with OpenAPI. 6 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 GraphQL for Content Fragments. 6 Not available
Webhooks The CMS can call an external URL when content is created, changed or published. Built in AEM Eventing delivers events through Adobe I/O Events. 7 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 HTL page rendering or Edge Delivery Services. 10 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 Edits stay on the author tier until published. 11 Built in 51
Scheduled publishing An editor can set a future date and time for content to publish or unpublish. Built in Publish later and unpublish later. 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 Separate preview tier. 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 Universal Editor and Page Editor. 9 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 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. Built in Launches group changes across pages and promote them together. 8 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. Limited Only with document authoring in Word or Google Docs. The Universal Editor has no co-editing. 10 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 AEM groups with repository permissions. 12 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. Limited Repository ACL restrictions can target named properties. No per-field setting in the editors. 12 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 SAML or OIDC federation through Adobe Admin Console. 13 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 Page, replication and DAM audit logs. 14 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 Multi Site Manager with live copies. 15 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 UI extensions built with App Builder. 16 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 Extension Manager catalogue of Adobe and partner extensions. 16 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. Built in Core Components form container emails, posts or stores submissions. 17 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. Limited Publish-tier login via SAML or OIDC. Sign-up flows need custom code and user sync. 1813 Not available
AI writing assistant A first-party AI feature in the editing interface generates, rewrites or translates content. Built in Generate Variations needs AEM Cloud Service with Edge Delivery entitlement. Licence includes an action allowance; extra actions cost more. 19 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. Built in AEM MCP Server for pages, fragments and assets. 20 Built in Built in at /_instatic/mcp, with OAuth or scoped personal access tokens. 20

Considering more platforms? Compare Adobe Experience Manager and Instatic with the rest of your shortlist in the CMS comparison tool.

Where they differ

Adobe Experience Manager and Instatic get a different status on 12 of the 28 features and the same status on 16. Adobe Experience Manager has 25 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
Adobe Experience Manager is closed source (Proprietary). Instatic is open source (MIT).
Self-hosting
Adobe Experience Manager cannot be self-hosted. Instatic can be self-hosted.
Vendor cloud
Adobe Experience Manager has a vendor-run cloud. Instatic has no vendor-run cloud.
Free option
Adobe Experience Manager has no free option. Instatic has a free option.

Built in on Adobe Experience Manager, a different answer on Instatic 10

  • Content model in code Adobe Experience Manager: Built in. Instatic: Not available.
  • Localization Adobe Experience Manager: Built in. Instatic: Not available.
  • REST API Adobe Experience Manager: Built in. Instatic: Limited.
  • GraphQL API Adobe Experience Manager: Built in. Instatic: Not available.
  • Webhooks Adobe Experience Manager: Built in. Instatic: Not available.
  • Approval workflows Adobe Experience Manager: Built in. Instatic: Limited.
  • Content releases Adobe Experience Manager: Built in. Instatic: Limited.
  • Single sign-on Adobe Experience Manager: Built in. Instatic: Not available.
  • Multiple sites Adobe Experience Manager: Built in. Instatic: Not available.
  • Plugin marketplace Adobe Experience Manager: Built in. Instatic: Not available.

Built in on neither, with different answers 2

  • Field-level permissions Adobe Experience Manager: Limited. Instatic: Not available.
  • Site member accounts Adobe Experience Manager: Limited. Instatic: Not available.

More comparisons

Full write-ups with worked examples and costs: Adobe Experience Manager vs Payload.

Adobe Experience Manager against other platforms

Instatic against other platforms

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.

Book a 25-min call Or email us instead