Qblox supplies the electronics and software that generate control pulses and acquire qubit measurements. Its Cluster has configurable modules, low-level Q1ASM programming and a Python scheduling layer, allowing a laboratory to assemble a stack around its experimental needs.
Record dates use UTC and show when an assessment or clarification was saved. Review dates show the evidence check. Earlier records were recovered from QubitWire’s source history; no earlier score movement is inferred.
Université de Sherbrooke confirms installed Qblox control electronics in its quantum FabLab. Joint work with QphoX and Rigetti demonstrated optical readout of a superconducting qubit; the published study reports 81% single-shot fidelity using a demolition-readout technique.
Now
Université de Sherbrooke confirms installed Qblox control electronics in its quantum FabLab. Joint work with QphoX and Rigetti demonstrated optical readout of a superconducting qubit; the published study reports 81% single-shot fidelity using a demolition-readout technique. A September 2026 Qblox/Riverlane integration exercises a real control-and-decoding loop with emulated measurement data. It is an integration test, not a live-qubit error-correction demonstration.
No dated name or ownership transition is recorded here. An alias is a search aid, not evidence of a legal ownership relationship.
Product scope
Modular quantum control and readout with synchronized programmable electronics
A company profile may discuss several systems. Capabilities remain attached to the product and conditions named in each source; they do not transfer automatically to related organizations. A verified security relationship has not been attached to this record.
Dated company evidence, its limits and the next test to follow. These notes do not change a QRank score.
QbloxControl electronics and QEC integration
Sources reviewed 20 Oct 2026. Event dates remain attached to the original evidence.
Qblox and Riverlane announced an integrated control and error-correction collaboration in March 2026, combining Qblox control hardware with Riverlane’s Deltaflow 2. The evidence concerns a control-stack integration; it does not establish the performance of a complete fault-tolerant quantum computer.
The useful question is what happens between a qubit measurement and the next operation that depends on it. A controller can generate precise pulses while still losing valuable time at an interface to a decoder. An integrated design deserves attention when it makes that entire path observable and repeatable. Readers should therefore look for a timing diagram with the start and stop points identified, the sustained measurement rate, and the behavior when many measurements arrive together. A demonstration using a small code can establish the interface without establishing how it behaves on a larger processor. That distinction makes Qblox a valuable control supplier to follow: the commercial proposition is dependable orchestration of someone else’s qubits. An evidence card should reward clear interface documentation and customer acceptance separately from any processor partner’s qubit count.
For a reader evaluating Qblox, the practical question is whether a controller/decoder combination can meet the experiment’s complete feedback deadline. A useful next evidence check is specific: capture acquisition, transport, decoding and corrective-action timestamps on a live QPU, including slow-tail events. A fast decoder can still miss the physical correction window when transport or buffering dominates. These are proposed tests for judging a later update, not claims that the company has already passed them.
Security status: No public security verified in reviewed material; directory/watch profile only
Facts, comparisons and next evidence
At a glance
label
Quantum role
value
Control and feedback
label
Evidence date
value
2026-03-16
label
Assessment action
value
Evidence enrichment
Dated milestones
date
2026-03-16
Date scope
source publication date; unknown if undated
event
Integrated control/QEC announcement
status
Published primary evidence; retain the narrower maturity statement
what it does not establish
A fast decoder can still miss the physical correction window when transport or buffering dominates.
Quantum role
layer
Control and feedback
Question
Whether a controller/decoder combination can meet the experiment’s complete feedback deadline.
Questions for comparison
Measurement-to-action latency boundary
Sustained concurrent channel throughput
Documented decoder/controller interface
Related approaches
name
Quantum Machines
relationship
Proposed comparison of relevant dimensions; not a claim of equivalent products or a ranking
dimensions
Measurement-to-action latency boundary
Sustained concurrent channel throughput
Documented decoder/controller interface
name
Riverlane
relationship
Proposed comparison of relevant dimensions; not a claim of equivalent products or a ranking
dimensions
Measurement-to-action latency boundary
Sustained concurrent channel throughput
Documented decoder/controller interface
Limits and missing evidence
A fast decoder can still miss the physical correction window when transport or buffering dominates.
Live-QPU end-to-end trace with code and channel count
Tail latency and overload behavior
Named customer acceptance of integrated configuration
What would change this assessment
trigger
Capture acquisition, transport, decoding and corrective-action timestamps on a live QPU, including slow-tail events.
Evidence needed
Dated primary technical report, product specification or customer/issuer disclosure directly answering the test.
Test
Identify the configuration, time boundary and measured outcome; retain unsuccessful attempts and stated limitations.
Limit
A fast decoder can still miss the physical correction window when transport or buffering dominates.
A starting question
question
Why can a quantum controller matter as much as another qubit?
answer
A measurement is useful only if the machine can act on it in time. The controller coordinates that action. Compare the complete feedback loop, including data movement and decoding, rather than one fast electronic component.
Dateline March 16; webpage metadata March 17. Component specifications are not a complete fault-tolerant-computer benchmark.
Read, question, follow the source
A closer look at the evidence
Company evidence guideQblox: baseband control makes interference and timing visibleEvaluate control electronics against an experiment’s signals and timing obligations.Context reviewed +
Qblox’s July 2026 explanation of its DC Cluster focuses on baseband control and readout for spin-qubit experiments. Its sequencer documentation describes separate programme-logic and real-time execution functions. Together these sources support an organization profile about a control stack’s experimental boundary: producing the intended signals at the intended times while keeping classical processing from disrupting the measurement sequence. They do not establish that every attached qubit platform will reach the same fidelity or scale.
Control electronics are often described through channel count, sampling rate or bandwidth. Those specifications matter only in relation to an experiment. A channel can exist physically while still being unsuitable for a particular signal range, noise requirement or timing relationship. A useful profile would therefore begin with the kind of waveform and measurement the user needs, then show which hardware and scheduling properties constrain that task. This gives the reader a reason to care about the architecture beyond the size of the instrument rack.
The interference question is similarly concrete. An experiment can be limited by unwanted coupling between control and readout paths, by grounding arrangements or by changes in the signal as it passes through the wider setup. A supplier’s explanation of a design choice is a starting point for an acceptance test. The profile should ask what was measured, over which frequency range, with which cabling and termination conditions. It should not convert a general design statement into a universal claim that interference is absent from the customer’s complete laboratory.
Sequencing introduces a different failure mode. The programme logic must prepare work quickly enough for the real-time execution layer to maintain its schedule. A useful educational example is a sequence with two equivalent scientific goals but different control-flow complexity. Readers can examine whether a long branch or repeated calculation changes the ability to deliver timely instructions. This is a software-analysis exercise; it should use a documented simulator or offline trace where available, and it does not establish operation of physical Qblox equipment. The relevant outcome is an explained timing contract, not an invented hardware benchmark.
Sector
Quantum control electronics
Comparison unit
Specified module, waveform and timing contract
Listing status
No direct listed security verified
Ticker
Not asserted
Documentation version observed
2026.10.1 on Q1ASM guide
Measurement boundary
Instrument claims are not complete-laboratory performance
Offline exercise
Annotated sequence trace; no hardware execution claimed
Questions to take with you
Why is channel count insufficient?
The channels must support the required amplitude, noise, bandwidth, synchronization and readout relationships. A larger count cannot answer those compatibility questions by itself.
What should accompany a timing claim?
The instruction sequence, controller and module configuration, software version, timing definition and measured or simulated trace. The record should distinguish an offline model from a physical measurement.
Evidence context only. This guide does not change QRank scores or supply a current price.
Q1 and real-time cores; queue and instruction timing semantics
Mutable main documentation; match instructions to installed hardware and software.
SOURCE REVIEW
Control and readout across qubit types
Qblox supplies modular control and readout electronics. Its current application descriptions cover superconducting circuits, semiconductor spins and optically driven systems, including photon counting and time tagging.
What this establishes—and its limits
A stated channel or qubit capacity describes control infrastructure. It is not a count of operational logical qubits and does not establish fault tolerance for the connected processor.
Evidence to look for next
Check simultaneous channel performance, synchronization, noise and full feedback latency on the intended device.
Sources reviewed . This review does not create or change a QRank assessment.
Modular quantum control and readout with synchronized programmable electronics
Who should look closer
Hardware teams building or extending quantum experiments that need modular control, readout and accessible pulse-programming tools.
QubitWire’s editorial assessment of practical fit.
Explore the control stack
Commercial Cluster hardware is evaluated through Qblox, with product details and documentation available online. Module selection depends on the device and measurement workflow.
Université de Sherbrooke confirms installed Qblox control electronics in its quantum FabLab. Joint work with QphoX and Rigetti demonstrated optical readout of a superconducting qubit; the published study reports 81% single-shot fidelity using a demolition-readout technique. A September 2026 Qblox/Riverlane integration exercises a real control-and-decoding loop with emulated measurement data. It is an integration test, not a live-qubit error-correction demonstration.
Optical readout is a joint system experiment, with results that cannot be attributed to the controller alone. An 81% demolition-readout demonstration does not establish scalable fault-tolerant operation.
The next question to watch
Can larger customer systems demonstrate reproducible timing, calibration and readout performance as the number of modules and controlled devices increases?
A research question, not a promised milestone.
QubitWire coverage
Hardware · Published · Source report · Sources checked
Qblox reports round trips below 4.0 microseconds for RTX PRO 6000 Blackwell and below 7.2 microseconds for DGX Spark.
Open research questions
Editorial questions for this profile. No reviewed closure decision has been recorded; unanswered questions do not lower the official score.
Open research question
Can larger customer systems demonstrate reproducible timing, calibration and readout performance as the number of modules and controlled devices increases?
What evidence would help
A source addressing this question must identify the named system, experiment or deployment, its conditions, measured outcome and remaining limitations. Are performance limits stated under realistic loads and operating conditions?
What would resolve it?
An editorial review must explain which part of this question the evidence resolves. A roadmap or an announcement alone does not close it.
No resolved, partial or disputed outcome is asserted without a reviewed transition and its evidence.
Which named system or service can I use under the documented access route?
What evidence would help
Check the current terms for explore the control stack. Identify the system version, eligibility, restrictions and whether the result used hardware or simulation.
What would resolve it?
Current primary documentation must identify the offering, eligible user and access conditions. An unspecified company-level access claim is insufficient.
No resolved, partial or disputed outcome is asserted without a reviewed transition and its evidence.
Are the interfaces compatible with your existing hardware?
What evidence would help
Provide the source location, relevant product or generation, workload, resource constraints and reported uncertainty. Keep measurements, simulations and announced targets distinct.
What would resolve it?
A source reviewer must map the evidence to this exact scope. Missing disclosure remains unknown; it is not technical failure.
No resolved, partial or disputed outcome is asserted without a reviewed transition and its evidence.
Questions are drawn from the existing brief and sector reading guide. Research brief reviewed 23 Sept 2026. Following stores a local bookmark; it does not send email alerts or imply a scheduled review.
Since your review
Scope: Qblox. Reading a page never marks its records reviewed.
Keep a baseline and explicitly mark the evidence you have reviewed. This optional journal stays in this browser.
Existing material records remain available after setup. Routine rechecks and initial entries are excluded from material counts.
These are the existing assessment claims and their recorded criterion links. A source link is not an independent replication. New research does not change these published ratings automatically.
Rigetti identifies Qblox as a participant in a demonstrated superconducting-qubit optical-readout experiment with QphoX; replacing large-scale wiring remains a prospective application.
Université de Sherbrooke confirms its quantum FabLab is equipped with Qblox modular control electronics, alongside a collaboration and training agreement.
Qblox reports automated Rigetti Novera bring-up using the Cluster and QuantrolOx Quantum EDGE; the accessible page does not expose a full quantitative benchmark.
Repeated coverage can describe the same experiment. The assessment does not contain a reviewed claim-family grouping, so the number of links is never shown as a replication count. Source pages can change independently of this saved assessment; the original source text is not archived here.
Rigetti identifies Qblox as a participant in a demonstrated superconducting-qubit optical-readout experiment with QphoX; replacing large-scale wiring remains a prospective application.
Université de Sherbrooke confirms its quantum FabLab is equipped with Qblox modular control electronics, alongside a collaboration and training agreement.
Qblox reports automated Rigetti Novera bring-up using the Cluster and QuantrolOx Quantum EDGE; the accessible page does not expose a full quantitative benchmark.
Author manuscript, subsequently published in Nature Physics 21, 401–405 (2025), reports 81% single-shot optical demolition-readout fidelity in the collaborative experiment. Date is the initial manuscript submission.
Qblox and Riverlane announced an integrated control and error-correction collaboration in March 2026, combining Qblox control hardware with Riverlane’s Deltaflow 2. The evidence concerns a control-stack integration; it does not establish the performance of a complete fault-tolerant quantum computer.