# Install Patine Pro

> Install Patine Pro charts, blocks, screens and app templates into a React Native or Expo app with your license key and npx shadcn add. Plain source in your project, no runtime license check.

# Install Patine Pro Pro

Pro comes as plain source, through a licensed registry that works with the shadcn CLI. Each chart, block, screen or app
lands in your project under `components/patine-pro/`, with what it needs from other Pro items. Nothing phones home: once
the files are in your app, they're yours.

You need [`patine-ui`](../getting-started/installation.mdx) installed, and a Pro license from the [pricing page](pathname:///pricing).

## 1. Get your license key

After checkout, Polar emails a link to your customer portal. Your license key is there, under your Patine Pro purchase.
On a Team plan, each seat holder gets their own key once they accept their seat.

The same portal has your seats, invoices and renewal, and is where you cancel. It's linked as **Account** in this site's
navbar.

## 2. Set the key as an environment variable

```bash
# .env.local, which git ignores. Never commit the key.
PATINE_LICENSE=your-license-key
```

In CI, add `PATINE_LICENSE` as a secret instead.

## 3. Add the registry to components.json

Create `components.json` at your project's root, or add `registries` to the one you have:

```json
{
  "$schema": "https://ui.shadcn.com/schema.json",
  "style": "new-york",
  "rsc": false,
  "tsx": true,
  "tailwind": { "config": "", "css": "", "baseColor": "neutral", "cssVariables": false },
  "aliases": { "components": "@/components", "utils": "@/lib/utils" },
  "registries": {
    "@patine-pro": {
      "url": "https://registry.patine.dev/r/{name}.json",
      "headers": { "Authorization": "Bearer ${PATINE_LICENSE}" }
    }
  }
}
```

Pro files go in `aliases.components`, so `@/components` puts them in `components/patine-pro/`. Expo's templates already
map `@/*` to the project root.

## 4. Add what you need

```bash
npx shadcn@latest add @patine-pro/kanban
npx shadcn@latest add @patine-pro/bar-chart @patine-pro/pie-chart
npx shadcn@latest add @patine-pro/budget
```

If the CLI doesn't pick up `.env.local`, pass the key inline: `PATINE_LICENSE=… npx shadcn@latest add @patine-pro/kanban`.

Item names follow the docs pages: blocks by their name (`kanban`, `event-calendar`, `data-grid`), charts as
`<type>-chart` (`line-chart`, `gauge-chart`) plus `sparkline` and `status-tracker`, apps by their key (`store`,
`crypto`, `budget`), and `icons` and `brands` for the icon sets. The full list is at
`https://registry.patine.dev/registry.json`, with the same key.

Then import from where the files landed:

```tsx
import { Kanban } from '@/components/patine-pro/blocks/kanban';
```

## Updates

While your license is active, run the same `add` command with `--overwrite` to take the latest version of an item. Your
changes to those files are replaced, so commit first and review the diff. When a license ends, the code you already
installed keeps working; new downloads stop. The [Pro license](pathname:///legal#pro-license) has the terms.

## Errors

| Status | Meaning |
| --- | --- |
| 401 | No key reached the registry: check `PATINE_LICENSE` is set where you run the command. |
| 403 | The key isn't active: it was mistyped, revoked, or the subscription ended. Check it in the customer portal. |
| 404 | No item by that name: see `registry.json`. |
| 429 | Too many requests from your network: wait a minute. |

## Related

- [Pricing](pathname:///pricing)
- [Responsive layout](./layout.mdx)
- [MCP server](../resources/mcp.mdx): your agent can run the same `npx shadcn add` commands.
