Part of my job description is travelling, and I had the opportunity to visit London and talk with several customers during the last two years. UK teams want LoRaWAN for the reason everyone does: long range, low power, cheap sensors, and no SIM cards. The appeal is that someone else runs the network and you just deploy devices.
Several networks advertise wide UK coverage, and on a map it looks settled. The problem is that “national coverage” rarely means your specific warehouse, your basement plant room, or your field in the middle of nowhere. Coverage is local, and a map drawn at national scale hides the gaps that matter to you. So before you buy a single sensor, verify coverage for your sites using the options below.
Public versus private, the real choice
In the UK you have two paths. Join a public network and pay per device or per message, or run your own gateways and own the coverage. Most deployments land on one of these based on site count, location, and how much control you need.
Public is faster to start and good when your devices are spread across populated areas. Private is better when your sites are fixed, remote, or sensitive, and when you want coverage that does not depend on anyone else’s roadmap.
The public options and where they are strong
- The Things Network gives you free, community-run coverage that is strong in cities and around active communities, and thinner elsewhere. Good for prototypes and urban pilots.
- Helium offers a decentralized network with pay-as-you-go data and patchy but growing UK presence. Coverage depends on local hotspots, so check your exact postcodes.
- Netmore and other carrier-grade operators run managed UK LoRaWAN aimed at utilities and metering, with coverage and service agreements you can contract for.
- Regional networks exist around specific cities and operators, so a local option may cover your site even when national ones do not.
None of these is “the answer.” The answer is whichever one actually covers your sites, which only testing tells you.
How to verify coverage before you commit
Do not trust the map. Put a single LoRaWAN device, or a coverage tester, at each site and confirm it joins and holds a usable data rate from where the sensors will live, including indoors and below ground if that is where they go. Walk the building. Check the far corner of the field. Coverage that works in the car park and fails in the basement is a failed deployment.
Run this test before you order hardware in volume. A day of testing saves a quarter of returns.
When going private wins
If your sites are fixed, your locations are remote, or your data is sensitive, a private LoRaWAN network is often cheaper and more reliable over three years. You place gateways where you need them, you control uptime, and you stop paying per message. The trade is that you run the network, including the network server.
For many UK industrial and building deployments, one or two well-placed gateways cover everything that matters, which makes private the simpler choice, not the harder one.
The platform sits above the network
Whichever coverage you choose, your application platform should not care. It should accept data from any LoRaWAN network server, public or private, so the coverage decision stays separate from the software decision.
TagoIO ingests from major network servers, including The Things Network and ChirpStack, so you can start on public coverage, move to private gateways later, and keep the same dashboards, alerts, and integrations through the change. The coverage map can evolve without forcing an application rebuild.
Connect your first UK LoRaWAN device on the free plan, or book a demo to talk through public versus private for your sites.
