Multisite licensing is where “one licence, unlimited sites” marketing collides with the reality that each subsite is often a separate activation. For an agency running client sites on a multisite network — the common deployment model — this matters for both cost and compliance, and the details are not obvious until they bite. This covers how multisite activation actually works, how plugin licensing maps onto it, and what to check before you network-activate, so the licensing model does not surprise you mid-project.
It is the multisite deep-dive of our developer’s guide, paired with white-labelling as the two agency-delivery pieces.
Network-activated vs per-site activation
The first fork on multisite is how a plugin is activated. Network-activated: the super-admin activates the plugin across the entire network, it runs on every subsite, and individual site admins cannot deactivate it — useful for plugins every site must have, but a blunt instrument. Per-site activation: the plugin is available on the network but each subsite chooses to activate it (if the super-admin allows), so only sites that need it run it. The choice shapes both behaviour and, often, licensing — and the common advice “always network-activate” or “never network-activate” is too blunt; it depends on whether every site genuinely needs the plugin and how the licence counts activations.
The licensing reality
Here is the part that surprises people. Even on a single multisite network, each subsite generally counts as a separate licence activation for a commercial plugin — the network is not automatically “one site” for licensing purposes. So a “5-site licence” on a 20-subsite network may only cover 5 of the subsites, not all 20, depending on how the plugin counts. This is not universal (some plugins offer genuine network or unlimited licences), but the default assumption should be “each subsite is an activation” until the plugin’s licensing says otherwise. For an agency, this directly affects cost: a network of many client subsites may need a higher licence tier than the subsite count’s worth of single-site licences would suggest, which is why “unlimited sites” or genuine network licensing is a real selection criterion for agency plugins.
Walk through the cost arithmetic, because it is where the surprise becomes a budget problem. Suppose you run an agency network of 25 client subsites and a plugin sells at $79 for a single site, $199 for five sites, and $399 for “unlimited.” If each subsite is an activation — the default assumption — then covering all 25 with the five-site tier means buying five copies of that tier ($199 × 5 = $995/year), or twenty-five single-site licences ($79 × 25 = $1,975/year). The “unlimited” tier at $399 is not the premium option in that light; it is the cheapest way to cover the network by a wide margin. The mistake agencies make is reading “$79 single site” and budgeting 25 × $79 without first checking whether a genuine network or unlimited tier exists — and whether “unlimited” means unlimited subsites on one network or unlimited single-site installs, which are different promises. Read the licence definition, not just the price ladder.
How Freemius (and similar) handle it
Many commercial plugins license through Freemius, which has explicit multisite handling worth understanding because it is common. On a network, a super-admin can network-activate and apply a licence across sites, delegate licence activation to individual site admins, or hand-pick specific subsites to license — and Freemius provides a network-level Account page for managing this. The flexibility is useful, but it also means the behaviour depends on how the plugin’s developer configured Freemius and what licence the agency holds. FotoGrids licenses through Freemius (its bootstrap is in the Pro source) plus a custom verification layer, and ties the licence to the de-www’d domain plus a per-install UUID — which means, on multisite, each subsite’s domain matters for how activations are counted. The practical point: with Freemius-licensed plugins, check the network Account page to see how your licence is actually being applied across subsites.
Do this now. Before network-activating a commercial gallery plugin on a multisite, answer two questions. Does every subsite genuinely need it (if not, per-site activation is cleaner)? And how does the licence count activations across subsites — one network activation, or one per subsite? Check the plugin’s licensing terms and, if it uses Freemius, its network Account page. Answering these up front avoids the mid-project surprise of a licence covering fewer subsites than your network has.
Per-subsite domain implications
A subtlety specific to domain-tied licensing: when a plugin ties its licence to the domain (as FotoGrids does, to the de-www’d domain plus a per-install UUID), the domain structure of your multisite affects licensing. A subdomain multisite (client1.agency.com, client2.agency.com) and a domain-mapped multisite (each subsite on its own client1.com, client2.com) can count differently, because the licence sees different domains. Domain mapping — common for agency client sites that each have their own real domain — generally means each mapped domain is its own licensed install. This is worth knowing before you architect the network: how you structure subsite domains interacts with how domain-tied licences count, and getting it wrong means re-activating licences after a domain change.
What happens when a domain changes
This is the failure mode worth rehearsing before it bites, because domain changes are routine agency work — a client launches their real domain after a staging build, rebrands, or moves from a subdomain to a mapped domain. When a plugin ties its activation to the domain, that change can look to the licensing system like a brand-new install on a brand-new domain, leaving the old activation stranded and the new one needing a fresh activation. The de-www’d matching FotoGrids uses softens one common version of this — www.client.com and client.com are treated as the same domain, so adding or dropping the www does not re-trigger activation — but a genuine domain change (staging.client.com to client.com, or client.com to client-rebrand.com) is a different domain and is expected to need re-activation.
The practical playbook: before a planned domain change, deactivate the licence on the old domain so the activation slot is freed, make the change, then activate on the new domain. Doing it in that order means you are moving one activation rather than burning a slot and discovering you have hit your activation cap. For a launch where staging becomes production, treat it the same way — the staging domain held an activation, and production is a new one. Building this single step into your launch checklist turns a confusing “the licence stopped working” support ticket into a thirty-second routine.
The agency multisite pattern
The classic agency setup is one multisite network hosting many client sites, often with mapped domains so each client has their own URL. This is efficient operationally — one WordPress install, one set of updates, shared infrastructure — but it concentrates the licensing question: every client subsite that needs the gallery plugin is (typically) an activation, so the agency needs a licence tier sized to the number of client sites, not to “one network.” The agency-tier licences that plugins offer exist precisely for this: genuine network or high-volume licensing that makes the per-subsite-activation reality affordable at agency scale. Pairing this with white-labelling (so each client site feels bespoke) is the full agency-delivery pattern — one network, many branded client sites, licensed at agency scale.
Performance and maintenance on multisite
Two operational notes beyond licensing. Performance: a network-activated gallery plugin runs on every subsite, so its footprint multiplies across the network — another reason to consider per-site activation if only some sites need it, and a reason the plugin’s own performance matters more on multisite (it is paid for many times over). Maintenance: the upside of multisite is one-update-for-all, which is genuinely valuable for an agency — you update the gallery plugin once and every client site gets it. The trade-off is that a bad update affects every client at once, so staging-test updates before applying them network-wide. These operational realities — multiplied footprint, centralised updates — are part of why the plugin you choose for a multisite agency deployment needs to be both performant and well-maintained, not just feature-complete.
Key takeaways
- Each subsite generally counts as a separate licence activation — the network is not automatically “one site.”
- Network-activate only if every site needs it; per-site activation is cleaner otherwise.
- Domain-tied licensing interacts with your subsite domain structure — mapped domains usually count separately.
- Agency scale needs genuine network/high-volume licensing; staging-test network-wide updates.
Does one plugin licence cover a whole multisite network?
Usually not automatically. Each subsite generally counts as a separate licence activation for a commercial plugin, so a 5-site licence on a 20-subsite network may only cover 5 subsites. Some plugins offer genuine network or unlimited licences, but the default assumption should be one-activation-per-subsite until the plugin’s terms say otherwise.
Should I network-activate a gallery plugin?
Only if every subsite genuinely needs it — network activation runs the plugin on all sites and prevents site admins deactivating it. If only some sites need the gallery plugin, per-site activation is cleaner and may reduce licence activations and performance footprint. Decide based on actual need and how the licence counts activations.
How does domain mapping affect plugin licensing on multisite?
For plugins that tie the licence to a domain, your subsite domain structure matters. Domain-mapped subsites (each on its own real domain) generally count as separate licensed installs, where subdomain subsites may count differently. Architect the network with this in mind, because a domain change can require re-activating the licence.