Multi-Tenant CMS vs WordPress Multisite: What Running 20+ Sites Really Costs
- RedClaw Performance Team
- RedClaw Performance Team
- Date
- Reading time
- 10 min read
TL;DR: WordPress Multisite hosting can be cheap, and Multisite already solves part of the problem: one codebase, and only the network's Super Admin can install plugins and themes. For a head office running 20 or more agent or franchise sites, the real cost is elsewhere: who tests every plugin update for every site, who stops an agent from switching themes or editing settings, how you hand a site over when an agent leaves, and how SEO↗ rules stay consistent when 20 people publish. A managed multi-tenant CMS swaps that work for a fixed monthly fee and fewer choices. Pick Multisite if you have a WordPress developer on staff and need plugins. Pick a managed platform if you'd rather nobody on your side touches servers. Below: a cost worksheet you can fill in with your own quotes, and a year-one calculation for our platform.
Disclosure: we build one of the managed options, the RedClaw Site Network. It is in development and has no live clients yet, so nothing below is a customer result.
What WordPress Multisite already gets right
Multisite runs many sites from one WordPress install, and the network's Super Admin controls which plugins and themes exist at all.
Per the WordPress handbook on creating a network↗ (checked 2 November 2026), individual sites in a network can activate plugins and themes but "install neither". The roles and capabilities documentation↗ (checked 2 November 2026) lists the update and install capabilities that, on Multisite, only the Super Admin has: update_core, update_plugins, install_plugins, install_themes and a few more.
That is a real advantage over 20 separate WordPress installs, and comparisons that skip it aren't being fair. But read the same page for what a site Administrator still keeps on Multisite: activate_plugins, switch_themes, edit_theme_options, manage_options and delete_site. If you make each agent the Administrator of their own site, they can still change the theme, deactivate the SEO plugin or delete the site. You can give agents the Author role instead, which is the right move, but then someone at HQ is doing every settings change for 20 sites by hand.
Where the cost of 20+ sites actually sits
The hosting line is the smallest number on the sheet. Updates, plugin risk, onboarding and SEO consistency are the lines that grow with each site.
We're not going to quote WordPress hosting prices here, because they vary by provider, contract length and renewal terms, and any number we print would be out of date by the time you read it. Get your own quotes and put them in the left column.
| Cost line | WordPress Multisite (fill in your quote) | Managed multi-tenant CMS |
|---|---|---|
| Hosting, SSL, backups | Host's quote for a Multisite-capable plan | Included in the per-site fee |
| Core, theme and plugin updates | Developer hours per month × rate | Included |
| Premium plugin licences | Sum of licences that bill per site or per network | None to buy |
| Security monitoring and cleanup | Monitoring service + incident hours | Included |
| Agent onboarding and offboarding | HQ admin hours per agent | Invite and transfer in the dashboard |
| SEO consistency across sites | Audit hours per month | Rules enforced by the dashboard |
| Design per site | Theme licences + customisation | Template choice; custom template fee |
The plugin line deserves more weight than it usually gets. Patchstack's State of WordPress Security in 2025↗ report (updated 14 March 2025, checked 2 November 2026) counted 7,966 new vulnerabilities in the WordPress ecosystem in 2024, with 96% found in plugins and 4% in themes; only seven were in core. On Multisite a plugin is installed once for the whole network, so one vulnerable plugin is code that sits behind every site in it. That is the same property that makes Multisite convenient, seen from the other side.
The SEO cost nobody budgets for
With 20 people publishing, SEO rules drift unless software enforces them. Manual audits catch drift after it ships.
We run more than 20 SEO sites of our own, and drift is the cost we underestimated most. On our main site, a scan on 23 August 2026 found 398 internal links missing the trailing slash our URLs require, across 67 articles. Each one cost a redirect. A week later, on 30 August 2026, 240 of 447 internal link targets (54%) did not return a clean 200. Nobody did anything wrong on purpose: each writer followed what looked right. One editor, one site, and it still happened.
Multiply that by 20 agents who aren't SEO people. A plugin can warn them, but they can switch it off or ignore it. What changes the outcome is rules that live in the publishing tool and can't be bypassed: required title and description fields, required author details, outbound commission links marked rel="sponsored" automatically, sitemaps and canonicals generated rather than typed. That's the main reason we built our platform as a multi-tenant CMS instead of selling clients WordPress installs. When we costed 20 WordPress sites for a prospective client, the honest summary was 20 systems to update and 20 sets of settings an agent could change.
What a managed multi-tenant CMS changes
In a multi-tenant CMS one codebase serves every site, the vendor runs it, and roles are narrower than WordPress roles. You give up flexibility for control.
Our own platform works like this, as specified while it's still in development. The head office has one account that opens and sees every site. Agents can write posts and upload images, and that's all; they can't touch layout, menus or settings, so they can't break a site. There are five templates. We run hosting, SSL, backups and updates. Domains, content, Search Console and GA4↗ stay in the client's name and can be exported in one step. You don't install plugins on it, which also means you can't extend it with them. If your sites need a plugin that does something specific, that is a point for WordPress.
Year-one cost for a head office with 20 agent sites on a ready-made template, at our published prices in USD: setup 20 × 180 = 3,600; head-office dashboard 12 × 99 = 1,188; platform fee 20 sites × 12 months × 20 = 4,800. Total 9,588, or about 39.95 per site per month including setup. From year two it's 1,188 + 4,800 = 5,988, about 24.95 per site per month. A custom template adds a one-off 500; strict isolation (its own deployment, outside routine platform updates) adds 10 per site per month, which would be 2,400 a year across all 20. Compare that with the filled-in left column of the worksheet above, not with a hosting price alone.
When WordPress Multisite is the better choice
Multisite wins when you already have WordPress skills in house, need plugins, or want to host the network yourself.
| Your situation | Better fit |
|---|---|
| A WordPress developer on staff with time for updates | Multisite |
| Sites need e-commerce, memberships or other plugins | Multisite |
| You want to self-host and control the server | Multisite |
| Agents aren't technical and must not change layout | Managed multi-tenant CMS |
| Agents join and leave often; sites must stay with HQ | Managed multi-tenant CMS |
| Nobody on your side should touch servers or updates | Managed multi-tenant CMS |
| You need 5 to 10 sites and have one capable admin | Either; cost the left column first |
One more thing that applies whichever you pick: the risk in a network of agent sites is mostly about content, not software. Twenty sites with the same articles reworded are a problem on any CMS. We wrote up the four Google policies that matter in Google spam policies for multi-site networks. And if you'd rather rent established sites than run your own, that's a different product with ownership the other way round; see our SEO sites for sale or lease.
Questions to ask any managed WordPress Multisite host
Managed WordPress Multisite hosting sits between the two options: you keep WordPress, and the host takes over part of the maintenance.
If that middle path appeals, these are the questions we'd ask, because they map to the cost lines that usually stay with you: Who tests plugin updates before they reach all sites, and what happens when one breaks a site? Are premium plugin licences included? Can agents be limited below Administrator without HQ doing every settings change? Who is the verified Search Console owner of each site? Can you leave with a full export, and in what format? If the answers put the work back on your team, put those hours in the worksheet.
FAQ
Is WordPress Multisite cheaper than a managed multi-tenant CMS?
The hosting usually is. The full cost depends on developer hours, plugin licences and admin time, which are the lines most comparisons leave out. Fill in the worksheet with your own quotes before comparing.
Can agents break a site on WordPress Multisite?
Site Administrators on Multisite can't install plugins or themes, but per WordPress's roles documentation they can still activate plugins, switch themes and change options. Giving agents the Author role prevents that, at the cost of HQ handling every settings change.
What is a WordPress Multisite alternative for agent networks?
A managed multi-tenant CMS: one platform serves every site, the vendor runs hosting and updates, and agents get a narrow publishing role. The trade-off is fewer plugins and less customisation.
Does RedClaw Site Network have live clients?
Not yet. The platform is in development, so we publish prices and product rules, not customer results.
Can we move off the platform later?
Domains, content, Search Console and GA4 are in your name, and everything can be exported in one step.
Related Posts
- strategyGoogle Spam Policies That Matter for Multi-Site Networks: Doorways, Scaled Content, Link Spam, Expired DomainsFour Google spam policies decide whether an agent or franchise site network is a business or a liability. What each one says, and the compliant way to run 20+ sites.
- strategyGEO Maintenance: Is It One and Done? AI Citations Have an 11-Day Half-LifeProfound tracked 883,000 pages for a year: AI citations fall by half a median 11 days after their peak. Why GEO maintenance is monthly work, plus our 5 steps.
- strategyAI Content Quality Checklist for Bulk Publishing: 12 Pre-Publish Checks and a Front-End AuditAI publishing errors at scale are template errors: one bug ships in a dozen posts. Our 12 pre-publish checks, a front-end audit, and why auto-fixes need a lint.