Instatic vs Wagtail
Instatic is an open-source site builder that you host yourself. Wagtail 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 16.
- Instatic Site builder · Open source · 15 of 28 built in
- Wagtail Traditional · Open source · 18 of 28 built in
Sources checked: Instatic on 30 Sept 2026, Wagtail 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
Built inPaid tierPlugin or add-onLimitedNot available
| Platform | |  |
|---|---|---|
| Overview | ||
| What it is | 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. | Open-source CMS built on Django. Content types are Python models, and you host it yourself on any Python stack. |
| Edition compared The product and release each column describes. | Instatic 0.0.20, open source Version 0.0.20, released 13 Sept 2026 | Wagtail 8, open source Version 8.0, released 25 Aug 2026 |
| Vendor | CoreBunch instatic.com | Wagtail core team (created by Torchbox) wagtail.org |
| Licence | Open source MIT | Open source BSD-3-Clause |
| Hosting | Self-hosting No vendor cloud No managed hosting. You deploy the Docker image to your own server, or use the Railway and Render templates. | Self-hosting No vendor cloud The Wagtail project runs no managed hosting. Deploy it like any Django app. |
| Built with | TypeScript, Bun, React admin | Python, Django |
| Database | SQLite, PostgreSQL | PostgreSQL, MySQL, MariaDB, SQLite |
| Pricing Public list prices only. Hosting and implementation are extra everywhere. | Free to start Free and open source, with no paid tiers. You pay only for hosting. | Free to start Free and open source. No licence fee. |
| 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. | Not available Tables and fields live in the database and change in the Data workspace. Plugins can create tables through the SDK. 610 | Built in Page and snippet types are Django models. 2 |
| Content model in the UI Admins can create and change content types and fields in the admin interface without writing code. | Built in Custom post types and data tables in the Data workspace. 616 | Not available Developers define content types in Python only. |
| Reusable blocks Editors compose pages from reusable, typed components or blocks, and can reorder them. | Built in Visual Components with typed parameters and named slots, placed and reordered on the canvas. 72 | Built in StreamField blocks. 2 |
| Localization Editors translate content per locale inside the CMS, by field or by entry, without a separate site for each language. | Not available One site-wide language setting. No per-locale fields or entries. 21 | Built in Core i18n with simple_translation. The wagtail-localize package adds a translation workflow. 3 |
| Image transformations The CMS resizes, crops or converts images on request, through URL parameters or generated sizes, with no external service. | Built in Uploads get a set of WebP sizes, and the publisher writes srcset and sizes from the layout. 81 | Built in Renditions with resize, crop and format filters. 4 |
| APIs and delivery | ||
| REST API A documented REST or JSON HTTP API returns content. | Limited The JSON API under /admin/api/cms serves the admin behind a session cookie. No token-based content API outside MCP. 920 | Built in Read-only v2 API. Writable v3 API in preview since 8.0. 51 |
| GraphQL API The vendor or an official module provides a GraphQL API for content. | Not available | Plugin or add-on wagtail-grapple, maintained by Torchbox. 6 |
| Webhooks The CMS can call an external URL when content is created, changed or published. | Not available No built-in webhooks. A plugin with network access can call a URL from content hooks. 10 | Not available Django signals such as page_published. No webhook settings. 18 |
| Renders the website The CMS itself renders and serves the public pages through themes or templates. Headless-only products answer no. | Built in Publishing renders every page to static HTML on the server's disk. 11 | Built in |
| Editorial workflow | ||
| Drafts Editors save changes as a draft and publish them later. The live version stays untouched until then. | Built in 51 | Built in |
| Scheduled publishing An editor can set a future date and time for content to publish or unpublish. | Built in Per page and per post-type entry. 5 | Built in Go-live and expiry dates. 7 |
| Version history The CMS keeps earlier versions of an entry, and editors can compare or restore them. | Built in Published versions of pages and entries, restorable into the draft. Added in 0.0.20. 124 | Built in Editors can compare and revert revisions. 11 |
| Preview Editors can see unpublished content rendered as it will appear on the site before publishing. | Built in The canvas renders drafts in the site design. Branch preview links work without an account. 122 | Built in 20 |
| Visual editing Editors can click on the rendered page and edit content in place or in a side panel next to it. | Built in Editing happens on the rendered page canvas, with a live mode for the full-size page. 214 | Limited Preview panel beside the edit form. No click-to-edit on the page. 20 |
| Approval workflows Content moves through review stages you configure, such as draft, review and approved, with permissions per stage. | Limited Branch merge requests with a review page and comments. No configurable review stages. 12 | Built in Moderation workflows with tasks assigned to groups. 8 |
| Content releases Editors group changes across several entries and publish them together as one release. | Limited Publish ships all draft pages at once. Branches group edits across pages and entries, but entries still publish one by one. 125 | Not available |
| Real-time co-editing Two or more editors can work on the same entry at once and see each other's changes live. | Limited Live co-editing of pages, components and layouts in the Site editor. Content workspace entries save separately. 13144 | Not available Concurrent editing notifications warn editors. No live co-editing. 12 |
| Access and governance | ||
| Custom roles Admins define their own roles with granular permissions instead of picking from a fixed set. | Built in The Owner builds roles from a fixed list of capabilities. 1516 | Built in Groups with page, collection and model permissions. 9 |
| Field-level permissions Admins can restrict access to single fields, on top of content types and entries. | Not available Capabilities apply per table type and edit category, not per field. 16 | Built in Set in code with the permission argument on panels. 10 |
| Single sign-on Editors can sign in through SAML or OpenID Connect against a company identity provider. | Not available Email and password with optional TOTP two-factor. 15 | Plugin or add-on django-allauth supports SAML and OpenID Connect. 19 |
| Audit log The CMS logs who changed what and when across the whole installation, and admins can review the log. | Built in Append-only log of logins, content changes, role edits and plugin actions. 17 | Built in Site-wide history report of logged actions. 11 |
| Platform and extensibility | ||
| Multiple sites One installation or account can manage several separate websites or brands with shared users. | Not available One site per installation. 2 | Built in Several sites in one installation with shared users. 9 |
| Extensible admin UI Developers can add their own components, views or fields to the editing interface. | Built in Plugins add admin pages, editor extensions, dashboard widgets and canvas modules. 10 | Built in Hooks, viewsets and custom panels. |
| Plugin marketplace The vendor runs an official directory or marketplace of installable extensions. | Not available Plugins install as uploaded zip packages. No official directory. 10 | Built in Wagtail packages directory on wagtail.org. 17 |
| Form builder Editors can build and publish forms and collect submissions without code. | Built in Forms are built on the canvas and submissions land in a data table. 18 | Built in wagtail.contrib.forms form builder. 13 |
| Site member accounts The platform handles sign-up and login for public site users or members, separate from editors. | Not available | Limited Login for private pages is built in. Public sign-up needs a package such as django-allauth. 14 |
| AI writing assistant A first-party AI feature in the editing interface generates, rewrites or translates content. | Built in Built-in agent in the Site and Content workspaces, with your own Claude, OpenAI, OpenRouter or Ollama key. 19 | Plugin or add-on Wagtail AI, an officially supported package. 15 |
| Official MCP server The vendor publishes a Model Context Protocol server so AI agents can read or write content. | Built in Built in at /_instatic/mcp, with OAuth or scoped personal access tokens. 20 | Limited Experimental wagtail-mcp package, announced September 2026. 16 |
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
Wagtail sources
Checked 29 Sept 2026. Wagtail 8, open source.
- Wagtail 8.0 release notes
- How to use StreamField for mixed content
- Wagtail docs: Internationalization
- Wagtail docs: Images
- Wagtail API v2 usage guide
- wagtail-grapple on GitHub
- Wagtail guide: Scheduled publishing
- Wagtail guide: Configure workflows for moderation
- Wagtail docs: Permissions
- Wagtail docs: Panels reference
- Wagtail docs: Audit log
- Wagtail 6.2: content metrics and concurrent editing
- Wagtail docs: Form builder
- Wagtail docs: Private pages
- Wagtail AI
- Experiments with MCP in Wagtail
- Wagtail docs: Packages
- Wagtail docs: Signals
- django-allauth: SAML provider
- Wagtail 4.0 release notes: live preview panel
Considering more platforms? Compare Instatic and Wagtail with the rest of your shortlist in the CMS comparison tool.
Where they differ
Instatic and Wagtail get a different status on 16 of the 28 features and the same status on 12. Instatic has 15 built in on its baseline edition, Wagtail has 18. Two matching statuses can still name different paid tiers or limits, so read the notes in the table before treating a row as equal.
Built in on Instatic, a different answer on Wagtail 4
- Content model in the UI Instatic: Built in. Wagtail: Not available.
- Visual editing Instatic: Built in. Wagtail: Limited.
- AI writing assistant Instatic: Built in. Wagtail: Plugin or add-on.
- Official MCP server Instatic: Built in. Wagtail: Limited.
Built in on Wagtail, a different answer on Instatic 7
- Content model in code Instatic: Not available. Wagtail: Built in.
- Localization Instatic: Not available. Wagtail: Built in.
- REST API Instatic: Limited. Wagtail: Built in.
- Approval workflows Instatic: Limited. Wagtail: Built in.
- Field-level permissions Instatic: Not available. Wagtail: Built in.
- Multiple sites Instatic: Not available. Wagtail: Built in.
- Plugin marketplace Instatic: Not available. Wagtail: Built in.
Built in on neither, with different answers 5
- GraphQL API Instatic: Not available. Wagtail: Plugin or add-on.
- Content releases Instatic: Limited. Wagtail: Not available.
- Real-time co-editing Instatic: Limited. Wagtail: Not available.
- Single sign-on Instatic: Not available. Wagtail: Plugin or add-on.
- Site member accounts Instatic: Not available. Wagtail: Limited.
More comparisons
Instatic against other platforms
- Adobe Experience Manager vs Instatic
- Contentful vs Instatic
- Contentstack vs Instatic
- CoreMedia Content Cloud 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 Webflow
- Instatic vs Wix
- Instatic vs WordPress
- Instatic vs Xperience by Kentico
Wagtail against other platforms
- Adobe Experience Manager vs Wagtail
- Contentful vs Wagtail
- Contentstack vs Wagtail
- CoreMedia Content Cloud vs Wagtail
- Craft CMS vs Wagtail
- DatoCMS vs Wagtail
- Decap CMS vs Wagtail
- Directus vs Wagtail
- Drupal vs Wagtail
- EmDash vs Wagtail
- FirstSpirit vs Wagtail
- Framer vs Wagtail
- Ghost vs Wagtail
- HubSpot CMS vs Wagtail
- Hygraph vs Wagtail
- Joomla vs Wagtail
- Keystone vs Wagtail
- Kirby vs Wagtail
- Liferay DXP vs Wagtail
- Optimizely CMS vs Wagtail
- Wagtail vs Payload
- Prismic vs Wagtail
- Progress Sitefinity vs Wagtail
- Sanity vs Wagtail
- Sitecore vs Wagtail
- Squarespace vs Wagtail
- Statamic vs Wagtail
- Storyblok vs Wagtail
- Strapi vs Wagtail
- TYPO3 vs Wagtail
- Umbraco vs Wagtail
- Wagtail vs Webflow
- Wagtail vs Wix
- Wagtail vs WordPress
- Xperience by Kentico vs Wagtail
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.