Up to 24 qubits
State-vector simulation
The CPU simulator is the default first run, with the same job flow and the same record.
Execution infrastructure
Execution is where most of the cost and most of the doubt live. So the checks come before the job and the evidence comes back with the result.
Send a job from the SDK, the CLI or MCP with an access key. The Softquantus Research Platform checks your licence and credits.
A dry run returns the estimated cost. QCOS checks the job against your plan limits and credit balance, and holds hardware runs and higher-cost jobs until you confirm the cost.
You name the backend for every job; QCOS does not pick one for you yet. Every computer is reached through Softquantus Cloud.
The result returns over TLS with a sealed evidence bundle: SHA-256 content hashes under a Merkle root, ready to check offline.
Up to 24 qubits
The CPU simulator is the default first run, with the same job flow and the same record.
Up to 10 qubits
A second simulator for smaller circuits, with the same job flow and the same record.
Local CPU executors
Experimental. Classical and quantum steps in one workflow; there is no GPU executor.
On the simulator
Stabilizer algebra, a library of codes and a BP+OSD decoder.


Toward a quantum cloud operating system
Say what the job needs. QCOS proposes a machine and shows why, and the choice stays yours.
Send a colleague one link. They confirm what ran, on what and with which seed, with no account.
Submit from the scheduler your computing centre already runs, next to your classical jobs.
Cropped and recompressed. Film: NASA Ames Research Center (public domain); Supercomputer cabinets: Oak Ridge National Laboratory (CC BY 2.0); Rack rear: Derrick Coetzee (CC0). These machines and facilities are not SoftQuantus sites or customers, and no partnership or endorsement is implied.