Measurement and control
for QPU teams.
The hardware-facing half of QCOS, for teams building or operating quantum processors. In early access by request with a small group of partners; hardware adapters are in development with early partners.
The layer between your OS
and your electronics.
qcos-mc/1 protocol boundary
A typed measurement-and-control protocol between the operating system and lab electronics. Instruments speak a defined contract instead of ad-hoc scripts — so the OS can drive any rack that implements it.
Calibration workflows
Rabi, Ramsey and T1/T2 sweeps as first-class workflows, not notebooks. A calibration simulator ships with the plane, so teams develop and test calibration logic before touching a fridge.
Circuit-to-pulse compiler
Compile circuits down to pulse schedules targeting OpenPulse, Quil-T and Pulser. One compilation path, three pulse-level formats — the modality decides the target, not the toolchain.
QEC Architecture Advisor
Recommends error-correction code families from your device's own metrics. Instead of picking a code from a paper, you pick one the advisor argues for from measured error rates and connectivity.
Predictive noise-aware routing
PSR places circuits using calibration data — the same routing engine that serves the Assist plane, fed directly from the calibration workflows running on your device.
Sealed evidence on every run
Every run closes with a sealed evidence bundle carrying a Merkle SHA-256 root over code, configuration and results. Tamper-evident and reproducible — built to be checked by someone who wasn't in the room.
Measure. Analyse.
Decide. Seal.
Measure
Calibration sweeps — Rabi, Ramsey, T1/T2 — run through the qcos-mc/1 boundary against your electronics, or against the calibration simulator while the rack is still a diagram.
Using a QPU and building one
are different jobs.
QCOS is the quantum operating layer under every SynapseX surface. It ships two faces of the same engine: an Assist plane for the people who run circuits, and a Control plane for the people who run the machine underneath them. Same compiler, same calibration data, same sealed evidence.
For teams who use QPUs.
Researchers and application teams who want answers from quantum computing without owning hardware: the Labs agent, free simulators, and an approval-first path to partner QPUs, which are in development.
- Research agent with its own laboratory
- Free simulators on the Free plan
- Partner QPUs in development, approved per run
- Reproducible, sealed run records
For teams who build them.
OEMs, hardware labs and HPC centers who operate the processor itself: a typed instrument boundary to the lab electronics, calibration workflows, pulse-level compilation, and an advisor layer that turns device metrics into decisions.
- qcos-mc/1 measurement-and-control boundary
- Rabi, Ramsey, T1/T2 calibration workflows
- Circuit-to-pulse compiler: OpenPulse, Quil-T, Pulser
- Sealed evidence (Merkle SHA-256) on every run
The HAL abstracts these four modalities by construction. Adapter phases are in development with early partners — not finished, and we won't say otherwise.
Put an operating system
under your processor.
QCOS Control Plane is in early access with teams building or operating quantum hardware. Tell us about your device and your electronics — we'll tell you honestly where the adapters stand.
QCOS Control Plane · early access · sales@softquantus.com