Skip to content

Lathe Pro

87 more components and assemblies, installed with the same CLI as the free core. One payment, lifetime updates, and the code is yours to keep.

What Pro includes

  • All 72 components that are not in the free core, such as Data Table, Sheet, Command Palette, Line Chart and File Dropzone.
  • All 17 assemblies, including dashboards, checkout, workbenches, inbox and upload manager. These are the hours saved.
  • Page templates built from the assemblies, as they ship.
  • Lifetime updates: every component, assembly and fix added to Pro, for as long as Lathe Pro exists.
  • Personal and commercial use in unlimited projects. Pro covers one developer; Team covers 10. See Pricing.

Set up

Your license key is in your purchase email. In your project's root, next to components.json, run:

pnpm dlx latheui init --key <your key>

It checks the key, sets up the @latheui registry in components.json to send it, saves the key to .env.local and makes sure that file stays out of git. Nothing is installed globally or added to your dependencies.

It also remembers the key on this computer, in ~/.lathe/config.json. In your next project, run it without the key:

pnpm dlx latheui init

It also picks up LATHE_LICENSE_KEY when it's set in your environment. Add --no-save to skip remembering the key, and run npx latheui logout to forget it. Projects you already set up keep their own copy.

Manual setup

Prefer to do it by hand? Set up the registry in components.json. The shadcn CLI reads the key from the environment and sends it with each request, so it never sits in the file.

components.json
{
  "registries": {
    "@latheui": {
      "url": "https://latheui.dev/api/registry/{name}.json",
      "headers": {
        "Authorization": "Bearer ${LATHE_LICENSE_KEY}"
      }
    }
  }
}
.env.local
LATHE_LICENSE_KEY=your-license-key

On CI or a deploy server, set LATHE_LICENSE_KEY as an environment variable there instead. Once the registry sends a key, the shadcn CLI asks for it on every @latheui install, free ones too, so anyone installing in the project needs it set.

Install

Pro items install by name, exactly like free ones. Anything they depend on comes along automatically.

pnpm dlx shadcn@latest add @latheui/data-table

Agents use the same names. With the registry set up, the MCP server lists Pro items next to free ones.

Updates

Run the add command again to pull the latest version, and review the diff like any other change to your code. The changelog lists what changed in each release.

Team

A Team license covers up to 10 developers. Share the key with your team; each developer runs the setup command with the key once on their own computer, and after that plain npx latheui init in each new project.