QCOS and QuantumLock licensing
Licensed for how you actually deploy.
One commercial platform for both products. Start with an annual licence, or take the stack into a dedicated cloud or your own facility under contract.
Deployment
One stack, three ways to run it
Developers and research teams
Cloud service
The shared service, hosted on Azure in the EU, with separated workspaces. Annual licences are bought on the Research Platform.
Regulated enterprise and public bodies
Dedicated sovereign cloud
A single-tenant environment for one organisation. Region, tenancy and access are agreed per engagement and written into the contract.
HPC centres, QPU labs and restricted networks
On-premise or air-gapped
Deployed in your facility, with offline licence bundles and offline evidence verification. The pattern is scoped with you.
QCOS use case
Match each workload to the right target
A research group starts on the simulators and moves up as the circuit grows. QCOS keeps the same job flow and the same record from one target to the next.
- CPU state-vector simulation up to 24 qubits
- CPU density-matrix simulation up to 10 qubits
- Hardware by kind, through Softquantus Cloud
Best fit against published limits
- Rank 1Up to 24 qubitsSimulatorCPU state-vector
- Rank 2By deviceThrough Softquantus CloudTrapped-ion
- Rank 3By deviceThrough Softquantus CloudSuperconducting
- Rank 4By deviceThrough Softquantus CloudNeutral-atom
- Rank 5Over the 10-qubit limitSimulatorCPU density-matrix
QCOS use case
Fit into the tools your team already uses
Notebook, terminal, agent or your own platform: each one reaches the same runtime, under the same licence and controls.
SDK
Python SDK
Submit a job, wait for it, and read back the counts and the sealed evidence bundle.
from softqcos_sdk import QCOSClient
qcos = QCOSClient(api_key="your-api-key")
backends = qcos.backends.list()
artifacts = qcos.jobs.artifacts(job_id)Recomputing the seal
- Sealed with
- SHA-256 Merkle root
- Signature
- None. Evidence is sealed, not signed
- Recomputed
- In this browser, just now
QuantumLock and QCOS Ledger use case
Hand over proof they can check themselves
QCOS seals the record of each run, so anyone can recompute it without trusting us. QuantumLock signs what you ship and holds the licences. Try it: change one count and verify again.
- Evidence recomputed offline with softquantus-verify
- ML-DSA-65 signatures on software, firmware and licences
- Keys held in your cloud KMS or PKCS#11 HSM
Commercial use cases
What organisations license it for
QuantumLock
Sign what you ship
Sign software, firmware and licences with ML-DSA, using the KMS or HSM you already run.
QuantumLock
Enforce licences offline
Validate licences on machines that never reach the internet, through offline bundles.
QCOS Ledger
Answer the auditor
Give a funder or a reviewer a record of each run that they can recompute themselves.
QCOS
Build on one interface
Hardware vendors and integrators work against one conformance programme instead of many.
Licensing guide
How each product is licensed
Every licence has a name, a metric and a term. Direct licences are bought on the Research Platform, and everything else starts with a proposal.
| Licence | What it covers | Metric | Term | Where |
|---|---|---|---|---|
| QCOS License | API, SDK, CLI and MCP | 5 seats | Annual | Research Platform |
| QCOS + QuantumLock Bundle | QCOS License with QuantumLock Starter | QCOS 5 seats. QuantumLock 25 seats, 1 protected product | Annual | Research Platform |
| QuantumLock Developer | RSA-4096 licence validation and API access | 1 protected product | Annual | Research Platform |
| QuantumLock Starter | RSA-4096 licence validation, full API, SDK and CLI | 25 seats, 1 protected product | Annual | Research Platform |
| QuantumLock Enterprise | ML-DSA signing, key custody in your KMS or HSM, on-premise and air-gapped use, custom policies | Seats and protected products set in the contract | Contract | By proposal |
| QCOS, dedicated or on-premise | QCOS in a single-tenant environment or in your facility | Set in the contract, from seats and scope | Contract | By proposal |
Programmes
Agreements for larger commitments
Multi-year commitment
By agreementA longer term for organisations planning several years ahead.
Volume licensing
By agreementOne agreement across several clusters, sites or tenants.
Research institutions
By agreementTerms for universities and national laboratories.
HPC centres
By agreementTerms for shared facilities that serve many research groups.
OEM and QCOS Inside
By agreementThe QuantumLock SDK, integration guidelines and a QCOS integration review for vendors that embed the stack.
Before you sign
What we do not claim
- We hold no SOC 2, ISO 27001, FIPS 140-3 or Common Criteria certification.
- QuantumLock has had no third-party penetration test.
- ML-DSA-65 runs through liboqs, and the implementation is not CAVP-validated.
- QCOS evidence bundles are sealed under a SHA-256 Merkle root. They are not signed.
- There is no published SLA. Any service level is a contract term.
- We answer security questionnaires during a pilot, and a DPA is available on request.
Questions
Licensing questions, answered
Do I need QCOS to use QuantumLock?
No. They are separate products with separate licences, and the Bundle puts QCOS License and QuantumLock Starter together. A QCOS licence does not grant QuantumLock rights.
Why are there no prices on this page?
Enterprise terms depend on deployment and scope, so we set them in a proposal. Licences sold directly show their current terms on the Research Platform.
Is compute included in a licence?
No. A licence covers the software. Compute is reached through Softquantus Cloud and measured separately. The Research Platform handles licences, credits and invoices, so there is no second bill.
Can it run on an air-gapped network?
That is the on-premise deployment. It uses offline licence bundles and offline evidence verification with softquantus-verify, and the pattern is agreed per engagement.
Does the stack make us NIS2, DORA or AI Act compliant?
No product can do that for you. Conformity is your assessment. The stack contributes records and controls to it, and the brief from the configurator lists them.
How do we start?
Run the configurator and send the brief to solutions engineering. Most evaluations begin on the simulators, followed by a scoped pilot and then a contract.
See how it fits
Answer three questions and leave with an architecture brief for your team.