License

What you can build with Ingot UI, in plain English.

The short version

  • Allowed: Use it in unlimited personal and commercial projects: your SaaS, paid products and client work.
  • Allowed: Free components are free forever, for commercial work too.
  • Allowed: Pro components need an active Pro or Lifetime plan when you copy them.
  • Allowed: What you copied and shipped stays yours, even if you stop paying.
  • Not allowed: Don't resell or redistribute the library itself as a UI kit, template or theme.
  • Not allowed: One plan is for one person. Don't share your account or API key.

What each plan covers

Find your use case, read across. Prices and seats are on pricing. The Team plan gives each seat the Pro terms.

  • Your own SaaS product

    An app, dashboard or site you build and run.

    Free
    YesWith free components
    Pro or Lifetime
    YesWith every component
    Team plan
    YesFor every seat
  • A paid SaaS with paying users

    No fee per end user, per sale or by revenue.

    Free
    YesWith free components
    Pro or Lifetime
    YesNo user or revenue limit
    Team plan
    YesNo user or revenue limit
  • Client projects as a freelancer or agency

    You build the product, the client owns it.

    Free
    YesUnlimited clients
    Pro or Lifetime
    YesUnlimited clients, by the person on the plan
    Team plan
    YesUnlimited clients, by each seat
  • Open-source project

    Your app's source code is public.

    Free
    YesFree components inside your app
    Pro or Lifetime
    Contact usWrite to us before publishing Pro code
    Team plan
    Contact usWrite to us before publishing Pro code
  • Templates or themes for sale

    Buyers get the source to build their own products.

    Free
    No
    Pro or Lifetime
    No
    Team plan
    No
  • A UI kit or component library for sale

    Selling or giving away the components themselves.

    Free
    No
    Pro or Lifetime
    No
    Team plan
    No
  • Sharing code with teammates

    Teammates work on the product's repo.

    Free
    YesFree components, anyone on the project
    Pro or Lifetime
    YesIn your product's code; anyone who copies Pro items needs a plan
    Team plan
    YesEach seat copies from the library
  • Code your AI agent writes with our MCP

    Output from the MCP server, CLI or registry.

    Free
    YesFree components, 50 MCP calls a day
    Pro or Lifetime
    YesEvery component, unlimited calls
    Team plan
    YesFor every seat

Questions

Can I use Ingot UI in my SaaS?

Yes. Use the components in unlimited personal and commercial products, including paid SaaS with paying users. There is no fee per end user, per sale or by revenue. Free components need only a free account; Pro components need an active Pro or Lifetime plan when you copy them.

Can I use it for client projects?

Yes, for as many clients as you like. You build the product, hand it over, and the client owns it and can change it. The client doesn't get a licence to the library itself: to copy new items they need their own plan. If several people at your agency copy from the library, each needs a plan. For an agency setup, write to support@ingotui.com.

What happens to my code if I stop paying?

Everything you already copied or shipped stays yours to use. You only lose the ability to copy new Pro items. Free components stay free forever.

Can my teammates work on the code?

Yes. Teammates can read, change and deploy the code in your product's repository. A plan is for one person, though: anyone who copies Pro items from the site, CLI or MCP needs their own plan or a Team seat. Don't share your account or API key.

Is code my AI agent writes with the MCP covered?

Yes. Components your agent adds through the MCP server, CLI or registry are covered exactly like components you copy by hand. Pro components come through only on a Pro or Lifetime plan.

Can I sell a template, theme or UI kit made with Ingot UI?

No. You can ship the components inside your own products and your clients' products, but you may not resell or redistribute the library itself as a UI kit, template pack, theme or competing library.

Can I use it in an open-source project?

Free components can go in an open-source app. Publishing Pro component code in a public repository puts it where anyone can copy it, so write to support@ingotui.com first and we'll tell you what works.

Questions? Write to support@ingotui.com. A person replies.

Full licence terms

Version 1.0, effective . This is the binding text; the summary, table and answers above explain it.

  1. 1.Who and what this covers

    1. 1.1“Ingot UI”, “we” and “us” means the publisher of ingotui.com.
    2. 1.2“The library” means the design systems, components, code, tokens, icons, Figma files and screens we publish, however you get them: the website, the CLI, the shadcn registry or the MCP server.
    3. 1.3“You” means the one person who holds an Ingot UI account. On a Team plan, each seat is one person.
    4. 1.4“End product” means a website, app, SaaS, internal tool or other software in which the library is part of a larger work, made by you for yourself, your employer or a client.
  2. 2.What you may do

    1. 2.1You may use, change and include the library in an unlimited number of end products, personal or commercial, for yourself, your employer or your clients.
    2. 2.2End products may be sold, rented or offered as a paid service with any number of users. There is no royalty, per-user fee or revenue limit.
  3. 3.Free components

    1. 3.1Components marked Free can be used by anyone with an account under these terms, for commercial work too. They stay free forever.
  4. 4.Pro components

    1. 4.1Components marked Pro may be copied only while you have an active Pro plan, a Lifetime plan or a Team seat. Lifetime does not expire.
    2. 4.2Everything you copied while your plan was active stays yours to use after it ends, in what you already shipped and in new end products. You lose only the ability to copy new Pro items.
  5. 5.One plan, one person

    1. 5.1Each plan is for one person. Don't share your account, sign-in or API keys.
    2. 5.2Teammates and contractors may work on the code of an end product that contains the library. Anyone who copies items from the library (website, CLI, registry or MCP) needs their own plan or seat.
  6. 6.Client work

    1. 6.1You may build end products for clients and hand them over, including the source code. The client may own, run and change that end product.
    2. 6.2Handing over an end product doesn't give the client a licence to the library itself. To copy new items, the client needs their own plan.
  7. 7.AI agents

    1. 7.1Code that an AI agent produces with the library through the MCP server, CLI or registry counts as copying by you, under the same terms and the same plan limits.
  8. 8.What you may not do

    1. 8.1Resell, sublicense, share or redistribute the library, or a substantial part of it, on its own: as a UI kit, component library, design system, template pack, theme, starter, Figma kit or icon set, paid or free.
    2. 8.2Build a product whose main purpose is to let other people get or copy the components.
    3. 8.3Publish Pro component source code where anyone can copy it, such as a public repository, without our written permission.
    4. 8.4Use the Ingot UI name or logo in a way that suggests we made or endorse your product.
  9. 9.Ownership

    1. 9.1We keep the copyright in the library. You own your end products and everything you add to them. The licence in these terms is what lets you use our part inside them.
  10. 10.No warranty

    1. 10.1The library is provided as it is. We work to keep it correct and accessible, but we don't promise it is free of errors or fit for every purpose. Check it in your product before you ship.
  11. 11.Changes to these terms

    1. 11.1We may publish a new version of these terms on this page. Each version shows its number and the date it takes effect.
    2. 11.2A new version applies to items you copy after its effective date. Items you copied earlier stay under the version that applied when you copied them.
  12. 12.Questions and special cases

    1. 12.1Anything these terms don't cover, or a use you aren't sure about: write to support@ingotui.com before you ship. A written yes from us is part of your licence.

Related: Pricing, Docs, MCP and CLI, Support.