Wagtail alternative

Hatamoto vs Wagtail

Wagtail's own docs say it is not an instant website in a box and that you should expect to write code. Hatamoto is built for the opposite case: content types, SEO, forms and redirects you set up in the admin, with no code. Wagtail is ahead on editorial workflow and languages.

Install Hatamoto See the full comparison

Hatamoto ahead: 14 No-code setup, built-in SEO, AI agents, plugins and updates
Wagtail ahead: 12 Workflow, permissions, languages, multisite and custom Django code
About the same: 11 Licence, preview, revisions and forms

Line by line

The full comparison

37 lines in nine groups. Open a group to see each line. "Ahead" means better out of the box for a typical business website.

Hatamoto aheadWagtail aheadAbout the same

Platform and hostingHatamoto 1Wagtail 3Even 2

Platform and hosting: Hatamoto vs Wagtail
Line	Hatamoto	Wagtail	Ahead
What you run	One Go binary and a Postgres database	A Django project in Python that a developer builds and deploys	Hatamoto
Licence	Apache-2.0, open source	BSD-3-Clause, open source	Even
Database	Postgres only	Postgres, MySQL, MariaDB or SQLite	Wagtail
Hosting	A VPS or container host	Any Django host, or a specialist host such as CodeRed Cloud	Even
More than one language	No, one language per site	A page tree per language, with translation tools	Wagtail
Several sites from one install	No, one install per site	Built in, with each site a branch of the page tree	Wagtail

Editing and contentHatamoto 1Wagtail 4Even 3

Editing and content: Hatamoto vs Wagtail
Line	Hatamoto	Wagtail	Ahead
Adding a content type	In the admin, no code	A Python model, a migration and a template	Hatamoto
Flexible page content	Section-based page builder	StreamField blocks, each one defined by a developer	Even
Live preview	Built in	Built in, and it refreshes as you type	Even
Revisions and scheduling	Built in	Built in, with revision comparison	Even
Review and approval	Not included	Moderation workflows, on by default	Wagtail
Editor comments	Not included	Inline comments with email alerts	Wagtail
Roles and permissions	Owner and editor	Group permissions on any branch of the page tree	Wagtail
Accessibility checks while editing	Not included	A built-in accessibility checker	Wagtail

SEO and AI searchHatamoto 4Even 2

SEO and AI search: Hatamoto vs Wagtail
Line	Hatamoto	Wagtail	Ahead
SEO titles and descriptions	Built in and printed in every page head	Fields on every page, printed by your templates	Even
Open Graph and social tags	Built in	Added by hand in your templates	Hatamoto
Sitemaps	Built in	A contrib module you switch on and add a route for	Hatamoto
Schema markup (JSON-LD)	Built in for every content type	Not in core or contrib	Hatamoto
Redirects	Built in, with a 404 log	A contrib module, with automatic redirects when a page moves	Even
AI crawler reports and llms.txt	Built in	Not available	Hatamoto

AI agents and developer toolsHatamoto 1Wagtail 1Even 1

AI agents and developer tools: Hatamoto vs Wagtail
Line	Hatamoto	Wagtail	Ahead
MCP server	Built in	An experimental package whose README calls it an early prototype	Hatamoto
AI writing help	Not included	The Wagtail AI package, for titles, alt text and feedback	Wagtail
API	REST API with scoped keys	A read-only API, plus a read and write API in preview	Even

SpeedEven 2

Speed: Hatamoto vs Wagtail
Line	Hatamoto	Wagtail	Ahead
Page caching	In memory, cleared on every edit	Django caching, plus CDN purges when you publish	Even
Site search	Built in	Built in, with Elasticsearch for large sites	Even

Site featuresHatamoto 3

Site features: Hatamoto vs Wagtail
Line	Hatamoto	Wagtail	Ahead
Forms	Built in, with spam protection and CSV export	A contrib module, once a developer adds a form page type	Hatamoto
Visitor analytics	Built in, no cookies	Not included	Hatamoto
Webhooks	Built in and signed	A developer writes Django signal handlers	Hatamoto

Plugins and themesHatamoto 2Wagtail 1

Plugins and themes: Hatamoto vs Wagtail
Line	Hatamoto	Wagtail	Ahead
Plugin safety	Every plugin runs in a WebAssembly sandbox	Packages are Django apps with full access to your site	Hatamoto
Packages	A small signed first-party set	A directory of Python packages, plus all of Django	Wagtail
Themes	Installable themes with a page builder	None, your developer writes the templates	Hatamoto

Security and dataHatamoto 1Wagtail 1Even 1

Security and data: Hatamoto vs Wagtail
Line	Hatamoto	Wagtail	Ahead
Updates	Signed and automatic, with release channels and rollback	pip upgrades, migrations and a deploy, every three months	Hatamoto
Long-term support	Fixes on the latest minor	An LTS release every year, supported for 18 months	Wagtail
Staff sign-in	Password, rate limits and a private admin address	Django sign-in, which Django packages can extend	Even

