← Back to NewsComparison

Public vs Private LoRaWAN Networks: TTN, Helium, or Your Own Gateways?

·7 min read
Rooftop LoRaWAN gateway overlooking a city centre

LoRaWAN is unusual among IoT technologies: you can use someone else's network, or you can build your own. That choice shapes your coverage, your costs, and how much control you have over your data for the whole life of the project. This guide compares the main options and explains when each one makes sense.

The Main Network Models

Broadly, there are four ways to get LoRaWAN coverage for your devices.

Community networks: The Things Network

The Things Network (TTN) is a global community network built largely from gateways that individuals and organisations have chosen to share. It is free to use and excellent for learning and prototyping. Coverage depends on where volunteers have put gateways, and it can change when a gateway owner moves or switches off. The community network has a fair use policy, currently 30 seconds of uplink airtime per device per day and 10 downlinks per day, and no service guarantee. Commercial, supported options are offered separately.

Decentralised networks: Helium

Helium gateways are deployed by individuals who are rewarded for providing coverage, and users pay for data as they use it. Coverage can be wide in some cities, but it depends on where hosts have chosen to place hardware. You have no say in where gateways go or how long they stay there.

Operator-run public networks

In some countries, telecom operators or specialist providers run national LoRaWAN networks. These offer contracts and support, but coverage, pricing, and long-term commitment vary widely between providers. Check the roadmap carefully: your sensors may need the network for ten years.

Private networks

A private network means you have your own gateways where you need coverage, connected to a network server you choose. You decide where coverage goes, how much redundancy you have, and where your data flows. No licence is needed in Europe, because LoRaWAN uses licence-exempt spectrum.

Side-by-Side Comparison

FactorCommunity / DecentralisedOperatorPrivate
Coverage where you need itNot guaranteedWhere the operator has builtYes, by design
Indoor and basement sensorsOften unreliableVariesAdd gateways as needed
Service guaranteeNone on free tiersContractualYours, or your provider's
Usage limitsFair use or pay per messagePer contractOnly regulatory duty cycle
Data pathThird-party infrastructureOperator infrastructureYour choice of network server
Upfront costLowestLowGateways and setup

The Device Lifetime Problem

LoRaWAN sensors are designed to run for five to ten years on a battery. Whatever network you choose needs to outlast them. If a community gateway disappears or an operator changes its terms, your devices lose coverage, and moving them to another network can mean re-registering every device or, in the worst case, visiting each one.

Whichever model you use, make sure you hold the device keys (DevEUI, JoinEUI, and AppKey) yourself. With the keys in hand, devices can be moved to a different network server without being touched.

When a Public Network Makes Sense

  • →Prototypes and proofs of concept where you want to test devices before investing in infrastructure.
  • →Non-critical data where an occasional missed reading does not matter.
  • →Mobile assets that roam across areas where you could never place your own gateways.

When You Want Your Own Gateways

  • →Business-critical data: Alarms, compliance records, or anything you sell on to your own customers with a service level.
  • →Fixed sites: Farms, factories, warehouses, and buildings where you know exactly where coverage is needed.
  • →Difficult locations: Basements, steel buildings, and rural land that public networks rarely cover well.
  • →Data control: Requirements for European data residency or a known, auditable data path.

The Hybrid Approach

The choice is not always either-or. Many organisations run private gateways at their core sites and use roaming or peering arrangements to reach devices that travel beyond them. Peering services such as Packet Broker allow traffic to be exchanged between networks, so a tracker that leaves your site can still be heard elsewhere.

Private Doesn't Have to Mean Self-Managed

The traditional objection to a private network is the work involved: buying gateways, arranging internet at every site, maintaining firmware, and running a network server. Today those layers can be handled separately. EdgePilot manages the gateways, including 4G connectivity, monitoring, and updates. For the network server, ChirpCloud provides hosted ChirpStack, or you can connect to the server you already use.

That gives you the control of a private network with the operating effort closer to a public one. To compare the economics, read our breakdown of the true cost of running LoRaWAN gateways, or see our managed gateway pricing.

Public vs Private LoRaWAN FAQ

Can I use The Things Network for a commercial project?

You can, within the fair use policy, but the community network comes with no coverage or uptime guarantee. For commercial deployments, most teams either pay for a supported service or run their own gateways.

Can I move devices from a public network to a private one?

Yes, provided you have the device keys. OTAA devices can be registered on a new network server and will join through your own gateways. Without the keys, migration becomes much harder.

Do I need a licence to run my own LoRaWAN network in Europe?

No. LoRaWAN in Europe uses the licence-exempt 868 MHz band. You do need to respect the duty cycle and power limits, which our EU868 regulations guide explains.

Want your own network without running it?

EdgePilot gives you private, fully managed gateway coverage that works with the network server of your choice.

Request a Demo