Deployment infrastructure

Put a quantum job inside the software you already run.

No new control room and no second queue. A QCOS job is a call from your code or a line in your script, with access, cost and evidence handled the same way each time.

Talk about your deployment For HPC centres

Access you control

Jobs are sent with an access key. The Softquantus Research Platform checks your licence and credits, and every key sits in your workspace.

Cost you see first

A dry run returns the estimated cost. QCOS checks plan limits and credit balance, and holds hardware runs and higher-cost jobs until you confirm.

A record you can check

Results come back over TLS with a sealed evidence bundle: SHA-256 content hashes under a Merkle root, ready to check offline.

In practice

The controls, as you will meet them.

Before the job runs

Estimated costReturned by the dry run
Plan limitsChecked before the job runs
Credit balanceChecked before the job runs
Cost confirmationHardware and higher-cost jobs

Four checks before a job runs

Estimate, plan limits, credit balance and, where it is needed, your confirmation of the cost.

Softquantus Research Platform

Workspaces
API keys
Usage
Credits

Keys and usage in one workspace

The Research Platform holds workspaces, access keys, usage and the credit ledger.

A row of supercomputer cabinets with cooling lines overhead.

Batch script

#!/bin/bash
#SBATCH --job-name=ghz-check
#SBATCH --time=00:10:00

softqcos jobs submit --circuit circuit.qasm \
    --backend simulator --shots 1000
softqcos jobs evidence <job-id> \
    --output evidence.json

Next to your classical jobs

The softqcos CLI runs from an ordinary SLURM, PBS Pro or LSF script. No daemon on the login node, no second queue.

Circuit hash

SHA-256

Backend identity

Named for the job

Measurement results

With parameters and seeds

A record that leaves with the result

Five items per job, sealed under one Merkle root. The softquantus-verify tool checks it offline, with no account.

1 / 4

Where QCOS lives

Three ways to deploy it.

Cloud (SaaS)

Managed by SoftQuantus on Azure Container Apps in West Europe, with automatic updates. You bring code and an access key.

Hybrid / VPC

Your infrastructure, our control plane. Contact us to scope it.

Air-gapped / sovereign

Offline operation with QuantumLock licence tokens, for sites that cannot call out.

Into the workflows you already have.

A Python service

Call the SDK from the code you already deploy, and keep the evidence bundle with your own results.

A nightly script

Call the CLI from cron or CI. Status, results and evidence are all commands.

A scheduler queue

The scheduler provides the key in the job environment, and the job is one more line in the batch script.

An assistant

Connect softqcos-mcp, and your assistant works through the same checks as everything else.

Keep reading

Development infrastructure

Write and check a job from the SDK, the CLI, MCP or REST.

Learn more

Execution infrastructure

Follow a job from your code to a sealed result.

Learn more

Cropped and recompressed. Film: NASA Ames Research Center (public domain); Supercomputer cabinets: Oak Ridge National Laboratory (CC BY 2.0); Colour field derived from: NIST (public domain). These machines and facilities are not SoftQuantus sites or customers, and no partnership or endorsement is implied.