LEO Satellite for UK Business and IoT: The Managed Connectivity Layer

The worked example: what sat365 actually is

A good way into this topic is a single, concrete UK product. Comms365, a Milton Keynes based connectivity provider, launched sat365 as a managed LEO satellite service aimed squarely at business rather than the consumer. The underlying access is Low Earth Orbit capacity, quoted at up to 400Mbps with latency in the region of 25 to 70ms, and a lead time as short as a couple of days. Those headline figures matter less than what wraps around them.

The important part of sat365 is not the connection, it is the service. Comms365 layers its Continuum Constellation management platform on top, adding fixed public IP, quality of service, VPN, SD-WAN integration, remote management, proactive monitoring and automated 4G or 5G failover, all supported from a UK based network operations centre on UK sovereign data infrastructure. In other words, it takes a best-effort consumer-grade satellite feed and turns it into something an IT team can actually put on a corporate WAN with an SLA behind it.

Why the raw dish is not enough

Plug a standard Starlink kit in and you get fast, genuinely impressive connectivity in minutes. You also get carrier-grade NAT, a shared and shifting public address, no committed information rate, no quality of service, no VPN termination you control, and a support model designed for households. For a home or a pop-up that is fine. For a site that has to appear on a corporate network, host inbound services, meet compliance requirements or sit behind a firewall estate, it is a series of problems waiting to surface.

The managed model exists to close that gap. Traffic is tunnelled from the site back to the provider’s core, where the customer is handed a fixed public IP, policy is applied, and the link is integrated with the rest of the WAN through SD-WAN. The satellite becomes one more transport underneath a managed overlay, sitting alongside fibre, 4G and 5G rather than replacing the network team’s control of it. That is the difference between satellite as a gadget and satellite as infrastructure.

The UK coverage reality (yes, including north Scotland)

There is a comfortable myth that LEO has already solved rural Britain. It has not, and being honest about that is the whole point of choosing the right service.

Starlink covers the overwhelming majority of the UK, but the far north of Scotland remains the weakest part of the map, precisely the sort of location where a resilient link is most needed and least available from anything terrestrial. Even where the availability map shows green, terrain shading is a real constraint: a dish in a Highland glen with mountains on two sides can lose the clear sky view it depends on, so a genuine site survey beats a postcode check every time.

Then there is capacity. Starlink’s residential service works on a cell-by-cell basis, and popular areas periodically show as sold out or waitlisted while the network adds ground-station and satellite capacity. The South East of England has hit that wall more than once. Some areas have also carried a congestion surcharge. None of this is a fault as such, it is simply how a shared, oversubscribed medium behaves, but it means you cannot assume that because a neighbour has Starlink, you can get it, or that a residential activation will behave like a business circuit.

This is also where the choice of constellation starts to matter. A near-polar constellation behaves very differently at 58 degrees north than one optimised for mid latitudes, which brings us to the players.

The UK LEO players compared

Three Western LEO broadband constellations are relevant to a UK buyer in 2026, and they reach the market in very different ways.

Starlink (SpaceX)

By far the largest and most mature, with roughly ten thousand satellites in orbit at altitudes around 340 to 550km and an inclination that gives broad UK coverage. It sells direct to consumers and businesses, and is also the capacity behind most UK managed offerings including sat365. Latency is the best of the three at roughly 25 to 60ms. Its weaknesses for business are structural rather than technical: default CGNAT, dynamic addressing even on Business plans, and consumer-grade commercial terms unless someone wraps a managed service around it.

Eutelsat OneWeb

The second operational Western constellation, around 648 satellites at roughly 1,200km in a near-polar orbit. That high, near-polar geometry gives it genuinely strong high-latitude coverage, which is directly relevant to northern Scotland and the isles. OneWeb is wholesale only: it never sells direct, reaching customers exclusively through distribution partners such as telcos and specialist integrators. The trade-off for the higher orbit is higher latency than Starlink. It is part-owned by the UK government, and a next-generation fleet with 5G integration is on order from Airbus for delivery from late 2026 onwards. For enterprise, maritime, government and high-latitude use it is the natural alternative to Starlink.

Amazon Leo (formerly Project Kuiper)

The newcomer, rebranded from Project Kuiper in late 2025. Around 390 production satellites were in orbit by mid-2026 against a first-generation target of 3,236, with enterprise beta live and a commercial launch targeted for the middle of 2026. The UK is one of the first five launch countries. Two caveats matter for a UK buyer. First, coverage builds from the northern and southern latitudes inward, but the Phase 1 shell sits at an inclination optimised for roughly 30 to 56 degrees, so the very far north of Scotland is not where early Amazon Leo coverage will be strongest. Second, at this stage it is a promising option to track rather than something to design a live UK deployment around. We covered its arrival separately in our Amazon Leo piece{{AMAZON_LEO_POST_URL}}.

For most UK business and IoT deployments today, the practical choice is Starlink capacity inside a managed service, with OneWeb as the alternative where you need the near-polar coverage, a wholesale relationship or a non-SpaceX supply chain. Amazon Leo is one to watch and pilot, not yet one to standardise on.

The public IP problem nobody mentions

This is the single most under-appreciated issue in business satellite, and it is the reason the managed model exists at all.

