Ubidots
Remote asset monitoring software development

Custom remote asset monitoring software, built around your sites

You own the application; we keep everything underneath it running. We build the tank, generator and pump-station apps your field teams work from, on a platform already in production, over cellular, LoRaWAN or the gateways you already run.

Why it is faster

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

Most of a remote monitoring application has nothing to do with your assets. It is ingestion over unreliable links, storage, maps, logins and alerting — and whoever builds it has to maintain it forever.

Building from scratch You pay for all of it

Before anyone draws the site map 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 remote operations

Custom software for the assets you can't visit every day

Every project starts from a list — a handful of screens, a calculation, an integration. These are the ones operators of remote assets bring us most.

Tank level monitoring

Fuel, water and chemical tanks: level, consumption and days of supply per site, so deliveries go where they're needed instead of on a fixed route.

  • Level and consumption per tank
  • Refill and sudden-drop alerts
  • Delivery planning views

Generator monitoring

Run hours, fuel, battery and alarm status for every genset, with an alert the moment one stops reporting rather than when someone happens to notice.

  • Run-hour and service counters
  • Fuel and battery trends
  • Offline detection

Remote equipment monitoring

Pumps, compressors, rectifiers and other equipment in the field: pressure, flow, vibration, temperature and current, trended per asset to show its condition.

  • Asset condition per site
  • Threshold and trend alerts
  • Work orders for field crews

SCADA remote monitoring

Supervisory screens for people who aren't on site: live values, alarms and history from any browser, next to the SCADA you already run.

  • Multi-site overviews
  • Alarm queues with acknowledgement
  • Trend history per tag

Mobile apps for field teams

Branded iOS and Android apps for technicians on the road — built as a customisation of an existing app, so login, navigation and push alerts are reused, not rebuilt.

  • Site list with live status
  • Push alerts and acknowledgements
  • Readings log per site

Industrial AI across your sites

Agents that keep an eye on every site's data, summarise the overnight alarms and answer questions like “which sites stopped reporting?” through Channels like WhatsApp.

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

Connect sites wherever they are

Remote assets rarely sit next to a network cable. We work with the connectivity your sites already have, or specify what they need. Hardware is specified, not supplied.

CELLULAR

LTE-M, NB-IoT and 4G

Sensors and gateways that report over the mobile network, for sites with coverage and no other link.

LORAWAN

Long range, low power

Battery-powered sensors spread across a field, a network or a plant, through a managed network server or your own.

GATEWAYS

PLCs and RTUs on site

Equipment already wired to a controller reports through an edge gateway, over Modbus or MQTT.

SYSTEMS

Your other systems

ERP, CMMS, billing or a customer portal, connected by API or webhook and scoped as its own work package.

Site connectivity:MQTTHTTP / RESTLoRaWANLTE-M / NB-IoTModbus via gatewayWebhooks
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

One connected-product build by our team, and one remote monitoring deployment running on the platform today.

Industrial distributor · connected product

A gas-detection distributor that needed connectivity of its own

Their detectors competed well on sensing and badly on connectivity. After winning a tender, they needed a connected layer in time to deliver it.

5gases decoded per frame
20–30 spublish interval

An Android app turns the phone into the gateway: it pairs over Bluetooth, decodes the manufacturer's binary frame, tracks location and publishes to a central console with a live map and alarm panel. The client owns the source.

Proposals signed August 2026 · dedicated team, sprint demos as acceptance. The app relays detector data; it is not a safety device and does not replace the detector or its alarms.

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.

FAQ

Questions operators ask first

What is remote asset monitoring?

Remote asset monitoring is collecting readings from equipment at sites nobody staffs full time — tanks, generators, pumps, compressors — and turning them into alerts, maps and reports a team can act on. Custom software fits it to your assets, your sites and the way your field teams work.

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.

Which connectivity works for remote sites?

Whatever reaches the site. Sensors and gateways report over cellular (LTE-M, NB-IoT, 4G), over LoRaWAN, or through an edge gateway connected to existing PLCs and RTUs over Modbus or MQTT. We specify the hardware for each site; we don't supply it.

What happens when a site stops reporting?

You find out. Inactivity rules flag any device that stops sending data, and the alert goes out by SMS, email, voice call, Telegram, WhatsApp or webhook, with escalation if nobody acknowledges it.

Can it work alongside our SCADA?

Yes. Remote monitoring software usually complements SCADA rather than replacing it: an edge gateway reads the same controllers, and the platform gives off-site staff live values, alarms and history from a browser or a phone.

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 remote asset monitoring 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 sites you need to see without driving to them

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)