Licensing
How BlakeUI Pro licensing, perpetual access, renewals, and v2 upgrades work.
BlakeUI 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 — BlakeUI 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 BlakeUI 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
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:
- Purchase a Team plan.
- Go to Dashboard → Teams.
- Create your team.
- Invite members by email.
- Each member accepts the invitation and links a GitHub account.
After an invitation is accepted, BlakeUI Pro creates the individual license keys for the products included in your team plan automatically, along with that member's Personal Token.
Personal Token
BlakeUI Pro includes a Personal Token for every licensed user. This token is for human local workflows such as MCP server setups in editors (Cursor, Claude Code, VS Code, Windsurf, Zed), Skills installs, and other local AI or developer-tooling flows that should be attributed to a specific user.
Use the environment variable BLAKEUI_PERSONAL_TOKEN. This token is only visible to the
licensed user it belongs to.
CI/CD Token
BlakeUI 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.
Use the environment variable BLAKEUI_AUTH_TOKEN as the secret your CI system exposes to
the step that installs BlakeUI Pro.
Keep the CI/CD token server-side only. Do not expose it to client-side code or public logs. Rotate it from Settings immediately if you think it was leaked.
Personal vs CI/CD
| Token | Who can view/reset it | Use it for | Env var |
|---|---|---|---|
| Personal Token | The licensed user only | Local MCP, Skills, and install flows | BLAKEUI_PERSONAL_TOKEN |
| CI/CD Token | License owner or team owner only | CI/CD pipelines and shared automation | BLAKEUI_AUTH_TOKEN |
For BlakeUI Pro v2 Customers
If you previously purchased BlakeUI 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 it does not, contact support@blakebill.com.