Web applications, data platforms, APIs, cloud infrastructure — built to plug into the messy real world and grow from a four-week MVP into something quietly running an entire estate. The dashboard is the easy 10%.
Energy software almost never gets to live in a clean room. It has to talk to SCADA, IoT gateways, building management systems, market APIs, and a legacy database somebody stood up in 2008 and never wrote down. Most of the real engineering is in surviving that contact with reality — keeping the thing reliable when every feed it depends on is, in its own particular way, slightly broken.
“The hard part of energy software isn't the dashboard — it's everything behind it that has to be real-time, reliable and honest about the data.”
Map the systems, data sources and users. Define the smallest platform that delivers real value.
Choose a stack that scales: cloud, data model, APIs, security and integration points.
Focused sprints with working software in front of you early and often.
Connect to SCADA, IoT, BMS and market data. Make the real-world plumbing reliable.
Harden for production and grow — same team, no handoff, no knowledge loss.
Platforms quietly running live energy assets right now.
Disparate site data unified into one cloud-native platform on Azure, Kubernetes and Docker — MVP in four weeks, scaled across the estate.
View project →MQTT → Telegraf → InfluxDB ingestion behind a bespoke Grafana portal with dashboards and live schematics, on AWS.
View project →An Azure IoT platform managing thousands of remote gateways across 30+ parks in six countries, with billing and device management.
View project →A revenue-grade meter feeding a browser app that turned readings into the metrics behind a 25% average saving across 300 facilities.
View project →Yes — that's usually the core of the work. We bridge SCADA, building management systems, IoT gateways and market APIs over protocols like MQTT and MODBUS, and make that integration reliable, not brittle.
That's our default. We ship the smallest platform that delivers real value — often a four-week MVP — then harden and scale it for production with the same team, so nothing is lost in a handoff.
You do. Full IP ownership of the code, designs and deliverables transfers to you as standard.
Typically Python and modern web front-ends on AWS or Azure, with Kubernetes/Docker, time-series stores like InfluxDB, relational databases, and Grafana for visualisation — chosen per project, not by default.
From a four-week MVP to an enterprise estate — built to integrate and built to last.