Licensing

An on-prem installation runs under a signed license issued by Kapable. The license is the wall — this documentation is public, the platform bits are licensed. You never receive or handle signing keys; you receive a license for your installation.

kapable-ops --help

How licensing works

• Platform services validate a signed license at startup and bind it to the machine they run on (a fingerprint of the box). A license moved to different hardware fails validation by design.
• Licenses are issued by Kapable, scoped to your installation, and renewable. Issue and revocation are functions of the Kapable release service; validation happens locally on your box — a running install does not phone home to stay up.
• The installer places license material on the box during node 5 (fleet-deploy); you don't hand-install files.

The bootstrap window

A fresh installation boots its services inside a 72-hour bootstrap window, so the install itself never blocks on license logistics. Activate with your issued license inside that window and the installation transitions to its durable license; after the window closes, unlicensed services stop accepting work with an error that says exactly this.

Getting the bits

Two things are distributed to you: the kapable-ops installer CLI, and the artifact bundle — the set of signed platform binaries for a release, which you point --artifact-source at.

Current status, honestly: self-service distribution through https://releases.kapable.ai (download a release bundle with your license key, installer validates it offline) is rolling out. Until it lands, artifact bundles and license issuance are operator-assisted — contact us and we provision both with you, typically same-day. The install procedure on these pages is identical either way; only how the bundle reaches your workstation changes.

Next Steps

Next

Getting Started · Authentication