This release is a pre-release and may not be stable for production use.
Divi
Generate, parallelize, and execute quantum programs at scale.
Divi is a Python library by Qoro Quantum for building and running quantum programs at scale. It handles circuit generation, job parallelization, and cloud execution — with built-in support for variational algorithms, custom workflows, and more — so you can focus on the quantum problem, not the plumbing.
📦 Installation
pip install qoro-divi
That covers local and cloud execution, VQE, QAOA, and program ensembles.
Heavier features live behind optional extras — pennylane (PennyLane circuits,
operators, and molecules), aer (Qiskit Aer backends), qubo-decompose
(partitioned QUBO solving), chem (PySCF/OpenFermion chemistry), ai, and
jupyter — or pip install "qoro-divi[all]" for everything. See the
installation guide
for what each unlocks and what keeps working without it.
Nightly Builds
To install the latest development build (published daily from main):
pip install qoro-divi --pre
Learning Divi
For the shortest introduction, start with the
five-minute tutorial.
Algorithm guides, execution guides, and the API reference live at
divi.readthedocs.io; hands-on examples are in
the tutorials/ folder.
⚡ At-Scale Example
Split a graph into quantum-sized MaxCut problems, solve the partitions, and stitch their candidates into a global solution:
import networkx as nx
from divi.backends import MaestroSimulator
from divi.qprog import BeamSearchStrategy
from divi.qprog.optimizers import ScipyOptimizer, ScipyMethod
from divi.qprog.problems import GraphPartitioningConfig, MaxCutProblem
from divi.qprog.workflows import PartitioningProgramEnsemble
graph = nx.barbell_graph(4, 0)
problem = MaxCutProblem(
graph,
config=GraphPartitioningConfig(
max_n_nodes_per_cluster=4,
partitioning_algorithm="kernighan_lin",
),
)
backend = MaestroSimulator()
ensemble = PartitioningProgramEnsemble(
problem=problem,
n_layers=1,
backend=backend,
optimizer=ScipyOptimizer(method=ScipyMethod.COBYLA),
max_iterations=10,
seed=42,
)
ensemble.run()
cut, _ = ensemble.aggregate_results(
strategy=BeamSearchStrategy(beam_width=3, n_partition_candidates=5)
)
print(f"Cut edges: {nx.cut_size(graph, cut)}")
print(f"Circuits executed: {ensemble.total_circuit_count}")
PartitioningProgramEnsemble handles decomposition, parallel execution, and
candidate aggregation while each partition remains small enough for the chosen
backend.
🌐 Cloud Execution with Qoro Service
Run the same workflow on Qoro's cloud platform by swapping only the backend:
from divi.backends import QoroService
backend = QoroService() # reads QORO_API_KEY from .env or environment
Get started for free → Sign up at dash.qoroquantum.net and receive $100 worth of credits to run your first quantum programs on our cloud.
🤖 divi-ai: AI Coding Assistant
Ask questions about Divi directly in your terminal — no API keys, no internet required after setup.
pip install qoro-divi[ai]
divi-ai
Answers questions about Divi APIs, generates code examples, and explains concepts — powered by a local LLM that runs entirely on your machine. See the full documentation for model options and usage.
🧩 Key Features
| Feature | Description |
|---|---|
| VQE & QAOA | Built-in variational algorithms with pluggable ansätze and optimizers |
| Circuit Pipelines | Expand → execute → reduce pattern for complex circuit workflows |
| Program Ensembles | Parallel execution of multiple quantum programs with automatic scheduling, over one round or many adaptive ones |
| Flexible Backends | MaestroSimulator for local simulation, QiskitSimulator for Qiskit-native noise models (extra: aer), QoroService for cloud execution |
| Execution Config | Control bond dimension, simulator type, and simulation method per job |
| Live Reporting | Real-time dashboards and convergence tracking via callbacks |
Contributing
Contributions are welcome! See CONTRIBUTING.md for development setup, testing, and code style guidelines.
📄 License
Apache 2.0 — see LICENSE for details.
2 maintainers
Metadata
2 maintainers
Release files for qoro-divi 0.16.0.dev202610080047
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| qoro_divi-0.16.0.dev202610080047.tar.gz | 24.3 MB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| qoro_divi-0.16.0.dev202610080047-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 47.5 MB
Release files / qoro_divi-0.16.0.dev202610080047.tar.gz
| Download URL | qoro_divi-0.16.0.dev202610080047.tar.gz |
|---|---|
| Size | 24.3 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
64841e60b10392537d9c0a5e81a615675847071275c08c7bbd10be1c665882d4
|
|
BLAKE2b-256 checksum How to use checksums |
cc011c43be2fd44b368e8e1e0c90e8e3873f936a02384790eeada6d89d2fa270
|
| 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 Oct 8, 2026.
Transparency logRelease files / qoro_divi-0.16.0.dev202610080047-py3-none-any.whl
| Download URL | qoro_divi-0.16.0.dev202610080047-py3-none-any.whl |
|---|---|
| Size | 23.2 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6a14d07d39eff9b026b22df0c822f2e8a4f9e2186ffb4ddce633189c1b9688ec
|
|
BLAKE2b-256 checksum How to use checksums |
05bd9ce2416f42bc641d87e8fe225993e06da7e8c6adc8ff8080fbbb743600fe
|
| 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 Oct 8, 2026.
Transparency log
