Licence keys

What a key looks like

snowpro_ followed by 32 letters and digits. It arrives by email after your purchase. The licence server keeps only a hash of it, so a lost key can’t be looked up and sent again — it is replaced with a new one instead (below).

Where it goes

In an environment variable, SNOW_UI_PRO_TOKEN, that components.json refers to (see installation). Put it in .env.local or your shell’s environment, never in a committed file, and never in a variable your app exposes to the browser (such as one starting with NEXT_PUBLIC_).

Teams

A licence covers a number of developers (its seats); they all use the licence’s key. Share it the way you share other secrets, through a password manager or a secrets store, not in chat. When someone leaves the team, their seat passes to whoever replaces them. If the key may have left with them, ask for a new one.

CI and deployments

The key is only needed where shadcn add runs. The files it writes are part of your code, so builds and deployments don’t need the key at all. If a CI job does run the CLI, give it the key as a secret:

# .github/workflows/<workflow>.yml — only if CI runs `shadcn add`
env:
  SNOW_UI_PRO_TOKEN: ${{ secrets.SNOW_UI_PRO_TOKEN }}

Lost or leaked keys

Write to support from the email address you bought with, quoting the first 16 characters of the key (snowpro_ and 8 more) if you have them — never the whole key. The old key is revoked and a new one is emailed to you; the old one then answers 403 licence_revoked.

How long a key works

For the 12 months of updates that come with your licence. After that the registry answers 403 updates_expired, but everything you installed is yours to keep using under the licence: nothing in it checks the key. A refund is different: it ends the licence itself (see the refund policy).