Wagtail

How to choose a Wagtail agency: 10 checks before you hire

To choose a Wagtail agency, look for a team that builds in Django, starts on a supported Wagtail release, designs the editor with you and hands over code you own.

Most guides to choosing an agency were written for WordPress or for software in general. Wagtail needs a few checks of its own, because it behaves differently from a theme-based CMS. Below are the ten we would make if we were the ones hiring, with the version dates that matter in November 2026.

Why a Wagtail agency is really a Django agency

Wagtail is an open-source CMS built on Django, the Python web framework. That changes what you are buying. Each type of page on your site is a Python model, written by a developer. The blocks your editors drag into a page are Python classes. Forms, search, logins and links to your CRM are ordinary Django code.

So the people who build your site need to be comfortable in Python and Django, not only in HTML and CSS. A studio that mostly installs WordPress themes can learn Wagtail, but it will be learning on your project. The developers you want have built Django applications before, and use Wagtail as the editing layer on top. That is how we describe our own Wagtail CMS development: editor-friendly content management on top of a Django app.

Ten checks before you hire a Wagtail agency

1. They build in Django, not just templates

Ask to see Django work as well as Wagtail sites: an application, an API, an integration. Then ask how they would build the most awkward part of your site, such as a members' area, a booking form or a product feed. A good answer names models, permissions and tests. A weak one talks only about the page design.

2. They start on a supported release

Wagtail ships a new feature release every three months. Normally a release gets fixes only until the next one comes out. Every fourth or so is a long-term support (LTS) release, which keeps getting security and data-loss fixes for about eighteen months. These are the dates on Wagtail's release schedule today:

Wagtail releases and support dates, checked 19 November 2026 (sources: Wagtail release schedule and Wagtail upgrade docs)
ReleaseReleasedSecurity fixes endDjango versions
7.0 LTS6 May 20252 November 2026 (ended)n/a (no longer supported)
7.4 LTS4 May 20262 November 20275.2, 6.0
8.025 August 20262 February 20275.2, 6.0, 6.1
8.12 November 20264 May 20275.2, 6.0, 6.1

The Django column comes from Wagtail's compatibility table. A new build today should start on 7.4 LTS or 8.1, on Django 5.2 LTS, which Django supports until April 2028. If a proposal names an older version, or doesn't name one at all, ask why. Wagtail 7.0 LTS lost support on 2 November 2026, so anyone still quoting it is working from an old template.

3. They show you the editor before they write code

The editor is where your team will spend its time, so it deserves a design of its own. A good agency sits down with the people who will publish, lists the content they produce, and agrees which page types and blocks they need. Wagtail's StreamField lets editors build a page from blocks you have chosen, and our guide on how StreamField works explains why that beats one big rich-text box. Ask to see a page model or a block list in the first weeks, not just a homepage design.

4. Accessibility is part of the build

Ask which standard they build to. WCAG 2.2 AA is a sensible answer, and we build every site to it. Wagtail helps editors keep pages accessible after launch: it has a built-in content checker, based on the Axe testing engine, that runs from the user bar and in editing views that support preview. Images can carry a description for alt text (added in Wagtail 6.3), and editors can mark an image as decorative. Ask whether the agency will turn those on and show your editors how to use them.

5. They have a plan for languages

If you publish in more than one language, ask how. Wagtail has multilingual support built in, switched on with the WAGTAIL_I18N_ENABLED setting. There are two ways to manage translations. The built-in simple_translation app copies a page into another language as a draft, still in the source language, for someone to translate. The wagtail-localize package goes further, with PO files, machine translation and external translation services. Which one fits depends on who translates your content, and the agency should ask you that before choosing.

6. Migration is costed, not waved through

Most Wagtail projects replace an existing site, and moving the content is often the riskiest part. Ask how they will map old pages to new page types, whether the import is scripted or done by hand, and how they will keep every old URL working with redirects. If you are moving from WordPress, our WordPress to Wagtail migration guide lists the steps to look for in their plan.

7. Upgrades are in the plan

With a feature release every quarter and LTS support of about eighteen months, your site will need an upgrade every year or so to stay covered. Ask who does that work, how it is priced, and how they test it. An agency that leaves upgrades out of its proposal is leaving you a bill for later.

8. You own the code and the accounts

The repository, the hosting account, the domain and the analytics should be in your name, or handed over at launch. Wagtail itself is open source under a BSD licence, so there is no CMS licence to rent. Check the contract says the code written for you is yours, and ask what the handover includes: documentation, a setup guide for another developer, and training for your editors.

9. You meet the people who will build it

Ask who will write the code and who you will talk to each week. In a large agency the people at the pitch are often not the ones on the project. That isn't always a problem, but you should meet the developers before you sign. At Webbyfox the person who emails you is the person who builds your site; we are small on purpose.

10. They can show live Wagtail work

Ask for links to Wagtail sites they built and still look after, and ask to see the editor of one if the client agrees. Made with Wagtail, a showcase maintained by the Wagtail project, credits the developer or agency behind each site, so you can look up who built what.

Agency, freelancer or in-house team?

A freelance Wagtail developer can be a good fit for a small site with a clear brief, or for extra help alongside your own team. The risk is cover: one person means one point of failure for holidays, illness and upgrades. An agency costs more per day, but gives you design, development and support in one contract. Hiring in-house makes sense once the site is a product your company works on every week. We compare the three on cost and risk in in-house, freelancer or agency?

Red flags in a Wagtail proposal

  • No Wagtail or Django version named, or a version that is already out of support.
  • A fixed price before anyone has looked at your content or your current site.
  • Nothing about redirects, editor training or what happens after launch.
  • The agency keeps the hosting or the repository in its own name, with no handover clause.
  • Every example of their work is a WordPress theme.
The ten checks
  • 1. They build in Django, not just templates.
  • 2. They start on Wagtail 7.4 LTS or 8.1, on Django 5.2 LTS.
  • 3. They design the editor with you before building pages.
  • 4. They build to WCAG 2.2 AA and set up Wagtail's accessibility checker.
  • 5. They ask who translates before choosing a translation set-up.
  • 6. Migration and redirects are in the plan and the price.
  • 7. Upgrades after launch are planned and priced.
  • 8. You own the code, hosting, domain and analytics.
  • 9. You meet the developers before you sign.
  • 10. They show live Wagtail sites they still look after.

If you would rather settle these questions before committing to a full build, our two-week discovery sprint ends with a scope, an estimate with its assumptions written down, and a working prototype in your repository.

Questions

Is Wagtail free to use?

Yes. Wagtail is open source under a BSD licence, so there is no licence fee. You pay for the people who build and look after the site, and for hosting.

Can a WordPress agency build a Wagtail site?

Only if it has Python and Django developers. Wagtail page types, blocks and integrations are written in Python, so theme and plugin skills don't carry over. Ask to see Django work as well as finished websites.

Which Wagtail version should a new site use?

As of November 2026, Wagtail 7.4 LTS (security fixes until 2 November 2027) or 8.1 (until 4 May 2027), on Django 5.2 LTS. Pick the LTS if you want fewer upgrades; pick 8.1 if you need its newer features and will upgrade again soon.

How often does a Wagtail site need upgrading?

Wagtail releases a new version every three months, and an LTS release gets about eighteen months of security fixes. Plan for at least one upgrade a year, more if you follow the newest release.

Need this on your codebase? Talk to us about Django development.
See Django development
R
Rizwan Mansuri, Technical Director Builds and upgrades Python web applications for UK teams. More about us.

Keep reading