License Agreement

Learn what you can and can't do with the Pro Blocks and Skills you get after purchasing Initium PRO.

Summary

Three rules cover almost everything below:

Build anything. Use the Pro Blocks and Skills to create unlimited websites, apps, and products for yourself or your clients, and sell them however you like.
Never expose the source publicly. The component source code must never appear in a public repository, public package registry, or anywhere third parties can extract or reuse it. This applies even inside a finished open-source application.
Never turn the components into a product. Don't repackage the Pro Blocks or Skills as a UI kit, library, registry, template, starter kit, builder, or AI generator, whether free or paid, whether modified or not.

The rest of this page explains these rules in detail, with examples.

This section outlines the licensing options available and helps you determine which one fits your situation. Whether you're a solo developer, a freelancer, or part of a small product team, Initium's licensing matches how many people at your company will actually install and use the Pro Blocks and Skills.

When to buy a Personal License?

You are the only person who will install or use the Pro Blocks and Skills, even if you build for multiple clients or projects.
You can use a Personal license inside a company or agency, as long as you remain the only person with access to the license key and the Pro Blocks/Skills files.

When to buy a Team License?

More than one person at your company will install or use the Pro Blocks or Skills.
You need up to 5 team members to have access to the license key, the Pro Blocks code, and the Skills files.

If you need more than 5 people to have access, contact us (see "Extending your license" below) and we'll put together a custom plan.

Licensing Agreement for Pro Blocks (Code)

By purchasing Initium Pro ("Item") from this website, you are granted an ongoing, non-exclusive, worldwide license to use the Pro Blocks, React and Tailwind CSS components built for shadcn/ui, under the conditions below. You may use them to create unlimited End Products for yourself or for your clients, and the End Product may be sold, licensed, sub-licensed, or freely distributed.

An End Product is: a customized implementation of the Item, such as your unique finished website, web app, or software product, that does not allow third parties to extract or reuse the components' source code. A deployed website or compiled application qualifies, because visitors only see the rendered output. A public repository, a published package, or a product with a "view source" or code-export feature does not qualify, because the component source can be taken out of it.

You are allowed to:

Create an End Product for a client.
Create an End Product for personal or commercial use.
Sell, license, sub-license, or distribute any number of copies of the End Product.
Modify and customize the components to fit your needs.
Combine the Item with other code and create derivative works from it. The resulting work is subject to this same license.
Use the Item multiple times, across multiple projects ("multi-use" license).
Organize the components into an internal library, private package, or private registry for your own workflow, as long as access is limited to the people covered by your license (you alone on a Personal license, up to 5 named team members on a Team license).
Let your AI coding agent (Cursor, Claude Code, Codex, v0, or similar) read, adapt, and assemble the components as part of building your End Product.

You are NOT allowed to:

Share or distribute the source code of the Item in its original or modified form.
Include the component source code in any public repository, including open-source projects, even inside a complete, functioning application.
Publish the components to public package registries (npm, yarn, or similar), even as a package intended only for your own project, if others can install or import it.
Redistribute the Item as a starter kit, development kit, library, boilerplate, template, or shadcn registry.
Sell, resell, or distribute the components as a standalone product.
Create a website builder, app builder, page generator, or any product whose end users assemble or generate their own sites or apps from the components, whether or not the source code is exposed. This includes AI products that generate sites or apps from the components on behalf of others.
Include any feature in your End Product that lets end users view, export, or extract the component source code.
Give access to the component source code to people not covered by your license.
Create a derivative component library based on Pro Blocks for distribution.
Use our components to create and sell (or give away) your own UI kits, design systems, templates, starter kits, or component libraries, on any marketplace or channel.

Examples of allowed usage:

