Marqov SDK
Orchestration engine for hybrid quantum-classical workflows.
Run a Bell state immediately — no credentials, no infrastructure:
import asyncio
from marqov.circuits import Circuit
from marqov.executors import LocalExecutor
async def main():
result = await LocalExecutor().execute(
Circuit().h(0).cnot(0, 1), shots=1000
)
print(result.counts) # {'00': ~500, '11': ~500}
asyncio.run(main())
Scale to parallel workflows across any backend:
from marqov import task, workflow, bell_state
from marqov.executors import LocalExecutor
@task
async def measure(shots):
result = await LocalExecutor().execute(bell_state(), shots=shots)
return result.counts
@workflow
def multi_shot_study(shot_counts):
return [measure(n) for n in shot_counts] # all run in parallel
dispatch = multi_shot_study([100, 500, 1000, 5000])
# dispatch.run(client) — needs a Temporal worker
Independent tasks execute in parallel automatically. Marqov handles scheduling, retries, and result collection across any supported backend. Run your own Temporal worker (see marqov/workflows/) — or skip the infrastructure entirely with the hosted Marqov Platform.
Installation
pip install marqov
With framework- or backend-specific extras:
# AWS Braket
pip install "marqov[braket]"
# IBM Quantum
pip install "marqov[ibm]"
# QuTiP solvers and Marqov's result-recording helper
pip install "marqov[qutip]"
# Combine selected frameworks
pip install "marqov[qutip,qiskit]"
# Broad framework bundle
pip install "marqov[all]"
AWS Braket is an optional provider dependency. Existing Braket installations
should use marqov[braket] (or marqov[all]) when upgrading. Core workflows,
LocalExecutor and Circuit.simulate() do not require it. MarqovDevice with
local or marqov-sim uses Braket's local simulator and needs the extra, as do
Braket circuit conversions. Hosted compiler/task environments can pin
their serialization version without inheriting Braket's separate job serializer
constraint.
See the QuTiP guide for a copy-and-run simulation, recorded observables, seed replay and saved-state handling. In a source checkout, run:
python examples/qutip_decay.py
The example prints JSON and runs locally without an account. Installing the wheel does not install the examples directory or enable managed execution.
For local development:
git clone https://github.com/marqov-dev/marqov-sdk
cd marqov-sdk
pip install -e ".[all,dev]"
pytest tests/ -v
Cloud Executors
Swap in a cloud backend when you're ready to run on hardware — on your own provider accounts, no Marqov account needed:
import asyncio
from marqov.circuits import Circuit
from marqov.executors import ExecutorFactory
async def main():
circuit = Circuit().h(0).cnot(0, 1)
executor = ExecutorFactory.create_executor("sv1", {
"provider": "AWS Braket",
"device_arn": "arn:aws:braket:::device/quantum-simulator/amazon/sv1",
"s3_bucket": "my-bucket",
"s3_prefix": "jobs",
})
result = await executor.execute(circuit, shots=1000)
print(result.counts)
asyncio.run(main())
Or run directly on IonQ hardware via the native REST API (no AWS account needed):
executor = ExecutorFactory.create_executor("qpu.aria-1", {
"provider": "IonQ Direct",
"api_key": "your-ionq-api-key", # or set IONQ_API_KEY
})
result = await executor.execute(circuit, shots=1000)
Or run on Rigetti QPUs (or the local QVM, no cloud account needed) via Rigetti QCS:
executor = ExecutorFactory.create_executor("2q-qvm", {
"provider": "Rigetti QCS",
})
result = await executor.execute(circuit, shots=1000)
Supported Backends
| Backend | Status |
|---|---|
| Local (QuantumFlow simulator) | Available |
| AWS Braket | Available |
| IBM Quantum | Available |
| Azure Quantum | Available |
| IonQ Direct | Available |
| Rigetti QCS | Available |
| Quantinuum | Available |
| Quantum Brilliance | Available — requires qristal installed separately (not on PyPI, no marqov[...] extra); build from source or use the Docker image: https://qristal.readthedocs.io/ |
| CUDA-Q | Available — not in [all] (GPU-heavy); install separately with pip install "marqov[cudaq]" |
Qilimanjaro (qilisdk local simulators — digital execute() and analog execute_analog()) |
Available — not on PyPI as a marqov[...] extra (like Quantum Brilliance): qilisdk's numpy floor is incompatible with marqov's own numpy ceiling outside a narrow macOS overlap window. Install separately: pip install qilisdk. |
| CESGA CUNQA (distributed-QC emulator, Slurm-based) | Available — not on PyPI at all (no wheel; build from source, see CESGA-Quantum-Spain/cunqa) and not a marqov[...] extra: CUNQA's exact qiskit==1.2.4 pin would downgrade the whole project's lockfile if included in [project.optional-dependencies], same class of problem qilisdk had. Install qiskit==1.2.4 separately in the environment where CUNQA is built. |
Circuit Interop
Circuit is a backend-agnostic abstraction that converts to any supported framework's native format:
from marqov.circuits import Circuit
circuit = Circuit().h(0).cnot(0, 1)
circuit.to_qiskit() # qiskit.QuantumCircuit
circuit.to_braket() # braket.circuits.Circuit
circuit.to_cirq() # cirq.Circuit
circuit.to_pyquil() # pyquil.Program (requires pip install marqov[pyquil])
Import from other formats:
circuit = Circuit.from_qiskit(qiskit_circuit)
circuit = Circuit.from_cirq(cirq_circuit)
circuit = Circuit.from_pennylane(tape)
circuit = Circuit.from_pyquil(pyquil_program) # requires pip install marqov[pyquil]
Using the hosted platform (marqov.platform)
The SDK runs fully standalone — everything above needs no Marqov account.
If you want managed backend credentials, persistent job history, execution traces, and spend controls without running your own infrastructure, the Marqov Platform is an opt-in value-add.
marqov.platform is an optional import — loading marqov never loads the
platform client. It is only activated when you import it explicitly.
Live-server caveat: The examples below are not yet verified against a live server — live verification is pending our staging environment.
v1.0 scope: v1.0 supports free backends (e.g.
dwave-sim). Paid backends andCircuitsubmission are coming in a future update.
Quickstart
1. Set your API key (get one from the Marqov Platform dashboard):
export MARQOV_PLATFORM_KEY="marqey_live_your_key_here"
2. Submit a script and poll for results:
from marqov.platform import MarqovClient
# Key is read from MARQOV_PLATFORM_KEY automatically
client = MarqovClient()
script = """
import asyncio
from marqov import task
@task
async def bell(shots):
from marqov.circuits import Circuit
from marqov.executors import LocalExecutor
result = await LocalExecutor().execute(
Circuit().h(0).cnot(0, 1), shots=shots
)
return result.counts
# An async @task called outside a @workflow isn't awaited automatically
# (see marqov/workflows/decorators.py for details) — drive it with
# asyncio.run() rather than calling bell(1000) bare.
asyncio.run(bell(1000))
"""
job = client.submit(script, backend="dwave-sim", framework="marqov", shots=1000)
print("Job ID:", job.id)
# Block until complete (up to 5 minutes by default)
result = job.result(timeout=300.0)
print(result.counts) # e.g. {'00': 507, '11': 493}
print(result.probabilities) # e.g. {'00': 0.507, '11': 0.493}
3. Check available backends:
for b in client.backends():
print(b.slug, b.name, "available:", b.is_available)
4. Reconnect to a job from a previous session:
job = client.job("550e8400-e29b-41d4-a716-446655440000")
result = job.result(timeout=60.0)
Error handling
All platform errors inherit from MarqovPlatformError:
from marqov.platform import AuthenticationError, JobFailed, RateLimited
try:
job = client.submit(script, backend="dwave-sim", framework="marqov")
result = job.result(timeout=120.0)
except AuthenticationError:
print("Check your MARQOV_PLATFORM_KEY")
except JobFailed as e:
print("Job failed:", e.message)
except RateLimited as e:
print(f"Rate limited — retry after {e.retry_after}s")
except TimeoutError:
print("Timed out — job is still running server-side")
For the full error taxonomy and retry guidance see
docs/platform-client/error-handling.md.
Platform documentation
Contributing
See CONTRIBUTING.md for the executor interface spec, canonical gate set, factory registration steps, and local QVM setup for Rigetti development.
The bounty issues that were open through unitaryHACK 2026 — have been claimed, but follow the issues page as we will be looking at ongoing and rolling issue bounties to support and encourage community participation.
Authors
This project was created by David Ryan (@ddri), with contributions from the community.
License
Release files for marqov 0.7.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| marqov-0.7.0.tar.gz | 460.0 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| marqov-0.7.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 598.6 kB
Release files / marqov-0.7.0.tar.gz
| Download URL | marqov-0.7.0.tar.gz |
|---|---|
| Size | 460.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0a7ad22df0bad8aeb2b1c7c87bb0102aab1ac04b762272c507798790355f6e74
|
|
BLAKE2b-256 checksum How to use checksums |
15a73ee5c8c95ee211833ba607302f5b0ce0bb3179b87e0f577ce0b254709d4a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 12, 2026.
Transparency logRelease files / marqov-0.7.0-py3-none-any.whl
| Download URL | marqov-0.7.0-py3-none-any.whl |
|---|---|
| Size | 138.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8843a6d43201ef219aba06ca35d2ee02326a83ff216cec618aedd50b1c8e24c7
|
|
BLAKE2b-256 checksum How to use checksums |
4442a8a22557e53270f41442645e009dd70bbc43853f831e8522408c1fb16a5f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 12, 2026.
Transparency log