License
Last updated: July 21, 2026
The Short Version
Buy the right number of seats for the people who can access Termcn Pro source. Those people can use and modify it to build unlimited personal, commercial, internal, and client End Products. Do not share the source or access credentials outside those licensed people, and do not repackage the source into a competing library, template catalog, builder, generator, or marketplace.
This page is a readable summary, not a substitute for the binding End User License Agreement. If the two differ, the EULA controls.
Choose the Right License
| License | Who may access source |
|---|---|
| Personal | One named developer |
| Team | Named employees and contractors, up to the Seat Limit on the order |
Seats count people with source or registry access. They do not count projects, repositories, clients, deployments, or end users of a finished application.
You May
- build unlimited End Products for yourself or your company;
- build unlimited custom End Products for unlimited Clients;
- use End Products commercially and charge their end users;
- modify the source to fit your product; and
- distribute a finished or self-hosted End Product when its primary value is not the Termcn Pro source itself.
You May Not
- share one Personal license with another developer;
- give Team access to more people than the purchased Seat Limit;
- publish, sell, sublicense, or give away the source or derivatives as reusable components, blocks, templates, or starter kits;
- include the source in a public repository where it can be extracted and reused;
- use it as the content of a competing UI library, builder, code generator, marketplace, or training dataset; or
- share, sell, or expose a login, session, access token, or license key.
Common Examples
- Allowed: a commercial CLI, internal terminal dashboard, SaaS admin tool, or custom application for one client.
- Not allowed: publishing a collection of Termcn Pro ports, selling a TUI starter kit containing the source, or giving customers a way to download the underlying components.
- Needs another seat: a second developer, coworker, or contractor needs to inspect, install, copy, or modify the source.
- Does not need another seat: a customer or employee only uses the finished application and cannot access the source.
Questions
If your use case is unclear, contact hello@termcn.dev before distributing the product.