Skip to main content
Introducing The Quantum Infrastructure Cloud Learn more

Quantum systems and integration

Quantum computers are many. The path to them is one.

QCOS is software and provides no compute of its own. Every computer, from a CPU simulator to a quantum processor, is reached through Softquantus Cloud.

  • IonQ
  • Quantinuum
  • Rigetti
  • LUMI

Logos belong to their owners and identify the hardware. Apart from our partner IonQ, they imply no partnership, endorsement or commercial agreement.

How the parts fit together.

  1. Your code

    SDK, CLI, MCP or REST

  2. QCOS

    Checks the job, keeps the record

  3. Softquantus Cloud

    Where every computer is reached

One path

Your code talks to QCOS. QCOS talks to Softquantus Cloud. No vendor key sits in your code or in QCOS.

Machines by kind

through Softquantus Cloud

  • CPU state-vectorSoftQuantus simulator
  • Trapped-ionQuantum computer
  • SuperconductingQuantum computer
  • Neutral-atomQuantum computer

Every kind of machine

Simulators, trapped ions, superconducting circuits and neutral atoms, named by kind.

Render of a superconducting quantum chip against a dark prismatic background.

qcos-driver-cert

Eleven published tests against your driver.

SchemaSemanticExecutionLifecycle

A public bar for drivers

The tests are published, so a hardware team can see where it stands before it ever talks to us.

Concept render of a 2U rack unit whose front panel reads NIO-Q.

Concept render. Planned for 2027.

Our own instrument

NIO-Q is a 19-inch, 2U instrument for controlling and measuring quantum devices, independent of the qubit technology behind it. Planned for 2027.

1 / 4

For hardware teams

How a machine connects.

The tooling is qcos-driver-sdk and qcos-driver-cert.

Read the full path
  1. 01

    Implement one class

    A vendor implements a single QPUDriver class with two mandatory methods. A reference simulator driver shows the shape.

  2. 02

    Run eleven tests

    qcos-driver-cert runs the published ACOS-ISA v1.0 tests on your own workstation or CI, across schema, semantics, execution and lifecycle.

  3. 03

    Keep the report

    The result is a local, self-hashed certificate. Our limits are on the page: no backends are listed in the registry yet, and signed certificates are not issued.

Cropped and recompressed. Film: IBM Research (CC BY 4.0); Chip render: OJB Quantum (CC BY 4.0). These machines and facilities are not SoftQuantus sites or customers, and no partnership or endorsement is implied.