HeroUI Pro Native licensing: perpetual access, optional renewals, team seats, personal tokens, and v2 upgrades.
HeroUI Pro uses a simple license model: you make a one-time purchase, get one year of updates, and keep access to the version you already paid for even if you never renew.
Perpetual access means your HeroUI Pro license does not expire in the usual SaaS sense.
If your Updates Window ends and you choose not to renew:
Renewing extends your Updates Window for another year.
That means you keep receiving:
If you skip renewal, nothing breaks. You just stay on the latest eligible version from your last active Updates Window.
Team licenses are built for companies that want centralized billing, member management, and shared access under one plan.
Team plans are seat-based. Owners and Members use one seat each; Billing users do not use a seat.
Here is the current team flow:
After a Member invitation is accepted, HeroUI Pro creates the individual license keys for the products included in your team plan automatically. It also creates that Member's Personal Token automatically. Billing users receive financial access only.
| Role | Uses a seat | Product access | Team management | Billing management |
|---|---|---|---|---|
| Owner | Yes | Yes | Full access, including roles and ownership transfer | Yes |
| Member | Yes | Yes, including personal package keys and a Personal Token | Read-only roster | No |
| Billing | No | No product access, package keys, Personal Token, or CI/CD Token | Read-only roster | Plans, seats, payments, invoices, renewals, and AI credit purchases |
Team owners can:
Ownership controls team administration and is separate from the original purchase record. Transferring ownership does not move or duplicate Stripe charges, orders, or the commercial license record.
Invited members receive an email with an invitation link. To activate access, they need to:
GitHub is still required to provision the per-platform package license keys. Once the invitation is accepted, HeroUI Pro creates the member's Personal Token automatically as well.
Billing users can manage the plan, seat count, payment methods, invoices and receipts, renewal, and AI credit purchases. They can also view the team roster. They do not use a seat and cannot access Pro products, themes, downloads, package keys, Personal Tokens, CI/CD Tokens, or team-wide product usage.
Team owners can open Usage to monitor download activity across active license keys and local AI usage buckets.
The usage page currently lets owners:
When team members use their own Personal Token for MCPs, Skills, and installs, owners get practical per-member attribution. Team members do not get access to the team-wide usage page.
HeroUI Pro includes a Personal Token for every licensed user.
This token is for human local workflows such as:
See MCP Server and Agent Skills for setup instructions.
You can view your Personal Token in:
This token is only visible to the licensed user it belongs to. Team owners cannot view a team member's Personal Token secret, and team members cannot view someone else's token.
HeroUI Pro also includes a CI/CD Token for automated installs and deployment pipelines.
Unlike the Personal Token, the CI/CD Token is designed for non-interactive environments. It lets your pipeline authenticate without signing in with GitHub on every run.
If you are the license owner, you can view your CI/CD Token in:
If you are an invited team member, you will not be able to view or reset the CI/CD Token. Only the license owner or team owner can access it.
Use HEROUI_AUTH_TOKEN as the secret that your CI system exposes to the step that installs HeroUI Pro.
env:
HEROUI_AUTH_TOKEN: ${{ secrets.HEROUI_AUTH_TOKEN }}Keep the token server-side only. Do not expose it to client-side code or public logs.
The CI/CD Token is only for non-interactive automation.
CI/CD downloads appear in the same usage reporting as your other license keys. Owners can inspect CI/CD usage from Usage by selecting the CI/CD key from the license picker.
| Token | Who can view/reset it | Use it for | Env var | Attribution |
|---|---|---|---|---|
| Personal Token | The licensed user only | Local MCP, Skills, and install flows | HEROUI_PERSONAL_TOKEN | Per-user |
| CI/CD Token | License owner or team owner only | CI/CD pipelines and shared automation | HEROUI_AUTH_TOKEN | Shared team bucket |
If you previously purchased HeroUI Pro v2, you are eligible for an upgrade discount on v3. Use the same email address from your v2 purchase and the discount should apply automatically.
If you need your old dashboard or downloads, go to HeroUI Pro v2.
If the discount does not apply automatically, contact support@heroui.pro.
This page is the plain-English version. For the exact legal definitions of Perpetual, Renewal, and Updates Window, see the HeroUI Pro Terms and Conditions.