Skip to main content
Introducing The Quantum Infrastructure Cloud Learn more
Contour lines of a smooth field, lit from one side, in deep blue

Solutions · Enterprise R&D

Quantum research your
auditor can replay.

One API over 24 qubits of simulation, a sealed evidence record for every job, and a verifier your compliance team runs offline. Built for research groups whose results have to survive a review.

  • 24

    qubits of state-vector simulation behind one API

  • 5

    items in every evidence record

  • SHA-256

    Merkle root that seals each record (RFC 9162 layout)

  • 3

    ways to verify: API, SDK offline, open-source CLI

  • 1

    deployment: Azure West Europe, database in North Europe

Evidence per job

A record your auditor can keep, without an account on our side.

Every job through QCOS leaves a five-item evidence record: circuit hash, backend identity, execution window, parameters with seeds, and the measurement results, sealed under a SHA-256 Merkle root. The record is a file your auditor can hold without an account on our side.

  • 5 items per record, one Merkle root per job
  • Circuit hash compared with the submitted job
  • One SHA-256 root over the five items
  • Timestamp checked against the execution window
A Merkle tree with the leaf hashes converging on one root

Pilot in 30 days

Scope, success criteria and a verifier in your hands before any job runs.

A pilot starts with a written scope and the checks that will count as success. The group runs its own circuits on the 24-qubit simulator through the same API the production service exposes, and keeps every record. The documentation package is written for your compliance review, not for ours.

  • Scope and success criteria agreed in writing
  • Same API, SDK and CLI as the production service
  • 2,000-shot GHZ demonstration published for comparison
  • softquantus-verify is MIT-licensed; you keep the tool after the pilot
An evidence bundle laid out as a stack of sealed records

Procurement pack

The documents security and procurement ask for, answered as they stand today.

The pack states what is in place and what is not. SoftQuantus holds no certification; SOC 2 has not been started and ISO 27001 is not held. The service runs in one Azure region with TLS 1.2+ in transit and Azure-managed encryption at rest. A DPA template is available on request.

  • Security whitepaper: architecture, access controls, retention
  • Data handling policy: processing, storage, audit trail
  • Trade controls: export compliance and dual-use considerations
  • Support terms and DPA template
Rows of sealed records in a ledger view

Where the record is made

Five stages, one record.

The capability contract says what a job may do, the policy engine checks it, execution runs it, and the evidence record is sealed before the ledger ever sees it. Nothing downstream can alter a leaf without the root changing.

  1. 01

    Capability contract

  2. 02

    Policy engine

  3. 03

    Execution

  4. 04

    Evidence record

  5. 05

    Ledger

Look under the surface

Everything here can be checked.

The record format, the public benchmark records and the decision-reproducibility product are documented in the open. Start where your reviewer will start.

Security posture

What is in place, and what is not.

ItemTodayStatus
Audit trailTamper-evident log entriesIn place
Evidence recordOne sealed record per executionIn place
Transport and storageTLS 1.2+ in transit; Azure-managed encryption at restIn place
HostingAzure West Europe, database in North Europe, no failoverIn place
GDPRBuilt to GDPR requirements; DPA template on requestIn place
SOC 2 Type IINot startedNot yet
ISO/IEC 27001Not heldNot yet

Integrations

Fits a pipeline through the API first.

ItemTodayStatus
CI/CD hooksThrough the QCOS API and the softqcos CLI; no dedicated plug-ins yetIn place
SSOPlanned; not available yetNot yet
SIEM exportPlanned; not available yetNot yet

Verify from your own shell

softquantus-verify checks QCOS Bench reports offline and reports any file that changed after sealing. The CLI is MIT-licensed and needs no network connection.

Start with the record

Bring a circuit. Leave with a record you can prove.

  • A written scope and success criteria before the first job
  • Every record stays yours; verification never needs our service
  • No hardware claim: simulation today, hardware through Softquantus Cloud when it is switched on