Your question: Which organizations match computing hardware and my filters?
Search companies, technologies or applications. Arrow keys explore suggestions. Escape keeps your search and closes suggestions.
Rankings · 15
15 assessed organizations. Showing 1–12.
Rank1(tie)
Superconducting quantum annealing and hybrid optimizationCanada / United States
85.0 /100 · editorial assessment
Programs an energy landscape and samples candidate solutions with superconducting flux qubits. Leap also offers solvers that combine classical processing with quantum annealing.
Cloud accessResearch reviewed · research refresh due5 linked sources
Capability 3 / 4
Delivery 4 / 4
Use in practice 3 / 4
Integration 4 / 4
Limitation: An annealer does not execute arbitrary gate-model circuits. Reported hybrid business outcomes do not by themselves establish quantum speedup; the separate gate-model program is not validated by annealing results.
External sources support at least half of the weighted assessment. They can include collaborators; this does not imply independent replication or technical superiority.
5 assessment sourcesAssessment reviewed Assessment refresh due Why this position?
This score reflects documented maturity using the computing hardware weighting.
Capability 40% weight
3 / 4 · 30 points
Delivery 25% weight
4 / 4 · 25 points
Use in practice 20% weight
3 / 4 · 15 points
Integration 15% weight
4 / 4 · 15 points
Strength: An operating cloud service, detailed hardware controls and external experimental use give researchers concrete ways to work with annealing.
Limitation: An annealer does not execute arbitrary gate-model circuits. Reported hybrid business outcomes do not by themselves establish quantum speedup; the separate gate-model program is not validated by annealing results.
External corroboration · Assessment reviewed Score edition · Method 1.0. Editorial opinion within this sector, not a probability or performance benchmark.
Superconducting gate-model processors and quantum cloudUnited States
85.0 /100 · editorial assessment
Combines programmable quantum processors with Qiskit tools, cloud job execution and device calibration records, giving developers a route from circuit design to experiments on hardware.
Open and paid cloud plansResearch reviewed · research refresh due4 linked sources
Capability 3 / 4
Delivery 4 / 4
Use in practice 3 / 4
Integration 4 / 4
Limitation: Access, calibration and dynamic-circuit support depend on the selected plan and backend. The reviewed physics experiment does not establish commercial advantage across applications.
External sources support at least half of the weighted assessment. They can include collaborators; this does not imply independent replication or technical superiority.
Limitation: Access, calibration and dynamic-circuit support depend on the selected plan and backend. The reviewed physics experiment does not establish commercial advantage across applications.
External corroboration · Assessment reviewed Score edition · Method 1.0. Editorial opinion within this sector, not a probability or performance benchmark.
Superconducting gate-model systems and cloud accessFinland / Germany
85.0 /100 · editorial assessment
Uses controlled superconducting circuits to execute gates, delivered through cloud services and installed systems.
Cloud and installed systemsResearch reviewed · research refresh due5 linked sources
Capability 3 / 4
Delivery 4 / 4
Use in practice 3 / 4
Integration 4 / 4
Limitation: Results on Q-Exa and VTT Q50 apply to those systems and test conditions. Calibration variation affects circuit performance; future larger-machine announcements are not treated as completed delivery.
External sources support at least half of the weighted assessment. They can include collaborators; this does not imply independent replication or technical superiority.
5 assessment sourcesAssessment reviewed Assessment refresh due Why this position?
This score reflects documented maturity using the computing hardware weighting.
Capability 40% weight
3 / 4 · 30 points
Delivery 25% weight
4 / 4 · 25 points
Use in practice 20% weight
3 / 4 · 15 points
Integration 15% weight
4 / 4 · 15 points
Strength: External operational evidence and detailed, maintained access and calibration documentation.
Limitation: Results on Q-Exa and VTT Q50 apply to those systems and test conditions. Calibration variation affects circuit performance; future larger-machine announcements are not treated as completed delivery.
External corroboration · Assessment reviewed Score edition · Method 1.0. Editorial opinion within this sector, not a probability or performance benchmark.
Trapped-ion QCCD processors and hybrid quantum softwareUnited States / United Kingdom
85.0 /100 · editorial assessment
Provides programmable trapped-ion computers and tools for circuits with mid-circuit measurement, reset and classical feedback, alongside emulators for development.
Subscription hardware and emulatorsResearch reviewed · research refresh due6 linked sources
Capability 3 / 4
Delivery 4 / 4
Use in practice 3 / 4
Integration 4 / 4
Limitation: Reported gate fidelity and random-circuit performance are not interchangeable with useful application advantage or fault-tolerant scale.
The assessment is primarily supported by organization-originated evidence. External evidence does not meet the published half-of-weight threshold.
4 assessment sourcesAssessment reviewed Assessment refresh due Why this position?
This score reflects documented maturity using the computing hardware weighting.
Capability 40% weight
3 / 4 · 30 points
Delivery 25% weight
4 / 4 · 25 points
Use in practice 20% weight
3 / 4 · 15 points
Integration 15% weight
4 / 4 · 15 points
Strength: Measured component errors, programmable connectivity and commercial access backed by technical documentation.
Limitation: Reported gate fidelity and random-circuit performance are not interchangeable with useful application advantage or fault-tolerant scale.
Primarily organization-sourced · Assessment reviewed Score edition · Method 1.0. Editorial opinion within this sector, not a probability or performance benchmark.
Neutral-atom analog systems and gate-model research processorsUnited States
85.0 /100 · editorial assessment
Traps individual atoms with light and controls their interactions. Aquila programs a physical quantum evolution; Gemini uses gates and atom movement for digital and logical-qubit experiments.
Cloud access; digital pilotsResearch reviewed · research refresh due5 linked sources
Capability 3 / 4
Delivery 4 / 4
Use in practice 3 / 4
Integration 4 / 4
Limitation: Aquila cloud access does not provide Gemini’s gate-model or logical-qubit capabilities. Logical magic-state distillation is a component of fault tolerance, not a completed general-purpose fault-tolerant computer.
The assessment is primarily supported by organization-originated evidence. External evidence does not meet the published half-of-weight threshold.
5 assessment sourcesAssessment reviewed Assessment refresh due Why this position?
This score reflects documented maturity using the computing hardware weighting.
Capability 40% weight
3 / 4 · 30 points
Delivery 25% weight
4 / 4 · 25 points
Use in practice 20% weight
3 / 4 · 15 points
Integration 15% weight
4 / 4 · 15 points
Strength: The company combines a documented public analog workflow with peer-reviewed progress in logical operations on a separate digital processor.
Limitation: Aquila cloud access does not provide Gemini’s gate-model or logical-qubit capabilities. Logical magic-state distillation is a component of fault tolerance, not a completed general-purpose fault-tolerant computer.
Primarily organization-sourced · Assessment reviewed Score edition · Method 1.0. Editorial opinion within this sector, not a probability or performance benchmark.
Superconducting gate-model processors with a modular chiplet architectureUnited States
85.0 /100 · editorial assessment
Uses microwave-controlled superconducting qubits to execute quantum circuits. Its Cepheus architecture connects smaller chiplets to form a larger processor.
Cloud accessResearch reviewed · research refresh due4 linked sources
Capability 3 / 4
Delivery 4 / 4
Use in practice 3 / 4
Integration 4 / 4
Limitation: Physical qubit count and launch gate fidelity do not establish useful circuit depth or fault tolerance. An August 2026 external preprint finds substantial route-dependent performance; its results are specific to the tested conditions.
External sources support at least half of the weighted assessment. They can include collaborators; this does not imply independent replication or technical superiority.
4 assessment sourcesAssessment reviewed Assessment refresh due Why this position?
This score reflects documented maturity using the computing hardware weighting.
Capability 40% weight
3 / 4 · 30 points
Delivery 25% weight
4 / 4 · 25 points
Use in practice 20% weight
3 / 4 · 15 points
Integration 15% weight
4 / 4 · 15 points
Strength: Public access and device-characterization workflows support reproducible experiments on a modular superconducting processor.
Limitation: Physical qubit count and launch gate fidelity do not establish useful circuit depth or fault tolerance. An August 2026 external preprint finds substantial route-dependent performance; its results are specific to the tested conditions.
External corroboration · Assessment reviewed Score edition · Method 1.0. Editorial opinion within this sector, not a probability or performance benchmark.
Trapped-ion processors and cloud quantum computingUnited States
81.3 /100 · editorial assessment
Makes programmable trapped-ion hardware available through its cloud and partner platforms, supporting circuit experiments and hybrid quantum-classical research workflows.
Direct cloud and Amazon BraketResearch reviewed · research refresh due5 linked sources
Capability 3 / 4
Delivery 4 / 4
Use in practice 3 / 4
Integration 3 / 4
Limitation: The application study combines simulations and hardware. Reported gains depend on a chosen classical baseline and reusing a quantum-generated ordering across many solves; they do not establish a universal speed advantage.
This score reflects documented maturity using the computing hardware weighting.
Capability 40% weight
3 / 4 · 30 points
Delivery 25% weight
4 / 4 · 25 points
Use in practice 20% weight
3 / 4 · 15 points
Integration 15% weight
3 / 4 · 11.25 points
Strength: Concrete cloud access paths and hardware use in documented hybrid workflows.
Limitation: The application study combines simulations and hardware. Reported gains depend on a chosen classical baseline and reusing a quantum-generated ordering across many solves; they do not establish a universal speed advantage.
Primarily organization-sourced · Assessment reviewed Score edition · Method 1.0. Editorial opinion within this sector, not a probability or performance benchmark.
Supplies photonic computing systems, cloud access and the Perceval development framework.
Cloud and institutional accessResearch reviewed 5 linked sources
Capability 3 / 4
Delivery 4 / 4
Use in practice 2 / 4
Integration 4 / 4
Limitation: Ascella benchmarks do not establish identical performance on Lucy or Belenos. Postselection, photon losses and sampling cost limit interpretation; these sources demonstrate neither fault tolerance nor commercial advantage.
This score reflects documented maturity using the computing hardware weighting.
Capability 40% weight
3 / 4 · 30 points
Delivery 25% weight
4 / 4 · 25 points
Use in practice 20% weight
2 / 4 · 10 points
Integration 15% weight
4 / 4 · 15 points
Strength: Published hardware experiments connect to maintained software and named external infrastructure.
Limitation: Ascella benchmarks do not establish identical performance on Lucy or Belenos. Postselection, photon losses and sampling cost limit interpretation; these sources demonstrate neither fault tolerance nor commercial advantage.
Primarily organization-sourced · Assessment reviewed Score edition · Method 1.0. Editorial opinion within this sector, not a probability or performance benchmark.
Superconducting coaxmon processors and hosted quantum accessUnited Kingdom
75.0 /100 · editorial assessment
Executes circuits on superconducting coaxmon qubits and connects the quantum processor to cloud or high-performance computing workflows.
Cloud and HPC installationsResearch reviewed · research refresh due5 linked sources
Capability 3 / 4
Delivery 3 / 4
Use in practice 3 / 4
Integration 3 / 4
Limitation: The error-budget result concerns selected pairs on one device generation. HPC integration and commercial access do not demonstrate computational advantage, and hardware capability should not be inferred from emulator results.
The assessment is primarily supported by organization-originated evidence. External evidence does not meet the published half-of-weight threshold.
5 assessment sourcesAssessment reviewed Assessment refresh due Why this position?
This score reflects documented maturity using the computing hardware weighting.
Capability 40% weight
3 / 4 · 30 points
Delivery 25% weight
3 / 4 · 18.75 points
Use in practice 20% weight
3 / 4 · 15 points
Integration 15% weight
3 / 4 · 11.25 points
Strength: A measured error-improvement study paired with operational integration evidence.
Limitation: The error-budget result concerns selected pairs on one device generation. HPC integration and commercial access do not demonstrate computational advantage, and hardware capability should not be inferred from emulator results.
Primarily organization-sourced · Assessment reviewed Score edition · Method 1.0. Editorial opinion within this sector, not a probability or performance benchmark.
Neutral-atom analog quantum processors and cloud programming toolsFrance
71.3 /100 · editorial assessment
Arranges laser-trapped atoms and controls their collective interactions to study quantum dynamics or encode optimization problems. Pulser defines the pulse sequence submitted to a compatible device.
Cloud and installed systemsResearch reviewed · research refresh due5 linked sources
Capability 2 / 4
Delivery 4 / 4
Use in practice 3 / 4
Integration 3 / 4
Limitation: Current cloud evidence supports constrained analog execution. Simulation libraries and digital-analog roadmaps do not establish an unrestricted fault-tolerant gate-model service, and the cited external use does not demonstrate computational advantage.
External sources support at least half of the weighted assessment. They can include collaborators; this does not imply independent replication or technical superiority.
5 assessment sourcesAssessment reviewed Assessment refresh due Why this position?
This score reflects documented maturity using the computing hardware weighting.
Capability 40% weight
2 / 4 · 20 points
Delivery 25% weight
4 / 4 · 25 points
Use in practice 20% weight
3 / 4 · 15 points
Integration 15% weight
3 / 4 · 11.25 points
Strength: A documented route from pulse design to real hardware, with a national research center reporting use of an installed system.
Limitation: Current cloud evidence supports constrained analog execution. Simulation libraries and digital-analog roadmaps do not establish an unrestricted fault-tolerant gate-model service, and the cited external use does not demonstrate computational advantage.
External corroboration · Assessment reviewed Score edition · Method 1.0. Editorial opinion within this sector, not a probability or performance benchmark.
Neutral-atom gate-model computing and logical-qubit experimentsUnited States / United Kingdom
70.0 /100 · editorial assessment
Uses laser-controlled cesium atoms for digital circuits, with Superstaq compiling programs to the hardware’s operations.
Cloud and national testbedResearch reviewed · research refresh due5 linked sources
Capability 3 / 4
Delivery 3 / 4
Use in practice 2 / 4
Integration 3 / 4
Limitation: Postselected error detection does not establish general fault tolerance or commercial advantage. Testbed installation is distinct from repeated external application outcomes.
The assessment is primarily supported by organization-originated evidence. External evidence does not meet the published half-of-weight threshold.
5 assessment sourcesAssessment reviewed Assessment refresh due Why this position?
This score reflects documented maturity using the computing hardware weighting.
Capability 40% weight
3 / 4 · 30 points
Delivery 25% weight
3 / 4 · 18.75 points
Use in practice 20% weight
2 / 4 · 10 points
Integration 15% weight
3 / 4 · 11.25 points
Strength: A concrete hardware application with disclosed encoding limits and a documented software access path.
Limitation: Postselected error detection does not establish general fault tolerance or commercial advantage. Testbed installation is distinct from repeated external application outcomes.
Primarily organization-sourced · Assessment reviewed Score edition · Method 1.0. Editorial opinion within this sector, not a probability or performance benchmark.
This score reflects documented maturity using the computing hardware weighting.
Capability 40% weight
3 / 4 · 30 points
Delivery 25% weight
2 / 4 · 12.5 points
Use in practice 20% weight
3 / 4 · 15 points
Integration 15% weight
3 / 4 · 11.25 points
Strength: Peer-reviewed error-correction evidence and detailed programmable hardware experiments.
Limitation: Willow is not generally available to the public, and a logical-memory milestone is not a universal fault-tolerant computer.
Primarily organization-sourced · Assessment reviewed Score edition · Method 1.0. Editorial opinion within this sector, not a probability or performance benchmark.
Equal scores share a position within their sector.
15 assessed / 72 listed
Directory inclusion is separate from assessment.
A field guide to this sectorKnow what to compare
Match the machine to the experiment
Gate-based circuits, analog simulation and annealing offer different controls and solve different classes of problems. A larger physical-qubit count alone does not establish better useful performance.
Gate model
Programs a sequence of quantum gates.
Analog simulation
Programs an interacting physical system to model its dynamics.
Logical qubit
Quantum information protected by an error-correcting encoding in physical hardware, often across multiple physical qubits.
Can you access the named system today, and under which plan?
Does the result report errors, circuit depth and a credible classical baseline?
Are the qubits physical or logical, and what operations were actually demonstrated?
QubitWire’s editorial checklist. See company evidence for specific claims.
Four checks before comparing a hardware claim
Use these questions when reading a company’s sources. They explain comparisons; they do not assign or change a QRank score. Every numerical example below is synthetic.
Best device or typical device?
What population does the headline number describe?
A selected result and a median answer different questions. Compare the same statistic, selection rule, measurement method and population before ordering two devices.
Synthetic sample: five coherence times are 40, 50, 60, 70 and 100 microseconds. The best is 100; the median is 60. Both describe this sample, but neither establishes the performance of every qubit or a useful circuit.
Ask for: Find the sample size, tested device set, excluded measurements, distribution and calibration date. If only the best value is disclosed, leave the median unknown.
Operating a gate alone and operating it alongside other gates can expose different unwanted interactions. Simultaneous benchmarking explicitly tests an operating context that an isolated measurement does not establish.
Synthetic comparison: an error estimate rises from 0.2% in isolation to 0.8% with neighboring operations active. That is a 0.6 percentage-point change, or four times the original estimate. Without the method and uncertainty, those two numbers do not diagnose the cause.
Ask for: Find the active qubit set, simultaneous operations, benchmark protocol, uncertainty and calibration window. Do not compare an isolated best case with a simultaneous average as though they were the same test.
A physical-gate error, a logical-cycle error and an application failure rate use different units and protocols. Keep the operation, code and decoding conditions with the result. A smaller percentage with a different denominator does not settle a comparison.
Synthetic classical event model: if ten independent operations each have a 1% chance of a flagged failure, the chance of at least one flag is 1 − 0.99¹⁰, about 9.56%. This is not a conversion from quantum gate infidelity to circuit failure: coherent errors, correlations and cancellation can break that interpretation.
Ask for: Find the error definition, benchmark, number of repetitions and confidence interval. For logical results, also find code distance, cycle definition, decoding method and any discarded trials.
Circuit execution is one part of a complete experiment. Preparing the job, waiting for access, repeating measurements and processing the output can each take time. Device usage and elapsed time are also different accounting quantities.
Synthetic job: 1,000 repetitions of a 50-microsecond gate sequence contribute 0.05 seconds. Add 0.25 seconds for readout/reset, 2 seconds of preparation, 10 seconds waiting and 1 second processing: the complete toy job takes 13.3 seconds.
Ask for: Find included stages, repetitions, error-mitigation work, queue treatment and output-quality requirement. Compare equivalent completed tasks before interpreting a speedup.
Background sources checked 2026-10-16. The examples are QubitWire teaching calculations, not results from the cited experiments.
What matters in this sectorView scoring weights
A maturity index across hardware approaches. Scores do not compare raw qubits or prove one machine is faster.
40%Capability
Demonstrated system behavior, workload results and stated error conditions.
25%Delivery
Access to an actual system, operational documentation and support.
20%Use in practice
Named external experiments or deployments with reported outcomes.
15%Integration
Usable tooling, developer documentation and maintained integrations.
Read, question, follow the source
What would the next piece of evidence show?
Company guides trace the path from an announcement to a measured component, accepted system or exact product certification.
Company evidence guideIQM: installed-system acceptance becomes an investor questionFollow an installed quantum system from supplier delivery to customer acceptance.Context reviewed +
IQM’s current evidence trail connects two activities that readers often evaluate separately: supplying superconducting quantum systems and reporting as a public company. Its July 2026 transaction documentation identifies Nasdaq American depositary shares under IQMX, with each ADS representing one IQM share. Its first public-company results cover the first half of 2026. These are useful anchors for a profile focused on how an installed system becomes an accepted customer asset. They do not make a delivery announcement equivalent to a completed technical acceptance test.
An installed-system profile should describe the boundary of the customer’s purchase. A processor, refrigerator, control electronics, software interface, maintenance agreement and training package may arrive on different schedules. The reader needs to know which components are included, who operates the machine, and what the customer can change without invalidating support. Ownership can be valuable when an institution wants to study calibration or integrate a machine into its own computing environment. It can also move operational work from the supplier to the customer. Neither consequence follows from qubit count alone.
Consider a research centre evaluating two proposals. One provides scheduled access to a supplier-operated service; the other installs equipment locally. The local machine could improve experimental control while requiring staffing, facilities and planned downtime. A useful comparison would hold the research programme constant and compare completed experiments over a stated period, access to calibration records, recovery from failed runs, and the ability to reproduce a result after maintenance. Purchase price would be only one input. This is an editorial comparison framework, not a report of an IQM customer contract.
The same boundary helps interpret financial reporting. An order, a backlog entry, a shipment, customer acceptance and recognised revenue describe different stages of a commercial relationship. Their definitions belong beside the numbers. A change in backlog may reflect new commitments, delivery progress, cancellations, currency movements or another disclosed adjustment. Readers should not be asked to infer the cause from a single total. An evidence card can instead connect the reporting period to management’s definition and the relevant customer or deployment document, while marking any unreported acceptance conditions as unknown.
Issuer
IQM Quantum Computers Plc
Public exposure
Direct quantum hardware issuer
Exchange
Nasdaq Global Select Market
Ticker
IQMX
Traded instrument
American depositary shares, each representing one IQM share
Evidence boundary
Delivery, acceptance, support and recognised revenue are distinct milestones
Acceptance terms
Not verified for any individual customer contract
Questions to take with you
What does the ADS label change?
It identifies the traded instrument and its relationship to the underlying shares. Readers should use that instrument when checking issuer filings or a licensed quote provider; a warrant or Helsinki share line needs its own identity and market metadata.
What would make an installation update substantive?
A customer statement about accepted performance, available access, operational responsibility or reproducible use would add information beyond a photograph or shipment date. Each claim should name the system and the conditions under which it was measured.
Evidence context only. This guide does not change QRank scores or supply a current price.
The original completion release returned HTTP 403. The same issuer release on Nasdaq confirms the US ADS identity; the results release was directly checked.
One American depositary share represents one IQM share; Nasdaq Global Select Market trading under IQMX.
Issuer release establishes instrument identity, not a current price.
Company evidence guideXanadu: a foundry partnership needs a manufacturing evidence ladderConnect the new foundry agreement to the measurements that would establish manufacturing readiness.Context reviewed +
Xanadu’s October 6, 2026 announcement of a partnership with GlobalFoundries creates a concrete manufacturing question for its profile: which components move through which production process, and what evidence will show that the process is ready for a larger system? The issuer’s current material identifies Nasdaq and TSX symbol XNDU. Nasdaq identifies the traded shares as Class B Subordinate Voting Shares. This record connects that security identity with a component-level reading of the partnership, without treating the announcement as a measured production yield.
Manufacturing language can refer to several different achievements. A process design can be compatible with a foundry before a qualified production run exists. A fabricated component can pass a laboratory test before packaging, interconnects and system integration meet the required performance. A repeated process can still have variable yield across a wafer or between production lots. Readers should ask which of these stages the supporting document actually describes. That approach makes an industrial partnership informative while keeping the remaining engineering work visible.
For a photonic quantum system, the component chain is especially important. Light generation, manipulation, routing, detection and classical processing contribute different constraints. A good organization card should therefore pair a manufacturing update with a simple component map. The map would identify the component’s function and the measurement needed to accept it, rather than assigning one maturity label to the whole machine. If a source discusses detector fabrication, the linked card should not imply that every optical circuit, network connection or logical operation has received the same validation.
An illustrative supplier review makes the distinction practical. Suppose two candidate processes produce devices with similar laboratory performance, but only one has disclosed packaging reproducibility. The second process might still be promising; the purchasing decision depends on which risk matters for the next build. The appropriate comparison would include the test sample, distribution of results, rejected devices, integration conditions and planned production cadence. These are proposed questions for future evidence, not claims about the private terms of Xanadu’s agreement. Missing numbers remain missing rather than being filled from an industry average.
Issuer
Xanadu Quantum Technologies Limited
Ticker
XNDU
Exchanges
Nasdaq and TSX, as identified by issuer
Traded instrument
Class B Subordinate Voting Shares (Nasdaq identity verified)
Public exposure
Direct photonic quantum computing issuer
Manufacturing yield
Unverified; no numeric yield claimed
Evidence step
Announced strategic partnership
Questions to take with you
Does a foundry agreement establish mass production?
It establishes the agreement described by the parties. Production readiness needs additional evidence about fabricated devices, yield, repeatability, packaging and accepted system performance. The record deliberately treats those as separate steps.
Why retain the share class?
The class is part of the security’s identity. It helps prevent confusion with other voting classes or instruments and points readers toward the correct shareholder disclosures. This content does not infer voting rights beyond the class name.
Evidence context only. This guide does not change QRank scores or supply a current price.
Xanadu Quantum Technologies Limited Class B Subordinate Voting Shares
Quote values not collected or reproduced.
Company evidence guidePasqal: keep the listed company and the executable analogue task togetherA current PSQL identity card paired with the full meaning of an analogue computation.Context reviewed +
Pasqal completed its business combination in August 2026, and its subsequent financial reporting identifies Pasqal Holding SA as Nasdaq-listed under PSQL. The transaction release distinguishes ordinary shares from warrants. That completed status matters because earlier announcements still describe a proposed transaction, and a current footer can appear beneath an older article. A reliable profile should establish the issuer’s present identity from the later evidence and then separately explain what a reader can actually execute using Pasqal’s analogue platform.
The technical part of the profile should begin with a task description. An analogue programme specifies a physical evolution under the available controls; its meaning cannot be reduced to a familiar gate-circuit diagram without checking the mapping. The useful questions concern the allowed geometry, interactions, pulse constraints, initial state and measured output. A software example becomes more informative when the reader can connect each modelling choice to the device or emulator that will run it. That connection is an editorial target for the profile, not a claim that every example is currently available on hardware.
Imagine a team studying an optimisation formulation using an atom arrangement. The team should preserve the classical problem instance, the mapping into the physical model and the rule used to turn measurements back into candidate solutions. It should also record how invalid or missing outcomes are handled. Otherwise a change in post-processing could appear to be a hardware improvement. Repeating a small, well-described task can be more useful than publishing a large atom count with no accessible output definition. Scale and reproducibility answer different questions.
Commercial reporting adds another set of boundaries. Platform access, installed hardware, development services and collaboration programmes need not generate revenue in the same way. A reader-facing profile should link any financial figure to the relevant period and reporting definition, and should avoid assigning all issuer revenue to one technically interesting activity. Pasqal’s first-half report and the date of its later transaction also represent different time windows. A period-end figure must retain its own date even when a post-closing cash figure is more recent.
Issuer
Pasqal Holding SA
Exchange
Nasdaq
Ticker
PSQL
Traded instrument
Ordinary shares; PSQLW warrants are a separate instrument
Public exposure
Direct neutral-atom quantum computing issuer
Execution mode
Analogue task; exact device and access conditions must be attached to each example
Period boundary
First half ended June 30; business-combination closing in August
Questions to take with you
Can an old proposed-listing article remain linked?
Yes, as transaction history with its original date and status. The current identity card should cite later completed-transaction and reporting evidence, so a reader does not mistake the earlier proposal for the current state.
What belongs with an analogue demonstration?
The original problem, physical mapping, device or emulator, control constraints, measured outputs and decoding rule. These fields let a reader tell whether a revised result changes the computation or only the surrounding workflow.
Evidence context only. This guide does not change QRank scores or supply a current price.
Product roadmap and delivery dates require exact product scope; no unrestricted hardware access inferred.
Company evidence guideAlice & Bob: ask what the cat-qubit testbed lets a partner measureUse the Helium announcement to ask precise questions about encoded experiments and partner access.Context reviewed +
Alice & Bob unveiled its Helium Quantum System in June 2026 as a platform for on-premise deployment and research collaboration. The announcement describes a system engineered to encode a first logical qubit using as few as eighteen cat qubits, and an intended upgrade path. A later September announcement reports a collaboration with CEA on the quantum software stack and hybrid computing. These sources support a profile about a testbed and integration programme; they do not establish that every advertised logical capability has already been demonstrated for external users.
The distinctive question is how a partner would test the architecture’s central promise. A biased-noise approach aims to suppress some error processes strongly enough that the remaining correction problem becomes more manageable. That promise needs a measurement vocabulary that separates storage, gates, measurement, repeated correction and complete logical operations. A long-lived memory statistic cannot stand in for every one of these. The profile should let a reader ask which experiment was performed and which errors remained relevant during that experiment, without dismissing the value of improved protection against a particular error.
A useful partner brief would define a small experiment with a clearly observable outcome. For example, compare the same encoded task over several correction-cycle counts while retaining the decoder, treatment of rejected runs and calibration window. Then describe what a meaningful failure would look like: a regime where increasing protection does not improve the selected outcome, a control operation that changes the assumed noise bias, or a measurement cost that dominates the task. These are proposed evaluation questions. This record does not claim that Alice & Bob has published such a complete data set for Helium.
Integration evidence deserves its own paragraph because a testbed has to operate within a wider workflow. Researchers need to submit programmes, understand execution limits, retrieve results and connect those results to the machine configuration. A collaboration on the software stack can make these interfaces more concrete. It should still be described at the level reported by the parties. An agreement to work together differs from a supported interface, a public release and a customer-accepted deployment. Versioned documentation would be a particularly useful next source for this profile.
Technology
Cat-qubit architecture and error-correction testbed
Listing status
No direct listed security verified in consulted company sources
Ticker
Not asserted
Public exposure
Organization evidence profile; no investable instrument claimed
Current evidence
System announcement and research collaboration
Logical performance
Specific external-user experiment not independently verified
Access
Research-partner invitation; unrestricted public access unverified
Questions to take with you
Does suppressing one error solve every error problem?
No. The complete encoded operation still has to account for the error processes that remain, including those associated with control, measurement and correction. The value of a biased-noise architecture depends on how those parts work together.
Why focus on a testbed?
A testbed makes a proposed architecture measurable through specific experiments and interfaces. Its usefulness can be assessed before a universal machine exists, provided the profile states what is available and what remains a target.
Evidence context only. This guide does not change QRank scores or supply a current price.
Research collaboration on software-stack integration in hybrid centres
No production support contract or public interface inferred.
Company evidence guideDiraq: separate a foundry process from the distribution of usable qubitsRead the eight-qubit foundry result through the denominators that manufacturing requires.Context reviewed +
Diraq and imec reported coherent operation and readout of an eight-spin-qubit silicon MOS array in July 2026, using imec’s 300 mm CMOS-compatible platform. That is a specific manufacturing and device claim with a named partner and a bounded array size. It supports a profile about the path from a fabrication process to a functioning device. It does not establish a wafer-wide distribution of usable qubits, a complete production yield or a fault-tolerant computer. Those would require different evidence.
The word manufacturable can hide several engineering questions that deserve separate answers. Can the desired structures be produced using the stated process? Can devices be tuned into the intended operating regime? How much device-to-device adjustment is needed? How often does a fabricated device meet the selected performance target? Each question has a different denominator. A well-performing measured array is valuable evidence, but the sample may have been selected from a larger set whose results are not reported. Readers should be able to see when that selection information is missing.
A useful visual for the organization page would follow one imaginary wafer through four stages: fabricated structures, electrically addressable devices, successfully tuned devices and devices meeting an experiment’s acceptance criteria. The illustration would contain no invented percentages. Instead, each stage would show the kind of measurement that belongs there and a blank field where the source has not supplied a number. This helps readers understand why a process result can be an advance without allowing an attractive wafer photograph to imply universal device uniformity.
The next practical issue is calibration effort. A processor with many individually adjustable controls may need automated routines, reliable initialisation and procedures for recovering from a poor operating point. A future Diraq update could therefore become more informative by reporting tuning success across devices or repeated operation over time, rather than only a best-case gate statistic. That is a proposed reporting direction, not a claim about undisclosed results. The same discipline applies to data-centre deployment plans: an announced location, installed equipment and a supported computational service are different milestones.
Technology
Silicon MOS spin qubits
Reported sample
Eight-qubit array in July 2026 announcement
Fabrication context
300 mm CMOS-compatible platform at imec
Yield denominator
Unreported in this record
Listing status
No direct listed security verified in consulted sources
Ticker
Not asserted
Proposed comparison
Fabricated, addressable, tuned and accepted devices must retain separate counts
Questions to take with you
Why can a small array matter for manufacturing?
It can show that a particular process supports functioning quantum devices under stated conditions. The next questions concern reproducibility and integration; a small result need not answer those questions to be technically useful.
What number would improve the profile most?
A clearly defined distribution can be more revealing than a new best result: for example, the fraction of tested devices reaching an explicit operating criterion, with the selection method, test conditions and rejected samples reported.
Evidence context only. This guide does not change QRank scores or supply a current price.
Primary research index for device and quantum-logic work
Index alone does not validate every result or current service availability.
Company evidence guideQuantum Motion: a full-stack installation needs a reproducible acceptance recordTurn a full-stack deployment claim into a record of what users can reproduce.Context reviewed +
Quantum Motion’s May 2026 financing announcement points back to a silicon CMOS quantum-computer deployment at the UK National Quantum Computing Centre in 2025. Its product page describes a full-stack system built with 300 mm silicon CMOS wafer technology. These are concrete company statements about an installation and its manufacturing approach. The useful follow-up is to ask what a researcher can reproduce on that installation, which interfaces are supported and how the delivered system is evaluated over time.
Full stack describes an integration boundary, but the boundary must be drawn. A reader needs to distinguish the semiconductor device from cryogenic control, room-temperature electronics, orchestration software and the interface exposed to a user. A successful demonstration through all those layers can reveal problems that a component experiment cannot. It also makes diagnosis more difficult because a failed run may originate in several places. The organization profile should therefore treat integration as a technical achievement with its own tests, rather than as a decorative description attached to a chip.
An acceptance record could begin with a minimal experiment that travels through the complete interface: prepare a specified state, execute a bounded operation, measure, retrieve the data and reproduce the analysis. The value lies in preserving the configuration and the expected interpretation. A later software revision should state whether the same programme still works and whether any result change comes from calibration, compilation or hardware. This example is an editorial proposal for documenting a testbed. It does not assert that a particular Quantum Motion API or access entitlement has been publicly verified.
The installation also invites a fair comparison between manufacturing familiarity and operating maturity. Standard semiconductor processes offer a route to fabrication, but the complete quantum system still has to demonstrate the performance required by its intended workload. The right questions concern the process actually used, the measured device population, control resources and the cost of repeated operation. A profile should not imply that conventional transistor production automatically transfers all its economics to a quantum processor. Nor should it ignore the value of using a process that can be examined within an existing industrial ecosystem.
NQCC independently identifies Quantum Motion’s Silicon Cloverleaf testbed and confirms the installed system. That host-side confirmation is already reflected in the company profile. Contract acceptance criteria, a public execution route and a reproducible user-facing workload remain separate questions; the installation statement does not answer them by itself.
Technology
Silicon CMOS quantum computing
Reported location
UK National Quantum Computing Centre
Deployment date context
2025 deployment referenced in May 2026 announcement
Customer acceptance evidence
Not independently retrieved during this review
Listing status
No direct listed security verified in consulted sources
Ticker
Not asserted
Interface status
Public execution entitlement and exact API unverified
Questions to take with you
Why does the customer-side source matter?
It can clarify what was delivered, accepted and made available within the testbed. The supplier and customer may describe different boundaries, so retaining both documents helps readers understand the actual service or research capability.
Can a learning exercise use an imaginary interface?
Yes, if it is explicitly an exercise. A specification for inputs, result metadata and failures can teach integration skills without pretending to be Quantum Motion’s production API or an employer’s hiring assignment.
Evidence context only. This guide does not change QRank scores or supply a current price.
NQCC identifies Silicon Cloverleaf and confirms Quantum Motion’s installed system.
Installation confirmation does not supply contract acceptance criteria or establish unrestricted public access.
Company evidence guideOxford Ionics after acquisition: preserve the provenance of the benchmarkKeep original experiments, acquisition history and later integration results in separate dated records.Context reviewed +
IonQ completed its acquisition of Oxford Ionics on September 17, 2025. The completion release establishes a corporate relationship that a current organization directory should preserve: Oxford Ionics is not presented here as a separately traded issuer. IonQ’s earlier transaction announcement also contains future technical targets. Those targets belong to the dated roadmap record, while the completion event belongs to the corporate timeline. Combining them into a single present-tense claim would obscure what happened and what was expected to happen later.
The practical editorial challenge is benchmark provenance after an acquisition. A result originally associated with one team, device and experimental method may later appear in the parent company’s wider narrative. The original result should retain its device identity, publication date and measurement protocol. Corporate ownership can change without making measurements from different systems directly comparable. A profile should help readers follow that history rather than replacing the old source with a new corporate logo and a larger number.
Suppose an organization page contains three performance figures: a physical gate measurement, a complete-system benchmark and a future logical accuracy target. Their percentages may look similar in a short card, but their meanings differ. A useful comparison would identify the measured operation, the number of tested instances, the treatment of state preparation and measurement, and whether the number is measured or projected. If those fields cannot be aligned, the page should explain the mismatch. It should not rank the figures merely because they can all be displayed with percent signs.
Acquisition integration also has a technical boundary. Combining expertise, intellectual property and manufacturing relationships can create opportunities, yet the benefits require implementation. Readers can follow concrete evidence such as a shared control interface, a demonstrated system combining technologies, a released architecture document or a customer deployment. Staff biographies are unnecessary for this task. The profile can describe the organization and its technology lineage without expanding the excluded People section or turning individual researchers into the main content.
Corporate relationship
Acquired by IonQ; completion announced September 17, 2025
Standalone ticker
None asserted
Public exposure
Indirect through parent issuer; use existing IonQ security record
Benchmark requirement
Original device, protocol and date retained after corporate changes
Roadmap status
Earlier targets are not promoted to achieved status
People scope
Organizational and technical provenance only
Questions to take with you
Does a corporate change invalidate an older result?
No. It changes the organizational context, not the experiment that was performed. The result should retain its original provenance and be linked to the current ownership timeline.
Can two fidelity values be compared directly?
Only after their operations, error models, treatment of preparation and measurement, sample definitions and statistical methods are understood. A projected logical value should not be displayed as though it were the same kind of evidence as a measured physical gate.
Evidence context only. This guide does not change QRank scores or supply a current price.
Targets must remain forward-looking and tied to their date; not evidence of subsequent achievement.
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.
Company evidence guideQuantum Machines: a calibration result is also a versioned software resultTrace a calibration claim through its controller, software versions, fit and final validation.Context reviewed +
Quantum Machines reported operating a Rigetti Novera processor with OPX1000 hardware and QUAlibrate software in May 2026, including a stated median two-qubit gate fidelity. The useful organization follow-up is not simply another fidelity card. It is a profile of the calibration workflow and the hardware-software combination that produced the result. Current documentation also contains release compatibility and network-configuration information, illustrating why an experimental control stack needs a version record as well as a product name.
Calibration is a chain of decisions. A routine measures a response, fits a model, chooses new parameters and checks whether the resulting operation is acceptable. When several routines depend on one another, an apparently small change can affect later measurements. A clear organization dossier should explain which parts of this chain are automated, which parameters are carried forward and how unsuccessful fits are handled. It should avoid using automation as a synonym for scientific validation. A fast routine can still optimise the wrong quantity if its assumptions are not appropriate for the device.
An illustrative review would compare two calibration runs performed on the same nominal processor at different times. The reviewer would ask for the software environment, controller release, device configuration, input parameters, fit diagnostics and final validation measurements. If one run improves while another degrades, the history should make it possible to identify whether the change came from a new routine, a new calibration state or a different sample of gates. That analysis is more informative than displaying a median alone. It also reveals why the spread and selection of measured operations matter.
The controller’s real-time role should be described separately from work performed by a host computer. A control language can execute feedback close to the experiment, while analysis and orchestration may run elsewhere. A performance claim should name the boundary being timed: a feedback response, one measurement sequence, an entire calibration workflow or a complete application. Readers should not infer that every stage has the same latency. The current documentation is the appropriate place to check interfaces and compatibility, while the experimental paper or report establishes the scientific result.
Sector
Hybrid quantum-classical control
Named stack
OPX1000 and QUAlibrate in vendor Novera report
Listing status
No direct listed security verified
Ticker
Not asserted
Benchmark status
Attributed vendor result; independent reproduction not performed
Provenance fields
Device, controller release, software environment, fit diagnostics and validation sample
Timing boundary
Feedback, sequence and complete workflow must be distinguished
Questions to take with you
Why can a software version affect a hardware result?
It can alter waveform construction, fitting, scheduling, parameter selection or result handling. A version record helps separate those changes from physical-device changes and makes a later comparison more meaningful.
What would make an automated calibration convincing?
A documented input state, explicit acceptance criteria, fit diagnostics, failure handling and independent validation measurements. Repeating the workflow across time or devices can show whether the result is robust.
Evidence context only. This guide does not change QRank scores or supply a current price.
Latest URL is mutable; preserve installed versions before reproducing an experiment.
Company evidence guideBluefors: photonic computing still needs a thermal architectureA cryogenic partnership becomes useful when the cooled subsystem and thermal load are explicit.Context reviewed +
Bluefors and Xanadu announced a cryogenic-infrastructure partnership in September 2026. Earlier in the year, Bluefors introduced a modular cryogenic platform. These announcements offer a useful organization angle because they challenge an oversimplified visual assumption: a photonic quantum computer can still contain components with demanding cooling requirements. The profile should identify which subsystem is being cooled and why, rather than assigning one temperature label to an entire computational approach. The partnership announcement is a development commitment, not a published system-wide thermal acceptance test.
A thermal architecture is a distribution of responsibilities. Different components generate heat at different locations and require different operating conditions. Cables, optical fibres, mechanical supports and readout electronics can connect regions that must remain thermally distinct. A useful reader-facing explanation follows those interfaces through the apparatus. The central question is not merely how cold a refrigerator can become when unloaded. It is whether the intended system can operate with the relevant heat loads, access requirements, vibration environment and maintenance constraints.
Consider a hypothetical modular installation that adds a second subsystem. The change may increase useful capacity, but it can also add heat paths, control connections and service work. A fair evaluation would compare the operating configuration before and after expansion, including the load at each stage and the time needed to return to stable operation. The example contains no proposed Bluefors specification. Its purpose is to show why a scaling claim should retain its configuration and why a refrigerator’s headline capacity cannot be translated directly into a number of useful logical qubits.
Operational economics need the same care. Energy use, floor area, consumables, support staffing and downtime all depend on the installation boundary. A supplier’s platform announcement may describe a design intended to improve some of these factors, while a customer report can show how the design behaves in practice. Readers should look for the actual duty cycle and workload before comparing annual costs. A system used continuously for production and one used intermittently for laboratory development may have different priorities even if their lowest temperature is similar.
Sector
Cryogenic infrastructure
Public exposure
No direct listed security asserted
Ticker
Not asserted
Thermal unit
Specified stage, load and operating configuration
New evidence
September 2026 photonic-system partnership
Unsupported inference
Refrigerator capacity is not a useful-logical-qubit count
Customer acceptance
Not verified during this review
Questions to take with you
Why might photonic equipment need cooling?
The temperature requirements belong to particular components and detectors, not to the word photonic as a whole. A system-level description should identify those components and their operating conditions.
What makes two cooling systems comparable?
The same relevant loads, stage temperatures, access needs, vibration constraints and duty cycle. An unloaded base temperature alone cannot establish suitability for a specified experiment.
Evidence context only. This guide does not change QRank scores or supply a current price.
Headline qubit-scale language is a vendor design claim, not a measured logical-qubit count.
Company evidence guideArqit: a quantum-safe label needs a key-establishment boundaryClassify ARQQ through its security products and examine the trust boundary behind the label.Context reviewed +
Arqit’s issuer reporting describes its business through symmetric-key agreement and related encryption products, including SKA-Platform and NetworkSecure. Its 2026 prospectus identifies ordinary shares on the Nasdaq Capital Market under ARQQ. The appropriate QubitWire classification is security exposure associated with quantum-resistant communications, not ownership of a quantum-computer manufacturer. This profile asks readers to examine where keys come from, which parties are trusted and what deployment evidence supports a product claim. It supplies no live quote or investment recommendation.
A security product is easier to understand when its boundary is explicit. Protecting a communication link involves endpoints, authentication, key establishment, key storage, software updates and operational policy. A statement about the strength of one cryptographic component does not automatically establish the security of all these parts. Readers should ask which threat model the supplier is addressing and what the adversary is assumed to control. An explanation can be accessible without pretending that the underlying assurance work reduces to a single slogan.
The most useful organizational evidence would connect a described deployment to a specific integration. For example, a customer might use a service to establish keys between network devices. The profile should identify whether the evidence is a trial, a licensed deployment, a reseller arrangement or a production service, and should preserve the customer’s own account where available. These commercial stages are not interchangeable. A partnership can create a route to adoption without proving that every downstream user is already protected or that the product has become a material revenue source.
Readers also need a clear separation between symmetric-key approaches and the standardized public-key algorithms discussed in post-quantum migration guidance. They can appear within the same broader security programme while solving different parts of the problem. The profile should link the precise assurance document or standard when a certification claim is made. It should never infer that the presence of the words quantum-safe establishes certification, nor should it claim that one vendor product completes an organization’s whole migration. Inventory, interoperability and operational testing remain distinct tasks in a deployment assessment.
Issuer
Arqit Quantum Inc.
Exchange
Nasdaq Capital Market
Ticker
ARQQ
Traded instrument
Ordinary shares
Public exposure
Quantum-resistant security software; not a quantum-processor manufacturer classification
Assurance status
No blanket certification claimed
Deployment stage
Must be established per named customer or product integration
Questions to take with you
Is this the same kind of exposure as a QPU maker?
No. The profile concerns security products intended to address cryptographic threats, including future quantum threats. The business and technical evidence therefore centre on deployment, assurance and integration rather than processor benchmarks.
What should accompany a quantum-safe claim?
The algorithm or protocol, threat model, trust assumptions, integration boundary and applicable assurance evidence. A broad label cannot replace those details or establish the security of every endpoint.
Evidence context only. This guide does not change QRank scores or supply a current price.
No price data retained; warrants have separate identity.
Company evidence guideSEALSQ: certification belongs to an exact product and versionFollow each chip from a certification target to an exact, checkable assurance record.Context reviewed +
SEALSQ’s October 2026 reporting describes a business spanning secure semiconductors, public-key infrastructure and post-quantum security products. The issuer identifies Nasdaq symbol LAES. Its product announcements and certification roadmap discuss several named families and milestones. The useful new profile is a product-by-product assurance map: which item is being discussed, what stage of evaluation it has reached and which evidence applies to that exact configuration. A company-wide statement about security should not silently become a certification badge on every product.
Certification language has several stages that deserve distinct labels. A design may target a standard, enter evaluation, complete a laboratory activity, receive a certificate or ship in a validated configuration. These events have different meanings. A roadmap date is especially easy to misread once the date has passed. The page should not automatically promote a target to completed status. It should link to the relevant scheme’s certificate or validation record, retain the tested version and state any conditions attached to the result.
A reader-friendly evidence table could place product family, hardware revision, firmware, algorithm support, evaluation stage and certificate identifier in separate columns. Unknown fields should remain explicit. This is more useful than a single green check because it shows whether the assurance matches the device a customer intends to deploy. It also helps distinguish algorithm implementation from system-level key management, provisioning and update processes. A product can contain a standardized algorithm while the surrounding deployment still requires its own configuration and operational assessment.
Commercial statements need an equally careful boundary. Preliminary revenue, an active sales pipeline, a design win and a shipment subject to customer qualification describe different evidence. A pipeline is not recognised revenue, and a prospective customer programme does not guarantee future sales. The October issuer update can be retained as a dated business source, while the technical panel tracks the specific chip and assurance documents. This allows the reader to understand the relationship between product development and commercial adoption without collapsing every milestone into a single growth narrative.
Issuer
SEALSQ Corp
Exchange
Nasdaq, verified against exchange security page
Ticker
LAES
Traded instrument
Ordinary Shares, verified on Nasdaq security page
Public exposure
Secure semiconductors, PKI and post-quantum security products
Certification scope
Exact product, revision and scheme record required
Financial status
October figures explicitly preliminary and unaudited
Questions to take with you
Does a certification roadmap establish certification?
No. It states planned milestones. Completion requires the relevant authoritative record and the exact product configuration to which it applies.
Why state the share class explicitly?
The instrument being described must match the exchange record. Nasdaq identifies SEALSQ Corp Ordinary Shares as LAES; that identity does not supply a current price or validate any product claim.
Evidence context only. This guide does not change QRank scores or supply a current price.
