Licensing
How BlakeUI Pro subscriptions, access, and tokens work.
BlakeUI Pro is a subscription. While it is active you get the @blakeui/pro-*
packages, the AI agent skills, and the MCP server. Billing is handled by Polar.
How It Works
- Subscription — BlakeUI Pro is $20/month, billed securely through Polar.
- Full access while active — an active subscription unlocks every Pro package, all updates released while you're subscribed, the agent skills, and the MCP server.
- Cancel anytime — manage or cancel from Dashboard → Billing. You keep access until the end of the current billing period; after that it ends.
What You Get
While your subscription is active:
- Install
@blakeui/pro-react(and other Pro packages) from the private registry - Receive new components, fixes, templates, and features as they ship
- Use the AI agent skills and the MCP server
If the subscription lapses, package installs, skills, and MCP access stop working once the billing period ends — your tokens are revoked. Re-subscribe anytime from the dashboard to restore access.
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, and you can reveal or rotate it from
Dashboard → Tokens.
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 Dashboard → Tokens 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 | The license owner only | CI/CD pipelines and shared automation | BLAKEUI_AUTH_TOKEN |
Get either token from Dashboard → Tokens. Both are scoped to your license and can be rotated independently.