The choice of CMS decides the security, lifespan and autonomy of your website. WordPress runs a huge share of the web: 41.5% of all websites according to W3Techs (checked on 2 July 2026). Wagtail powers Google, NASA's Jet Propulsion Laboratory, the British NHS and more than 60 French government websites. Here is the honest comparison, without dogma.
WordPress: ease, at the price of debt
WordPress has one immense merit: everyone knows it, and there is a theme or plugin for everything. That is also its problem. A typical WordPress site rests on a pile of third-party extensions, each with its updates, its potential flaws and its conflicts. The common result after three years: a slow, fragile site that nobody dares update any more.
Wagtail: architecture first
Wagtail is an open source CMS built on Django (Python), one of the most solid frameworks on the market. The difference in philosophy is simple: instead of assembling plugins, features are developed to measure, in a clean architecture. Our full definition is in the glossary.
The comparison, criterion by criterion
| Criterion | WordPress | Wagtail |
|---|---|---|
| Getting started | Very fast (ready-made themes) | Custom development required |
| Day-to-day editing | Good, but interfaces cluttered by plugins | Clean interface, designed for your content |
| Security | Depends on the diligence of installed plugins | Django base, reduced attack surface |
| 5-year cost of ownership | Updates, plugin licences, fixes | Stable: few dependencies to maintain |
| Custom evolution | Limited by the plugin ecosystem | Free development, you own the code |
| Multilingual | Via third-party plugins | Native, designed into the architecture |
| Supplier ecosystem | Huge | Smaller, more specialised |
Choose WordPress if...
Honesty requires it: Wagtail is not the answer to everything.
- Your budget is under EUR 5,000 and you accept a standardised site.
- You want to run the site yourself from A to Z, without a technical partner, on an off-the-shelf theme.
- Your need is a simple blog or a temporary site, with no strong credibility stakes.
A well-built WordPress beats a botched Wagtail anyway. The CMS does not do everything: quality comes from the architecture, the design and the rigour of whoever builds.
Choose Wagtail if...
- Your website carries your commercial credibility and must last without a forced rebuild.
- You want to own the code, not rent an assembly of plugins.
- Your project involves multilingual content, business integrations or genuinely custom layouts.
- Security is an argument towards your own clients (accounting professions, medical sector, institutions).
The cost of ownership, item by item
The purchase price says nothing about the real cost. Over five years, a plugin-heavy WordPress site accumulates: yearly licences for premium extensions (forms, SEO, caching, security...), repair work when an update breaks a feature, and the internal time lost managing those incidents. Every plugin is an implicit maintenance contract nobody signed.
A Wagtail site inverts the logic: the initial investment is higher, but the base depends only on Django and your own code. Updates are planned, not suffered. Over the life of a busy professional site, the two curves cross well before year five.
Security, in practice
WordPress's security problem is not WordPress itself, which is patched regularly, but its supply chain: thousands of plugins of uneven quality, maintained (or not) by third parties. The vast majority of WordPress compromises come through an extension or a theme, not the CMS core. Every added plugin is one more door to watch.
Django, Wagtail's foundation, is a framework whose reputation was built on rigour: built-in protections against classic attacks, a serious patch cycle, and above all, on a custom site, only the code you actually need. Fewer doors, less watching, fewer bad surprises.
And the other options?
The question is not limited to these two. No-code platforms (Webflow, Wix, Squarespace) are legitimate for an entry-level site: fast, hosting included, but you remain a tenant, with the engine's limits and prices that change without you. One exception: entry-level sites generated by AI rather than built on a platform, where the produced code belongs to you. Drupal plays in Wagtail's league for sturdiness, with a steeper learning curve. Our simple rule: at entry budgets, a well-executed no-code build; as soon as the site carries your credibility and must last, custom code that you own.
What it looks like in real life
It is the choice we have made since 2015: more than ten years of Wagtail projects, often multilingual, often demanding. A telling example: the Venn Telecom website, a sharp technical offer (satellite, 5G, bonding) made readable for several audiences, on a base their team runs themselves.
And if you are starting from an ageing WordPress, the migration can be prepared: content carried over, redirects, visibility preserved. The full method is in this article.
The questions we get asked
Will my team really be able to edit without a developer? Yes: Wagtail's editing interface is precisely its strength. Text, images, pages, articles: everything is edited in-house, and getting started takes one short training session, included at delivery.
Is migrating from WordPress long? Count on a classic rebuild, about twelve weeks for a custom site, migration included. Content is carried over, addresses are redirected, visibility is preserved with method.
Is Wagtail here to stay? The project is open source, backed by a foundation and adopted by organisations that do not choose their tools lightly (Google, NASA, NHS). And since you own your code, you are nobody's prisoner, not even ours.
Hesitating for your own site? Describe your project and we will tell you honestly whether Wagtail is justified, or not.