​
Package

QuantumLock ships one Python package on PyPI: quantumlock, currently version 2.1.x. Python 3.11 or newer is required.
The install gives you:
  • The SDK — quantumlock.sdk: QuantumLockClient, LicenseValidator (v1, deprecated), LicenseValidatorV2, HybridLicenseValidator, plus the core modules the validators need (license artifacts, revocation, PQC verification).
  • The CLI — quantumlock and its short alias ql.
The wheel is client-only by design. Server-side code — the API service, the KMS providers, the transparency log, the enterprise key and PKI engines — is deliberately excluded from the published package. What you install is what you need to call the API and validate licenses offline; the service itself runs at quantumlock.softquantus.com.

​
Optional extras

The pqc extra requires the liboqs C library to be present on your system — liboqs-python is a binding, not a bundled build. Without it, ML-DSA verification is unavailable and the SDK verifies classical (RSA-PSS-SHA256) signatures only. The QuantumLock service container builds liboqs from source and gates its release on a real ML-DSA sign/verify round-trip, so server-side PQC signatures do not depend on your local install.

​
Verify the install

doctor checks local and runtime readiness (including whether PQC support is importable) and prints recommendations.

​
Configure the CLI

This prompts for the API URL (default https://quantumlock.softquantus.com) and your platform API key, saves them to ~/.quantumlock/config.json (chmod 600), and tests the connection. Environment variables override the file:

​
What is deliberately not distributed

  • There is no TypeScript/npm SDK. Integrations from other languages call the REST API directly.
  • There is no public server image: the API is consumed as SaaS. For enterprise deployment options see Deployment.