IoT Solutions

End any week, with one message. No notice period, no exit interview, no fine print. We invoice weekly, so the most you’re ever committed to is the current week.

It’s in your contract: tell us, and we refund that week. No questions, no invoices to dispute, no calls to escalate. The only rule: refunds apply to the most recent week.

Because hours are the wrong metric. If we’re optimizing for hours billed, we’re not optimizing for your outcome. The deal is simpler: every week, we earn the next one. If we don’t, you don’t pay. We’re free to spend zero hours or sixty. What matters is whether you’re blown away.

We work with operators, not lottery winners. If a request would require breaking physics, the law, or a third party’s systems, we say so, and if we can’t align, we walk. The guarantee is mutual: you can fire us any week; we can also fire ourselves.

LoRaWAN for long-range/low-power, MQTT for general telemetry, Zigbee for short-range mesh, and standard HTTP/WebSockets for higher-bandwidth devices. We pick the stack that matches power budget and range, not the one that’s familiar.

Yes. We deploy to AWS IoT Core, Azure IoT Hub, ThingsBoard, or self-hosted MQTT clusters depending on data residency and scale. Provisioning, certificate rotation, OTA updates, device shadowing, and fleet-wide telemetry are first-class concerns from day one, not a v2 problem.

No, we don’t build firmware. We write the decoders and encoders for your IoT devices, build the infrastructure that ingests their data, and handle everything on the application and monitoring side. If you need firmware itself written, we’ll point you to a hardware partner. But the hardware-to-dashboard pipeline above the firmware layer is ours.

Yes, that’s the work. We’ve decoded payloads from devices where the documentation was wrong, missing, or contradicted the firmware. We write per-vendor decoders, normalize everything into a single schema, and build the monitoring that catches when a vendor silently changes their payload format on a firmware update. Multi-vendor reality is the default in real deployments, not the exception.

Single-vendor pilot with 10-50 devices, LoRaWAN gateway, decoder, and a basic dashboard: €18-35k. Multi-vendor pilot with 100-500 devices, fleet management, OTA, and SLA dashboards: €40-90k. City-scale rollouts (5,000+ devices) move into multi-stage programs, €150k+ for software alone with hardware and connectivity quoted separately. We carve out gateway costs, LoRaWAN network fees (Helium, TTN, private), and cellular data plans so they don’t ambush you in month three.

When latency matters (LoRaWAN has uplink-only windows and seconds-to-minutes delivery). When payload exceeds ~50-200 bytes per message. When you need many-to-many messaging. When high duty-cycle telemetry is required (regulatory duty-cycle limits in EU868 cap transmit frequency). For those: NB-IoT or LTE-M for low-power cellular, Wi-Fi when power isn’t constrained, Zigbee or Bluetooth Mesh for indoor mesh, plain MQTT-over-cellular for higher-bandwidth fleets. We tell you which radio the use case actually wants, not the one that’s trending.