The open-source Django CMS's 2026 release, whose new v3 REST API turns your website content into an agent-drivable, AI-ready backend — with an OpenAPI schema endpoint agents can read.
Last verified · 2026-08-28 · by Moe Ameen
Wagtail is a free, open-source content management system built on Django and Python, maintained by the agency Torchbox and used to run content-heavy websites. Version 8.0, released August 25, 2026, is the release that made it interesting for AI workflows: it adds a preview v3 REST API that can write, not just read.
Where the older v2 API only served content out to headless front-ends, the v3 API exposes more than 50 admin operations over HTTP. An authenticated client — a script, an internal tool, or an AI agent — can create, edit, publish and unpublish, move, copy, and revert content, and manage drafts and revisions, across pages, images, documents, snippets, redirects, sites, and locales. It is built on Django Ninja with Python type hints, can return rich text as HTML or Markdown, and uses token authentication plus Wagtail's existing permissions model.
The AI-ready part is deliberate. The API ships a schema endpoint that auto-generates OpenAPI 3.1 documents, so an agent can fetch the schema, discover exactly what operations exist, and drive the CMS deterministically instead of guessing. Wagtail's framing is "a CMS with AI, not an AI CMS" — no AI features are switched on in the admin by default, and the separate Wagtail AI package is opt-in. The value is a clean, typed, writable backend that both people and agents can operate.
Two honest caveats. First, the v3 API is a preview and may change in backwards-incompatible ways until it stabilizes. Second, this is a developer tool: standing it up means Django, tokens, and permissions — not a no-code switch. And it is a website CMS, so it renders no social video, no captions, and no carousels, and publishes to no social platform. It is the backend, not the content factory or the distribution layer.
Think of Wagtail 8.0 as the programmable home for your website content, and Kompozy as the engine that fills it and carries the same ideas everywhere else. The v3 API is an excellent backend — typed, writable, agent-discoverable — but a backend is an empty warehouse until something generates the content and a system distributes it. Wagtail does neither the making nor the social publishing; that is exactly the half Kompozy owns.
The concrete build: point Kompozy at one source and it generates the full set under a single Persona Brief — a Blog Article, Email Newsletter, Persona Shorts and HeyGen avatar video, Clipped Shorts, brand-exact Carousel Posts, Quote Graphics, and Text Posts. The blog output can flow into your site through a destination like a Custom Webhook — the same programmatic, agent-friendly shape Wagtail's new API is built around — while the very same idea ships as captioned video, carousels, and posts across the eight primary social platforms plus email, on a schedule or on Autopilot with a per-post review gate. Wagtail 8.0 makes your website addressable by code; Kompozy is the content it serves and the social reach it will never have on its own.
Wagtail 8.0 is the August 25, 2026 release of Wagtail, the free open-source Django CMS built by Torchbox. Its headline feature is a preview v3 REST API that can write content — create, edit, publish, move, copy, revert — with an OpenAPI 3.1 schema endpoint designed for AI agents.
Yes. Wagtail is free and open-source, built on Django and Python. You host it yourself (or via a host), so the cost is infrastructure and engineering time rather than a subscription. Confirm current details on wagtail.org.
No. Wagtail is a website CMS — it stores, manages, and serves your site content. It generates no social video, captions, or carousels and publishes to no social platform. To generate that content and distribute it, pair it with a content engine like Kompozy.
It is a preview. Wagtail warns the v3 API may change in backwards-incompatible ways in any release until it stabilizes, so build against it carefully and confirm endpoint details in the official Wagtail 8.0 release notes.
For the v3 API, effectively yes — it means Django, token setup, and permissions work. If you want content generated and published across social and email without engineering, that is a different, no-code job better handled by an engine like Kompozy.