Building a website, web app, or SaaS product for yourself, your company, or a client, and charging for it however you like.
Running a closed-source SaaS built with the components on top of an otherwise open-source platform or business.
Keeping the components in a private package or internal design system for your own convenience, so you can reuse them across your own projects. It must stay private: only you (Personal license) or the up to 5 team members covered by your Team license can access it. Your customers, clients, or anyone else can never install it or see its code.
Using Cursor, Claude Code, Codex, v0, or a similar AI tool to build your projects with the components. Sending the component source to these tools as part of your own development does not count as sharing or distribution.
Delivering the finished source code of a project to the client it was built for (see "Delivering work to clients" below).

Examples of usage NOT allowed:

Publishing a public npm package that contains the components, even if it's "just for my own project," is mostly unmodified, and is never promoted as a product. If others can install it, it violates this license.
Putting an open-source application on GitHub (MIT, Apache, GPL, or any other license) with the component source code in the repository, even though the app itself is a finished product.
Creating a public shadcn registry, UI kit, template, boilerplate, or starter kit from the components, free or paid, even if modified.
Building a website builder, landing-page generator, or "describe your site and we'll generate it" AI product where end users create sites assembled from the components, even if the users never see the source code.
Adding a "download source," "export code," or "eject" feature to your product that outputs the component code.
Sharing your license key, the component files, or repository access with people not covered by your license, or participating in any form of group buy.

Delivering work to clients

Delivering the End Product's source code to the client it was built for is permitted and does not count as prohibited sharing. Your client may use, host, and modify that End Product, including with their own developers.

However, your client may not extract the components from that project to use in other projects, and may not redistribute them. If your client wants to build new things with the Pro Blocks, they need their own license.

AI agents and your responsibility

You're welcome to use any AI coding tool or agent with the components, including cloud-based ones. Two things to keep in mind:

You are responsible for what your AI tools do with the components. If your agent commits the component source to a public repository, publishes it in a package, or otherwise exposes it in a way this license prohibits, that is a breach of this license by you.
An AI product or agent that you offer to others, which generates sites or apps from the components, is treated as a builder under the rules above and is not allowed.

Licensing Agreement for Skills

By purchasing Initium Pro, you are also granted a license to use Initium's Skills: SKILL.md and its reference files that instruct AI coding agents how to plan, style, and build with your Style, Strategy, and Blocks. This license grants an ongoing, non-exclusive, worldwide license to use the Item. You may use it to build unlimited End Products for yourself or your clients.

An End Product is: the website, page, or application your AI agent builds while following the Skill's instructions. The Skill itself is a tool used during the build. It is not something you deliver to your end clients.

You are allowed to:

Use the Skills to instruct any AI agent (Cursor, Claude Code, Codex, v0, or similar) on unlimited projects, for yourself or for clients.
Modify the Skill files locally to fit your own workflow.
Use the End Products the Skills help you build however you like, including selling or distributing them.

You are NOT allowed to:

Share, publish, or redistribute the Skill files (SKILL.md or its references) in original or modified form, publicly or privately, outside your own licensed team. This includes committing them to any public repository or any repository shared with people not covered by your license.
Include the Skill files in work delivered to a client. Remove them (for example from .claude/skills/ or similar agent directories) before handing over a repository. If your client wants to keep building or maintaining the project with the Skills, they need their own license.
Repackage or resell the Skills, in whole or in part, as your own "skill pack," prompt pack, template, or AI-agent product, on any marketplace or channel.
Give access to the Skill files to people not covered by your license.

You are responsible for what your AI tools do with the Skill files, the same as with the Pro Blocks. If your agent commits a Skill file to a public repository or ships it inside a client deliverable, that is a breach of this license by you.

Examples of allowed usage:

Running the Skill with Claude Code or Cursor on every client project you take on.
Editing SKILL.md locally so the agent follows your team's conventions.
Selling the websites and apps your agent builds while following the Skill.

Examples of usage NOT allowed:

Committing SKILL.md or its reference files to a public GitHub repository, even as part of a finished project.
Handing a client a repository that still contains the Skill files.
Publishing a "prompt pack" or "agent skills bundle" that includes the Skills, original or modified, free or paid.