Track record and communityHatamoto 1Wagtail 2

Track record and community: Hatamoto vs Wagtail
Line	Hatamoto	Wagtail	Ahead
Maturity	Pre-1.0, runs hatamoto.dev	Since 2014, now on version 8	Wagtail
Community	Small and growing	About 20,000 GitHub stars and close to 1,000 listed contributors	Wagtail
Importing from WordPress	Built in, with a URL audit	A Torchbox package with stale compatibility notes	Hatamoto

Compared against Wagtail 8.0 core and its contrib modules on 28 October 2026. Sources: Zen of Wagtail, product strategy, Wagtail on GitHub, sitemaps, wagtail-mcp, release schedule. Found something out of date? Open an issue.

01
Wagtail expects you to have a developer

Page types are Python models, and the Zen of Wagtail page in its docs says to expect to write code. In Hatamoto you set up content types in the admin, with no code.
Content types
02
Wagtail is aimed at larger organisations

Its 2026 product strategy says the low-budget, low-complexity website market is not Wagtail's market. That is the market Hatamoto is built for.
Install Hatamoto
03
SEO markup with no template work

Hatamoto prints the meta tags, social tags and JSON-LD itself and serves the sitemap. In Wagtail your templates print them, and the sitemap is a module you switch on.
SEO and AI search
04
An MCP server in the core today

Hatamoto's MCP server is part of the core. Wagtail's MCP package describes itself as an early prototype.
Hatamoto's MCP server
05
Upgrades without a deploy

Hatamoto installs signed patch and minor releases itself. A Wagtail site is a Python project that you upgrade, migrate and redeploy.
How updates work
06
Wagtail is ahead on editorial process

Moderation workflows, inline comments, tree-based permissions and per-language page trees suit large editorial teams. Hatamoto has two roles and one language.
What Hatamoto leaves out

Being straight with you

When Wagtail is the better choice

Choose Wagtail if any of these describe your organisation.

You have Python or Django developers on staff or on retainer.
Content needs review and approval before it goes live.
Different teams own different sections of the site.
You publish in several languages or run several sites from one install.
The site needs custom Django logic beyond publishing.
You want a long-term support release on a fixed schedule.

Moving from Wagtail

Moving from Wagtail through its API

There is no Wagtail importer. Wagtail's read API returns every page as JSON, so a script or an AI agent can carry the content across.

1
Install Hatamoto
Run it with Docker or as the single binary, next to a Postgres database. Getting started
2
Map your page models
Create a Hatamoto content type for each Wagtail page model, and sections for your StreamField blocks. Content types
3
Copy pages and images
Read pages from Wagtail's API, convert the StreamField JSON to sections or HTML, and create them through Hatamoto's MCP server or CLI. Connect an AI agent
4
Keep your URLs
Wagtail URLs follow the page tree. Match them with Hatamoto URL patterns or add redirects, then switch the domain over. URL patterns

Questions people ask

Written by the Hatamoto team, from Wagtail's documentation and releases as of October 2026.

Is Hatamoto a Wagtail alternative?

For a business site run without a developer, yes. Hatamoto is set up in the admin and has SEO, forms and redirects built in. For organisations with Django developers and complex editorial needs, Wagtail is the better choice.

Do I need a developer to use Wagtail?

Yes, to build the site. Wagtail's docs assume you know Django and virtual environments, page types are Python models, and the templates are yours to write. Once the site is built, editors get a friendly admin.

Does Wagtail have SEO features?

Every page has an SEO title and a search description, and contrib modules add sitemaps and redirects. Social tags and JSON-LD are up to your templates. Hatamoto outputs all of these with no template work.

Does Wagtail support AI and MCP?

AI is opt-in through the Wagtail AI package, by design. The official MCP package is experimental and labelled an early prototype. Hatamoto's MCP server is built in, with scoped keys and an audit log.

Is Wagtail free?

Yes. Wagtail is BSD-3 licensed, with no licence fees. The costs are developer time and Django hosting. Hatamoto is also free, and you set it up without writing code.

How do I move from Wagtail to Hatamoto?

Create matching content types, read your pages from Wagtail's API, convert the StreamField blocks, and create the pages through Hatamoto's MCP server or CLI. Add redirects for any URL that changes.

Hatamoto vs WordPress

The plugin stack most business sites run on, against one binary with SEO, caching and forms built in.
Read the comparison

Hatamoto vs Wagtail

37 lines compared

The full comparison

Six things to settle before you pick Wagtail

Wagtail expects you to have a developer

Wagtail is aimed at larger organisations

SEO markup with no template work

An MCP server in the core today

Upgrades without a deploy

Wagtail is ahead on editorial process

When Wagtail is the better choice

Moving from Wagtail through its API

Install Hatamoto

Map your page models

Copy pages and images

Keep your URLs

Questions people ask

Other comparisons

Hatamoto vs WordPress