--- title: "Five-Site vs Unlimited WordPress Plugin Licensing" date: 2026-06-28 author: "Imtiaz Rayhan" featured_image: "https://wpblocksuite.com/wp-content/uploads/2026/08/featured-five-site-vs-unlimited-plugin-licence.png" categories: - name: "WordPress Plugins" url: "/blog/category/wordpress-plugins.md" --- # Five-Site vs Unlimited WordPress Plugin Licensing Choose five-site licensing for stable demand below five eligible sites. Choose unlimited when recurring demand makes the sixth site operationally expensive. Count concurrent eligible sites, not every past project. Include staging rules, churn, migrations, handoffs, and a justified buffer. ## Five-site or unlimited plugin licensing? A five-site plan fits a small, predictable portfolio with spare capacity. Unlimited fits sustained growth and frequent reassignment. The price difference matters only after normalising features and terms. Capacity administration and ownership also have costs. ## Start with the exact allowance Five-site generally means five qualifying concurrent activations. Vendor policy decides which domains, environments, and multisite units qualify. Unlimited generally removes that numerical cap under eligible use. It does not remove client, support, or resale rules. ## The sixth site creates the real decision Sites one through five fit the stated tier. The sixth eligible concurrent site needs reassignment, another licence, or upgrade. Forecast when that sixth site will appear and how long it remains. A temporary overlap differs from permanent growth. ## Count current production demand - Live sites using the paid capability. - Sites under active maintenance. - Sites awaiting an approved handoff. - Archived sites retaining supported operation. - Sites using related bundle components. Remove sites where the plugin is installed without need. Never install [shelfware](https://wpblocksuite.com/blog/plugin-bundle-shelfware/) to justify a larger plan. ## Count staging only under vendor rules Some vendors exempt recognised staging or development sites. Others pair one testing site with production. WooCommerce documents a production plus staging allowance for its subscriptions. Freemius documents recognised non-production patterns. ## Count custom staging conservatively An unusual hostname may consume ordinary capacity until the vendor recognises it. Keep written evidence for exceptions. Do not plan all five slots from ideal assumptions. Confirm portal behaviour on the intended host. ## Count multisite correctly One network can contain many subsites. Licensing systems may count activated subsites individually. Freemius documents default per-subsite activation in multisite. The seller’s implementation can change the result. ## Count temporary migration overlap Old and new production identities can coexist during domain or hosting moves. Both may require valid coverage temporarily. Estimate migration duration and rollback needs. Do not deactivate the old site before approval. ## Count launch pipeline separately - Funded sites under active build. - Approved launches with target dates. - Uncertain proposals and sales opportunities. - Replacement builds retiring existing slots. - Temporary campaign sites. Do not count every proposal as future demand. Weight uncertain work and include likely closures. ## Forecast concurrent eligible sites Create a monthly or quarterly timeline. Add launches, remove verified closures, and mark temporary overlaps. The peak determines capacity pressure. The average helps measure utilisation and wasted allowance. ## Use three demand cases - Base case uses funded, likely work. - Low case includes closures and delays. - High case includes plausible launches and overlap. Do not make the high case fantastical. Use evidence from historical portfolio movement. ## Add a deliberate capacity buffer Running at five of five leaves no space for emergency migration or unexpected counted staging. A buffer has value. Choose the buffer by launch frequency and response tolerance. Do not reserve slots without a plausible need. ## Measure utilisation clearly Five-site utilisation equals active eligible assignments divided by five. Track both used capacity and unresolved unknown records. Unlimited plans lack a capacity percentage. Track active site count and meaningful feature use instead. ## Identify capacity churn Client launches consume slots. Closures, handoffs, and plugin replacements release them after supported deactivation. High churn creates assignment work even below five. Unlimited reduces the cap but not the records. ## Account for stale activations Deleted and migrated sites can remain in vendor portals. They can make a five-site plan appear full. Map every entry before removal. Unknown domains can still serve a client or rollback environment. ## Calculate the comparable price gap Subtract the five-site plan’s comparable cost from the unlimited plan’s comparable cost. Use current verified prices. Normalise billing period, taxes, currency, features, support, and service quotas. Avoid comparing unlike plans. ## Calculate the sixth-site alternatives - Upgrade to unlimited. - Buy another single-site entitlement. - Buy another five-site entitlement. - Transfer ownership to the client. - Retire an obsolete assignment. - Choose a different approved plugin. Compare legitimate options without disrupting maintained sites. Do not borrow a production slot for convenience. ## Calculate capacity administration Estimate time spent approving, activating, reconciling, moving, and releasing five slots. Include incident and migration pressure. Unlimited removes some decisions but still needs site assignment evidence. Do not value administration at zero. ## Calculate ownership and handoff work A shared five-site or unlimited plan can be difficult to split among clients. Vendor transfer rules may limit separation. WooCommerce says legacy multi-site subscriptions cannot be split. Other vendors define their own package rules. ## Calculate renewal concentration One unlimited renewal can cover the portfolio. One payment failure can also affect portfolio-wide update access. A five-site plan has smaller exposure but may combine unrelated clients. Assign commercial and backup owners. ## Calculate support demand More sites create more configurations and edge cases. Unlimited activations do not necessarily include unlimited support effort. We settle it in [whether staging sites count toward activations](https://wpblocksuite.com/blog/do-staging-sites-count-plugin-activations/). Read support terms and authorised-user rules. Build internal triage before expanding deployment. ## Calculate hosted service quotas Cloud storage, scans, templates, AI, email, or API calls can retain limits. Site count is one dimension. Model usage and overages separately. Confirm whether five-site and unlimited tiers include different service allocations. ## Model sites one through three A five-site tier provides visible spare capacity at this stage. Compare its price with smaller available tiers. Unlimited usually needs another strong benefit here. Future growth alone may remain too uncertain. ## Model sites four and five The plan approaches full utilisation. Review funded launches, migration overlaps, and the speed of supported upgrades. Set an approval trigger before allocating the final slot. Keep emergency capacity needs visible. ## Model the exact sixth site Name the project, owner, launch date, environment, and expected duration. Confirm that it actually requires paid features. A concrete sixth site supports a purchase decision. A vague ambition does not. ## Model sites seven and beyond Recurring additions strengthen the unlimited case. They also increase update, support, and client-handoff work. Confirm the operating team can maintain the projected portfolio. Capacity cannot replace service delivery. ## Compare two five-site plans A second five-site purchase may cost less than unlimited. It can also create another account or renewal record. Check whether purchases can share one organisation account. Record which sites belong to each entitlement. ## Compare client-owned single-site coverage The sixth client can buy independently. That approach preserves ownership and avoids expanding agency entitlement. Include setup, collaborator access, renewal coordination, and support routing. Independence still requires operating work. ## Compare delayed deployment Delaying a needed production capability can cost more than an upgrade. Estimate business impact rather than hiding it. Do not delay a security or compliance requirement for licence optimisation. Purchase suitable coverage promptly. ## Use a fixed comparison period Choose a planning window matching contract visibility and portfolio history. Apply it to every pricing option. Short windows can undervalue durable growth. Very long windows can exaggerate uncertain demand and vendor continuity. ## Normalise annual and one-time plans Convert charges into the same planning period. Include expected renewals without assuming prices remain unchanged. One-time payment removes scheduled fees, not product or vendor risk. Keep continuity assumptions separate. ## Assign probability to pipeline demand Funded work can receive high confidence. Early proposals deserve lower weighting until approval. Keep the unweighted high case visible for capacity planning. Do not charge all uncertainty into the base case. ## Model offboarding lag A departing client may need transition time before replacing agency entitlement. Slots remain occupied during that period. Use the contractual exit window and observed history. Do not assume immediate capacity release. ## Model failed or paused projects A paused build can retain staging capacity and commercial dependency. Assign a review date and closure owner. Remove entitlement only after preserving required work and confirming future restart needs. ## Create a capacity reservation queue Record approved upcoming assignments, priority, expected date, and duration. Do not reserve slots for unapproved ideas. Review the queue before every activation. Escalate conflicting commitments before they become site-limit incidents. ## Define who approves the upgrade Name the commercial owner, technical reviewer, and finance approver. Give them current forecast and vendor evidence. Document the decision and effective allowance. Update the inventory after purchase. ## Choose five-site for a stable small portfolio - Three or four current eligible sites. - Slow and predictable launch volume. - Few temporary migration overlaps. - Low portfolio churn. - Clear ownership under one account. - Unlimited price gap remains large. - Upgrade path is documented. - Spare capacity remains available. Five-site capacity is valuable when the portfolio genuinely uses it. The unused slots provide modest flexibility. ## Choose unlimited for sustained growth - Six or more concurrent eligible sites. - Funded launches continue regularly. - Migration overlaps occur often. - One organisation controls deployments. - Terms permit intended client use. - Central maintenance can support the portfolio. - Handoff consequences are explicit. - Price remains justified under the base case. Unlimited should support real operation, not a speculative future agency. Use conservative demand. ## Stay on five-site when the sixth site is temporary A short migration overlap may be handled through vendor staging or migration rules. Ask before upgrading. Never falsify environment purpose. Purchase temporary or additional capacity when required. ## Upgrade before capacity becomes an incident Review the pipeline when four slots are committed. Confirm upgrade pricing, timing, and effective allowance. Do not wait for a production activation failure. Procurement and account access can delay the response. ## Do not upgrade solely to avoid cleanup Stale records and unused plugins still require resolution. Unlimited capacity can hide poor entitlement hygiene. Clean the inventory first. Then calculate demand using legitimate active assignments. ## Plan client exits before choosing unlimited Departing clients may need their own entitlement. The unlimited agency plan may remain indivisible. State replacement or transfer terms in the service agreement. Do not surprise clients at offboarding. ## Plan account recovery before choosing unlimited A central account can control many sites. Use organisation access, strong authentication, and a tested backup owner. Preserve order and assignment evidence outside one person’s inbox. Restrict raw key exposure. ## Plan renewals before choosing unlimited Record the renewal date, approval owner, payment owner, and portfolio impact. Review value before billing. Do not assume future pricing remains fixed. Run a sensitivity case using plausible increases. ## Review actual use after purchase - Current active eligible sites. - Sites using required paid features. - Unknown and stale portal records. - Launches and closures since purchase. - Assignment administration time. - Support use and open cases. - Client exits needing independent coverage. - Current five-site and unlimited pricing. A growing portfolio can justify upgrade later. A shrinking portfolio can justify downgrade when supported. ## Use a capacity decision record - Decision date and accountable owner. - Current plan and price. - Current eligible assignments. - Base, low, and high forecasts. - Staging and multisite assumptions. - Required capacity buffer. - Sixth-site alternative costs. - Handoff and support consequences. - Chosen plan and review trigger. This record makes future renewal rational. Keep current vendor evidence beside every assumption. ## Know the honest weak case Unlimited licensing can waste money when a portfolio remains small and stable. Spare capacity has limited value without likely use. Five-site can remain efficient with good forecasting and an upgrade path. Avoid buying growth before it exists. ## Use the five-site comparison checklist 1. Confirm exactly what each plan counts. 2. Count current concurrent production sites. 3. Confirm staging and development rules. 4. Confirm multisite and mapped-domain rules. 5. Remove verified stale assignments. 6. Map funded launches and likely closures. 7. Forecast monthly or quarterly peak demand. 8. Build low, base, and high cases. 9. Set a justified capacity buffer. 10. Normalise prices, terms, and features. 11. Calculate sixth-site alternatives. 12. Estimate capacity administration. 13. Estimate support demand and service quotas. 14. Review client ownership and exit. 15. Review account and renewal concentration. 16. Confirm upgrade and downgrade processes. 17. Choose from the conservative base case. 18. Set the next review trigger. ## Frequently asked questions When should an agency upgrade from five sites? Upgrade when sustained sixth-site demand and administration justify the comparable price difference. Should a five-site plan run at full capacity? Only with low volatility. A buffer helps launches, migrations, and unexpected counted environments. Do staging sites use one of five licence slots? Sometimes. Check product policy and whether the licensing system recognises the environment. Does unlimited licensing remove site tracking? No. Assignments still affect compliance, support, ownership, security, and client handoff. Can a five-site licence be split among clients? Vendor rules decide. Some multi-site packages cannot transfer individual seats separately. ## The verdict Verdict **Choose five-site for stable demand:** keep spare capacity and a documented upgrade path. **Choose unlimited for recurring sixth-site pressure:** prove eligible growth and support capacity. Confirm client terms and comparable value. The sixth concurrent site should trigger arithmetic, not panic. [Review WP Block Suite’s $299 lifetime licence](https://wpblocksuite.com/#pricing).