Docs

Pro and the CLI

Install Pro pieces with your licence key, in your project, in CI and with your team.

Pro unlocks every piece: the source on the site, the downloads and the CLI. It is paid once ($149), with updates included. Team covers up to 10 developers in one company ($399).

1. Your licence key

Use the licence key from your receipt email, or the CLI key on your account page. Either works. Keep it out of your repository.

2. Add the registry, once

Add the @obsyde registry to your components.json:

{
  "registries": {
    "@obsyde": {
      "url": "https://obsydeui.com/r/{name}.json",
      "headers": {
        "Authorization": "Bearer ${OBSYDE_LICENSE_KEY}"
      }
    }
  }
}

3. Set the key

Put the key in .env.local (the CLI reads .env and .env.local):

OBSYDE_LICENSE_KEY=your-licence-key

4. Install

npx shadcn@latest add @obsyde/fuse-button

Free pieces install by name the same way. Search the whole collection from the terminal:

npx shadcn@latest search @obsyde -q chart

In CI and with a team

Set OBSYDE_LICENSE_KEY as a secret in your CI or hosting provider; the same commands work there. With Team, every developer on the licence uses the team key.

Searching and installing free pieces through @obsyde work without Pro, but the CLI wants the variable to exist. Set it to anything, such as OBSYDE_LICENSE_KEY=free, or install free pieces by URL instead.

If the CLI answers 401

The piece is Pro and the request had no valid key. Check that OBSYDE_LICENSE_KEY is set in the shell or .env.local you run the CLI from, that the key is the one from your receipt, and that the @obsyde entry is in the components.json of the project you are in. Questions: support@obsydeui.com.