Licence

Last updated 3 September 2026 · Said how many sites a key covers, and named the extended key ·

In plain terms

One licence covers one production site. It includes one year of updates and email support. After that year the plugin keeps working exactly as it is; only new versions and support stop unless you renew. The code is GPL v2 or later: you may read it, change it and keep it. The licence key is what unlocks automatic updates, not what makes the plugin run.

Two different things are called a licence here, and conflating them is how customers end up feeling cheated. So, separately:

1. The code: GPL v2 or later

Our plugins extend WordPress and are therefore derivative works of it. They are licensed under the GNU General Public License, version 2 or later, and that gives you real rights, not decorative ones:

run the code on as many sites as you like;
read it, and change it;
give it to somebody else, changed or not.

We are not going to pretend otherwise. Plenty of plugin shops write terms implying the code is locked to one site. It is not — not ours, not anybody’s, not under the GPL.

2. The licence key: what you are actually paying for

A key entitles you to updates and support for one year, for the number of sites shown on the product page. It is a subscription to our continued attention, and that is the honest description of it.

The key expires; the plugin does not. When a year is up, the software keeps running exactly as it did. What stops is our end of the arrangement.

How many sites a key covers

One key, one production site. A staging or development copy of that same site is included and does not need a second key — it is the same site, and asking somebody to pay twice to test their own installation would be mean.

A second live site needs a second key. Client work is the same rule: each site you build for somebody else is its own installation.

Some products also offer an extended key, priced separately and labelled as such on the product page. It covers unlimited installations, including sites you run for clients and products your own users pay to access. Where a product has only one price, that price is the ordinary key described above.

None of this restricts the code. The GPL rights in section 1 are unaffected by which key you hold — what a key buys is updates and support, and how many installations those cover.

What we ask

Do not resell the key. Sharing the code is your right; selling somebody a key that bills our support desk is not the same act, and it is the one thing that would make this model impossible to keep offering.

Bought on CodeCanyon?

Then Envato’s Regular or Extended Licence governs your purchase, and the code is still GPL — Envato’s terms cover the item as sold, and the GPL covers the PHP inside it. Support comes from us either way; write to [email protected].

See also the terms and the refund policy.