Skip to main content
All SolutionsSovereign & Air-gapped

Offline License Enforcement & Sovereign Deployment

Deployment patterns for restricted and sovereign environments, with QuantumLock offline licence-token validation. Available on request, scoped per engagement.

Why Organizations Need Sovereign Quantum

National Security

Sensitive quantum algorithms may not be allowed to transit public networks or foreign infrastructure.

Defense / Intelligence

Data Sovereignty

Regulatory requirements mandate data processing within national borders.

EU GDPR / DORA

Air-gapped Operations

Critical infrastructure requires complete network isolation.

Energy / Finance

Sovereign Deployment Package

Building blocks for offline and restricted-network quantum operations, scoped per engagement.

Offline Licensing

QuantumLock validation without internet

Hardware Binding

Licences bound to specific machines

Local Evidence

Sealed evidence bundles and audit logs inside your environment, on request

Post-Quantum Signatures

ML-DSA via liboqs for licence tokens (not FIPS-validated)

QuantumLock: Offline Licence Validation

QuantumLock verifies ML-DSA signatures on licence tokens (via liboqs, not CAVP-validated) to enforce software licensing without any network connectivity. Designed for air-gapped and sovereign deployment patterns.

  • Offline Validation — License checks without internet
  • Hardware Binding — Licenses tied to specific machines
  • Tamper Detection — Licence-token signature check (ML-DSA)
  • Post-Quantum Signatures — ML-DSA licence tokens via liboqs (not CAVP-validated)
  • Periodic Sync — Optional updates when connectivity available
Explore QuantumLock
$ qlock validate --offline

QuantumLock Offline Validation
==============================

License File: /etc/softqcos/license.qlock
Hardware ID:  HW-7f3a2b1c4d5e6f70

Checking licence token... (illustrative sample - not a real execution record)
  ✓ ML-DSA signature valid
  ✓ Hardware fingerprint match
  ✓ Expiry: 2027-01-04
  ✓ Features: enterprise, offline, hpc

┌──────────────────────────────────┐
│  License Status: VALID           │
│  Mode: Air-gapped                │
│  Network: Not required           │
└──────────────────────────────────┘

Air-gapped Deployment Architecture

Offline operation with local evidence and audit logs, scoped per engagement.

Secure Zone

  • QCOS Orchestrator
  • QuantumLock Agent
  • Local Evidence Bundles
  • Local Simulation

Air Gap

Network isolation under your control. No inbound or outbound connectivity required.

External (Optional)

  • License provisioning
  • Periodic updates

Security & Compliance Position

Cryptographic Standards

  • No FIPS-validated modules; ML-DSA runs via liboqs (not CAVP/FIPS-validated)
  • ML-DSA licence-token signatures via liboqs (not CAVP-validated)
  • ML-KEM key generation (no encapsulation or decapsulation implemented)
  • SHA-256 hashing
  • SHA-256 Merkle root seal for evidence bundles

Compliance Support

  • Evidence bundles for audit requirements
  • Local audit log retention
  • Tamper-evident licence tokens
  • Data stays inside your deployment zone

Note: Sovereign deployments require a custom security review. SoftQuantus holds no certifications today (no FedRAMP, no FIPS validation, no Common Criteria). Contact our solutions team for government and defense inquiries.

Sovereign Use Cases

Defense & Intelligence

Isolated quantum algorithm development with tamper-evident audit trails (90-day retention).

Air-gap mandatoryCustom security reviewOffline operation

Critical Infrastructure

Simulation for energy systems in offline environments.

Offline operationCustom security review

Financial Services

Quantum risk modeling in regulated environments with data sovereignty requirements.

EU data residencyAudit retentionCustom security review

National Labs

Research computing with reproducibility requirements and funding body audit needs.

ReproducibilityEvidence bundlesAudit retention

Discuss Your Sovereign Requirements

Tell us your isolation and licensing requirements and we will scope a deployment pattern.