Common questions

Free vs subscription — what's the actual difference?

Free components are MIT licensed and need nothing — velocityx add <slug> fetches them straight from the public registry. Subscription components need a licence key first ( velocityx login vx_live_...) — the CLI re-requests them from a licence-gated endpoint using that key. The library and this site list both side by side on purpose: you can see what a subscription unlocks before paying for it.

What happens when my subscription lapses?

You keep every file you already installed — they're plain files in your repo, and nothing about them checks back in with Aidxn. What stops is installing new paid components: the next velocityx add for a subscription-only slug fails with "Your Velocity Components subscription has been cancelled" (or "is past due"), and that's as far as it reaches — it doesn't touch, re-check, or revoke anything already on disk.

Astro or React — what if I'm on neither?

Every component in the registry ships as either Astro or React source — those are the only two the registry serves today. On Vue, Svelte, or plain HTML, there's no automatic port: pull a component anyway with velocityx add <slug>, read the markup and class list it writes, and hand-translate the structure into your framework. The CSS is the easy part — it's all primary-* / accent-* Tailwind classes, which work unchanged once your project has the theme installed.

Can I edit the code?

Yes — that's the whole point. Nothing about an installed component is generated at build time or re-read from a package; it's a file you own from the moment it lands.

Do updates overwrite my edits?

No, not by default. Running velocityx add for a component you already have leaves every existing file alone and tells you so:

Left alone (already present — pass --force to overwrite):
  · src/components/velocity/badge-tag/BadgeTag.astro

Pass --force and it will overwrite — but first it hashes the files currently on disk and compares that hash against what velocityx.lock.json recorded at install time. If they differ (you've edited the file), it still honours --force — that's what the flag is for — but it warns first, once, instead of silently clobbering your changes:

⚠  badge-tag has changed on disk since it was installed (hash no longer matches velocityx.lock.json).
   Overwriting anyway because --force was passed. Local edits to these files will be lost.