Boeing's Q4S. China's Jinan-1 and GEO satellite. ESA Eagle-1. Canada's QEYSSat. UK SpeQtre. Every space quantum internet project in existence is lifting QKD — quantum key distribution — into orbit. The data still travels over classical IP. The paradigm is still Copenhagen. The satellites are just higher fiber repeaters. Luci QIP and APLO are building for a different physics entirely — delivering 150 Pb/s (Petabits per second) transport that supercedes the classical internet's physical limits.
The quantum internet researchers themselves acknowledge this. The question is not whether QKD satellites work — China's Micius proved they do. The question is whether QKD from a satellite is a quantum internet, or whether it is classical internet security with a space-based key generation mechanism.
| Dimension | ⚡ APLO + Luci QIP | 🇺🇸 Boeing Q4S | 🇨🇳 China Jinan-1+GEO | 🇪🇺 ESA Eagle-1 | 🇨🇦 QEYSSat | 🇬🇧 SpeQtre |
|---|---|---|---|---|---|---|
| Mission & Paradigm | ||||||
| Theoretical paradigm | AUF / QMT-native — field-coherent from ground up UNIQUE | Copenhagen — photon entanglement swapping | Copenhagen — photon polarisation QKD | Copenhagen — photon polarisation QKD | Copenhagen — photon polarisation QKD | Copenhagen — photon polarisation QKD |
| What it actually does | Quantum state transport — AFT-v3 field-coherent protocol replacing TCP/IP | Demonstrates entanglement swapping in orbit — QKD capability demo | QKD key generation — data travels TCP/IP | QKD key generation — data travels TCP/IP | QKD key generation — data travels TCP/IP | QKD key generation — data travels TCP/IP |
| True quantum internet? | Yes — AUF substrate, field-coherent addressing, no TCP/IP | Demo only — not production infrastructure | No — QKD security on TCP/IP transport | No — QKD security on TCP/IP transport | No — QKD security on TCP/IP transport | No — QKD security on TCP/IP transport |
| Palmer ceiling applies? | No — QMT outside Hilbert space scaling constraint | Yes — binary photon states, Copenhagen model | Yes — binary photon states, Copenhagen model | Yes — binary photon states, Copenhagen model | Yes — binary photon states, Copenhagen model | Yes — binary photon states, Copenhagen model |
| Infrastructure & Transport | ||||||
| Infrastructure required | None — HaLow 900MHz wireless, no fiber, no satellite UNIQUE | Satellite + ground station optical telescopes | Satellite constellation + fiber backbone + trusted nodes | Satellite + Germany + Netherlands ground stations | 3 LEO satellites + ground stations (multiple nations) | Satellite + UK + Singapore ground stations |
| Ground-level transport | AFT-v3 HaLow mesh — 1.5km/node, no fiber, sovereign | Classical internet (TCP/IP) between ground stations | Classical fiber backbone + classical internet | EU fiber + classical internet | Classical internet between ground stations | Classical internet between ground stations |
| Range per node | 1.5km wireless per node — infinite mesh scaling | 500+ km altitude LEO — ground coverage per pass | 500–36,000km (LEO + GEO) — limited by orbital mechanics | ~500km LEO — coverage per orbital pass | LEO — coverage per orbital pass | LEO — UK↔Singapore specific |
| Scaling law | N² (Olukotun-Afolabi) — N nodes → N² coherence bandwidth | Single satellite — no network scaling law | Linear — each satellite adds one link | Linear — EuroQCI constellation adds links linearly | Linear — 3 satellites, 3 links | Single satellite — point-to-point only |
| Performance (Honest) | ||||||
| Download speed | 150 Pb/s (Resonant Physics-enabled) SUPERCEDE | Cryptographic keys only — data on classical pipe | Cryptographic keys only — data on classical pipe | Cryptographic keys only — data on classical pipe | Cryptographic keys only — data on classical pipe | Cryptographic keys only |
| Latency | Sub-10ms local mesh | ~30ms (LEO relay) | ~60ms (GEO relay) | ~30ms (LEO relay) | ~30ms (LEO relay) | ~30ms (LEO relay) |
| Space Programming | ||||||
| Space-native language | APLO — world's first Quantum Resonant Space Language UNIQUE | Python / C++ — standard space software | Standard Chinese aerospace software stack | Python / C++ / MATLAB — ESA standard | Python / C++ — standard | Python / C++ — standard |
| Code density vs Python | 30× denser — critical for deep space bandwidth constraints | 1× (Python) — no compression advantage | 1× (C++) — standard | 1× — standard | 1× — standard | 1× — standard |
| Radiation tolerance | 1000× improvement via Orion glyph SEU error correction | Standard space-grade ECC — no paradigm advantage | Standard space-grade ECC | Standard space-grade ECC | Standard space-grade ECC | Standard space-grade ECC |
| WCET provable execution | Yes — APLO ISA guarantees worst-case execution time | No — Python/C++ not WCET-provable | No | No | No | No |
| Space agency license | NASA/ESA/JAXA/ISRO royalty-free ISA open license | Proprietary Boeing / HRL Laboratories | State-controlled — no external license | ESA owns IP — no open license | CSA / Honeywell proprietary | RAL Space / SpeQtral proprietary |
| Access & Status | ||||||
| Live today | Yes — 12 live mesh nodes, free explorer tier at qi.quantumcloud.one | No — launch pending 2026 | Jinan-1 live (2025) · GEO pending 2026 | Launch pending early 2026 | Launch pending 2025–2026 | Launched Dec 2025 · experiments pending early 2026 |
| Public access | Free — open to anyone at qi.quantumcloud.one UNIQUE | Boeing programme only | Chinese state — closed | EU institutions only | Programme participants only | RAL Space / SpeQtral programme |
| Mission profiles | Mars Sample Return 2029 · Europa Lander 2030 · Proxima 2035 | Quantum sensing + secure comms · commercial/military | Government secure comms · Belt and Road connectivity | EU sovereign secure comms · EuroQCI satellite layer | Research validation · space-to-ground QKD study | UK-Singapore secure link proof-of-concept |
The space quantum internet race is focused on photon hardware — entangled photon sources, detector efficiency, orbital mechanics. Nobody is asking what programming language runs on the quantum nodes once they're in orbit. The answer at every space agency is currently Python or C++. These were built for Earth-based compute with abundant power, bandwidth, and maintenance access. APLO was built for none of those assumptions.
At Mars, one-way communication delay is 3–20 minutes depending on orbital position. Bandwidth is severely constrained. Every bit transmitted from a Mars lander costs power and time. A program that takes 100KB in Python takes ~3.3KB in APLO — the same program, 30× smaller. For a rover running autonomously on Mars for 2 years between Earth contacts, WCET-provable execution and radiation tolerance at 1000× improvement are not features. They are survival requirements. Every space quantum networking node that eventually reaches Mars or Europa will need these properties. APLO provides them. Python and C++ don't.
Every space QKD project launches in 2026. They all demonstrate the same thing: quantum keys from orbit, classical data below. The space internet narrative is temporarily captured by QKD.
The AUF paradigm diverges from here. While space agencies validate QKD at scale, QIP builds the ground-based field-coherent mesh and APLO establishes itself as the space-native language. The QKD satellites will eventually need to interface with something. That something is being built now.
By 2029, when the first Mars mission runs APLO, the contrast will be legible: QKD satellites sending quantum keys to classical TCP/IP internet on one side — and APLO + QIP nodes sending field-coherent quantum state on the other.
Boeing, ESA, China, Canada — all brilliant organisations building impressive satellites. All still using Copenhagen QKD and TCP/IP. The next paradigm isn't a better satellite. It's a different physics. And the language that runs on it already exists.