TL;DR
Get the latest gadgets delivered free with Prime
- Fast, free delivery on millions of items
- Prime Video, Amazon Music and more included
- Member-only deals all year
EigenOrbit researchers evaluated 12 quantum execution providers using eigenkit, an open-source Python library for running circuits through a common interface. Their study reports that no backend consistently performs best: simulator results vary by workload, and hardware results depend partly on circuit-to-processor connectivity.
EigenOrbit researchers have published a study comparing 12 quantum execution providers with eigenkit, an open-source Python library designed to run circuits across simulators and quantum hardware through a shared interface. The team reports that no single backend performed best across all workloads, with results depending on circuit characteristics and, on hardware, the fit between circuit topology and processor connectivity.
The study, titled “eigenkit: A Provider-Neutral Quantum Computing Library,” evaluates eight simulator backends and four hardware execution routes. The hardware experiments include IBM Heron and IQM Emerald processors. EigenOrbit says the library separates a quantum algorithm’s definition from the provider used to execute it, allowing developers to use the same circuit across supported environments without rebuilding the surrounding workflow for each one.
According to the researchers, simulator performance varied with circuit size, structure, batching and application workload. A simulator that was suitable for one task could be less suitable for another. For hardware, the study says backend choice also depended on how closely a circuit’s topology aligned with the processor’s physical connectivity; its comparisons of IBM Heron and IQM Emerald showed that this relationship could affect which processor was better suited to an algorithm.
EigenOrbit describes eigenkit as an open-source Python library with backend-independent gradient computation and integrations for NumPy, PyTorch and scikit-learn. The release also lists tools for quantum machine learning, optimization and chemistry, along with benchmarking features for comparing quantum models with classical baselines. These are capabilities described by the project; the supplied report does not independently assess them.
Backend Choice Shapes Quantum Runs
The findings point to a practical issue for developers: an algorithm’s performance cannot be assumed to carry over unchanged when it moves between quantum platforms. Simulator choice can affect computational efficiency, while hardware connectivity can influence how well a circuit maps to a processor. Comparing providers before selecting one may help researchers identify a more suitable execution environment for a particular workload.
A common interface could reduce the effort involved in making those comparisons. If developers can keep circuit definitions and training workflows consistent while switching providers, they can test alternatives without rewriting an entire application for each platform. However, portability does not make the backends interchangeable: the study’s reported differences mean users still need to measure performance for their own circuits and conditions.
The report frames this as a software and evaluation problem, not evidence that one processor or simulator is generally superior. It also does not establish that a backend performing better in the study will do so for every user, workload or future hardware configuration.
Products Worth Considering

Bose SoundLink Flex Bluetooth Speaker (2nd Gen), Waterproof, Dustproof, USB‑C, Up to 12 hr Battery, Black

Samsung 34-Inch Odyssey G5 Ultra-Wide Curved Gaming Monitor

Bose QuietComfort True Wireless Earbuds with Active Noise Cancellation, Black
As an affiliate, we earn on qualifying purchases.
Quantum developers work with a growing mix of simulators, hardware architectures and cloud execution routes. Each provider can impose different requirements, making direct comparisons harder when workflows are tied to a single platform. EigenOrbit developed eigenkit to let users define a circuit independently of its execution provider and then run it on supported alternatives.
The study combines that software proposal with an experimental comparison across 12 providers. Its stated purpose is to examine whether a provider-neutral workflow can make cross-platform evaluation more practical, while also showing that the choice of backend remains workload-dependent. The paper is available on arXiv, and EigenOrbit has published the library’s project and GitHub pages.
“No single backend is consistently preferable across different workloads.”
— EigenOrbit research team, as summarized in the report
Limits of the Published Comparison
The supplied report does not provide detailed benchmark tables, numerical results, test conditions or uncertainty estimates, so readers cannot assess the size of the performance differences from that material alone. It also does not specify how broadly the tested workloads represent applications beyond those included in the experiments. The reported comparisons should not be treated as universal rankings of IBM Heron, IQM Emerald or the simulator providers.
The source identifies the study as research and links to an arXiv paper, but it does not state that the work has been peer reviewed. The report also does not provide independent validation of eigenkit’s listed features or indicate whether all 12 execution routes are available under the same access conditions. Those details remain unconfirmed in the supplied material.
Paper and Library Access
Readers can consult the paper, library documentation and source code through the links cited by EigenOrbit: the study is hosted on arXiv, and eigenkit is available through the project website and GitHub. The next useful step for evaluating the claims is to examine the paper’s methods and benchmark data, then test the library with representative workloads. No further release, independent replication or follow-up study is specified in the source report.
Key Questions
What did the EigenOrbit study compare?
It evaluated 12 quantum execution providers: eight simulator backends and four hardware execution routes, including experiments on IBM Heron and IQM Emerald processors.
What is eigenkit?
Eigenkit is an open-source Python library intended to let developers run quantum circuits across supported providers through a common interface, without tying a circuit definition to one execution backend.
Did one provider perform best overall?
No. The researchers report that no backend consistently performed best across the workloads they tested. Simulator results varied by workload, while hardware suitability also depended on circuit topology and processor connectivity.
Does the study prove IBM Heron or IQM Emerald is better?
No. The report says which processor was better suited depended on the algorithm and its fit with physical connectivity. It does not provide a general ranking or establish that either processor is best for all circuits.
Has the study been peer reviewed?
The supplied report links to an arXiv paper but does not say whether the research has been peer reviewed. That status cannot be confirmed from the source material provided.
Source: thequantuminsider.com
