Skip to main content
QCOS™ — Quantum Computer Operating System

An operating system for quantum computers

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

QCOS is the runtime layer between quantum backends and your application. Run CPU state-vector simulations (≤ 24 qubits) through QCOS, bring your own provider credentials for trapped-ion, superconducting or neutral-atom backends, and get a SHA-256 Merkle-sealed evidence bundle for every run. Proprietary architecture; invention disclosure in process.

One runtime for the backends you connect

Like Linux abstracts CPUs from different vendors, QCOS abstracts quantum backends behind one API. Run on the CPU state-vector simulator (≤ 24 qubits) through QCOS, or bring your own provider credentials for other backends.

Deployment Environments

Azure (West Europe)
Hybrid / VPC
Air-gapped

Execution paths (via HAL drivers)

CPU simulator

State-vector

≤ 24 qubits

Trapped-ion

Provider backend

BYO credentials

Superconducting

Provider backend

BYO credentials

Neutral-atom

Provider backend

BYO credentials

Unified Runtime

One API for the backends you connect

Hardware Abstraction

One interface across the backends you connect

Portable Workloads

Like containers for quantum

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 (90-day retention) 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.

Sealed Evidence Bundles

SHA-256 Merkle seal, verified offline

Formal Capability Contracts

Verified backend specifications

Variational Optimization

Autopilot closed-loop VQE/QAOA

State Tomography

Fidelity & entanglement metrics

Error Mitigation

ZNE, PEC, Dynamical Decoupling

Standards-Based

OpenQASM 3.0Native
Quantum VolumeReference

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

Post-Quantum Ready

Licence-token signaturesML-DSA (liboqs, not CAVP-validated)
Key GenerationML-KEM
Validationliboqs, not CAVP-validated

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

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 tuningCPU state-vector simulatorSealed 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 executionGREEN / YELLOW / REDSealed 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 managementAsync executionResult 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) is available through QCOS; trapped-ion, superconducting and neutral-atom providers connect with your own provider credentials.

Unified APIBackend discoveryCapability 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 runningConfirm before spendingWorkspace-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 controlsRBAC enforcementApproval 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 sealFull provenanceOffline 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 requestLocally verified licence tokens

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.

QCOS is

  • Quantum operating system — unified runtime across the backends you connect
  • Hardware abstraction layer — vendor-neutral drivers for the backends you connect
  • Quantum kernel — scheduler, policies, resource management
  • Evidence system — execution records sealed under a SHA-256 Merkle root
  • Portable — cloud, with hybrid and air-gapped on request

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
Architecture

OS architecture for quantum

Applications → QCOS (Runtime · Scheduler · Kernel) → Quantum Hardware

User Space

ApplicationsAlgorithmsAI/ML

Qiskit · Cirq · PennyLane · Custom Workflows

Kernel Space

QCOS

RuntimeSchedulerPolicy EngineEvidence Ledger

Hardware Abstraction Layer

CPU Simulator DriverTrapped-ion DriverSuperconducting DriverNeutral-atom Driver

Execution Backends

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

Cloud · Hybrid and air-gapped on request

Generated at every execution

Evidence Bundle

Sealed under a SHA-256 Merkle root

Audit Log

Tamper-evident trail

Cost Ledger

Chargeback/showback ready

Deployment

Cloud today; hybrid and air-gapped on request

Cloud (SaaS)

Managed by SoftQuantus on Azure Container Apps (West Europe). Fast deployment and automatic updates.

Hybrid / VPC

Your infrastructure, our control plane. Contact us to discuss deployment options.

Air-Gapped / Sovereign

Offline operation with QuantumLock licence tokens, available on request.

QEC Stack — NEW

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

Ready to deploy the OS for quantum?

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

What happens next:

1We reply by email2NDA & scoping3Technical assessment4Pilot proposal

Sign up for QCOS updates

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