License, in plain language

This is the readable version of the terms you agree to when you buy the Web Kit. The full text ships as LICENSE.md inside the repository you get access to, and it says the same things at more length. If anything here is unclear, email abhimanpanwar6@gmail.com before you build on it. A licensing question is cheap to answer up front and expensive to answer after you have shipped.

What you can do

Use it in unlimited projects. One licence covers every personal and client project you build with the kit, commercial or not, for as long as you hold it. There is no per-project fee and no cap on how many products you ship.

Modify it freely. Change the code, rebrand it, delete what you do not need, rewrite what you do. Once you have bought it, it is yours to edit without restriction inside the terms below.

Ship what you build, however you like. The products, apps and sites you build with the kit are entirely yours. Sell them, licence them, open-source them. This licence covers the kit's own source code, not what you build with it.

Get updates. Your licence includes future updates for as long as the kit is actively maintained, pulled from the same repository you were granted access to. See Getting access.

Who a seat covers

Web Kit Solo covers one developer. If you are a freelancer or a solo founder, this is you. One repository invitation.

Web Kit Team covers up to five developers at one organisation, all working from the same repository grant. Up to five invitations. Everything else about the two tiers is identical: same code, same updates, same terms.

Seats are about people who have the kit's source checked out, not about how many products you ship. One developer building six products needs one seat. Six developers building one product need the team licence.

More than five developers? Write in. Extra seats beyond five need an additional licence, and it is a short conversation.

What you cannot do

Do not resell or redistribute the source. You cannot package the kit itself, as-is, lightly modified, or as a derivative "starter kit", and sell, give away or otherwise distribute it to third parties. Not as a standalone product, not in a bundle, not as a template marketplace listing, not as a free bonus with something else. What you are licensed to distribute is the product you build, not the kit itself.

Do not sublicense it. You cannot grant someone else the right to use the kit under your licence. Each developer or team who wants to work with the kit's source directly needs their own.

Do not share repository access outside your seats. A solo licence means one person has access. A team licence means up to five. Sharing the grant wider is the one thing that makes this business impossible to run.

Support

Licensed users can reach abhimanpanwar6@gmail.com for setup questions, bugs in the kit itself, and licensing questions. That is support for the kit as shipped. It is not a guarantee of custom development or of debugging help for your own product, which would be a different service at a different price.

No warranty

The kit is provided as-is. The code that ships is tested (81 tests, and you can run them yourself), but you are responsible for testing and securing whatever you build with it before it handles real customers or real money. Your product is your responsibility, and that is the correct arrangement.

When your case is not covered here

Agency work across many end-clients, an internal tool at a large company, a contractor who leaves mid-project, anything unusual: ask. Email abhimanpanwar6@gmail.com and describe the situation. We would much rather answer the question than have you guess.