2026 order book open
Boutique access to LEO and hybrid connectivity for routes where terrestrial fiber is no longer fast—or resilient—enough.
GLOBAL BACKHAUL / ORBITAL + TERRESTRIAL
Vacuum carries light roughly 47% faster than standard silica fiber.
Physics is the opportunity. Route design determines the result.
01 / THE LATENCY THESIS
Light in vacuum travels at exactly 299,792 km/s. In common long-haul silica fiber, the effective group index is about 1.468—roughly 204,000 km/s before cable detours, repeaters, switching, queues, and protection paths.
That makes orbital laser routing compelling over long distances. It does not make every satellite path faster.
Great-circle distance divided by a representative fiber velocity. This is a lower bound, not a purchasable circuit.
A favorable optical path near a 600 km shell, plus up/down propagation. It excludes RF scheduling, switching, queueing, path churn, and metro tails.
Current LEO internet often lands traffic at a gateway or PoP and continues on terrestrial networks. An operational laser mesh is not automatically a dedicated city-pair route.
Illustrative engineering estimates, rounded. Final route studies require provider topology, endpoint coordinates, gateway/PoP choice, spectrum and regulatory availability, terminal geometry, weather strategy, and measured acceptance testing.
02 / NETWORK POSITION
We are building a carrier- and constellation-aware brokerage layer for difficult routes: source the viable path, combine it with the right terrestrial underlay, define measurable acceptance criteria, and manage the handoffs.
COMMERCIAL NETWORK
Its laser mesh is operational. Starlink reported more than 24,000 lasers in its 2025 network and 30–40 ms improvements in parts of Asia and Africa. Published access latency is not proof of an exchange-to-exchange laser route.
2025 progress report ↗ENTERPRISE PREVIEW / ROLLOUT
Formerly Project Kuiper—not “Kaipur.” Amazon began an enterprise preview in November 2025 and says wider rollout will continue through 2026. Its prototypes demonstrated 100 Gbps optical links; production city-pair performance remains route-specific.
Amazon Leo overview ↗03 / INITIAL MARKETS
We are starting where a different physical route creates disproportionate value. Each reference design below is generic and illustrative—not a claim about a deployed customer.
For strategies where geography is an input, not a constraint. We study metro handoff, orbital path opportunity, deterministic failover, and jitter—not bandwidth alone.
A trading firm needs a Chicago–Tokyo path independent of its incumbent subsea route. A qualified design pairs exchange-proximate cross-connects with a reserved orbital path and automatic terrestrial reversion.
Design objective: lower steady-state RTT with a physically diverse hot standby.Primary traffic policy follows the qualified path; protected fallback is tested independently.
Pre-positioned connectivity for incident command, first responders, FEMA/AID partners, and logistics teams—built to come online before local infrastructure fails.
An aid operator stages two transportable terminals outside the projected impact zone, then advances them with logistics teams to restore voice, mapping, dispatch, and cloud access.
Design objective: an independent link available in hours, with local mesh and power redundancy.Primary traffic policy follows the qualified path; protected fallback is tested independently.
Private, resilient paths for board sessions, command decisions, and extreme-security operations where route sovereignty and continuity matter as much as picture quality.
A global operator links hardened rooms in two regions through encrypted customer edges, route-separated access, and a private interconnect that avoids the public internet where available.
Design objective: stable presence, controlled egress, and seamless degradation—not a consumer video link.Primary traffic policy follows the qualified path; protected fallback is tested independently.
Connectivity for business aviation, aircraft fleets, merchant marine, and specialist vessels—designed around mobility, beam handoff, coverage windows, and port or airport operations.
A fleet operator uses multi-orbit-ready terminals for primary crew and operational traffic, then policy-separates passenger services from telemetry and safety-related applications.
Design objective: continuous service domains across oceanic segments with shore-side private interconnects.Primary traffic policy follows the qualified path; protected fallback is tested independently.
Route engineering for live global productions, invitational tournaments, remote contribution, and professional esports where packet timing shapes the experience.
A tournament operator reserves a low-jitter primary path between venue edges, carries production separately, and keeps commodity internet only as tertiary recovery.
Design objective: consistent game-state and contribution timing with measurable failover behavior.Primary traffic policy follows the qualified path; protected fallback is tested independently.
04 / ORDER WINDOW
Endpoint, traffic, performance, regulatory, and commercial qualification.
Provider selection, terrestrial diversity, terminal plan, acceptance test, and procurement.
Initial arrangements activate as provider coverage, route capacity, hardware, and approvals permit.
Target dates are planning goals, not guaranteed service dates. Availability depends on constellation coverage and capacity, partner contracting, terminal certification, licensing, landing rights, and site readiness.
05 / ROUTE INTAKE
Enough detail to determine whether the route merits a technical conversation. Nothing more.
No newsletter.
No onward sale.
No consumer solicitations.