One license. Everyone at your company.

OnSystem is run by one person. These are the actual terms, written the way I would explain them to you in a message rather than the way a legal template would. Nothing here is hiding a clause somewhere else.

The short version

The one real limit: if you build software for clients, this does not cover what you hand to them. See agency and client work below, because that is the part people ask about.

Two different things called "license"

Worth separating, because the same word does two jobs here.

• Your license key is the credential that unlocks the registry. It arrives at checkout and it is what npx shadcn add authenticates with.
• Your license is this page: what you are permitted to do with the components once you have them.

The key is per purchase. The permission is per company.

Who is covered

When you buy a kit, the license is held by the company that paid for it. If you expensed it, that is your employer. If you are a freelancer or a company of one, that is you.

Everyone working for that company may use it:

• Employees, full-time or part-time, however many. There is no seat count and no headcount tier.
• Contractors and freelancers working on your company's products, for as long as they are working on them.
• Subsidiaries and companies you wholly own.

Nobody has to register, activate a seat, or be named anywhere. Add a developer on Monday and they can install the kit on Monday.

What you can build with it

• Your company's own products, commercial or internal, as many as you want, with no revenue cap.
• Internal tools, dashboards and back offices that only your staff will ever see.
• Client-facing products your company owns and operates, including ones you charge money for.
• Modified components. The code lands in your repo. Change it, rename it, fork it, delete half of it. It is yours to edit.
• Prototypes, demos, pitches and throwaway work.

Agency and client work

This is the honest boundary and I would rather state it plainly than bury it. A company license is generous precisely because it stops at the edge of your company. Without this line, one $499 purchase would cover an unlimited number of separate businesses, and the pricing would not survive that.

Two cases that come up:

• You run the product for the client under an ongoing arrangement, on your infrastructure, as your service. That is your product. Your license covers it.
• You build it, hand over the repo, and they run it. That is their product. They need a license.

If your situation sits between those, email me and I will give you a straight answer rather than make you guess. I would rather sort it out in a two-line exchange than have you avoid buying because the terms were ambiguous.

What you cannot do

• Resell, redistribute or republish the components as components. Shipping an app built with them is the point; shipping the kit itself, or a repackaged version of it, is not.
• Publish the source to a public repository or anywhere the components can be extracted by people without a license. Private repos are completely fine.
• Share your license key outside your company, or use it to give registry access to people who are not covered above.
• Build a competing component library, kit or template out of them.
• Use them as training data for a machine learning model, or include them in a dataset assembled for that purpose. Using AI tools to write your own application code alongside these components is expected and fine. The AI context pack exists specifically to make that work.

How long it lasts

Permanently, for every version you have received. The components in your repo are yours to keep and use forever. There is no renewal, no expiry, and nothing stops working if you never buy anything again.

What is not permanent is registry access, which is a live service. It stays on for as long as your purchase stands. It ends if a purchase is refunded or charged back, which is the one case where a key stops resolving. Nothing already installed is affected.

Updates and new components appear in the registry while your access is live. All Access additionally covers kits released through 2027.

If you bought before today

These terms apply to you too, automatically, with nothing to do. They are strictly more permissive than what was written before, which was almost nothing. Every existing purchase is now a company license, retroactively. You do not need to re-buy, upgrade, or ask.

Which kits this covers

All of them, on the same terms: Internal Tools, Fintech, E-commerce, and All Access. The kit you bought determines which components your key unlocks. It does not change any of the permissions on this page.

Refunds and payment

Payment is handled by Lemon Squeezy as the merchant of record, under their terms and refund policy. If something is wrong, email me first. I would rather fix the problem than process a refund, but I will process the refund if that is what you want.

Warranty and liability

The components are provided as they are, without warranty of any kind, express or implied, including warranties of merchantability, fitness for a particular purpose, and non-infringement. You are responsible for testing what you ship.

To the maximum extent permitted by law, my total liability arising out of or relating to these components is limited to the amount you paid for them. I am not liable for indirect, incidental, special or consequential damages, or for lost profits or lost data.

Said less formally: these are UI components and I have taken real care with them, but I cannot carry the risk of your production system. Review what you ship, as you would with any dependency.

Changes to these terms

If I revise this page, the version in force for your purchase is the one published on the day you bought. I will not retroactively narrow rights you already have. If a change makes the license more permissive, as this one did, you get it automatically.

Questions

Anything that is not answered here, or any situation the wording does not obviously cover: [email protected]. It reaches me directly, and I will answer.

Last updated 1 September 2026. Governed by the laws of Portugal. If you need this as a signed document or a PDF for procurement, email me and I will send one.