Skip to content

Ecosystem map

Quantum computing software in 2026: the open-source map

Most newcomers meet the ecosystem as a list of logos and acronyms. That is a bad way to learn it. A better map starts with the jobs the software is trying to do: teach the basics, build circuits, simulate behavior, optimize hard problems, compile to targets, or prepare systems for a post-quantum world.

Quantum computing software in 2026: the open-source map illustration

Superposition

Qtangl keeps the feasible plan space visible long enough to compare the best options before one plan is selected.

Phase

Qtangl checks feasibility first, then compares valid options against the operational objective in a readable hybrid workflow.

Measurement

The product returns a ranked plan, a short explanation, and the measurement behind the recommendation.

The ecosystem is really a stack of different jobs

General-purpose SDKs like Qiskit, Cirq, PennyLane, and ProjectQ help people write and run circuits. Simulators help people test ideas locally. Compiler and language projects sit between high-level code and backend constraints. Domain-specific tools bring in chemistry, optimization, photonics, or networking concerns that generic SDKs do not fully capture.

Once you see the ecosystem this way, the project list becomes much easier to navigate. You stop asking which library is the winner and start asking which layer or workflow problem you are actually trying to solve.

Categories matter more than brand familiarity

Beginners often recognize a few major brands and assume the rest of the ecosystem is just smaller alternatives. That is rarely true. Many of the most valuable projects are specialized tools built for a narrow but important job: error mitigation, annealing, pulse scheduling, photonics, circuit rewriting, or interactive learning.

A good ecosystem map helps people avoid two mistakes at once: choosing a general SDK when they really need a specialized tool, and dismissing specialized tools because they do not look like full platforms.

How to use this map

If you are new, begin with games, katas, and a major SDK. If you care about optimization, compare QUBO, QAOA, and annealing libraries next. If you care about chemistry, simulation, or PQC, go straight into those domain clusters instead of staying stuck in a generic starting stack.

The point is not to memorize every repository. It is to build a mental model of where each tool belongs and what question it answers.

Resources to open next

The goal of this guide is to help you navigate toward the right tools, not stop at the overview. The resources below are the strongest next clicks for this topic.

Cirq illustration
quantumlibGeneral-purpose SDKs

Cirq

Cirq is an open-source quantum project.

MixedUnknownFlagship
dwave-ocean-sdk illustration
dwavesystemsAnnealing and Ising

dwave-ocean-sdk

dwave-ocean-sdk is an open-source quantum project.

MixedUnknownFlagshipQtangl relevant
liboqs illustration
open-quantum-safePost-quantum cryptography

liboqs

liboqs is an open-source quantum project.

MixedUnknownFlagship
pennylane illustration
XanaduAIGeneral-purpose SDKs

pennylane

pennylane is an open-source quantum project.

MixedUnknownFlagshipQtangl relevant
qiskit illustration
QISKitGeneral-purpose SDKs

qiskit

qiskit is an open-source quantum project.

MixedUnknownFlagshipQtangl relevant
QuantumKatas illustration
MicrosoftGames and learning

QuantumKatas

QuantumKatas is an open-source quantum project.

MixedUnknownFlagship

Next step

Browse the full library.