Style and Strategy

Style and Strategy are free and don't require a license key. The DESIGN.md and STRATEGY.md files they generate are built from your own input, so they're yours to use, modify, and distribute without restriction.

Ownership

Initium and its licensors retain all rights, title, and interest in the Pro Blocks and Skills, including the source code, design, and documentation. Purchasing a license does not transfer ownership of the components or Skills to you.

You own the End Products you create, excluding the components and Skills themselves.

Termination

We may revoke your license without refund if you breach this agreement, including by sharing your license key or files with unlicensed users, publishing the components or Skills publicly, or participating in group buys. Users whose licenses are terminated for breach are not eligible to purchase again.

We reserve the right to pursue DMCA takedowns and any other legal remedies available to us for unauthorized copying, sharing, or distribution of the Pro Blocks or Skills.

Extending your license

If you outgrow your Personal license and need Team access, contact us and we'll upgrade you for the difference between what you paid and the current Team price. Include:

The email address you purchased the license with.
The license you want to upgrade to.

Need access for more than 5 people? Reach out the same way and we'll put together a custom plan.

If you're not sure whether your use case fits this license, email us before you build. We'd rather clarify up front than debate afterwards.

Contact: hi@shadcndesign.com

Learn what you can and can't do with the Pro Blocks and Skills you get after purchasing Initium PRO.

Summary

Three rules cover almost everything below:

Build anything. Use the Pro Blocks and Skills to create unlimited websites, apps, and products for yourself or your clients, and sell them however you like.
Never expose the source publicly. The component source code must never appear in a public repository, public package registry, or anywhere third parties can extract or reuse it. This applies even inside a finished open-source application.
Never turn the components into a product. Don't repackage the Pro Blocks or Skills as a UI kit, library, registry, template, starter kit, builder, or AI generator, whether free or paid, whether modified or not.

The rest of this page explains these rules in detail, with examples.

Personal vs Team Licensing

When to buy a Personal License?

You are the only person who will install or use the Pro Blocks and Skills, even if you build for multiple clients or projects.
You can use a Personal license inside a company or agency, as long as you remain the only person with access to the license key and the Pro Blocks/Skills files.

When to buy a Team License?

More than one person at your company will install or use the Pro Blocks or Skills.
You need up to 5 team members to have access to the license key, the Pro Blocks code, and the Skills files.

If you need more than 5 people to have access, contact us (see "Extending your license" below) and we'll put together a custom plan.

Licensing Agreement for Pro Blocks (Code)

You are allowed to:

Create an End Product for a client.
Create an End Product for personal or commercial use.
Sell, license, sub-license, or distribute any number of copies of the End Product.
Modify and customize the components to fit your needs.
Combine the Item with other code and create derivative works from it. The resulting work is subject to this same license.
Use the Item multiple times, across multiple projects ("multi-use" license).
Organize the components into an internal library, private package, or private registry for your own workflow, as long as access is limited to the people covered by your license (you alone on a Personal license, up to 5 named team members on a Team license).
Let your AI coding agent (Cursor, Claude Code, Codex, v0, or similar) read, adapt, and assemble the components as part of building your End Product.

You are NOT allowed to:

Share or distribute the source code of the Item in its original or modified form.
Include the component source code in any public repository, including open-source projects, even inside a complete, functioning application.
Publish the components to public package registries (npm, yarn, or similar), even as a package intended only for your own project, if others can install or import it.
Redistribute the Item as a starter kit, development kit, library, boilerplate, template, or shadcn registry.
Sell, resell, or distribute the components as a standalone product.
Create a website builder, app builder, page generator, or any product whose end users assemble or generate their own sites or apps from the components, whether or not the source code is exposed. This includes AI products that generate sites or apps from the components on behalf of others.
Include any feature in your End Product that lets end users view, export, or extract the component source code.
Give access to the component source code to people not covered by your license.
Create a derivative component library based on Pro Blocks for distribution.
Use our components to create and sell (or give away) your own UI kits, design systems, templates, starter kits, or component libraries, on any marketplace or channel.

