License

In short

The core: MIT

@alea/ui, @alea/motion, @alea/tokens and @alea/cli are under the MIT license: use them in any project, commercial or not, change them, ship them and even build other libraries on them. The only condition is keeping the copyright and license notice in copies of the source.

MIT License

Copyright (c) 2026 Alejandro Vasquez (https://alevasquez.dev)

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.

Alea Pro

Who needs a license

One license is one seat, for one developer: anyone who installs, copies, changes or builds with the Pro source. People who only use the products you ship (your users, your clients, testers) don't need one. A team of five developers working with Pro needs five seats; designers who only use the Figma kit need a seat too.

What you can do

• Use Pro in any number of end products, for yourself, your employer or your clients, commercial or not.
• Change the Pro source for those products.
• Ship it inside them, compiled or bundled, to as many users as they have.
• Hand a client project over with Pro inside; the client needs their own seats only if their developers keep working on it.

What you can't do

• Share, sell or publish the Pro source, the Figma kit or your license key (including in public repositories).
• Make anything people can build interfaces with: templates, themes, UI kits, component libraries, design systems for sale, or website and app builders.
• Use the Pro source or the Figma kit to train or fine-tune AI models.
• Remove the license and copyright notices from the source.

An "end product"

A site, app or tool with its own purpose beyond showing Alea: a store, a dashboard, a SaaS, a portfolio. A starter kit or boilerplate whose main value is Alea Pro is not an end product.

The Figma kit

Use the kit in your own and your team's Figma files, publish it as a library inside your organization, and share designs made with it with clients and developers. Don't redistribute the kit file or the plugin, or publish them to the Figma Community.

AI tools

Using AI assistants (Claude, Copilot, Cursor and others) with the Pro source to build your own products is fine, the same as reading it yourself. Making the Pro source available to others through an AI tool, or training models on it, is not. The free core and its docs are open: llms.txt lists them for assistants.

Open source projects

An open source app can depend on Alea Pro: keep the Pro source out of the repository (install it from the registry; CI uses a key in a secret). Contributors who build the app locally need their own key. Open source libraries and templates can't include Pro; build them on the free core.

Updates, refunds and transfers

• Updates: every version published while the license is active, through the private registry and the CLI.
• Refunds and payments: licenses are sold through Lemon Squeezy; their terms and refund policy apply.
• Transfers: a seat can move to another developer in the same team; write to move it.
• When it ends: if the terms are broken, the license ends; products shipped before keep working.

The Alea name and logo

"Alea" and the logo identify this project. Say your product is "built with Alea"; don't use the name or logo as your product's name or in a way that suggests it is made or endorsed by Alea. No attribution is required in your products.

Open source notices

A few open source pieces inside the packages (icons, a QR encoder, accessibility and date utilities) and the default fonts keep their own permissive licenses. Their notices ship with every package, in THIRD_PARTY_NOTICES.md, and none of them limits how you use Alea.

This site

The text, images, the Alea name and the logo on alea.alevasquez.dev are © 2026 Alejandro Vasquez, all rights reserved. The code in the free examples is yours to copy into your projects under MIT; examples of Pro components follow the Pro license.

Questions about a specific use: write. This page summarizes the licenses; if they ever differ, the license texts in the packages decide.