Pro access

Pro components and blocks live in a private registry, @blank-pro. It serves the same JSON as the free registry, behind a licence check. Setup takes about two minutes.

1. Get a licence

Buy Blank Pro on the pricing page. The licence key arrives by email with your receipt. Team licences share one key across the team and CI.

2. Store the key

Put the key in an environment file the CLI can read. In most projects that is .env.local, which should already be in .gitignore:

BLANK_LICENSE_KEY=your-licence-key

For CI, add BLANK_LICENSE_KEY as a secret in the pipeline instead.

3. Add the registry

List @blank-pro next to @blank in components.json. The CLI expands ${BLANK_LICENSE_KEY} from the environment and sends it as a bearer token:

{
"registries": {
  "@blank": "https://useblank.design/r/{name}.json",
  "@blank-pro": {
    "url": "https://useblank.design/r/pro/{name}.json",
    "headers": {
      "Authorization": "Bearer ${BLANK_LICENSE_KEY}"
    }
  }
}
}

The key never goes into components.json itself, so the file is safe to commit.

4. Install

npx shadcn@latest add @blank-pro/hero-02

Pro items can depend on free ones; the CLI resolves both namespaces in one run. Every Pro page on this site shows its exact command.

Troubleshooting

401 — "A valid Blank Pro licence key is required." The registry did not receive a key it accepts. Check, in order:

1. echo $BLANK_LICENSE_KEY in the same shell prints the key. If not, the env file is not loaded — run the command from the project root, or export the variable first.
2. The header reads Bearer ${BLANK_LICENSE_KEY} exactly, with a space after Bearer.
3. The key has no quotes or trailing spaces in .env.local.
4. The licence is active. Refunded or disabled keys stop working.

404 — "No Pro item". The name is wrong or the item is free. Free items install from @blank, not @blank-pro.

"Unknown registry @blank-pro". The registries entry is missing or components.json has a syntax error. Upgrade the CLI if it predates namespaced registries: npx shadcn@latest.

Still stuck? Contact us with the command you ran and the full error.