Pro license

Install Pro packages, set LicenseInfo, and import with // @velkin-pro.

Before you begin

MIT core packages already work without a key (Quick start)
Pro needs a commercial runtime license in production — get a key from Pricing / your dashboard

Install

Install the wrapper (and Pro) packages only. Core, license, and Lit helpers ship as dependencies — you do not maintain them separately.

# React MIT
npm install @velkin/react

# React Pro (includes @velkin/react, @velkin/ui, @velkin/license)
npm install @velkin/react-pro

# Vue MIT
npm install @velkin/vue

# Vue Pro (when published)
npm install @velkin/vue-pro

# Lit / HTML MIT
npm install @velkin/ui

# Lit / HTML Pro
npm install @velkin/ui-pro

Set the license key

Call once before rendering Pro components. Use your framework's public env prefix:

import { LicenseInfo } from "@velkin/license";

// Vite
LicenseInfo.setLicenseKey(import.meta.env.VITE_VELKIN_LICENSE_KEY ?? "");

// Next.js (client)
LicenseInfo.setLicenseKey(process.env.NEXT_PUBLIC_VELKIN_LICENSE_KEY ?? "");

// Optional: same-origin revocation sync on Official hosts
LicenseInfo.configure({ syncEndpoint: "/api/v1/license/check" });

Validate formats on License.

Import Pro components

// @velkin-pro
import { VuDataTable } from "@velkin/react-pro/data-table";

export function Grid() {
  return <VuDataTable /* … */ />;
}

Always use @velkin/react-pro/…, @velkin/vue-pro/…, or @velkin/ui-pro/… subpaths — never the MIT path for Pro-only tags. Keep the // @velkin-pro comment next to Pro imports so tooling can flag them.

Pair core velkin() with the Pro plugin when your app imports Pro packages. See Installation for your framework. Next.js: defineVelkin from @velkin/react/next.

Next steps