Skip to content

RQM Documentation

Status: Active development · Production-ready architecture

Write once. Run on any quantum backend.

RQM is a compiler-first quantum software platform that separates mathematical representation, compilation, and execution across multiple quantum backends.

It provides a backend-agnostic workflow where the same program can be compiled and executed on different runtimes such as Qiskit and Amazon Braket.

Architecture Overview

RQM is structured as a layered pipeline from canonical math to backend execution:

RQM architecture: rqm-core feeds into rqm-compiler, which feeds into rqm-qiskit and rqm-braket

Layer Repository Responsibility
Math rqm-core Canonical representations: quaternions, spinors, Bloch vectors, SU(2)
Compiler rqm-compiler Instruction generation, gate normalization, and IR lowering
Execution rqm-qiskit Qiskit circuit execution backend
Execution rqm-braket AWS Braket execution backend

The math layer has no backend dependency. The compiler layer transforms programs into a normalized instruction set. Execution backends consume that normalized form — they do not reimplement math or compiler logic.

Start Here

If you are new to the platform, follow this path:

  1. Quickstart — install and run your first program in minutes.
  2. Understand the ecosystem — see how each layer connects.
  3. Explore the concepts — understand compiler-first design and backend abstraction.
  4. Browse the API guides — reference the key modules and functions.

What is RQM?

RQM is a compiler-first quantum software platform. It separates three concerns that are often conflated in quantum frameworks:

  • Mathematical representation — handled by rqm-core, which defines canonical quaternion, spinor, and SU(2) structures with no backend dependency.
  • Compilation — handled by rqm-compiler, which transforms those structures into a normalized instruction set that any backend can consume.
  • Execution — handled by rqm-qiskit and rqm-braket, which map the compiled instructions onto their respective runtimes.

This separation means the same program can run on Qiskit or Amazon Braket without modification. Swapping backends is a one-line change.

New to the platform?

Start with Quickstart for a working example, then read Concepts to understand the architecture.

🌐 Website: https://rqmtechnologies.com