Licensing

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.

How It Works

• One-time purchase — HeroUI Pro is not a mandatory subscription.
• 1 year of updates included — Your license includes an Updates Window with access to new components, fixes, templates, and features released during that period.
• Renewal is optional — If you want another year of updates, you can renew. If you do not renew, you keep using the latest version you were entitled to.

What "Perpetual" Means

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:

• You keep access to all components, templates, and features released before your license expired
• Your existing projects can continue using that version
• You are not locked out of your previous purchase
• You simply stop receiving new releases after that point

What Renewal Gives You

Renewing extends your Updates Window for another year.

That means you keep receiving:

• New components and templates
• Feature updates
• Bug fixes and improvements
• New releases across the products included in your plan

If you skip renewal, nothing breaks. You just stay on the latest eligible version from your last active Updates Window.

Team Licenses

Team licenses are built for companies that want centralized billing, member management, and shared access under one plan.

Team plans are seat-based, and each seat maps to one team member.

Here is the current team flow:

1. Purchase a Team plan.
2. Go to Dashboard Teams.
3. Create your team.
4. Invite members by email.
5. Each member accepts the invitation and links a GitHub account.

After an 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.

Team Owners

Team owners can:

• Create and rename the team
• Invite members by email
• Remove members or cancel pending invitations
• Add more seats from Billing when all seats are in use
• View usage data for active license keys

Team Members

Invited members receive an email with an invitation link. To activate access, they need to:

• Sign in to HeroUI Pro
• Link a GitHub account in their account settings
• Return to the invite link and accept the invitation

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.

Usage and Visibility

Team owners can open Usage to monitor download activity across active license keys and local AI usage buckets.

The usage page currently lets owners:

• See total downloads for a selected license
• Change the date range
• Switch between active license keys, including member-assigned keys, Personal Tokens, and the CI/CD Token

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.

Personal Token

HeroUI Pro includes a Personal Token for every licensed user.

This token is for human local workflows such as:

• MCP server setups in editors like Cursor, Claude Code, VS Code, Windsurf, and Zed
• HeroUI Pro Skills installs
• Other local AI or developer-tooling flows that should be attributed to a specific user

See MCP Server and Agent Skills for setup instructions.

How It Is Created

• For license owners, the Personal Token is created automatically when the license becomes active
• For invited team members, the Personal Token is created automatically when they accept the invitation
• Every licensed user gets their own Personal Token

Where to Find It

You can view your Personal Token in:

• Overview
• Settings

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.

Why It Matters

• Personal Token usage is attributed to the specific licensed user
• It is the correct default for local MCP and Skills usage
• Team members should use this token for normal local AI workflows

CI/CD 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.

How It Is Created

• The CI/CD token is created automatically for active licenses
• It is intended for CI providers like GitHub Actions, Vercel, Railway, and similar deployment systems
• It works without an interactive GitHub login
• Plan access still applies: React requires a Web or Super plan, and React Native requires a Mobile or Super plan
• CI/CD usage does not have monthly download limits

Where to Find It

If you are the license owner, you can view your CI/CD Token in:

• Overview
• Settings

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.

Environment Variable

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.

Scope

The CI/CD Token is only for non-interactive automation.

Security Best Practices

• Store the token in your CI provider's encrypted secrets
• Never commit it to your repository
• Never expose it in browser code, preview builds, or public environment variables
• Rotate it from Settings immediately if you think it was leaked
• After rotating, update every pipeline that used the old token

Usage Tracking

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.

Personal vs CI/CD

Which Token Should I Use?

• Use the Personal Token for any local editor, MCP, or Skills setup
• Use the CI/CD Token only for non-interactive environments like GitHub Actions, Vercel, or Railway
• Use the Personal Token for all local AI tooling, including MCPs, Skills, and installs

For HeroUI Pro v2 Customers

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.

Legal Terms

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.