IKB
City-wide IoT backbone for Innsbruck. Joined the build, scaled it, handed it back, still on call.
IKB (Innsbrucker Kommunalbetriebe) is the municipal utility of Innsbruck, Austria, water, energy, waste, telecom. They had a Smart City build underway and needed someone to take it to city scale, not write another slide deck about it.
Overview
IKB (Innsbrucker Kommunalbetriebe) is the municipal utility of Innsbruck, Austria, water, energy, waste, telecom. They had a Smart City build underway and needed someone to take it to city scale, not write another slide deck about it.
What's the challenge?
Take an in-flight Smart City build to city scale. Real streets, real devices from real vendors, none speaking the same dialect. LoRaWAN backbone on Kubernetes to harden and extend. Multi-manufacturer hardware to evaluate and integrate. Per-device uplink and downlink payloads to decode. Connectivity drops, divergent gateway firmwares, datasheets that lied.
Every device, its own dialect. And every device, its own clock.
IKB had work underway when we joined. Extending the LoRaWAN backbone to production scale was tractable. Writing codecs against datasheets that lied was not. Every manufacturer handled packets its own way. Some devices spoke daily, some quarterly, some only when a water meter detected a leak. A wrong byte cost a full cycle to verify. We built a per-vendor codec workbench, captured real packets, replayed them offline.
What We Did
We joined an in-flight Smart City build and extended it to city scale against multi-vendor reality where no two devices speak the same dialect. One team across the stack, more devices, the research, decoders, vendor calls, so nothing fell between the seams. Year one: extended the Kubernetes cluster running ChirpStack, field testing on water meters and cargo-bike trackers, the uplink decoders and downlink encoders, hardened the infra. Years two to four: handed the platform to IKB’s in-house team and stayed on as support, new device integrations, the Grafana stack, field connectivity, manufacturer calls.
Outcomes
Production architecture
The diagram illustrates a simplified high-level architecture and omits confidential implementation and security details.
What We Learned
City-scale IoT is a coordination problem dressed up as a hardware problem. Protocols are tractable. Datasheets are not. Every vendor lies a little, every payload is its own dialect. One team across the stack is the only path that works.
Want outcomes like this?
Tell us what you're building. We'll tell you whether we're the right team for it.
Book a call