pricingfree on npmSource is one-time

Your invite is on the calendar.

npm is free, forever, with every feature. Source is a one-time license: the whole calendar as files in your repo, through the shadcn registry. Accept the invite and it lands in about a minute.

$299one-time · per team

or $0 on npm, with everything but the files

invitation

kloq Source — your copy lands

When
Today · 4:04 PM – 4:34 PM · it takes about a minute
Where
components/kloq/
Guests
kloq · organizerYou · pending

Going?

or click the event and answer in the panel — same store

01what lands

181 files. 37,866 lines. In your tree.

Counted from the payload the registry serves, not a brochure. One command copies all of it under components/kloq/ and installs the five dependencies it needs.

components/kloq/whatfileslines
calendar/views, event panel, drag engine, ⌘K, chrome6116,844
lib/quick add, rrule, ics, springs, projection, keymap6811,715
timeline/102,829
ui/coss primitives202,335
styles/tokens, springs, nineteen themes31,795
design-mode/the ⌥D inspector141,503
index.ts1578
LICENSE.kloq.md1146
test/287
settings.ts134

dependencies: @base-ui/react · class-variance-authority · clsx · lucide-react · tailwind-merge — blocks: calendar · timeline · utc-gutter · zone-gutter

02two tiers

Same component. Different address.

Everything kloq does is in both. The only question is whether it lives in node_modules or in your tree.

free

npm

The compiled, typed build in node_modules. Every feature, every theme, design mode included.

  • npm install kloq
  • All six views, nineteen themes, ⌘K, design mode
  • Updates with npm update

paid

Source

The whole calendar as licensed files in your repo, through the shadcn registry. Edit anything from the moment it lands.

  • Engine, views, themes, ⌘K and design mode as source
  • A spring tweak is a line; a custom slot is a file
  • Add-on blocks: calendar, utc-gutter, zone-gutter
  • Nothing updates unless you re-run the CLI
Get the source$299 · one-time · per team

03questions

The short answers.

Do I need both?
No. npm is the compiled build; Source is the same calendar as files. Pick one — switching later is a change of import paths, kloq/… to @/components/kloq/….
What exactly lands?
The whole library under components/kloq/ — 181 files today — and the CLI installs its 5 npm dependencies. The add-on blocks (calendar, timeline, utc-gutter, zone-gutter) declare it as a dependency, so installing any of them pulls the calendar in.
Does it update under me?
Never. Nothing changes unless you re-run the CLI on purpose. That is the trade: the licensed source lives in your tree, under your control.
What do I need?
React 19, Tailwind CSS v4, a browser with pointer events and WAAPI (every evergreen one), and a container with a real height.
Will it fight my styles?
Every token lives on [data-kloq-root] — the calendar and the container its menus render into. It never writes to :root, html, body or *.
Can I try it first?
Everything on this site is the real component — the calendar above, the landing page hero, the demo. Drag things around; press ⌥D.

Accept the invite.

$299, one-time. Or stay on npm for free — it is the same calendar.

Source purchases are governed by the Kloq Source License.