LoRaWAN consulting — when it fits, and public vs private trade-offs.

Three stages, mapping to /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: vendor-neutral pilot design, success criteria, validation against accuracy / battery-life / coverage targets in production environments.

Stage 3 — Production rollout: full deployment plan, vendor 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.

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.

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 /comparisons/public-vs-private-lorawan for the deeper treatment. We model both economics and architecture in stage 1.

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.

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 /integrations for our enterprise patterns and /comparisons/public-vs-private-lorawan for network architecture detail.

Carriers and vendors will tell you their option is the right one. We don't have that bias — our fees come from clients only and we have no economic stake in the network choice or device selection.

We've advised enterprises on deployments ranging from 50-device pilots to 50,000-device rollouts; we know where the costs and pitfalls are. See /about/independence for our independence policy.

Carriers (Orange / Objenious, Bouygues, KPN, Swisscom, Senet, Everynet and peers) will correctly push public LoRaWAN wherever their coverage map looks strong. Network-server vendors (Actility ThingPark, The Things Industries, ChirpStack specialists) and gateway OEMs will correctly push private. Device makers 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 earn margin on 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 — fees come from clients only. 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.