Space and satellites
Satellite tasking: the operations problem that fits a quantum computer
An imaging satellite has more observation requests than it can serve. Each request has a time window and a value, windows overlap, and overlapping observations cannot both be taken. Choose the schedule of maximum total value.
Why this one is different
Every problem on the neighbouring logistics and manufacturing pages fails on encoding cost before it fails on anything else: a 20-stop route needs 400 binary variables and a 10 by 10 job shop needs tens of thousands. Satellite tasking does not have that problem.
It is a maximum weighted independent set on the conflict graph, which takes exactly one binary variable per observation request. Sixteen requests means sixteen qubits. That linear encoding is what makes it the rare operations problem you can actually put on a quantum computer today, and it is the reason this page has a benchmark at all rather than an explanation of why one is impossible.
The setup
Observation windows generated from seed 20260902 with random start times, durations and values, giving a realistic conflict density. Two classical baselines: exhaustive search over all 2^n subsets, which proves the optimum, and OR-Tools CP-SAT, which is what a mission planner would actually use. QAOA at depth 2, 512 shots, COBYLA with three restarts of 150 iterations, with every circuit evaluation counted.
Results
Measured 2 September 2026. Higher total value is better.
| Requests | Qubits | Exhaustive | Time | CP-SAT | Time | QAOA | Time | Evals | Optimal |
|---|---|---|---|---|---|---|---|---|---|
| 12 | 12 | 32.305 | 0.010 s | 32.306 | 0.0078 s | 28.352 | 9.7 s | 110 | no |
| 14 | 14 | 32.513 | 0.081 s | 32.514 | 0.0105 s | 32.513 | 10.4 s | 111 | yes |
| 16 | 16 | 34.668 | 0.210 s | 34.667 | 0.0116 s | 33.403 | 11.8 s | 118 | no |
CP-SAT and exhaustive search differ in the third decimal because CP-SAT optimises integer-scaled values (multiplied by 1,000 and rounded). Both select the same schedule; the gap is rounding, not disagreement.
What the numbers say
QAOA matched the proven optimum once in three runs, at 14 requests. At 12 requests it came in 12 percent below the best schedule and at 16 requests 3.6 percent below. As a heuristic it is respectable and it is not reliable.
CP-SAT solved every instance in around 10 milliseconds, roughly a thousand times faster than QAOA, and its solve time barely moved as the problem grew. Exhaustive search rose from 0.010 to 0.210 seconds across the same range, which is the exponential curve becoming visible. CP-SAT's flatness is the point: constraint solvers prune, so they do not follow that curve.
At the sizes a quantum computer can address, the classical solver is not merely winning. It is finishing before the quantum optimiser has evaluated its first circuit.
Where this could go
The linear encoding is genuinely favourable, so the interesting extrapolation is real rather than rhetorical. A constellation-scale tasking problem with a few thousand candidate observations would need a few thousand qubits, which is a plausible hardware target in a way that 40,000 for a delivery route is not.
Two things would have to hold for that to matter. Error rates would have to fall far enough that a depth-2 QAOA circuit on thousands of qubits returns signal, and QAOA's solution quality would have to stop degrading as the instance grows, which our three data points already show it doing. Neither is settled, and the second is a software question that could be answered long before the hardware exists.
The roadmaps make the first condition concrete. Hundreds of logical qubits by 2029, which IBM and Quantinuum both target, would cover a few hundred candidate observations. That is a real constellation planning problem rather than a toy, and it is reachable precisely because the encoding is linear.
Meanwhile CP-SAT will also have improved, and it currently solves these instances in around 10 milliseconds with room to spare. Any honest projection has to beat where the classical solver will be, not where it is now, and on this problem it is not close today.
For context: where the hardware actually is
Gaps on this page are quoted against the devices ZKSF can run, which are Amazon Braket’s public processors. That is not the frontier. Quantinuum, IBM, QuEra and Atom Computing are not resellable through us, and their machines are considerably further along. As of September 2026:
Physical qubits built
| Infleqtion Sqale | 1,600 | Neutral atom |
| Atom Computing | 1,180 | Neutral atom, 1,225 sites |
| IBM Condor | 1,121 | Superconducting, 2023 |
| IBM Heron R2 | 156 | Superconducting, ~99.5% two-qubit fidelity |
| Rigetti Cepheus | 108 | The largest available through ZKSF |
Two-qubit gate fidelity
The number that actually governs what a circuit can do.
| IonQ | 99.99% | Trapped ion, first past four nines |
| Silicon Quantum Computing | 99.99% | Silicon spin |
| Quantinuum | 99.97% | Trapped ion, all-to-all |
| IQM | 99.91% | Superconducting, available through ZKSF |
Logical qubits demonstrated
Published results, not roadmap targets.
| QuEra | 96 logical / 448 physical | Neutral atom |
| Quantinuum | 48 logical / 98 physical | Trapped ion, iceberg code |
| Atom Computing | 24 logical | On the 1,180-qubit system |
| 1 logical / 105 physical | Surface code, below threshold |
Announced roadmap
Targets. Roadmaps slip, and these are not results.
| Quantinuum Sol, 2027 | 192 physical, ~100 logical | Iceberg code, distance 2. Error detection with postselection, not correction |
| IBM Starling, 2029 | ~200 logical | Bivariate bicycle qLDPC, 100 million gates |
| Quantinuum Apollo, 2029 | hundreds of logical | Thousands of physical, logical error 1e-6 or better |
Run a tasking instance yourself.
The QAOA template is the same machinery with a different conflict graph. Load it, substitute your own observation windows and values, and export a certificate for your own run.