Registry

The ReUI Registry uses a single @reui namespace for free c-* components, paid blocks, paid icons, and paid templates. The shadcn CLI resolves the full alias suffix into the registry URL, so you can install everything from one namespace and let ReUI handle access rules on the server.

Setup ReUI Registry

Add the ReUI registry namespace to your components.json. Learn more about registry config from shadcn registry docs.

{
  "registries": {
    "@reui": "https://reui.io/r/{style}/{name}.json"
  }
}

Free Components

Free component examples use the c-* naming pattern and can be installed without a license key.

pnpmnpmyarnbun
pnpm dlx shadcn@latest add @reui/c-alert-1
Copy

Some free c-* items pull shared @reui/* primitives such as @reui/alert or @reui/data-grid as registry dependencies. Those supporting files remain publicly accessible so free component installs keep working.

Paid Blocks, Icons, And Templates

Premium blocks, icons, and templates use the same @reui namespace, but they require a valid license key.

If you want the full premium setup flow with a visible account key state, copy-ready snippets, and install examples in one place, see the License Setup guide.

1. Add your license key to .env.local.

REUI_LICENSE_KEY=your-license-key

2. Change the registry entry to the authenticated object form.

{
  "registries": {
    "@reui": {
      "url": "https://reui.io/r/{style}/{name}.json",
      "headers": {
        "Authorization": "Bearer ${REUI_LICENSE_KEY}"
      }
    }
  }
}

3. Install premium items from the same namespace.

pnpmnpmyarnbun
pnpm dlx shadcn@latest add @reui/banner-1
npx shadcn@latest add @reui/icons/default/solid/all
Copy

Free items keep working with the authenticated config too, so you do not need a second registry namespace.