For IoT that is not a minor inconvenience, it is a hard blocker. Consider what routinely needs an inbound path: a VMS or NVR pulling from remote CCTV, a site-to-site VPN terminating at the edge, a SCADA or BMS head end reaching field controllers, remote management of routers and gateways, IP whitelisting for a customer’s platform, or simply SSH to a device for support. Under CGNAT all of these either fail outright or need brittle workarounds such as dynamic DNS, outbound-only tunnels or reverse relays.

Starlink’s Business and Priority tiers can offer a publicly routable address, but it is typically DHCP assigned and can change without warning, which is not the same as a fixed public IP you can build firewall rules and whitelists around. That gap is exactly what a managed service closes: the provider back-hauls your traffic to its core and hands you a genuine fixed public IP, so the site behaves like any other managed WAN endpoint. It is the least glamorous feature on the datasheet and often the one that decides whether the deployment works.

5G FWA plus LEO: the diverse-path hybrid

LEO is at its strongest when it is not working alone. The most resilient designs pair it with cellular, and increasingly that means 5G fixed wireless access rather than 4G.

The two transports fail in different ways, which is the whole point. 5G FWA gives you low latency and high throughput where there is mast coverage and clear line of sight, but nothing where there is no mast. LEO gives you connectivity almost anywhere with a clear sky, but is more exposed to obstruction, weather and cell congestion. Put them together under an SD-WAN and you get true path diversity: the router steers traffic across whichever link is healthiest, holds sessions up during a failover, and can even bond or load-balance where the application needs it.

The design choice is usually which one is primary. In a town-edge or industrial-estate location with solid 5G, FWA is primary and LEO is the always-there backup that survives a fibre cut or a mast outage. In a genuinely remote site, LEO is primary and cellular is the opportunistic secondary. Either way, the managed overlay and the fixed public IP mean the WAN looks identical to the rest of the estate regardless of which transport is carrying it at that moment. We go deeper on the cellular side of this in our coverage of 5G FWA.

The other layer: NTN IoT and direct-to-device

Everything above is about the fat pipe: broadband-class LEO delivering a megabit-heavy managed WAN to a site. There is a second, quieter satellite story that matters just as much for IoT, and it works completely differently.

Non-terrestrial network IoT, or NTN IoT, is about connecting individual low-power devices directly to satellites with no dish and no site infrastructure at all. Since 3GPP Release 17, the NB-IoT and NR standards have been extended to satellite, so a sensor with the right module and a normal-looking antenna can send small, latency-tolerant messages straight to space. This is the domain of asset trackers, utility meters, pipeline and grid monitoring, livestock collars, environmental sensors and maritime tracking, anywhere outdoors, remote and with a clear view of the sky.

The providers here are a different cast. Skylo runs a 3GPP standards-based NB-NTN service over geostationary capacity and integrates with mobile operators as easily as a roaming agreement, and it has a live Vodafone IoT partnership. Sateliot and OQ Technology are building LEO NB-IoT constellations. Starlink, separately, runs its Direct to Cell service (now Starlink Mobile) for direct-to-handset messaging. Amazon’s move to acquire Globalstar points at the same direct-to-device space.

How it gets deployed and managed

For the broadband layer, the mechanics are refreshingly quick, which is much of the appeal. A managed LEO service typically follows the same shape whichever provider you use.

• Terminal and install: a flat or dish-style user terminal with a clear sky view, powered and cabled to a managed router. Site survey first, ideally, to rule out terrain shading.
• Back-haul and core: traffic is tunnelled to the provider’s core, where the fixed public IP, QoS, VPN and any SD-WAN policy are applied. This is what makes the link a managed WAN rather than a raw internet feed.
• Failover: optional 4G or 5G is configured as an automatic secondary path, holding sessions up when the primary degrades.
• Monitoring and support: proactive monitoring from a NOC, with an SLA and committed information rates rather than best effort. For UK regulated sectors, UK-based support and sovereign data handling are often the deciding factor.
• Lead time: because there is no civils and no line install, a site can be live in days rather than the weeks or months a fixed circuit can take.

The NTN IoT layer is different again: no site install, just a device with a certified module, an NTN-capable SIM or profile, and a platform that presents satellite traffic alongside cellular. In the better implementations the device keeps the same IP whether it is on a terrestrial or a satellite network, so the application does not need to know or care which one carried the packet. The eUICC and remote provisioning that underpins this sits close to our work on eUICC and eSIM.

Where this fits in IoT

Strip away the space glamour and the use cases are the familiar ones, just extended to places terrestrial connectivity cannot reach or cannot be trusted to hold.

• CCTV and security: remote and temporary sites where a fixed public IP is essential for the VMS to reach the cameras and for IP whitelisting. This is the clearest case where CGNAT alone would kill the deployment.
• Utilities and energy: substations, remote plant and metering where secure VPN, fixed IP and remote management are non-negotiable and cellular alone is patchy.
• Construction: pop-up sites that need enterprise connectivity in days, with the whole compound moving on in months.
• Maritime and agriculture: the classic clear-sky, no-infrastructure environments, increasingly split between a LEO-backed vessel or farm hub and NB-NTN sensors in the field or the water.
• Business continuity: a diverse, out-of-the-ground backup path for any site whose fibre single point of failure is a real operational risk.