Edge computing promised to bring computation closer to users. But the edge has a geography problem: some places just don't have infrastructure. The ultimate edge isn't a cell tower or a micro data center—it's a satellite overhead.
The Evolution of Edge Computing
Computing architecture has oscillated between centralization and distribution for decades. Each swing corrects the excesses of the previous era:
1960s Mainframes → Centralized (shared terminals)
1980s PCs → Distributed (local processing)
2000s Cloud computing → Centralized (hyperscale DCs)
2015s Edge computing → Distributed (CDNs, edge nodes)
2025+ Orbital computing → Ubiquitous (everywhere coverage)Each generation didn't replace the previous one—it added a new layer. Orbital computing doesn't replace cloud or edge. It adds a layer that fills the coverage gaps neither can reach.
Why Current Edge is Insufficient
The Coverage Gap
Today's edge infrastructure follows population density. AWS Local Zones, Cloudflare Workers, Fastly's edge nodes—they're concentrated in cities and along fiber routes. This leaves massive gaps:
- 71% of Earth's surface is ocean, with zero edge infrastructure
- Polar regions have minimal connectivity despite growing scientific and commercial interest
- Developing nations lack the fiber backbone that edge computing depends on
- Remote industrial sites (offshore platforms, mines, pipelines) have satellite-only connectivity
For these locations, the “edge” is still a data center thousands of kilometers away. Round-trip latency to the nearest cloud region can exceed 200 ms, making real-time applications impossible.
The Infrastructure Dependency
Terrestrial edge nodes need power, cooling, physical space, and fiber connectivity. Each dependency is a point of failure and a limiting factor for deployment. You can't put an edge node in the middle of the Pacific Ocean.
Orbital Edge: The Advantages
1. True Global Coverage
A constellation of 48 satellites in optimized orbital planes provides continuous coverage of every point on Earth. No fiber required. No power grid required. The satellite brings its own energy (solar) and its own connectivity (ISL mesh + ground stations).
Coverage Analysis (SolarNode Constellation):
──────────────────────────────────────────────────
Phase Nodes Coverage Max Gap
──────────────────────────────────────────────────
Phase 1 6 Intermittent ~45 min
Phase 2 24 Regional ~8 min
Phase 3 48 Global 0 min (continuous)
──────────────────────────────────────────────────
At 48 nodes, every location on Earth has at least
2 satellites visible at all times.2. Latency That Beats Fiber
Counterintuitively, orbital paths can be faster than terrestrial paths for intercontinental traffic. Light in vacuum travels at c (300,000 km/s), while light in fiber travels at ~200,000 km/s (due to the refractive index of glass). For paths longer than ~3,000 km, the orbital route wins.
London → Tokyo latency comparison:
────────────────────────────────────────────
Path Distance Latency
────────────────────────────────────────────
Subsea fiber (via Suez) ~11,000 km 55 ms
Subsea fiber (via US) ~20,000 km 100 ms
Orbital (2-hop ISL) ~9,500 km 32 ms
────────────────────────────────────────────
Orbital advantage: 42% faster than best fiber3. Disaster Resilience
When earthquakes sever undersea cables, when hurricanes destroy cell towers, when wars disrupt ground infrastructure—satellites remain operational. Orbital edge is the only compute layer that survives any terrestrial catastrophe.
IoT and Sensor Networks
The explosive growth of IoT creates a perfect use case for orbital edge. Consider these scenarios:
Maritime IoT
100,000+ commercial vessels at sea at any time, each generating sensor data (engine telemetry, weather, AIS, cargo monitoring). Today, this data is either not processed in real time or sent via expensive VSAT links to distant data centers.
With orbital edge, an ML model running on a SolarNode overhead can process vessel sensor data with <50 ms latency, enabling real-time anomaly detection, route optimization, and predictive maintenance—anywhere on any ocean.
Precision Agriculture
Satellite imagery combined with ground sensor data, processed at the orbital edge, enables real-time crop monitoring even in regions with no terrestrial internet. Farmers in sub-Saharan Africa get the same AI-powered insights as those in Iowa.
Environmental Monitoring
Climate monitoring sensors in remote locations (glaciers, rainforests, ocean buoys) generate data that's often collected months later. Orbital edge enables real-time processing, turning passive monitoring into active alerting.
5G/6G Integration
The telecommunications industry is already planning for space integration:
- 3GPP Release 17+ includes Non-Terrestrial Networks (NTN) specifications for direct satellite-to-device communication
- 6G roadmaps from major telecom players (Nokia, Ericsson, Samsung) all include LEO satellite layers
- Direct-to-cell services (T-Mobile/SpaceX, AST SpaceMobile) demonstrate consumer demand for ubiquitous connectivity
SolarNode extends this vision: not just connectivity from space, butcompute from space. Instead of backhauling IoT data to a terrestrial cloud, process it at the orbital edge and return only the insights.
Traditional IoT Path:
Sensor → Satellite link → Ground station → Internet
→ Cloud DC → Process → Return path
Round-trip: 200-500 ms, $0.10/MB
Orbital Edge IoT Path:
Sensor → Satellite link → Process on SolarNode
→ Return result
Round-trip: 30-80 ms, $0.02/MB10-Year Vision
By 2035, we envision orbital edge as a standard tier in every cloud architecture:
2025: Proof of concept (SolarNode One)
First workloads processed in orbit
2026: Early commercial (6-node constellation)
Maritime IoT, disaster resilience use cases
2028: Scale deployment (24 nodes)
Regional coverage, enterprise contracts
Integration with major cloud providers
2030: Full constellation (48+ nodes)
Global continuous coverage
Orbital edge as a standard cloud tier
Direct-to-device compute offloading
2032: Second generation
Higher compute density (10x current)
Inter-constellation federation
Standardized orbital edge APIs
2035: Ubiquitous orbital computing
Every cloud deployment has an orbital tier
Real-time global AI inference
Orbital edge indistinguishable from terrestrialWhat Needs to Happen
For this vision to become reality, several things must converge:
- Launch costs must continue falling — Starship and competitors will drive costs below $500/kg to LEO
- Standards must emerge — Common APIs for orbital compute, building on cloud-native foundations (Kubernetes, OCI)
- Regulation must adapt — Space traffic management, spectrum allocation, and data sovereignty frameworks need updating
- The ecosystem must grow — Not just SolarNode, but a healthy market of orbital compute providers creating competition and choice
The future of edge computing isn't at the edge of the network. It's at the edge of the atmosphere. And it's closer than you think.
References:
- 3GPP TR 38.811: Study on NTN for NR (Release 17)
- McKinsey, “Space: The $1.8 Trillion Opportunity” (2024)
- Nokia Bell Labs, “6G Architecture Vision” (2023)
- SolarNode Constellation Design & Coverage Analysis v3.0
Remco Oostelaar
Contributing to the future of orbital infrastructure