--- title: "Single-Site vs Unlimited-Site Plugin Licences" date: 2026-06-27 author: "Imtiaz Rayhan" featured_image: "https://wpblocksuite.com/wp-content/uploads/2026/08/featured-single-site-vs-unlimited-plugin-licence.png" categories: - name: "WordPress Plugins" url: "/blog/category/wordpress-plugins.md" --- # Single-Site vs Unlimited-Site Plugin Licences Choose a single-site plugin licence for isolated ownership and predictable use. Choose unlimited for many eligible sites under one accountable model. Unlimited removes a site counter, not commercial terms. Verify staging, clients, multisite, support, transfers, and services. ## Single-site or unlimited-site plugin licence? Single-site fits one maintained production site with clean client ownership. Unlimited fits portfolios where recurring deployment justifies shared entitlement. Compare concurrent eligible sites and operating responsibilities. Do not decide from expected lifetime installations alone. ## Define single-site licensing A single-site plan normally permits one qualifying production identity. Staging or development treatment depends on product rules. The purchase can still include several products or services. Single-site describes allowance, not feature depth. ## Define unlimited-site licensing An unlimited plan normally removes a stated numerical activation cap within eligible use. Other restrictions can remain. Ownership, clients, redistribution, hosting, support, services, and fair-use conditions still need review. ## Unlimited does not mean unrestricted - Only one purchasing organisation may qualify. - Client use may require an ongoing relationship. - Resale of keys may remain prohibited. - Hosted services can retain quotas. - Support can have user or request limits. - Accounts and keys remain protected credentials. - Terms can define eligible site types. - Transfer and sharing can remain restricted. Read the full offer and terms. The word unlimited describes only the stated dimension. ## Count eligible sites before comparing price - Current production sites. - Approved staging and development sites. - Upcoming launches within the decision period. - Temporary migration overlaps. - Branch previews and demonstrations. - Multisite networks and qualifying subsites. - Archived sites retaining update coverage. - Client sites approaching handoff. Count according to vendor policy, not internal labels. Keep uncertain environments separate until confirmed. ## Use concurrent demand A licence can often move after supported deactivation. Therefore total historical sites may overstate required capacity. Forecast the highest concurrent eligible demand. Add a controlled buffer for launches and migrations. ## Staging rules can change the comparison WooCommerce documents one live site plus one staging or development site for its subscriptions. Other vendors differ. Freemius documents recognised non-production domains that can avoid paid capacity. Sellers can configure their implementation. ## Custom staging hostnames create uncertainty A licensing service may not recognise an unusual domain. It can count as another normal site. Confirm the hostname before purchase. Keep dated vendor evidence for any manual exception. ## Multisite can change the count materially One WordPress installation can contain many subsites. Vendors may count each activated subsite or the network. Freemius notes that its default multisite behaviour uses one activation per subsite. Product implementation can vary. ## Mapped domains can create separate identities Multisite subsites can use distinct domains. Licence services may therefore treat them as independent commercial sites. Give the vendor the actual network design. Do not describe only the server count. ## Single-site licences create clean ownership units Each site can have its own client account, invoice, renewal, and support history. Handoff becomes easier to explain. Account volume and separate renewals increase administrative work. Automate reminders without hiding ownership. ## Unlimited licences create shared ownership One agency or organisation usually controls entitlement across many sites. Client sites depend on that continuing relationship. State the dependency in contracts and inventories. Define what happens when maintenance ends. ## Single-site licensing suits client purchase A client can purchase directly and preserve independent renewal, support, and recovery. The agency can receive collaborator access. This model often survives provider changes cleanly. It also places billing responsibility with the enduring owner. ## Unlimited licensing suits managed service An agency can include plugin access while it actively manages sites. Central updates and support may become efficient. The service agreement must explain included entitlement, limits, termination, and replacement cost. ## Do not promise an unlimited licence to each client The agency’s commercial right is not automatically transferable. Clients may not retain access after service ends. Follow vendor sharing and transfer rules. Do not distribute raw keys as client property. ## Single-site licensing isolates billing failure One missed renewal normally affects one entitlement. Other clients can remain commercially independent. Many individual renewals create more chances for missed administration. Assign owners and central visibility. ## Unlimited licensing concentrates billing failure One expired plan can affect update or support access across a portfolio. Monitor renewal and payment state carefully. Keep invoices, account recovery, and renewal decisions under organisation control. Assign a backup owner. ## Single-site licensing isolates account exposure A compromised account or key can affect a smaller entitlement scope. Client boundaries remain visible. More accounts create more credentials and recovery paths. Standardise access security and offboarding. ## Unlimited licensing concentrates account exposure A central key or account can control many assignments. Treat it as a high-value entitlement credential. Limit raw key visibility and use named collaborators where available. Reconcile site assignments regularly. ## Support scope can differ from activation scope Unlimited sites do not necessarily include unlimited support users or implementation help. Read the support policy. Estimate portfolio support demand. Keep internal diagnosis and documentation rather than forwarding every issue. ## Hosted services can retain separate quotas A plugin may include scans, storage, templates, AI, email, or cloud processing. Site allowance may not cover usage. We cover the method in [five-site vs unlimited licensing](https://wpblocksuite.com/blog/five-site-vs-unlimited-plugin-licence/). Model each quota, overage, and ownership separately. Unlimited activations cannot create unlimited infrastructure. ## Update access can depend on account connection Commercial packages may require valid activation for automatic updates. Verify every site’s connection after migrations. Unlimited entitlement does not guarantee accurate assignment. Stale and duplicate site identities still need cleanup. ## Use a total-cost comparison - Purchase and renewal charges. - Account and billing administration. - Site assignment and capacity management. - Client onboarding and handoff. - Update and support operations. - Unused capacity and portfolio churn. - Plan upgrades and downgrade constraints. - Replacement and migration cost. Do not assign imaginary savings to unlimited capacity. Value only eligible sites likely to use the plugin. ## Calculate the price break-even Divide the unlimited plan’s comparable cost by one single-site plan’s comparable cost. Interpret the result cautiously. Adjust for discounts, renewal differences, taxes, included support, and plan features. Use current verified prices. ## Calculate the operational break-even Estimate account setup, renewals, invoice allocation, transfers, and capacity administration for both models. Unlimited can cost more yet reduce repeat work. Single-site can cost more yet simplify client exits. ## Use conservative site forecasts - Current eligible sites. - Approved launches with funded work. - Likely closures and client exits. - Expected temporary overlaps. - Staging sites that actually count. - Multisite subsites that actually count. - Sites requiring independent ownership. - Sites where the plugin is genuinely needed. A sales pipeline is not an installed portfolio. Weight uncertain future sites rather than counting all prospects. ## Separate use from optional shelfware Unlimited availability can encourage unnecessary installation. Each plugin still adds code, updates, data, and governance. Install only for a current capability. Do not deploy merely to increase perceived plan utilisation. ## Consider growth volatility Rapid launches and temporary campaign sites can make capacity management expensive. Unlimited reduces numerical friction. High client churn can make shared entitlement and offboarding harder. Model both additions and exits. ## Consider plan availability changes Vendors can revise tiers, pricing, or new-purchase availability. Existing plans may receive separate treatment. Record the current offer and applicable terms. Do not assume an unlimited tier can be repurchased later. ## Consider upgrades and downgrades Ask how upgrades are priced and when new capacity begins. Ask what happens after a downgrade. Reconcile assigned sites before reducing allowance. Preserve coverage for maintained production environments. ## Consider refunds and trials A trial can test capability, update delivery, and account controls. It may not represent portfolio support load. Read refund eligibility, exclusions, and deadlines. Do not deploy widely before the evaluation is complete. ## Consider transfer and sharing A single-site subscription may transfer cleanly to one client. An unlimited plan may be indivisible. WooCommerce documents that legacy multi-site subscriptions cannot be split. Product and vendor rules differ. ## Consider compliance evidence Record purchasing owner, eligible use, active sites, and vendor terms. Unlimited plans still require controlled assignment. Do not infer permitted resale or hosting from activation behaviour. Ask the vendor when terms remain unclear. ## Single-site licensing often fits these cases - One independently owned business site. - A client requiring direct commercial ownership. - A plugin used on one specialised project. - A portfolio with uncertain long-term adoption. - A handoff expected soon after launch. - Strong cost allocation by client. - High concern about shared account exposure. - No suitable unlimited plan under current terms. ## Unlimited licensing often fits these cases - Many maintained sites need the same capability. - One organisation controls all eligible sites. - An agency includes access within active service. - Launch volume makes slot management expensive. - Client ownership and exit rules are explicit. - Central update and support operations exist. - Commercial terms permit intended portfolio use. - The plan remains valuable under conservative demand. ## Use a mixed licensing model An agency can use unlimited entitlement for retained clients. Departing clients can purchase independent single-site coverage. Some clients may own licences from the start. Record the model for every site and product. ## Review actual utilisation - Eligible sites currently assigned. - Sites actively using the capability. - Unknown or stale assignments. - Upcoming approved launches. - Client exits requiring replacement. - Support demand across sites. - Administrative time by model. - Current price and renewal state. Review before renewal and portfolio changes. A previously correct model can stop fitting. ## Create an unlimited-site assignment workflow Require the site, client, environment, owner, purpose, and approval before activation. Record the resulting portal identity. Unlimited capacity should not remove deployment governance. Unknown assignments still create support and compliance work. ## Create a single-site purchase workflow Choose the enduring owner before checkout. Use an organisation-controlled account and record renewal responsibility. Connect the exact site and verify update access. Keep order evidence beside the entitlement record. ## Create a site closure workflow Confirm the site no longer needs updates, support, services, or rollback. Deactivate through supported controls. Verify remote capacity and stop unnecessary billing. Retain required commercial evidence without storing secrets. ## Normalise annual and lifetime comparisons A single-site annual plan and unlimited lifetime plan use different time horizons. Compare an explicit evaluation period. The detail lives in [annual vs lifetime pricing for agencies](https://wpblocksuite.com/blog/annual-vs-lifetime-plugin-pricing-agencies/). Include renewal changes, expected site duration, and vendor survival uncertainty. Avoid infinite savings claims. ## Normalise feature differences Higher site tiers can include extra products, templates, or support. Value only features the portfolio needs. Do not attribute their entire price to site capacity. Compare like-for-like capability before calculating [break-even](https://wpblocksuite.com/blog/wordpress-lifetime-deal-break-even/). ## Plan for domain changes A new domain or protocol can create another recorded identity. Single-site users can encounter limits during migration. Unlimited users can still accumulate stale records. Reconcile old and new identities after launch. ## Plan for account recovery incidents Losing an unlimited account can affect many maintained sites. Test recovery and preserve approved purchase evidence. Single-site clients need the same controls at smaller scope. Avoid personal mailboxes and undocumented recovery. ## Ask about fair-use enforcement An unlimited activation offer can still apply fair-use rules to support or services. Request written clarification for unusual scale. Describe portfolio size and operating model accurately. Do not design a business around assumed silence. ## Know the honest weak case Several single-site licences can cost more while simplifying client ownership. Clean exits and isolated billing have real value. Unlimited capacity can cost less while increasing central dependency. Compare the whole operating model. ## Use the site-licence comparison checklist 1. Define eligible use under current terms. 2. Count current concurrent production sites. 3. Confirm staging and development treatment. 4. Confirm multisite and mapped-domain counting. 5. Forecast funded launches and likely closures. 6. Add a controlled migration buffer. 7. Separate client-owned and agency-owned sites. 8. Review transfer, sharing, and exit rules. 9. Compare features and support scope. 10. Compare hosted service quotas. 11. Calculate price break-even. 12. Calculate administrative and handoff work. 13. Assess account and renewal concentration. 14. Confirm update delivery and recovery. 15. Check upgrade and downgrade rules. 16. Record compliance and assignment evidence. 17. Choose a mixed model where useful. 18. Review utilisation before renewal. ## Frequently asked questions What does a single-site plugin licence cover? Usually one qualifying production site, with vendor-specific rules for testing environments. Does unlimited-site licensing allow any use? No. Ownership, clients, resale, support, services, transfer, and eligibility rules can remain. Do staging sites count toward plugin licences? Sometimes. Treatment depends on product policy and environment recognition. Are unlimited licences better for agencies? They can be when many maintained sites share one permitted, accountable operating model. Can an unlimited licence be transferred to each client? Usually not as separate ownership units. Follow the vendor’s exact transfer and sharing rules. ## The verdict Verdict **Use single-site for clean isolation:** it supports direct ownership and simple client handoff. **Use unlimited for proven portfolio demand:** verify eligible use and central control. Confirm support capacity, compliance, and exit. The right allowance follows concurrent need and ownership, not aspiration. [Review WP Block Suite’s $299 lifetime licence](https://wpblocksuite.com/#pricing).