The real value in intelligent hardware isn't in the measurement itself — it's in what you can do with the data once you have it. Our IoT platform closes the loop between the devices we build and the decisions our customers make, capturing telemetry from sensors in the field, processing it in Azure, and surfacing the results as reports, dashboards, and automated notifications.
Every engagement is end-to-end: the same team that designs the hardware and writes the control logic also builds and operates the data infrastructure behind it.
Sensing & Measurement
The journey starts with measurement. Our custom-built electronics and programmed PLCs sit at the edge of the physical world, reading sensors and generating the raw telemetry that everything else depends on.
The range of what we measure is broad: temperature across air and water environments, air quality parameters, water flow volumes, device states, and event counts. The right sensors for the application are selected as part of the hardware design — accuracy, range, and long-term stability matter as much as connectivity.
Because the hardware and the data platform are designed by the same team, the telemetry format, update frequency, and data quality are considered together from the outset. There are no integration surprises when the device reaches the field.
Connectivity
Within a solution, sensors communicate with a local hub or gateway using Thread and Matter — open standards designed specifically for reliable, low-power device-to-device communication. The gateway aggregates readings from multiple sensors before forwarding the data onwards.
From the gateway to the cloud, we use WiFi or cellular depending on what the installation environment supports. Both provide a reliable internet path to the Azure platform. Once data reaches the cloud boundary, it travels via MQTT to Azure IoT Hub — a protocol designed for constrained devices on unreliable networks, with built-in quality-of-service guarantees and device management capabilities.
Ingestion & Processing
Azure IoT Hub is the front door for all incoming telemetry. It handles device authentication, connection management, and message routing at scale. From there, Azure Event Hubs carries the data stream to the processing layer — a set of applications we've built and run on Azure Container Apps.
These applications validate and enrich incoming data, route messages to the appropriate storage and processing destinations, evaluate rules for real-time notifications, and manage the device estate. Processed data lands in a NoSQL store structured for efficient querying across large time-series datasets.
The processing layer is where raw telemetry becomes structured, queryable data — ready to be analysed and returned to customers in a form they can act on.
Analysis & Insight
Raw measurements tell you what happened. Analysis tells you what it means.
Individual sensor readings gain meaning when considered alongside each other and over time. A single temperature reading is a data point. Temperature trending upward over 48 hours in a water environment while flow rate drops is a signal worth acting on. Our platform is designed to hold enough context to make these connections.
The analytical questions we help customers answer are specific to their application and customer segment — but the common thread is translating a stream of measurements into a clear picture of what is happening in a piece of equipment or environment, and whether that picture represents normal operation or something that requires attention.
Reporting, Dashboards & Notifications
Insight has no value unless it reaches the right person, at the right time, in a form they can act on.
For reporting and dashboards, we expose a REST API that gives customers and their tools direct access to their data. We recommend Power BI for most visualisation use cases — it connects to our API cleanly and handles the presentation layer well. For customers who prefer a managed option, we have our own reporting tool.
Notifications are handled separately, because some information can't wait for a scheduled report. We support email and SMS alerts for threshold-based events, and a webhook capability that can trigger functions within the customer's own environment — an Azure Function, an AWS Lambda, or a Power Platform flow.
This last point matters: the customer's logic runs in the customer's environment. We supply the signal; they retain full control over what happens next.