Skip to main content
Introducing The Quantum Infrastructure Cloud Learn more

QCOS™ — Quantum Computer Operating System

An operating system for quantum computers

One runtime to run, govern and record your quantum jobs.

A real QCOS 3.14.0 run: a 5-qubit GHZ circuit, 2,000 shots, CPU state-vector simulator, from a terminal on an Ubuntu x86-64 virtual machine. The commands and output are as recorded, with waits and typing shortened. The right-hand panel plots that same output. The evidence is sealed, not signed.
Rendered illustration: a dark data hall of server racks with a dilution refrigerator at the end of the aisle.

QCOS is the runtime layer between quantum backends and your application.

Run CPU state-vector simulations (≤ 24 qubits) through QCOS and get a SHA-256 Merkle-sealed evidence bundle for every run. Proprietary architecture; invention disclosure in process.

Unified runtime

From your code to a sealed result, on one runtime.

  • Send a job from the SDK, the CLI or MCP with an access key. The Softquantus Research Platform checks your licence and credits.

Quantum · QCOS engine

The QCOS engine behind every run

QCOS compiles, routes and records quantum workloads. You reach it from the SDK, the CLI or MCP with an access key; the platform checks your licence and credits.

Create an access keySDKs & APIs
Available

QCOS Assurance

What QCOS checks before and after a run, and how to read it.

Open QCOS Assurance
Available

Licences

Your QCOS licence and what it covers. Licences are sold and checked on this platform only.

Open Licenses
Softquantus Research Platform interface with illustrative sample data, not a real execution record.

One runtime designed for several backends

The Hardware Abstraction Layer gives quantum backends one interface, the way device drivers do in a traditional OS. You write to that interface and name the backend for each job.

The CPU state-vector simulator (≤ 24 qubits) runs through QCOS. Trapped-ion, superconducting and neutral-atom backends are reached through Softquantus Cloud.

Quantum computers

  • IonQ
  • Quantinuum
  • Rigetti

Reached through Softquantus Cloud.

Supercomputers

  • EuroHPC Joint Undertaking
  • LUMI

EuroHPC AI Factory Large Scale allocation EHPC-AIF-2025LS13-019: 180,000 GPU-hours on LUMI-G. QCOS does not run there.

Logos belong to their owners and identify the hardware. Apart from our partner IonQ, they imply no partnership, endorsement or commercial agreement.

Evidence record

Sealed, unsigned

Four checks, by name

hashes_valid

Content hashes match the record (needs nothing but the record)

true

signature_valid

QuantumLock signature checks out over SHA-256(bundle_hash)

not computed

key_valid

Signing key is in the trust bundle, valid at signed_at, not revoked

not computed

evidence_valid

Record is internally consistent and matches its claimed level

true
Same four booleans, no network, no trust in QCOS or in this page.

softqcos evidence verify --offline record.json --trust-bundle trust-bundle.json

Download record JSON
Softquantus Research Platform interface with illustrative sample data, not a real execution record.

Every run leaves evidence you can check yourself.

Each execution produces a sealed evidence bundle with the circuit hash, timestamps, backend metadata, results and costs. QCOS seals it under a SHA-256 Merkle root, and results travel over TLS.

Verification runs offline and reports four named checks. A QuantumLock signature is a separate step: a record without one says so, and its signature checks read “not computed”.

Published sealed runs lists the runs workspaces chose to publish, with the record of each.

OS Architecture

Six subsystems that make QCOS a true operating system

Like a traditional OS has process scheduler, memory manager, and device drivers, QCOS provides the fundamental abstractions for quantum computing.

Autopilot — Closed-Loop Optimisation

Proprietary architecture; invention disclosure in process

A closed-loop optimiser that tunes circuit parameters against measured fidelity. No benchmark figure is published for it today: its earlier GHZ-6 result was withdrawn in August 2026.

  • Closed-loop tuning
  • CPU state-vector simulator
  • Sealed evidence bundle

Decision Reliability Rating

Know before you execute

Before running a circuit, QCOS scores the reliability of the expected result. A proprietary multi-dimensional analysis estimates how reliable your result is likely to be before you spend a shot. Returns a 0–100 score and a GREEN / YELLOW / RED semaphore.

  • Score before execution
  • GREEN / YELLOW / RED
  • Sealed evidence bundle

Quantum Runtime

Unified execution environment

The core execution layer that manages quantum job lifecycle — from circuit submission to result retrieval. Handles queuing, scheduling, and resource allocation across all connected backends.

  • Job lifecycle management
  • Async execution
  • Result aggregation

Hardware Abstraction Layer

Vendor-neutral drivers

Like device drivers in a traditional OS, the HAL provides a unified interface to quantum backends. The CPU state-vector simulator (≤ 24 qubits) runs through QCOS; trapped-ion, superconducting and neutral-atom backends are reached through Softquantus Cloud.

  • Unified API
  • Backend discovery
  • Capability contracts

Job Control

You choose the backend

You name the backend for every job; QCOS does not pick one for you yet. A dry run returns the estimated cost first. Before a job runs, QCOS checks it against your plan limits and credit balance, and holds hardware runs and higher-cost jobs until you confirm the cost. Jobs are scoped to your workspace.

  • Cost estimate before running
  • Confirm before spending
  • Workspace-scoped jobs

Policy Engine

Governance-as-code

Define and enforce policies at the OS level. Budget limits, approval workflows, and access controls — checked before every execution.

  • Budget controls
  • RBAC enforcement
  • Approval workflows

Evidence Ledger

Sealed audit trail

Every execution produces a sealed evidence bundle — circuit hash, timestamps, backend metadata, results, costs. Bundles are sealed under a SHA-256 Merkle root and can be verified offline with softquantus-verify.

  • SHA-256 Merkle seal
  • Full provenance
  • Offline verification

Deployment Modes

Cloud, with hybrid and air-gapped on request

QCOS runs as a managed SaaS on Azure Container Apps (West Europe). Hybrid / VPC and air-gapped installations with locally verified licence tokens are available on request.

  • Managed SaaS (West Europe)
  • Hybrid and air-gapped on request
  • Locally verified licence tokens

Architecture

OS architecture for quantum

Applications → QCOS (Runtime · Scheduler · Kernel) → Execution backends

01 · User Space

Applications

  • Applications
  • Algorithms
  • AI/ML

Qiskit · Cirq · PennyLane · Custom Workflows

02 · Kernel Space

QCOS

  • Runtime
  • Scheduler
  • Policy Engine
  • Evidence Ledger

03 · Hardware Abstraction Layer

Drivers

  • CPU Simulator Driver
  • Trapped-ion Driver
  • Superconducting Driver
  • Neutral-atom Driver

04 · Execution Backends

Backends

  • CPU state-vector (≤ 24 qubits)
  • Trapped-ion
  • Superconducting
  • Neutral-atom

Cloud · Hybrid and air-gapped on request

05 · Generated at every execution

Evidence

  • Evidence Bundle — Sealed under a SHA-256 Merkle root
  • Audit Log — Tamper-evident trail

Built for infrastructure operators

Organizations that require operational control

Quantum hardware vendors

Differentiate with enterprise-ready governance. Offer customers audit trails and cost controls.

National labs & HPC centers

Integrate quantum into existing HPC governance. Unified policies, reproducible results, and sovereign deployment options.

Regulated enterprise R&D

Pharma, defense, energy, and finance. Sealed evidence bundles and audit logs to support your own regulatory reviews.

Sovereign infrastructures

Governments and critical infrastructure. Air-gapped deployment on request and offline licence validation with QuantumLock.

Scientific Foundations

Built on proven principles of quantum computing science

QCOS implements rigorous computational and physical frameworks that enable reproducible, verifiable quantum operations at scale.

Eight evidence sections recomputed offline with SHA-256. The Merkle root and the bundle digest match. Change one count, or one section hash, and the match fails. The evidence is sealed, not signed.

Standards-Based

OpenQASM 3.0
Native
Quantum Volume
Reference

Cross et al., Phys. Rev. A 100 (2019)

Post-Quantum Ready

Licence-token signatures
ML-DSA (liboqs, not CAVP-validated)
Key Generation
ML-KEM
Validation
liboqs, not CAVP-validated

ML-DSA signs QuantumLock licence tokens via liboqs. ML-KEM is key generation only.

What QCOS is — and what it's not

QCOS is not a wrapper around a single provider. It is the runtime layer your quantum jobs go through.

Four frosted glass layers stacked one above the other on a violet and green gradient.

QCOS is

  • Unified runtime across the backends you connect.

QCOS is not

  • A promise of quantum advantage

    that depends on your algorithm

  • A compiler or SDK replacement

    use Qiskit, Cirq, PennyLane

  • A proprietary runtime

    we integrate, not replace

  • A "magic optimizer"

    gains are from control, not physics tricks

  • Hardware-specific

    provider-neutral by design

SoftQuantus / QCOSNew

QEC Stack

Quantum Error Correction, built into the OS.

QEC middleware with generalized bicycle QLDPC codes, BP+OSD decoding, PBC compilation, and fault-tolerant isolation checks, validated on the QCOS CPU state-vector simulator.

Explore QEC Stack
The numbers come from a real QCOS pipeline run, simulated with no quantum hardware: a distance-3 surface code, 17 qubits, one X error injected on qubit 4. The mesh around the code and its motion are a visualisation.

Encode

codes

Repetition, Surface, GB QLDPC

[[72,12,6]] · [[144,12,12]] · [[288,12,18]]

Bivariate bicycle catalog: n and k checked, d as published.

stabilizer

Symplectic Pauli algebra (GF2)

syndrome

Automated circuit synthesis

Decode

decoder

BP+OSD syndrome decoding

code
surface, d = 3
error
X on qubit 4
z_syndrome
[1,0,0,1]
correction
qubit 4, weight 1
residual
[0,0,0,0]

Compile & check

pbc

Pauli-based computation compiler

ft_isolation

Fault-tolerant isolation checks

Ready to deploy the OS for quantum?

QCOS is an operating system for quantum workloads. One runtime designed for several backends: managed SaaS today, hybrid or air-gapped on request.

What happens next:

  1. 01

    We reply by email

  2. 02

    NDA & scoping

  3. 03

    Technical assessment

  4. 04

    Pilot proposal

Sign up for QCOS updates

Get the latest on QCOS features, releases, and quantum computing insights.