Ubidots
Energy & utility software development

Custom energy and utility software, from substation to meter

You own the application; we keep everything underneath it running. We build the network monitoring, alerts and reporting your operations and engineering teams rely on — for grid assets, water networks and distributed energy — on a platform already in production.

Why it is faster

A development shop starts with an empty repository. We start with a platform in production.

Most of a utility application has nothing to do with the network. It is ingestion, storage, logins, alerting and the history regulators ask for — and whoever builds it has to maintain it forever.

Building from scratch You pay for all of it

Before anyone builds the feeder view you asked for, a team builds — and then maintains — the whole stack underneath it.

Building on Ubidots You pay for the top

The work begins at your data model and your interface, because everything below that line already exists and is under support.

Reporting and alerting already running
Authentication, users and roles already running
Time-series storage already running
Device ingestion and protocols already running
Security, uptime and upgrades our job
What we build for utilities

Custom software for every asset on the network

Every project starts from a list — a handful of screens, a calculation, an integration. These are the ones utilities, renewable operators and their integrators bring us most.

Transformer and substation monitoring

Oil and winding temperatures, load against rating and alarm status from transformers and substations, so the units running hot and heavy are visible before they become an outage.

  • Top-oil and winding temperature
  • Load against rating
  • Breaker and alarm status

Grid and feeder monitoring

Load and voltage along the distribution network, outage and restoration events, and power quality where the meters report it, in one view for operations and engineering.

  • Load and voltage per feeder
  • Outage and restoration events
  • Power quality, where meters report it

Smart meter data and network losses

Meter data from your head-end system next to what the network delivered, so the energy balance per zone shows where losses are and which consumption patterns are worth investigating.

  • Meter data by API from the head-end
  • Energy balance per zone
  • Consumption patterns worth investigating

Water and wastewater networks

Pumping stations, tanks, pressure and flow across the network, with alerts when a pump draws too much current, a tank runs low or a station stops communicating.

  • Pump and station status
  • Tank levels, pressure and flow
  • Night-flow leak indicators

Solar, storage and distributed energy

Inverters, batteries and the meters at the grid connection, with production against expected, self-consumption and the value of what is exported at the hourly price.

  • Inverter and battery status
  • Production against expected
  • Grid export and its value

Industrial AI for utility operations

Agents that keep an eye on every asset, write the morning network summary and answer questions like “which feeders ran above 90% of rating this week?” through Channels like WhatsApp.

  • Morning network summaries
  • Questions answered from live data
  • Actions through Connectors
Connectivity

Connect every station, meter and system

A utility's data lives in substations and pumping stations, in meter head-ends and in SCADA. We work with what your network already has, or specify what it needs. Hardware is specified, not supplied.

STATIONS

Substations and pumping stations

RTUs, PLCs and monitors at each station, read through an edge gateway over Modbus or MQTT.

FIELD

Remote assets

Pole-mounted transformers, tanks and sensors along the network, over cellular (LTE-M, NB-IoT, 4G) or LoRaWAN.

METERS

Meter head-ends

Smart meter data from your head-end or meter data system, by API or scheduled export.

SYSTEMS

SCADA, GIS and billing

SCADA historians, GIS, work orders and billing, connected by API or webhook and scoped as their own work package.

Connectivity:Modbus via gatewayMQTTLTE-M / NB-IoTLoRaWANHTTP / RESTWebhooks
You own it. We run it.

Completely custom, without a maintenance backlog

A platform you build yourself is worth the most on the day it ships. After that, someone owns its uptime, its security patches and every dependency in it — permanently.

Here, everything above the line is yours: the data model, the screens, the brand. Everything below it is ours to run, under support, and it keeps improving underneath you without landing on your roadmap.

Where a custom application is the deliverable, the code is written as work for hire. You own the repository and have access to it throughout the build, not at the end.

How an engagement runs

Five stages, and the number gets tighter at every one

Nobody can price a conversation accurately. So we tell you how wide the estimate is at each stage, and narrow it by doing work rather than by guessing harder.

Qualification

A short call to capture scope and sizing, and to put an indicative range on the work.

±100%

Specification

Your requirements document — or a fixed-fee, timeboxed discovery that produces one.

±50%

Estimation

Every requirement mapped to a work package, each one sized. A range we can defend line by line.

±50%

Prototype

Something you can use on the real platform before the build is committed. Then re-estimated.

±25%

Build

Agreed scope, stated exclusions, delivered in reviewable increments with monthly effort reporting.

