QuantumLock
Enterprise License Management with Quantum-Enhanced Security
QuantumLock is a comprehensive software licensing solution that combines RSA-4096 cryptographic signatures with optional quantum-enhanced security features.
Features
- 🔐 Cryptographic License Signing - RSA-4096 with SHA-256
- ⚛️ Quantum-Enhanced Security - Optional quantum fingerprinting (Qiskit)
- 🌐 REST API - SaaS license management platform
- 💻 CLI Tool - Command-line license generation and validation
- 🔄 Floating Licenses - Concurrent seat management with Redis
- 📦 SDK - Embeddable validation library
Installation
# SDK + CLI: puts `quantumlock` and `ql` on PATH
pip install quantumlock
# Everything a client machine can run: quantum entropy (Qiskit, QCOS Runtime
# via softqcos-sdk) and ML-DSA / FIPS 204 signatures (liboqs-python)
pip install "quantumlock[full]"
The published wheel is the client (SDK, CLI, offline verifier). The REST
API and the floating license server are not in it; they run as SoftQuantus
services or from this repository (see Docker below). quantumlock[cli] still
resolves, but the CLI is part of the base install since 2.1.5.
liboqs-python is only the binding: ML-DSA also needs the native liboqs
shared library, and QuantumLock never downloads or builds it behind your back.
Provision it once, explicitly:
python -c "import oqs" # liboqs-python clones and builds liboqs into ~/_oqs
# (needs git, cmake and a C compiler)
# or point at an existing shared build (lib/liboqs.so or lib/liboqs.dylib):
export OQS_INSTALL_PATH=/opt/liboqs
Homebrew's liboqs is a static library and does not satisfy the binding.
Until the shared library is there, quantumlock doctor says so and ML-DSA
signing and verification are reported unavailable; nothing exits.
Quick Start
CLI
quantumlock doctor # local readiness: crypto, PQC, entropy
quantumlock configure # store your QuantumLock API key locally
# Issue a license through the QuantumLock API, then check it
quantumlock generate --customer acme@example.com --features pro,export \
--days 365 --output license.json
quantumlock validate <license_key> --file license.json
# Offline verification of a QCOS evidence record (no API key needed)
quantumlock trust-bundle --help
quantumlock verify --help
quantumlock --help lists every command (keys, trust-root, inventory,
v2, ...).
SDK
from quantumlock.sdk import LicenseValidator
validator = LicenseValidator("license.json")
if validator.validate():
print(validator.get_license_info())
print("pro" if validator.has_feature("pro") else "basic")
API Server (source checkout only; not in the PyPI wheel)
# Using Docker
docker-compose up -d api
# Or directly, from a clone of this repository
pip install -e ".[api,pqc]"
uvicorn quantumlock.api:create_app --factory --host 0.0.0.0 --port 8000
Architecture
quantumlock/
├── src/quantumlock/ # Main package
│ ├── core/ # Shared models, crypto, config
│ ├── api/ # REST API (FastAPI)
│ ├── cli/ # CLI tool (Typer)
│ ├── sdk/ # Embeddable SDK
│ └── server/ # Floating license server
├── lib/ # Shared libraries
│ ├── authority.py # RSA signing/validation
│ └── quantum_protocol.py # Quantum features
└── tests/ # Test suite
Docker
# API server
docker build --target api -t quantumlock-api .
# CLI tool
docker build --target cli -t quantumlock-cli .
# License server
docker build --target server -t quantumlock-server .
Deployment
Unified Deployment Script
The project includes a master deployment script that handles everything from zero:
# Full deployment (API + SDK + CLI)
./scripts/deploy_all.sh
# Staging environment
./scripts/deploy_all.sh --env staging
# Preview without executing
./scripts/deploy_all.sh --dry-run
# Skip components
./scripts/deploy_all.sh --skip-api # Only SDK/CLI
./scripts/deploy_all.sh --skip-sdk # Only API + CLI
./scripts/deploy_all.sh --skip-cli # Only API + SDK
Deployment Phases
- Bootstrap - Generate RSA-4096 keys and bootstrap license for API
- Build API - Nuitka compilation in Docker (Linux-compatible binaries)
- Deploy API - Push to Azure Container Apps
- Generate Licenses - Create SDK/CLI licenses via running API
- Build SDK/CLI - Nuitka with embedded licenses and public keys
- Deploy SDK/CLI - Push to Azure/Registry
Scripts
| Script | Purpose |
|---|---|
scripts/deploy_all.sh |
Master script - does everything |
scripts/build_docker.sh |
Nuitka build via Docker |
scripts/build_nuitka.py |
Core Nuitka compilation |
automation/3-deploy-protected-apis.sh |
Azure deployment (alternative) |
License Protection
- Binaries compiled with Nuitka have embedded license + public key
- Bootstrap license for API uses self-signed key pair
- SDK/CLI licenses generated via QuantumLock API (dogfooding)
- RSA-4096 signatures prevent tampering
Environment Variables
| Variable | Default | Description |
|---|---|---|
QUANTUMLOCK_DATABASE_URL |
sqlite:///quantumlock.db |
Database connection |
QUANTUMLOCK_SECRET_KEY |
(required) | JWT signing key |
QUANTUMLOCK_REDIS_URL |
redis://localhost:6379 |
Redis for server |
QUANTUMLOCK_DEBUG |
false |
Enable debug mode |
License
Proprietary Software - Copyright © 2025 SoftQuantus innovative OÜ
This software is proprietary and confidential. Use of this software is governed by the End User License Agreement (EULA) and Terms of Service.
Legal Documents
| Document | Link |
|---|---|
| EULA | docs/legal/EULA.md |
| Terms of Service | docs/legal/TERMS_OF_SERVICE.md |
| Privacy Policy | docs/legal/PRIVACY_POLICY.md |
| License | LICENSE |
Company Information
SoftQuantus innovative OÜ
- Registry Code: 17048927
- VAT: EE102767458
- Address: Veskiposti tn 2-1002, Tallinn, 10138, Estonia
Contact
| Purpose | Contact |
|---|---|
| Website | https://softquantus.com |
| Portal | https://platform.softquantus.com |
| Support | support@softquantus.com |
| Legal | legal@softquantus.com |
| Phone | +33 628315815 |
QuantumLock™ is a trademark of SoftQuantus innovative OÜ.
Metadata
Release files for quantumlock 2.1.7
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| quantumlock-2.1.7.tar.gz | 88.7 kB | Without provenance | Details for quantumlock-2.1.7.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| quantumlock-2.1.7-py3-none-any.whl | Python 3 | none | any | Details for quantumlock-2.1.7-py3-none-any.whl |
Total release size: 347.6 kB
Release files / quantumlock-2.1.7.tar.gz
| Download URL | quantumlock-2.1.7.tar.gz |
|---|---|
| Size | 88.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
039bd2321a6edd64016c7a0ff6ee2ce2442a7b22f4cee74acffedc1af4a065d5
|
|
BLAKE2b-256 checksum How to use checksums |
62178a3dcb46a920be9961b4f89d5149a02157eda50699509541f2cef0c821e0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.11.16
|
Release files / quantumlock-2.1.7-py3-none-any.whl
| Download URL | quantumlock-2.1.7-py3-none-any.whl |
|---|---|
| Size | 258.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d777d026c2f22c07cb5cf5d33bc58bbcdcf752b6c66781f29a42df4bacaf73a0
|
|
BLAKE2b-256 checksum How to use checksums |
12e2b0f2f8079070eca39a2c3a6ef90f5e90aaaac2fdc8f754986db42d179909
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.11.16
|
Security for quantumlock 2.1.7
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.