HorizonGrid was started in a borewell shed outside Pollachi, where a 7.5 HP submersible had burned out for the third monsoon in a row — not because the motor was weak, but because the grid that fed it was honest about how rural India delivers electricity.
We are an automation company that grew up downstream of the meter. Our work begins where the utility ends — at the panel, the starter, the float-switch — the thirty-rupee components that decide whether a season's irrigation goes through, or doesn't. Every device we ship is built to take a hit from a transformer four kilometres away and still log the event in plain English the next morning.
The architecture is deliberately boring. Sense → decide → act → report, in that order, with the first three loops closing on the device itself. A Fable starter does not need our cloud to know that its motor is running dry; it needs 50 ms and a current-sense resistor. The cloud is for the parts of the problem that genuinely benefit from hindsight — schedules, trend analysis, the conversation with the farmer — and nothing else.
That discipline shows up as a single radio fabric across the line. Every Horizon device speaks LoRa at 865 MHz, mesh-routed through the IoT Hub, with MQTT bridges out to whatever stack the customer already runs.
We design the enclosures ourselves. We pour potting compound by hand on the first hundred units of every revision. We test in 45 °C ambient because that is what May feels like in Erode, not because a datasheet asked us to.
Industrial design, in our reading, is the practice of taking promises seriously. A motor turns on, or it doesn't. A tank fills, or it floods. We are in the business of making sure the verb that follows the noun is the one the farmer was expecting — quietly, on time, season after season.