Understanding Site Limits and License Usage Guidelines

As of February 1st, 2025, we introduced a new pricing structure to make our tools more accessible and to provide flexible options for users at every level. These updates include the launch of a new entry-level plan and a shift to a per-site licensing model.

All Kadence Products are sold as Yearly Subscriptions. As long as your subscription remains active, you will have access to plugin downloads, new feature releases, security updates, bug fixes, and premium support.

Think of your Kadence subscription like a magazine subscription: it automatically renews each year using the payment information on file. 

• We’ll send you reminders before your license renews so you’ll know when to expect it. 
• If you disable auto-renewal, your subscription will expire one year from the date of your last purchase or renewal. 
• Expired license holders can renew at any time to regain access to updates and support.

An active subscription ensures automatic updates for installed plugins and premium help desk support, which is available only to the purchaser. (Please note that only one help desk account is provided per purchasing account.)

Site Limits Per Plan

All Plans include Limits on the number of sites.

What Counts Towards Site Limits?

Only active sites count towards your allowed sites limit. Our system will automatically ignore any staging or local development site and not count them against your allowed installations by your license key.

Please note the list of whitelisted domains below:
TLDs (domain endings)

• *.local
• *.localhost
• *.staging
• *.stage
• *.test
• *.tribe
• 127.0.0.1
• *.dev.cc

Subdomains (domain prefixes)

• dev.*, *.dev.*
• wpdev.*
• webdev.*
• test.*
• staging.*
• *.staging.*
• stage.*
• *.stage.*
• devsite.*
• sandbox.*
• composer.*

Staging domains of hosting providers

• *.nxcli.net, *.nxcli.io (for Nexcess)
• *.wpengine.com
• *.staging.wpengine.com
• *.wpenginepowered.com
• *.myftpupload.com
• *.mybluehost.com
• *.dreamhosters.com
• *.lightningbasehosted.com
• *.kinsta.cloud
• *.flywheelstaging.com
• staging.*.flywheelsites.com
• *.pantheonsite.io, *.panth.io
• staging*, www.staging*, *sg-host.com (SiteGround)
• *.wpstagecoach.com
• *.wpsc.site (WP Stagecoach)
• *.cloudwaysapps.com (Cloudways)
• *.cloudwayssites.com (Cloudways)
• *.myraidbox.de (RAIDBOXES.io)
• *.lndo.site (Lando dev environment)
• *.wpstage.net (BlogVault)
• *.mystagingwebsite.com (Pressable)
• *.ddev.site (DDEV.com)
• *.pressdns.com (pagely.com)
• *.onyx-sites.io (Krystal)
• *.go-vip.net (WordPress.com VIP sites)
• *.wp1.host (xCloud)
• *.plesk.page (Plesk)
• *.rapydapps.cloud (Rapyd Cloud)
• *.cloudaccess.host (CloudAccess.net)
• *.hostingersite.com (Hostinger)

Examples

If you tried using the same personal license key on both example.com and example.test, this would work fine! Both sites would receive updates, and you would not get an “out of installs” notice.

However, if you tried to use the same personal License Key on both example.com and devexample.com, this would not work—only one site would be able to use the License Key.

Last but not least, if you tried to use the same personal license key on example.com, example.test, example.staging, example.local, and localhost:8888/example, this would work fine! All sites would get updates, and you would not get any “out of installs” notices.

My dev site’s URL doesn’t match any of the patterns listed above. Will this work?

Unfortunately, no. At this time, we only support the specific patterns listed above. Everything else is considered a “live” site and will count against your install limit.