back to atlas

ks · kstack · commercial CLI

kstack · commercial distribution

KStack.

The professional way to engage with the Foundry's three artifacts. All six packages are live on npmjs.org under the @kashscript scope, and KStack ships as @kashscript/kstack with the kash binary on PATH. Three engagement paths: scaffold all artifacts at once, install per-artifact via the CLI, or skip the CLI entirely and consume the npm packages directly.

Install KStackSee the three artifacts

three ways to consume

boilerplate

All three artifacts, scaffolded together.

A single command lays down Identity, Trade, and Neuron in one project, pre-wired so the same signer drives all three. Framework-aware (Next.js, Vite, Remix, Expo).

kash init --foundry  # ← scaffolds all 3 artifacts + shared signer

status · preview · Q2 2026

cli · one artifact at a time

kash add <artifact> --apply.

Adopt incrementally. The CLI scans your stack, picks the right entry points, wires the SDK, and writes a backup. Dry-run by default; --apply commits. kash rollback reverses any edit.

kash add identity --apply
kash add trade --apply
kash add neuron --apply

status · shipping today

npm · skip the CLI

Install directly from npmjs.

Already know what you want? Pull packages straight from the public registry. The same tarballs the CLI installs, just without the framework-aware scaffolding.

bun add @kashscript/identity-core   # 0.3.0
bun add @kashscript/trade-sdk@alpha # 1.0.0-alpha.1
bun add @kashscript/neuron          # 0.1.0

status · live on npmjs.org

live on npmjs.org

Six packages under the @kashscript scope, owned by npm user kashinnov. Three are Apache-2.0 (free for any use); three are SSLA (source visible, commercial use gated by the LICENSE document plus a runtime license-key check — see the licensing section below).

  • @kashscript/identity-core0.3.0Apache-2.0Cryptographic substrate. Ed25519, did:kash, JCS.
  • @kashscript/lexicons0.1.0Apache-2.0Envelope + schema engine for Kash-Events.
  • @kashscript/identity-sdk0.1.2Apache-2.0React provider + hooks + headless storage.
  • @kashscript/identity-zkp0.2.1SSLAZK selective disclosure (Merkle + Groth16).
  • @kashscript/trade-sdk1.0.0-alpha.1SSLAFive paradigms · EIP-712 signals · CREATE2.
  • @kashscript/neuron0.1.0SSLAAgentic reasoning + signed receipt chains.

install kstack globally

Pick your runtime. The package is @kashscript/kstack; the binary it exposes is kash. npx works zero-install, but for repeated use, install globally.

$ npm install -g @kashscript/kstack

or run zero-install

For a single integration, npx / bunx / pnpm dlx fetch KStack on demand and exit. No global state, no PATH pollution.

one-shot · install Identity into the current project

$ npx @kashscript/kstack add identity --apply

Zero install. npx fetches @kashscript/kstack on demand, runs it, and exits.

command surface

Every command runs dry by default. Add --apply to actually write changes; every edit is backed up under ~/.kash/backups/ and reversible via kash rollback.

  • kash loginBind your machine to a did:kash via WebAuthn.
  • kash browseInteractive picker over the three artifacts; shows your Plan tier.
  • kash add <artifact> --applyInject Identity / Trade / Neuron into the current project. Idempotent.
  • kash trade deploy --chain …Deploy the Trade suite to a chain (factory + 5 blueprints + paymaster).
  • kash trade status --address …Read-only FSM dashboard for a deployed trade clone.
  • kash neuron statusHealth check + ledger tamper-detection self-test.
  • kash doctorVerify every installed artifact is wired correctly.
  • kash rollback listList backups; pass a match to restore.

licensing posture

Free to install. Paid for production.

KStack itself is free to install and use for local development. The artifacts it scaffolds inherit each artifact's own license posture — Identity stays Apache-2.0 (SSLA Schedule A); Trade and Neuron are Commercial (SSLA Schedule B) and require a paid Plan on the Kash-Registry for production use.

how the paywall actually works

Runtime license-key check on the commercial artifacts.

Trade-SDK and Neuron read KASH_LICENSE_KEY at module initialisation. The key is a compact JWT-style token signed by the Kash-Registry's Ed25519 private key. Each package ships with the matching public key baked into the tarball; verification is offline — no callback home.

# 1. Get a key after upgrading from Free → Trial / Paid
kash login
kash license issue --tier paid

# 2. Set it in your deployment environment
export KASH_LICENSE_KEY=eyJ2IjoxLCJkaWQiOiJkaWQ6a2FzaDoumvI...

# 3. trade-sdk + neuron now operate in production mode
#    (Free mode still works locally; gates trigger when NODE_ENV=production)

Token payload is { v, did, tier, iat, exp, sig }. TTL is short (≤ 7 days for paid, ≤ 1 hour for trial) so a leaked key auto-expires. Refresh via kash license refresh.

The license-server is the one piece of operational infrastructure that KashScript runs. It never stores user data, private keys, or record content — only the public DID + Plan tier + the issued-token audit log. The packages on npm host no telemetry; once installed, your data goes wherever you put it.

See artifact pricing →License terms (SSLA)
next

The Foundry

three artifacts

next

The Studio

workshop in Islamabad

next

The Journal

dated releases