Two gateway types and two ways of counting
In the standard deployment the watch talks to the gateway over the InnerWeb protocol, and the gateway translates the frames into HTTP requests to the system. Such a gateway has a single radio and costs roughly 100 PLN. These are indicative ranges from 2025-2026 deployments; pricing is individual.
The LoRaWAN option uses a gateway with an SX1302 or SX1303 concentrator with 8 EU868 channels and ADR rate adaptation, and the network server is ChirpStack under the MIT licence, run on the customer's own infrastructure. The gateway cost is roughly 700-900 PLN, and capacity grows from a few hundred to over 1000 watches per gateway. LoRaWAN is an option on request, not the standard.
Why comparing the gateway price alone is misleading
A simple gateway is seven to nine times cheaper, but it covers fewer devices, so more of them are needed. The real cost is the gateway price multiplied by the number of gateways needed to cover the site, plus power and the link of each of them. Only this total allows the two options to be compared.
What the cost of covering the site consists of
The price of the gateway itself is only one item. The cost of coverage consists of gateways, power, antennas, the way the gateway connects to the internet, and the deployment work. Gateways without Wi-Fi need a backhaul: a repeater gateway, an LTE module, or Ethernet or PoE in halls with cabling.
- Gateway: about 100 PLN for the simple one against about 700-900 PLN with a LoRaWAN concentrator.
- Power supply and an enclosure suited to the mounting place, especially outdoors.
- Link: Wi-Fi, Ethernet or PoE, an LTE module, or a repeater.
- ChirpStack network server in the LoRaWAN option: running cost on the customer's own infrastructure.
- Deployment work: frequency plan, mounting, coverage test.
Gateway hardware: simple variant and LoRaWAN, example calculation
When the pricier LoRaWAN gateway pays off
LoRaWAN returns to the table when a site exceeds roughly 200-300 watches or the customer requires the standard. On small sites the watch stays on the InnerWeb protocol, and the backhaul is built only at the first site without full Wi-Fi coverage, by default as a repeater gateway.
The choice of protocol is made per site: small sites stay on the InnerWeb protocol, large ones may get LoRaWAN, and the system and the panel are shared. There is no mixed mode on a single watch. In the LoRaWAN option the watch changes only the firmware of the radio layer and the hardware stays, so the switch does not require replacing devices.
Hidden cost: SOS in LoRaWAN
In LoRaWAN the system response returns in a window after the next uplink, so after an SOS the watch sends an extra empty uplink after roughly 3-5 s to receive the result. This solution must be designed and tested, which is a cost in work, not in hardware.
Example calculation for a mid-sized plant
The calculation below uses explicit assumptions and serves to compare orders of magnitude, not as an offer. The value of 100 PLN for a simple gateway and 800 PLN for a LoRaWAN gateway is the midpoint of the 700-900 PLN range. The assumed number of gateways is an example; in a real project it follows from a coverage test on the site.
The result shows that the hardware of simple gateways is cheap even when there are more of them, so the choice is decided not by the gateway cost but by the number of watches, the customer's requirements regarding the standard, and the running cost of the network server.
Gateway hardware: 6 simple or 2 LoRaWAN
| Parameter | Value |
|---|---|
| Price of a simple gateway | 100 PLN/unit |
| Price of a LoRaWAN gateway (midpoint of the 700-900 PLN range) | 800 PLN/unit |
| Number of simple gateways to cover the site | 6 units |
| Number of LoRaWAN gateways to cover the site | 2 units |
Result: Hardware: 6 x 100 PLN = 600 PLN against 2 x 800 PLN = 1600 PLN. Difference about 1000 PLN in favour of the simple gateways, before power, link and network server costs.
Note: Example calculation, indicative ranges from 2025-2026 deployments; pricing is individual. The number of gateways follows from a coverage test.
Video
Frequently asked questions
Is LoRaWAN the standard in the offer?
No. The standard is the InnerWeb protocol, and LoRaWAN with the ChirpStack server is an option on request, usually for sites above roughly 200-300 watches or when the customer requires the standard.
Does switching to LoRaWAN require new watches?
No. The firmware of the radio layer changes and the hardware stays. The inactivity logic, the BLE scan and the application data format remain unchanged.
Can both protocols be mixed in one plant?
The choice is made per site. There is no mixed mode on a single watch, and the system and the panel are shared by both variants.
Pricing radio coverage for your site
Based on the site map we will count the number of gateways and compare both options. Let us arrange a call about your site.
Let's talk