License limited

You are most likely here from a LICENSE file in one of our public repositories. That file is a real MIT license and it means what it says — but it covers only the code in that repository. This page draws the line, so nobody has to guess where it falls.

Last updated: Aug 13, 2026

The short version

The repository is free and open. The product it extends is not.

What we publish openly are the pieces meant to be taken apart and rebuilt: child themes, add-ons, examples, starting points. None of them is a product on its own. They extend software we sell, and they need that software installed to do anything at all.

Having the repository does not give you the product, and nothing in it changes the terms that came with a purchase.

What the MIT license gives you

For the files in that repository, and only those:

  • Use it for anything, personal or commercial.
  • Change it however you like. Fork it, rewrite it, strip it down.
  • Redistribute it, on its own or inside something larger.
  • Sell what you build with it. We take no cut and ask for no permission.
  • No attribution beyond keeping the copyright notice in the copies you distribute.

That is the whole MIT license. We chose it deliberately: this is code meant to be modified. Putting conditions on how you adapt your own site would be a strange thing for us to do.

What it does not give you

  • A copy of the product it extends, or any right to one.
  • Permission to redistribute that product, bundled with this code or otherwise.
  • Any change to your purchase terms. The MIT notice sits beside them; it does not override, weaken or extend them.

The two licenses cover different software. Neither one says anything about the other.

Questions this usually raises

It is on GitHub, so the product is free now?
No. What is on GitHub is the open piece we wrote and released. The product it extends is separate, has its own terms, and is not published there.

Can I sell what I build on top of this?
Yes. What you build is yours to sell. Bear in mind what you are selling: your customer still needs their own license for the underlying product for it to run, and that should be clear to them before they buy — not after.

Can I ship the product with it so my customer does not need a license?
No. That is redistributing commercial software, and the MIT notice on our open code does not authorize it.

What happens if I install this without a license for the product?
Not much. The code loads and does nothing, because the software it extends is not there. And any feature that talks to our servers only answers to a valid license — so a copy obtained elsewhere cannot pull data from us regardless of what else it appears to do.

I already own the product. Do I need anything else to use this?
No. Download it, install it, and go.

Where the actual terms live

This page explains a boundary; it is not the agreement itself.

  • The terms for your purchase: Terms of Service
  • The MIT text that applies to the repository: the LICENSE file inside it

If something here reads as contradicting either document, the documents win — and we would like to know about it. Open a ticket and we will fix the wording.