Hosted gateway
Jobs leave the centre for the hosted QCOS API in Azure West Europe. Fastest to start; the evidence record comes back with the result.

Solutions · HPC & national centres
QCOS runs from the scheduler script your users already write, and seals an evidence record for every job that stays with the centre. Built for research centres and national labs that have to reproduce what they report.

What changes for the centre
The softqcos CLI is called from an ordinary SLURM, PBS Pro or LSF script. No daemon on the login node, no second queue.
Five items per job, sealed under one SHA-256 Merkle root and written next to the job output, ready to archive with the rest of it.
Each record stays in the job directory. QCOS Bench reports verify offline with an MIT-licensed tool, no account and no network connection.
Three bottlenecks
A second portal means a second queue, a second accounting trail and users who leave the workflow they already know. QCOS is a command inside the batch script instead.
A count histogram does not say which circuit, which backend, which seed or which window produced it. The record keeps those together with the measurement results.
Records stay on your filesystem, and an air-gapped deployment with QuantumLock licensing runs simulation inside the perimeter.
Scheduler integration
The scheduler allocates, the script submits the circuit, waits for the result and writes the evidence record next to the job output. Scheduler plug-ins are planned; today the integration is the script.
#!/bin/bash
#SBATCH --job-name=ghz-check
#SBATCH --time=00:10:00
# The scheduler provides QCOS_API_KEY in the job environment.
softqcos jobs submit --circuit circuit.qasm --backend statevector_sim --shots 1000
softqcos jobs status <job-id>
softqcos jobs results <job-id>
softqcos jobs evidence <job-id> --output evidence.json
Evidence and verification
Five items per job, sealed under one SHA-256 Merkle root. The record is a file in the job directory, archived with the rest of the output. For QCOS Bench reports, softquantus-verify recomputes the hashes and reports one of four outcomes: valid, invalid, unsigned or error.
What we can show
Digital-twin validation
The classical pipeline stays where it is. QCOS adds the quantum step and the record, and the record stays with you once it exists.
Run the digital twin on the cluster as today and keep its outputs.
Submit the quantum part through QCOS. CPU state-vector simulation today; hardware through Softquantus Cloud when it is switched on.
QCOS seals the five-item evidence record for the job automatically.
Compare the quantum result against the classical reference with the seeds in the record.
Archive the record with the job output and keep it for as long as the centre keeps its results.
Deployment
Jobs leave the centre for the hosted QCOS API in Azure West Europe. Fastest to start; the evidence record comes back with the result.

The client on the centre side, execution through the hosted API, and the record kept with the job output.

Fully offline deployment with QuantumLock licensing. Simulation inside the perimeter; no outbound connection.

Before a pilot
The record
QCOS Bench
Start with one batch script
The film is an original render. Photographs, cropped and recompressed, public domain via Wikimedia Commons: Sierra, U.S. Department of Energy / LLNL (vendor badges retouched); Discover, NASA Goddard and NASA / Pat Izzo; fibre patching, USDA. These facilities are not SoftQuantus sites or customers, and no partnership or endorsement is implied.