Two licences. One project each.

Every script is sold under a Regular or an Extended licence, and which of the two are offered depends on the script. Either way a licence covers one commercial project: one live domain, plus a development and a staging host.

In force from 1 July 2026 Supersedes all earlier versions

In plain English Not the terms

01 One project per licence: A licence authorises a single commercial project. A second project needs a second licence.
02 Three hosts, one of them live: One production domain, one development host and one staging host, all serving the same project.
03 Extended unlocks SaaS: Multi-tenant and subscription features are licensed under Extended only. A Regular licence does not grant them.

Regular and Extended

Each script is offered under a Regular licence, an Extended licence, or both. The tier you purchase is recorded against your order and the key issued for it, and that tier is what governs your use.

Regular licence: Authorises one commercial project that is not operated as a service for third parties. The SaaS capabilities of the script are not licensed under this tier and must remain disabled.
Extended licence: Authorises one commercial project and additionally licenses the SaaS capabilities of the script — multi-tenancy, tenant provisioning, subscription billing, and any other capability the product documents as a SaaS feature.
Availability varies by script: Not every script is offered under both tiers. The tiers available for a product, and the price of each, are those shown on that product page at the time of purchase.
Upgrading: A Regular licence may be upgraded to Extended for the difference in the prices then published. Ask and we will issue the replacement key against the same project.

Neither tier is a subscription and neither expires. What differs between them is the scope of use granted, not its duration.

One commercial project per licence

A licence is granted for a single commercial project. It is not a general right to use the source wherever you please, and it is not a per-seat or per-developer licence either — the unit is the project.

One project, one licence: Every additional commercial project, whether your own or a client's, requires its own licence of the appropriate tier.
What counts as one project: A single application serving a single business purpose under a single production domain. Rebranding a deployment for a different business, or pointing a second live domain at it, is a second project.
Client work: You may purchase and deploy on a client's behalf. The licence covers that one project, and may be transferred to the client if they are to own it.
Transfer, once: A licence may be transferred in writing to the party that owns the project. On transfer the transferring party's own right to use the source under that licence ends.
Internal use: Developers, contractors and staff working on the licensed project may all hold a copy of the source while engaged on it. No additional licence is needed for a person, only for a project.

Where an order contains more than one unit of the same product, each unit is a separate licence covering a separate project.

One live domain, plus development and staging

Each licence entitles the project to three hosts, of which only one may serve the public.

One production domain: A single live domain, together with its www form, serving real users.
One development host: A local or private host used to build and test. Not publicly available, and not used commercially.
One staging host: A pre-production copy used for review. Access-restricted, and not to be used to serve real users or take real payments.
Register your hosts: Register the domains a licence is deployed on from your account. Registration is how a deployment is identified for support and for update eligibility.
Moving the live domain: The production domain may be changed — a rename, a migration, a client moving house — by retiring the old registration and adding the new. Only one production domain may be live at any time.

A second live domain is a second project and requires a second licence. Staging and development hosts carry no separate charge, but they are not substitutes for one.

What the licence grants

Within the scope set out above, and on payment in full, you receive a perpetual, worldwide, non-exclusive licence to use, modify and deploy the source of the item purchased.

Perpetual: The licence does not expire and is not revoked while its terms are honoured.
Full modification: Fork it, rename it, strip out what you do not need. What you build on top is yours.
Six months of updates: Every release of the same product published within six months of your payment, at no further cost.
Named holder: The licence belongs to the person or company that paid, for the project it was bought for.

Licence keys are issued the moment an order is marked paid and live on your purchases page, showing the tier granted and the domains registered against them.

What it does not allow

The line is a simple one: sell the work you build, not the source you bought, and stay inside the tier you paid for.

No SaaS use under a Regular licence: Operating the script as a hosted service, opening accounts to third parties, or enabling its multi-tenant or subscription capabilities requires an Extended licence. Doing any of it under a Regular licence is use outside the licence granted.
No use beyond the licensed scope: A further commercial project, or a further production domain, requires a further licence. Use beyond what your tier and your registrations cover is unlicensed use.
No redistribution: Do not publish, resell, sublicence or give away the source, in whole or in substantial part.
No competing products: Do not repackage an item as a template, boilerplate, theme or starter kit for other people to buy.
No shared keys: A licence key identifies one holder and one project. Publishing one, or using one issued to somebody else, ends the licence.
No claim of authorship: You own what you build. Copyright in the original source stays with us.

Support and updates

Every purchase includes six months of direct support from the date of payment, answered by the engineers who wrote the code.

In scope: Upgrades, configuration, and defects in the source as shipped.
Out of scope: Installing or deploying the product on your infrastructure, your own modifications, third-party packages, server administration and bespoke feature work. Those are quoted separately.
Attach a licence: Open a ticket from your dashboard and pick the licence it concerns, so the thread arrives with the tier, the version and the order already on it.
After six months: Your licence and your copy of the source are untouched. What closes is the window for support and for new releases, and continuing either is quoted separately — ask and we will price it.

Warranty and liability

The source is provided as it is. We test it hard and we fix what we ship, but what you deploy is yours to stand behind.

To the fullest extent the law allows, our total liability for any claim connected to a product is limited to the amount you paid for that product.

Nothing here limits liability that cannot be limited by law, including for death, personal injury, or fraud.

This licence is governed by the laws of England and Wales.

Ending the licence

The licence lasts until it is broken.

Breach: Redistributing the source, sharing a key, or using the source outside the tier, project or domain scope licensed to you ends the licence immediately, and without a refund.
Putting it right: Where the breach is scope rather than redistribution — an extra project, an extra live domain, SaaS features on a Regular tier — buying the correct licence within fourteen days of us raising it settles the matter.
What survives: Work already delivered to a client under a valid licence stays licensed for that project. Further deployments do not.
Changes to these terms: We may revise this page. The version that governs your purchase is the one published on the day you paid.