Examples of allowed usage:

Building a website, web app, or SaaS product for yourself, your company, or a client, and charging for it however you like.
Running a closed-source SaaS built with the components on top of an otherwise open-source platform or business.
Keeping the components in a private package or internal design system for your own convenience, so you can reuse them across your own projects. It must stay private: only you (Personal license) or the up to 5 team members covered by your Team license can access it. Your customers, clients, or anyone else can never install it or see its code.
Using Cursor, Claude Code, Codex, v0, or a similar AI tool to build your projects with the components. Sending the component source to these tools as part of your own development does not count as sharing or distribution.
Delivering the finished source code of a project to the client it was built for (see "Delivering work to clients" below).

Examples of usage NOT allowed:

Publishing a public npm package that contains the components, even if it's "just for my own project," is mostly unmodified, and is never promoted as a product. If others can install it, it violates this license.
Putting an open-source application on GitHub (MIT, Apache, GPL, or any other license) with the component source code in the repository, even though the app itself is a finished product.
Creating a public shadcn registry, UI kit, template, boilerplate, or starter kit from the components, free or paid, even if modified.
Building a website builder, landing-page generator, or "describe your site and we'll generate it" AI product where end users create sites assembled from the components, even if the users never see the source code.
Adding a "download source," "export code," or "eject" feature to your product that outputs the component code.
Sharing your license key, the component files, or repository access with people not covered by your license, or participating in any form of group buy.

Delivering work to clients

AI agents and your responsibility

You're welcome to use any AI coding tool or agent with the components, including cloud-based ones. Two things to keep in mind:

You are responsible for what your AI tools do with the components. If your agent commits the component source to a public repository, publishes it in a package, or otherwise exposes it in a way this license prohibits, that is a breach of this license by you.
An AI product or agent that you offer to others, which generates sites or apps from the components, is treated as a builder under the rules above and is not allowed.

Licensing Agreement for Skills

You are allowed to:

Use the Skills to instruct any AI agent (Cursor, Claude Code, Codex, v0, or similar) on unlimited projects, for yourself or for clients.
Modify the Skill files locally to fit your own workflow.
Use the End Products the Skills help you build however you like, including selling or distributing them.

You are NOT allowed to:

Share, publish, or redistribute the Skill files (SKILL.md or its references) in original or modified form, publicly or privately, outside your own licensed team. This includes committing them to any public repository or any repository shared with people not covered by your license.
Include the Skill files in work delivered to a client. Remove them (for example from .claude/skills/ or similar agent directories) before handing over a repository. If your client wants to keep building or maintaining the project with the Skills, they need their own license.
Repackage or resell the Skills, in whole or in part, as your own "skill pack," prompt pack, template, or AI-agent product, on any marketplace or channel.
Give access to the Skill files to people not covered by your license.

Examples of allowed usage:

Running the Skill with Claude Code or Cursor on every client project you take on.
Editing SKILL.md locally so the agent follows your team's conventions.
Selling the websites and apps your agent builds while following the Skill.

Examples of usage NOT allowed:

Committing SKILL.md or its reference files to a public GitHub repository, even as part of a finished project.
Handing a client a repository that still contains the Skill files.
Publishing a "prompt pack" or "agent skills bundle" that includes the Skills, original or modified, free or paid.

The email address you purchased the license with.
The license you want to upgrade to.

Need access for more than 5 people? Reach out the same way and we'll put together a custom plan.

If you're not sure whether your use case fits this license, email us before you build. We'd rather clarify up front than debate afterwards.

Contact: hi@shadcndesign.com

Plan it once. Build it right.

Plan it once. Build it right.