License

What the words mean

• Source is everything BoardUI puts into your project: components, blocks, chart cards, templates, tokens, styles, hooks and utilities, whether installed with the CLI or copied from the documentation.
• Free source is anything installable without a licence key, listed publicly at boardui.com/components.
• Pro source is anything that requires a paid licence key, marked with a PRO badge in the documentation.
• An end product is something you build using the Source: a website, an application, a product, an internal tool. The Source is a part of it, not the point of it.
• A developer is one human being who works with the Source. Seats are counted in people, not machines, so one person may use their licence on as many of their own computers as they like.

What each plan covers

• Free. No purchase, no account. Covers the Free source for unlimited end products, personal and commercial, under the terms on this page.
• Annual Access. One developer. Adds the Pro source, with new components and updates for one year from the date of purchase.
• Lifetime Access. One developer. Adds the Pro source, with new components and updates for as long as BoardUI publishes them.
• Unlimited for Startups. Up to five developers in one organisation. Otherwise identical to Lifetime Access.

Every plan is a one-off payment. Nothing renews automatically and nothing stops working when an updates window ends. See updates below.

What you can do

• Build unlimited end products, for yourself, for your employer, or for clients.
• Use it in commercial work, including products you sell and applications you charge for.
• Modify anything. Rewrite it, restyle it, delete half of it, combine it with your own code.
• Hand an end product over to a client, including the BoardUI code inside it, as part of delivering that work. Your client may use and modify what you delivered. They do not receive a BoardUI licence of their own, so they cannot install more BoardUI source without buying one. See client work.
• Keep the code in your own private repositories, including private monorepos your team can read.
• Use it to build your own internal design system, as long as that system stays inside your organisation.

What you cannot do

• Redistribute the Source, or any recognisable derivative of it, as source code. That includes selling it, giving it away, sublicensing it, or publishing it in a public repository, gist, template, starter kit or course.
• Use the Source to build anything that competes with BoardUI: a component library, UI kit, design system, template marketplace, theme, block collection or Figma kit offered to other people, paid or free.
• Resell a template, or a lightly changed version of one, as a starter kit, boilerplate, theme, admin panel or website template. You may build and sell your own product on top of a template. You may not sell the template.
• Build a tool that lets other people browse, preview, generate, export or customise the Source, whether or not you charge for it.
• Share a licence key, or use one across more developers than the plan covers. Keys are personal to the licence holder.
• Remove or obscure licence notices in the files that carry them.
• Use the Source for anything unlawful, or in a product whose purpose is unlawful.

The line between these two lists is simple. Shipping products built with BoardUI is the point. Shipping BoardUI itself, or a substitute for it, is not.

Seats and teams

Annual Access and Lifetime Access each cover one developer. If a second person on your team needs to install or edit BoardUI source, that person needs a licence. Unlimited for Startups covers up to five developers in one organisation.

People who never touch the Source do not need a seat. Designers reviewing screens, testers, managers and clients using the finished product are all outside the count.

Licences are not transferable between people, except that a seat freed up by someone leaving your organisation may be reassigned to someone joining it. If your team outgrows a plan, write to us and we will invoice the difference rather than ask you to buy again.

Updates, and what happens when they stop

Annual Access includes new components and updates for one year. Lifetime Access and Unlimited for Startups include them indefinitely. Updates are delivered through the CLI, so taking one means running a command, not upgrading a dependency.

When an Annual Access window ends, nothing breaks and nothing is taken back. Every file you installed stays in your repository, licensed under this page forever, in every project you have already shipped and in new ones. What ends is access to anything published after that date.

Because BoardUI copies files rather than versioning a package, we cannot promise that an update will drop into a component you have modified without conflicts. That is the trade for owning the code.

Client work

You may use BoardUI in work you deliver to clients, and you may leave the code in what you deliver. The licence stays yours: it travels with you between projects, not with the project between people.

Your client owns and may modify what you built for them. They do not inherit the right to install BoardUI source into other work, to hand it to another agency for reuse, or to redistribute it. If they want that, they need their own licence, and the same rules apply to them.

Who owns what

You own your end products, including every change you make to the Source. We claim nothing in what you build.

We keep ownership of the Source itself and everything in it that is ours: the designs, the code, the tokens, the name and the mark. A licence is permission to use those things under the terms on this page, not a transfer of them.

Third-party software

BoardUI is built on open-source work that carries its own licences, which continue to apply to those parts and are not affected by this page:

• React Aria Components (Apache 2.0), the accessibility behaviour under the interactive components.
• Recharts (MIT), which renders most of the chart cards.
• Motion (MIT) and Tailwind CSS (MIT).
• Remix Icon (Apache 2.0), the icon set used across the components and documentation.
• Inter (SIL Open Font License 1.1), the typeface.

The BoardUI CLI itself is published on npm under the MIT licence. The source it installs is not: that is covered by this page.

If the licence ends

This licence ends if you break it. In practice that means redistributing the Source or building a competing product with it, not making an honest mistake about seat counts. If we think something is wrong we will write to you first and give you a fair chance to put it right.

When a licence ends you must stop using the Pro source and remove it from projects you have not yet shipped. End products already delivered to real users are not affected, because pulling a licence out from under your customers helps nobody.

Warranty and liability

BoardUI is provided as is. We do not warrant that it is free of defects, that it fits a particular purpose, or that it will keep working with future versions of React, Tailwind or anything else. You are responsible for testing what you ship.

To the fullest extent the law allows, our total liability arising from BoardUI is limited to what you paid for your licence, and we are not liable for indirect or consequential loss, including lost profits, lost data or business interruption. Nothing here limits liability that cannot be limited by law, including liability for intent or gross negligence, or the statutory rights of consumers in the EU.

Governing law

Dutch law applies to this licence. Disputes go to the competent court in the Netherlands, unless mandatory consumer rules give you the right to bring a claim somewhere else.

These terms sit alongside our terms and conditions and our privacy policy. Questions about any of it can go to hi@boardui.com, and if you are unsure whether something is allowed, ask before you build it. The answer is usually yes.