
LoRaWAN consulting: when it fits, and public vs private trade-offs.Is LoRaWAN right for your site? Many find out too late.
LoRaWAN consulting with clear public vs private LoRaWAN advisory. Coverage, density, battery and backhaul scored before anyone buys gateways. Independent of network suppliers.
We don't sell hardware, so our advice stays independent. If you're scoping a LoRaWAN deployment and want an independent second opinion, this is what we do.
Free 30-minute call with an adviser · written proposal with the price after · fixed-scope engagements from £3k.
LoRaWAN programmes stall when coverage is assumed and device management is an afterthought.
RF survey rigour
Indoor industrial multipath is not a countryside gateway brochure. Survey the plant.
Join and lifecycle
OTAA keys, firmware and battery retirement need an owner. Orphans kill trust in the map.
Public vs private
Choose for data gravity and SLA, not ideology. Document the trade-offs for security review.
What we do in a LoRaWAN engagement
Three stages, mapping to the TRACIO programme method. Stage 1 · Scope, architect, cost: use-case validation, predictive RF coverage modelling, public vs private vs hybrid network choice, gateway and device sizing, integration architecture, 5-year TCO.
Stage 2 · Pilot: independent pilot design, success criteria, validation against accuracy / battery-life / coverage targets in production environments.
Stage 3 · Production rollout: full deployment plan, supplier management, integration with enterprise systems, handover to managed-services partner.
We work with public carriers (Orange, Bouygues, KPN, Senet, Everynet), private network platforms (Actility ThingPark, The Things Industries, ChirpStack) and devices across the LoRaWAN ecosystem.
Use cases we cover
Outdoor asset and returnable-container tracking: containers, livestock, plant equipment, vehicles. Hybrid LoRaWAN + GNSS designs (Semtech LR1110 / LR2021) for multi-year battery life.
Agriculture and farm sensing: soil moisture, livestock health, equipment location across hectare-scale fields.
Smart-city infrastructure: parking, waste, environmental, lighting. Remote equipment monitoring: utility / oil-and-gas / energy network sensors.
Industrial telemetry: factory ambient and process sensors, tank levels, run-hours. Building and facility management: occupancy, temperature, air-quality, restroom and meeting-room utilisation.
Public, private or hybrid
We don't have a default answer. It depends on use case, geography, security posture and economics. Public LoRaWAN for assets that move across regions where carrier coverage exists.
Private LoRaWAN for sensitive in-site applications (defence, regulated industries, large factories). Hybrid for distributed enterprises with both. See Public vs private LoRaWAN for the deeper treatment. We model both economics and architecture in stage 1.
Device selection and silicon
Semtech dominates LoRa silicon. Their LR1110 (with GNSS sniffing) and LR2021 (with GNSS + Wi-Fi sniffing) chips enable hybrid LPWAN-positioning at multi-year battery life: a material improvement for outdoor asset tracking.
We advise clients evaluate devices across the LoRaWAN ecosystem (Adeunis, Abeeway, Browan, Dragino, Elsys, Kerlink, Multitech, Tektelic, Yabby) for fit to specific use cases.
Integration architecture
LoRaWAN deployments connect to enterprise systems via the network server. REST, MQTT, AWS IoT, Azure IoT, Google Cloud IoT integrations are mature.
We design integration patterns into WMS, ERP, IWMS, BMS, asset-management and ITSM systems. See RTLS, RFID and IoT integrations for our enterprise patterns and Public vs private LoRaWAN for network architecture detail.
Why hire us rather than the carrier or supplier
Carriers and suppliers will tell you their option is the right one. We don't have that bias. We have no economic stake in the network choice or device selection.
We advise on deployments from small device pilots to large multi-site rollouts, and we know where the costs and pitfalls are. See our independence policy for our independence policy.
Who sells LoRaWAN advice and why the network choice is the real decision.
Carriers (Orange / Objenious, Bouygues, KPN, Swisscom, Senet, Everynet and peers) will correctly push public LoRaWAN wherever their coverage map looks strong. Network-server suppliers (Actility ThingPark, The Things Industries, ChirpStack specialists) and gateway OEMs will correctly push private. Device manufacturers with Semtech LR1110 / LR2021 silicon will correctly push hybrid GNSS-plus-LoRaWAN trackers. Each is right about their product and silent about the five-year TCO when device counts, sovereignty rules or coverage gaps break their default.
Independent LoRaWAN consultancies exist, but many still profit from gateways, LNS licences or managed SaaS. The structural bias shows up in the model: public looks cheap at fifty devices; private wins above roughly 500-2,000 devices per site or outside carrier coverage; hybrid fits distributed estates with both. Those breakpoints only appear when someone models both architectures against your geography, security posture and integration targets (WMS, ERP, IWMS, BMS, ITSM).
What programmes get wrong: picking the network from a coverage screenshot, then discovering indoor industrial multipath, backhaul ownership and device certification were never scoped. Or locking a managed LNS subscription that scales linearly with every sensor while ownership of ChirpStack would have been a fixed cost.
We have no stake in public, private or hybrid. Stage-one work models economics and architecture side by side; device shortlists stay open across the ecosystem. See public vs private LoRaWAN for the deeper treatment.
Frequently asked questions
Do you sell or resell hardware?
No. See our independence policy for the full policy and public commitments.
Is your LoRaWAN consulting advisory-only or end-to-end?
Both, depending on engagement. We lead the programme end to end (scoping, supplier management, deployment oversight, integration handover) for clients without internal IoT capability. We advise alongside internal teams for clients building capability.
Can you work with our existing LoRaWAN partner?
Yes, often. We work alongside your existing integrator, carrier or platform partner as the independent advisory layer. Independent by design.
How long is a typical LoRaWAN engagement?
Scoping engagement: 4-8 weeks. Pilot: 8-12 weeks. Production deployment: 12-24 weeks depending on scale. You can engage us for one stage or several.
How does public vs private LoRaWAN advisory treat NB-IoT / LTE-M?
Yes, see LoRaWAN: how it works, and where it fits for the LoRaWAN vs cellular IoT comparison. We advise clients choose between LoRaWAN, NB-IoT, LTE-M and hybrid stacks during stage 1.
Last updated: