Quantum Computing (hardware, cloud and software)

Where this market publishes its structure

• Amazon Braket supported devices (docs.aws.amazon.com braket-devices + aws.amazon.com/braket/quantum-computers/) machine-readable, 13 devices (8 QPUs from AQT, IonQ, IQM, QuEra, Rigetti; 5 AWS-own simulators); 2 linked (ionq, quera); AQT (aqt.eu) not in catalog; IQM page links only iqmacademy.com; Rigetti page gives no domain and Wikidata has no exact 'Rigetti' label
• Azure Quantum providers (learn.microsoft.com azure/quantum qc-target-list + provider pages) machine-readable, 4 providers, all linked (ionq, pasqal, quantinuum, rigetti); Quantum Circuits listed as coming soon (context only)
• Qiskit Functions catalog (quantum.cloud.ibm.com/docs/en/guides/functions + guide pages) machine-readable, 12 third-party functions from 11 providers; 3 linked (q-ctrl, kipu-quantum, multiverse-computing via Wikidata P856)
• QED-C members (quantumconsortium.org/members) machine-readable, 190 corporate members (+ academic 38, FFRDC 12, government 53, other 7, affiliate 1, no edges); 19 in-market providers linked; 14 linked holders held out-of-market
• IBM Quantum Network members (ibm.com/quantum/network) not machine-readable: no public member list: counts (300+), logos and case studies only (2026-10-20)
• qBraid device catalog (api.qbraid.com) not machine-readable: API answers 401 without an API key; account.qbraid.com/devices is a login app; not read
• Strangeworks backends not machine-readable: backend catalog inside the logged-in portal; not read

Own = declares at least one integration itself; covered = visible only because an aggregator, standards body, regulator or partner contract names it; distribution-only = listed only on cloud marketplaces it sells through, a channel reported beside, never counted as its own declared integrations; undeclared = nothing we can read, so no number; declares_compatibility = providers with a `compatible` shape vote, report only (kin, 2026-10-13): never counted as own, never in depth or position.

Taxonomy how this market maps onto apis.io

Derived 2026-10-21 from the 48 providers in this market we could resolve in the catalog. The percentage is the share of those providers carrying each one; it describes the market, not the tag or industry. Tag groups have no page of their own yet, so they are listed unlinked.

share of resolved cohort carrying it; tags >=0.20 & >=3 members (max 12, junk dropped), tag_groups >=0.20 (cooccurrence, non-cross-cutting; max 8), industries >=0.20 (max 6), areas >=0.10 (max 6; areas are keyword-matched and sparse), capabilities L1 >=0.20 (max 8); derive-market-taxonomy.py

Leaders by position (provisional)

Provisional: grouped by position, depth compared within a position only. Distribution (cloud marketplaces) and iPaaS bridges are counted beside position, never inside it. Unknown-builder listings are left out of position shares and counted here.

gravity 1 · other companies invest to build on it

builds-on 2 · publishes apps on other platforms' stores

standard 20 · listed by a voluntary standard's own directory

distribution 10 · only sells through cloud marketplaces

undeclared 15 · declares nothing we can read: no number