Pro

Pro is larger components and full page blocks, built to the same standard as the free library and installed the same way. Paying gives you a license key. The key unlocks the source: without it the live preview and props are still public, the code is not.

Buy Pro from the pricing section on the home page. Payment goes through Polar, who act as the merchant of record and handle tax. Your license key is shown on the confirmation page and sent in your receipt.

• One license covers one person, on up to 3 devices.
• Use the code in as many personal and commercial projects as you like.
• Lifetime access: every update and new Pro component, for as long as uibrik sells Pro.
• Don't share your key or republish the source as a library, template or component kit.

The full wording is in the terms. Purchases are non-refundable except for technical issues, see the refund policy.

Add the Pro registry to components.json. The CLI sends your key with every request, read from an environment variable so it never lands in the file.

{
  "registries": {
    "@uibrik-pro": {
      "url": "https://uibrik.com/r/pro/{name}.json",
      "headers": { "Authorization": "Bearer ${UIBRIK_LICENSE}" }
    }
  }
}

Put the key in .env.local and make sure that file is in .gitignore.

UIBRIK_LICENSE=your-license-key

Each Pro component page shows its own command. They all look like this:

npx shadcn@latest add @uibrik-pro/<name>

Your agent uses the same command, so with the registry and key set up it can install Pro components when you ask for them. Keep the key in the environment, not in the prompt.

Sign in with the email you bought with. Polar sends you a one-time code, so there is no password to keep. You stay signed in for 30 days on that browser. Signed in, your initial shows in the header, you can see your license key, read and copy the source of every Pro component on its page, and replace your key if it was shared or leaked. A replaced key stops working immediately, and a refund ends your access straight away.

• 401 or "not valid": the key is wrong, was revoked or the variable isn't set. Check .env.local and restart the terminal or dev server.
• 404: the component name doesn't exist. Copy the command from its page.
• Lost your key: sign in on your account page, or find it in your receipt email.