Skip to main content
Introducing The Quantum Infrastructure Cloud Learn more

Technology

A stack with one job per layer.

Between a person’s script and a quantum computer, SoftQuantus keeps execution, trust, compute and billing apart, so each can be checked and each can change on its own.

The stack

Five layers, top to bottom.

  1. 01

    Your work

    Scripts, notebooks, schedulers, agents

    Decides what to run and why.

  2. 02

    Quantum operating layer

    QCOS: API, SDK, CLI and MCP server

    Prepares the work, controls the scientific execution and seals the record. It is not a computer.

  3. 03

    Keys, licences and signatures, and the evidence that stays with each result.

  4. 04

    Compute

    Softquantus Cloud

    Being built as the one service through which simulators, GPUs and quantum computers are reached.

  5. 05

    Machines

    Simulators and quantum computers

    Do the work. CPU state-vector simulation today; hardware when it is switched on.

Why it is built this way

Three bottlenecks.

  1. 01

    Fragmented machines

    Each computer has its own interfaces and limits. One operating layer keeps the job description stable while the machine underneath changes.

  2. 02

    Unaccountable results

    A number without its circuit, backend and seed cannot be reviewed. Every run through QCOS can carry a sealed record of those facts.

  3. 03

    Scattered credentials and bills

    Provider accounts belong in one compute service and billing in one commercial platform, instead of spreading through every tool and team.

What it does today

Capabilities you can use and inspect.

One interface

REST API, Python SDK, CLI and MCP server over the same operations.

Simulation

CPU state-vector simulation up to 24 qubits through that interface.

Evidence

A record per run, sealed under a SHA-256 Merkle root.

Error correction

Stabilizer algebra, a code library and a BP+OSD decoder, exercised on the simulator.

Post-quantum signing

ML-DSA-65 signing through liboqs, not CAVP-validated, in QuantumLock.

Conformance

A published test specification for hardware vendors, ACOS-ISA v1.0.

Abstract contour lines on a deep green background.

Execution

Three parties, three responsibilities.

A job crosses three services, and none of them does another’s work.

The Platform charges
Licences, credits and invoices for every product, in one place.
QCOS controls the science
Checks that the work may run, and prepares and tracks it.
Cloud controls the hardware
Runs the compute and reports what was used.