Fixed scope

Discovery, when you need one, is a fixed fee credited in full against the project that follows. Build phases run under a not-to-exceed ceiling you set: work stops for your approval at the ceiling rather than running past it.

On the role of AI

AI compresses the build. Engineers still own the quality.

It would be easy to overclaim here, so plainly: AI-assisted development compresses the build step, which is the part that used to dominate a quote.

It does not compress the senior specification in front of it, or the code review and QA after it. Those are why the result is maintainable, they are done by engineers, and they sit inside the same rate.

Spec
Build — AI-compressed
Review
QA
15%45%15%25%

Typical effort split of a custom build. The cyan block is where the time goes away; the rest is the human quality floor.

In the field

What this looks like in practice

A city water utility and an energy integrator, both running on the platform today.

Water utility · pumping stations

A city's water and wastewater stations, monitored remotely

Interagua runs the potable water and sewer systems of Guayaquil, Ecuador's largest city. Its stations are monitored on the Ubidots platform, with alerts when a pump draws too much current, stays offline too long or a station loses communication.

170+stations
15%lower energy costs
18%fewer on-site inspections

Paper-based processes were eliminated along the way. Operators get a single-screen view of station health, with drill-down into each pump's performance and history.

Designed and deployed by Nextergy, an engineering firm and Ubidots partner, on the Ubidots platform; published as a case study on the Ubidots blog. Not a build by our development team.

Electrical integrator · solar, storage and meters

An integrator reselling energy monitoring under its own name

An electrical and automation contractor in Northern Europe monitors solar plants, battery storage, utility smart meters and water pumping stations for its clients — retail chains, a car dealer group and a municipality — under its own brand.

12client organisations
30inverters at the largest site

PLCs at each site read inverters, batteries and meters over Modbus. Derived variables on the platform add up plant output, self-consumption and the energy sold back to the grid, valued at the hourly spot price.

Built and run by the integrator on the Ubidots platform since 2020. Not a build by our development team.

FAQ

Questions utilities ask first

What does IoT do for energy and utility companies?

It shows what the network is doing between the control room and the customer: transformer and substation temperatures and load, feeder loading, meter data, pumping stations, tanks and pressure, and distributed generation. Custom software brings those into one view, alerts the right crew, and keeps the history engineering and regulators ask for.

Does it replace our SCADA?

No. It works alongside it. SCADA keeps controlling the network; this layer reads from it, from field devices it doesn't reach and from vendor platforms, and puts everything in front of the people who aren't in the control room. It monitors and alerts; it doesn't operate the grid or the network.

Why is building on Ubidots faster than building from scratch?

Because the work starts at your data model and your interface, not at an empty repository. Ingestion, time-series storage, authentication, roles, alerting and reporting already exist and are in production. AI-assisted development then compresses the build step itself, while specification, code review and QA stay with senior engineers.

Can it keep the long history utilities need?

Yes. Long-term history is available through the Extended Storage add-on on Enterprise plans, so years of network and consumption data stay available for engineering studies, regulatory filings and audits. What goes into a filing stays with your team.

Can integrators deliver it to utilities under their own brand?

Yes. Each utility, municipality or client gets its own organisation, users and roles, and the application carries your brand on the web and on mobile. Your team sees every client; each client sees only its own network.

Who maintains the software after it is delivered?

The infrastructure underneath your application — ingestion, storage, orchestration, security, availability and upgrades — is run and maintained by Ubidots under your platform subscription. You own the application layer. Changes to it after delivery are scoped as new work, the same way the original build was.

Do we own the code?

On engagements where a custom application is the deliverable, the code is written as work for hire: you own the repository and the source, with access throughout the build rather than at the end. The platform underneath stays Ubidots'.

How much does custom energy and utility software cost?

It depends on scope, and an honest first answer is a range rather than a number. We give that range on the first call, then narrow it at each stage: specification, work-package estimate, and a prototype you can use before the full build is committed. Discovery, when you need one, is a fixed fee credited against the project.

Do we need a Ubidots subscription?

Yes. The application runs on the Ubidots platform, and the subscription is scoped and quoted separately from the development work. Development is not part of a subscription, and a subscription is not part of a development engagement.

Start with one message

Tell us which parts of your network you can't see today

Tell us what you need. We'll get back to you to work out whether there's a project here, and put a range on it that's honest about how wide it still is.

Get in Touch

Get in Touch

Get the best of our product and team

Main IoT verticals (select up to 3)