Licences

Licence keys, how many sites you can use, moving installs, and what a tier allows.

A licence to use the product. Not ownership of it.

That is normal for software and it is not a catch: you can use it commercially, modify it, and keep using it. What you cannot do is resell it or give it away. The Licence Agreement is the document that governs, and it is written to be read.

Emailed to you when you buy, to the address on your order. Keep that email.

We store only a cryptographic hash of your key, never the key itself — so we genuinely cannot read it back to you, and neither can anyone who breaks into our database. That is the point of doing it that way.

Your licences shows a masked version so you can tell which is which, and offers a replacement if the original is gone.

Open your licences and request a replacement. It issues a new key and invalidates the old one.

Replacement is limited to once every 30 days per licence, to stop the feature being abused. If your key has actually leaked and you need it sooner, ask support — we can override that limit and we will not make you wait.

  • Single Site — one live installation.
  • Extended — the number of installations stated on the product page.
  • Developer — unlimited installations you own or build for clients.

Your licences shows how many slots you have used out of how many.

No. A staging, testing, local development or backup copy of an installation you have already licensed is not a separate installation, as long as it is not publicly serving real users.

Develop locally without worrying about it.

Deactivate the old installation from your licences, then activate the new one. That frees the slot and moves it across.

If you cannot reach the old installation — a deleted server, a host you have lost access to — tell us and we will release the slot for you. You will not be stuck.

No. Re-activating an installation that is already registered does not consume a second slot. Restoring a backup, reinstalling, or re-entering the key on the same site is free.

A slot is per installation, not per activation attempt. That is deliberate — a one-site licence should not be exhausted by a backup restore.

Every slot is taken. Three options:

  • Deactivate a site you no longer use, from your licences.
  • Buy an additional licence.
  • Upgrade to a tier with more installations — ask us about the difference in price.

Note what did not happen: your existing sites keep running. A new activation being refused never disables a site that is already working.

Yes, within your tier's installation count.

If the client will own and run the site afterwards, the licence should be transferred to them so they hold the updates and support. Email support with the licence and who it is going to — there is no fee for a transfer.

If you are going to keep operating the site for them on a retainer, keep the licence in your own name and count that install against your tier. Clause 11 of the Licence Agreement covers both.

Your own team, yes — employees and contractors working for you, on your permitted installations.

Anyone outside your organisation, no. Sharing or publishing a key is a breach of the Licence Agreement and it is the kind of thing we act on. If two businesses need it, buy two licences.

A fair question to ask about software you install on your own server, so here is the precise answer.

It sends: a value derived from your key (never the key), your domain as a hash, the product version installed, a timestamp and a one-time value to stop replay, and a signature.

It cannot send your site content, your database, your files, your visitors, your customers' data or your credentials. The mechanism has no access to any of that. Clause 5 of the Privacy Policy says the same in more detail.

Ordinarily one of: the payment was refunded or charged back; the key was shared or published; the product was being redistributed; or licence verification was bypassed.

We will have told you which, and why. If you think it is wrong, reply and ask for a review — a person will look at it. Clause 10 of the Acceptable Use Policy describes how we handle this, including that we normally contact you first where the problem can simply be fixed.