QCOS QuantumOS by Softquantus
While traditional quantum development toolkits treat the quantum processor (QPU) as an isolated device, QCOS by Softquantus integrates CPUs, GPUs, and QPUs into a single unified architecture. It extends research parallel computing ecosystem to allow developers to build software that seamlessly splits workloads across classical supercomputers and quantum hardware.
Documentation
What the QCOS quantum operating system does
QCOS is the SoftQuantus operating system for quantum computers: a vendor-neutral runtime for quantum, GPU and hybrid workloads. Use it to submit circuits, route jobs to simulators or QPUs, estimate costs, retrieve evidence and expose quantum capabilities to applications and LLM agents.
Quantum OS user manual
The complete end-user manual for the quantum operating system — no quantum background assumed.
Quantum computing use cases
QAOA portfolio optimisation, Grover DNA search, Shor RSA assessment and VQE chemistry.
Platform guide
The platform.softquantus.com console: workspaces, roles, API keys, credits and billing.
Which API key do I need?
A single map of every credential across QCOS, the Platform and QuantumLock.
Compute services
One Execution Plane for quantum simulators, real QPUs, and per-minute GPU/CPU compute — prepaid, budgeted, evidence-sealed.
QCOS & QuantumLock on your compute
Hosted runtime, free local simulation, hybrid containers on purchased GPUs, and the licensed on-prem paths.
Interfaces for running quantum circuits
QCOS quick start
Run a Bell-state circuit through the API, SDK, CLI or MCP in a few minutes.
REST API
Integrate QCOS from any application using HTTPS, API keys and JSON.
Python SDK
Build applications, notebooks and pipelines with softqcos-sdk.
CLI
Operate QCOS from local terminals, CI/CD and automation scripts.
MCP Server
Let MCP-compatible AI agents call QCOS through typed tools.
QuantumLock
Licensing, key governance and cryptographic evidence for the stack.
How to run a quantum circuit on QCOS
What QCOS sends to quantum backends
Large datasets, images and genomics files stay in the classical data layer. QCOS sends compact quantum workload artifacts to providers: circuits, parameters, Hamiltonians, QUBO/Ising models, observables and shot counts.
| Layer | Typical data | QCOS role |
|---|---|---|
| Data lake | Parquet, CSV, images, VCF/FASTA, embeddings | Read features and metadata |
| Classical preprocessing | Feature vectors, kernels, optimization models | Build quantum-ready inputs |
| Quantum execution | QASM, circuits, QUBO, Hamiltonians | Route to simulator/QPU |
| Post-processing | Counts, expectation values, evidence | Return API/SDK/CLI/MCP results |