Smart city IoT your utility team can operate.
Bring readings from different city or utility devices into the systems your team already uses. We integrate devices and LoRaWAN network services, translate their messages and make missing or unexpected readings visible to operators.
DIRECT ANSWER
Smart city IoT connects metering, tracking and environmental devices across a city to software the operator can run. This engagement covers LoRaWAN network server work, device evaluation, uplink and downlink codecs, and integration into agreed municipal systems, with a complete handover.
Best for
- Municipal utilities and cities scaling a LoRaWAN network beyond a pilot
- An in-house team that needs engineering hands for infrastructure, devices and codecs
Consider another approach
- Connecting machines inside a plant or production line
- Device firmware development or radio planning without a software scope
Scale is different engineering, not a bigger pilot
The network server layer
Network server and infrastructure
Deploy, extend and scale the network server on infrastructure your team can run, including Kubernetes where the platform has earned it, with gateway and tenant management documented.
Device onboarding
Register devices, manage keys and profiles, and agree who may add, move or retire a device in the field.
Data routing
Route decoded data via MQTT or the network server’s integrations to storage, dashboards and downstream systems, with each integration owned and monitored.
Monitoring
Watch gateways, join failures, silent devices and decoding errors, so a missing water meter shows up as an alert, not as a gap in next month’s report.
Every device, its own dialect
Metering, asset tracking and municipal systems
Assess, build, hand over
Assessment
Receive a network and device inventory, vendor and codec risks, integration targets and a prioritized plan with acceptance criteria.Build and acceptance
Receive the agreed network server changes, codecs with fixtures, integrations and monitoring, tested with real devices and accepted by your team.Handover and support
Receive documentation and a walkthrough for your in-house team. New device integrations and support are agreed separately. This does not establish 24/7 coverage or an uptime SLA.
Public infrastructure must not depend on its contractor
Engineering inside a city-scale LoRaWAN build
IKB documents engineering inside Innsbruck’s in-flight Smart City build alongside IKB’s own team, covering extension of the Kubernetes cluster running ChirpStack, field tests of water meters and cargo-bike trackers, and per-device decoders and encoders, with the platform handed over completely to IKB’s in-house team. It shows that published scope, not a promise of the same result for another network.
These are selected projects, not our full portfolio. We have shipped 100+ products since 2018.
Questions before you start
Scope your smart city IoT project
Describe the network, the device types and the municipal systems involved. A short outline is enough. Do not send device keys, network credentials or resident data in the first message.