Skip to main content
Introducing The Quantum Infrastructure Cloud Learn more

QuantumLock

BYOC & KMS

Keep your private keys in your own cloud or hardware security module. QuantumLock orchestrates cryptographic operations without ever accessing your key material.

  • Keys never leave your boundary
  • FIPS 140-2 / 140-3 HSM support
  • Air-gapped HSM mode available

Opening film: Jakub Bukowski on Pexels (Pexels License), cropped and graded. It is not a customer key ceremony or an HSM.

Use case

A signature made without the key leaving your boundary

The request goes in, the result comes out. The private key stays where you put it.

Request lines arriving at a glass enclosure from outside
Illustration of the request path, not a recording of a deployment.
  1. It calls the QuantumLock SDK or API to request a signature or a key operation.

Two dark glass slabs joined by a green link, the right-hand one holding a point of light

Separation of policy from custody

QuantumLock decides which algorithm to use and when to sign. Your KMS or HSM stores the keys and executes the cryptographic operations.

kms_provider_registry.py
KMSProviderRegistry
  .select(
    plan="enterprise",
    deployment="byoc",
    provider="azure-kv",
    hsn=true
  )

// Policy: QuantumLock decides what to do
// Custody: Your KMS holds the keys
// QuantumLock NEVER sees the private key
  1. 01

    Your Application

    Calls QuantumLock SDK or API to request signatures, encryption, or key operations.
  2. 02

    QuantumLock (Policy)

    Decides algorithm, key ID, signing parameters, and lifecycle rules. Routes operations to your KMS.
  3. 03

    Your KMS (Custody)

    Stores private keys. Executes cryptographic operations. Keys never leave your secure boundary.
Four pale glass slabs in a row, each with green circuit traces

Supported Providers

Four ways to own your keys

Each provider integrates through its native SDK. You control the cloud account, IAM, billing, and key material.

AWS KMS

Use your own AWS KMS keys. QuantumLock orchestrates cryptographic operations via AWS SDK. Supports AWS CloudHSM for hardware-backed keys.

  • Symmetric and asymmetric keys
  • Multi-region key support
  • Automatic key rotation
  • AWS CloudHSM integration

Azure Key Vault

Keep keys in your Azure Key Vault or Azure Managed HSM. QuantumLock communicates via Azure SDK with managed identity authentication.

  • Azure Key Vault Standard/Premium
  • Azure Managed HSM (FIPS 140-2 Level 3)
  • Soft-delete and purge protection
  • RBAC via Azure AD

GCP Cloud KMS

Your keys, your Google Cloud project. QuantumLock integrates via GCP Cloud KMS API with service account authentication.

  • Software and hardware (Cloud HSM) key protection
  • Global, regional, and regional-level key rings
  • Automatic and on-demand key rotation
  • IAM-based access control

PKCS#11 HSM

Connect your hardware security module via standard PKCS#11 (RFC 7512). Keys are generated and used inside the HSM and never leave the device.

  • Thales Luna / ProtectServer
  • Entrust nShield
  • Utimaco CryptoServer
  • YubiHSM 2
Two rows of server racks with lit status lines inside a faint green glass boundary

Sovereign Cloud

Deploy in European sovereign infrastructure

For organizations that require data residency, regulatory compliance, or sovereign cloud mandates.

  • OVHcloudFrance / Europe
  • ScalewayFrance / Europe
  • Outscale (SecNumCloud)France
  • T-Systems / Open Telekom CloudGermany
  • IONOS CloudGermany / Europe
  • ElastxSweden
A glass enclosure holding a lit core, with the one line leading out of it cut short

Air-Gapped Mode

Zero network. Maximum security.

For defense, national security, and critical infrastructure deployments. QuantumLock runs fully offline with keys delivered as a physical package. No external API calls at any time.

  • Docker image + keys delivered as offline package
  • License validation via offline SDK with local revocation list
  • Local KMS for cryptographic operations. PKCS#11 HSM optional.
# Air-gapped deployment

Threats eliminated:

  • MITM attacks
  • API key theft
  • Cloud provider breach
  • DNS poisoning

Attack surface: none

Two pale glass layers one above the other, blue marks on the upper layer and green marks on the lower

Shared Responsibility Model

Clear separation between what SoftQuantus manages and what your organization controls.

Shared Responsibility Model
Security LayerSoftQuantusYour Organization
Policy engine (algorithms, lifecycle rules)ResponsibleNot applicable
KMS provider integration (SDK calls, routing)ResponsibleNot applicable
API and Trust Console availabilityResponsibleNot applicable
Private key materialNot applicableResponsible
HSM hardware procurement and physical securityNot applicableResponsible
Cloud account, billing, and IAMNot applicableResponsible
API key management and scope assignmentResponsibleResponsible
Audit log retentionResponsibleResponsible

Own your keys. Control your security posture.

Schedule a BYOC architecture review. Our team maps QuantumLock to your existing KMS infrastructure.

Enterprise KMS and security updates

Get BYOC integration guides, HSM compatibility updates, and security best practices.

Back to QuantumLock