Contributed by Ferdinand Ruppert, Managing Director of MPC Service GmbH (Germany), a Consultant Alliance member. This is a condensed edition of MPC’s article; a link to MPC appears at the end. Information reflects the market and technology status as of July 2026.
Enterprise networks are becoming more distributed, while expectations around availability and deployment speed keep rising. New sites need connecting quickly, remote operations increasingly depend on cloud applications, and a second terrestrial line does not always provide the physical diversity that genuine resilience requires. This is where low Earth orbit (LEO) satellite connectivity is creating new options.
For decades, satellite communications were used mainly where terrestrial infrastructure was unavailable — on ships, at remote sites, or beyond the reach of fixed and mobile networks. Today, lower latency, more capable terminals and more sophisticated enterprise services are widening the range of realistic business applications. The opportunity is not simply faster satellite internet: LEO can deliver rapid connectivity for temporary locations, connect remote operations, or add a fundamentally different access path to a resilience strategy. The key question for IT and network teams is therefore not whether satellite connectivity can work, but where LEO adds genuine value alongside fiber, mobile and other access technologies.
What is LEO — and why the orbit matters
LEO refers to orbits below roughly 2,000 km, compared with geostationary (GEO) satellites at about 35,786 km. That much shorter distance means a much shorter signal path and significantly lower latency. There is also an architectural difference: a GEO satellite appears stationary from the ground, whereas LEO satellites move rapidly overhead, so continuous service needs a constellation with automatic handovers from one satellite to the next. Modern LEO networks manage this seamlessly, combining wide geographic reach with performance older satellite services could not achieve. The two are not necessarily competitors — each has different strengths, and multi-orbit approaches are increasingly common (Eutelsat, for example, combines its GEO fleet with the 600-plus-satellite OneWeb constellation).
| LEO | GEO | |
| Orbit | Below ~2,000 km | ~35,786 km |
| Latency | Lower | Higher (longer signal path) |
| Network design | Requires a larger constellation | Wide areas with fewer satellites |
| Typical strengths | Broadband, mobility, lower latency | Wide coverage, specialized services |
Why LEO is becoming more relevant for enterprises
The concept is not new; what has changed is the ecosystem around it. Satellite services are increasingly built around requirements familiar from enterprise networking: service-level commitments, prioritized traffic, public IP connectivity, professional support, central management and integration with private networks. Starlink offers enterprise Priority services, Eutelsat OneWeb provides services and terminals for fixed and mobile use, and Amazon Leo is building a major LEO network with an enterprise proposition including dedicated terminals and private connectivity.
Two developments matter especially. First, private networking: rather than running a VPN across the public internet, newer models offer private interconnection — Amazon Leo has announced connectivity into AWS environments and Private Network Interconnects, and Starlink provides private interconnection at global points of presence. This lets satellite access be treated as part of the WAN rather than just an external internet link. Second, new terminals: electronically steered flat-panel and phased-array antennas are replacing large, hard-to-install dishes, making LEO practical for fixed, portable and mobile deployments. (Headline maximum speeds, though, should never be confused with guaranteed application performance.)
The technology trends shaping LEO
Several underlying shifts are expanding what satellite networks can do. Some constellations now use optical inter-satellite links — lasers that let satellites exchange data directly in space, reducing dependence on nearby ground stations. Multi-orbit concepts are gaining ground, combining GEO, MEO and LEO by coverage, capacity and latency needs; Europe’s planned IRIS² is a 290-satellite multi-orbit (LEO/MEO) constellation aimed at both public authorities and commercial users. And satellite and mobile are converging: 3GPP has standardized support for Non-Terrestrial Networks (NTN) within 5G and continues to expand it. Dedicated LEO broadband and direct-to-device NTN remain distinct technologies today, but the long-term direction — increasingly integrated terrestrial and non-terrestrial networks — is clear.
Where businesses can use LEO today
LEO does not need to replace an existing technology to add value; its strength is providing an additional option where terrestrial networks are unavailable, slow to deploy or insufficiently diverse.
- Backup and business continuity. Two fixed lines do not guarantee true path diversity — circuits from different providers may share ducts or exchanges. A satellite link introduces a genuinely different access route that does not depend on the same terrestrial last mile. The real test is not just available bandwidth, but whether critical applications perform reliably under actual failover conditions.
- Remote and underserved locations. For production sites, energy and mining operations, agriculture, warehouses or offices outside well-served areas, new fiber can take months or be uneconomic and mobile coverage can be patchy. LEO can provide primary connectivity without first extending a physical network to the site.
- Temporary sites and rapid deployment. Construction sites, project offices, events and pop-up locations often need connectivity before permanent infrastructure exists. Here deployment speed matters more than peak performance; a LEO link can start as primary access and later become backup or move elsewhere.
- Mobile and industrial operations. Ships, aircraft and other moving platforms are established markets, as are industrial sites transmitting telemetry, sensor data or video. Network design should always start with the application — basic telemetry has very different needs from high-resolution video or large data transfers.
When LEO makes sense — and when it may not
LEO is most attractive when suitable terrestrial infrastructure is unavailable, a new site must be connected quickly, or an additional physically diverse path is needed. It is less compelling at a permanent site that already has genuinely diverse fiber, strong SLAs and demanding, highly consistent latency and capacity requirements — or where the terminal cannot get a sufficiently clear view of the sky. The decision should rest on the business and network requirement, not the technology alone.
How LEO fits into a hybrid enterprise WAN
For most organizations, LEO’s role is within a hybrid architecture. One site might use fiber as primary and LEO for resilience; another might combine mobile and satellite where no fixed line exists; a temporary site might use LEO first and keep it as backup later. SD-WAN can integrate these access types under one logical WAN, monitoring latency, packet loss and jitter and steering each application to the right path — with critical traffic normally on the most predictable connection and failover policies moving selected services to LEO when needed. The strategic question is not which single access technology is best, but how fiber, mobile and satellite combine — so LEO should be evaluated as part of the overall connectivity strategy, not as an isolated purchase.
What to consider before deploying
Beyond headline bandwidth, evaluate:
- Application requirements — upload capacity, latency, jitter and packet loss can matter as much as download speed.
- Installation conditions — terminals need a suitable location with a clear view of the sky.
- Resilience design — consider the full failure scenario, including power and local equipment.
- Network integration — routing, IP addressing, VPNs, firewalls and private interconnection must fit the existing architecture.
- Security — treat satellite access like any other external service within your security controls.
- Service levels and availability — contractual commitments, capacity models, support, and coverage/regulatory conditions that vary by country.
An increasingly integrated future
LEO is moving beyond its old role as a last resort. Enterprise services are more sophisticated, terminals more flexible and private-network options better integrated with corporate and cloud infrastructure, while multi-orbit architectures and 5G NTN point to an increasingly connected landscape of terrestrial and non-terrestrial networks. LEO will not replace fiber, 5G or established satellite services across the board; its value is in adding another technically distinct option to the enterprise connectivity portfolio — worth considering not only for exceptional locations, but as part of how modern networks become more flexible and resilient.
This is a condensed edition of an article by Ferdinand Ruppert, Managing Director of MPC Service GmbH (Germany), a Consultant Alliance member specializing in enterprise WAN and site connectivity. Learn more about MPC: visit mpcservice.com →.