Ubidots
Equipment-as-a-service software development

Custom equipment-as-a-service software, from machine to invoice

You own the application; we keep everything underneath it running. We build the usage metering, customer portals and service workflows that let you sell your machines by the hour, the cycle or the outcome — 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 an equipment-as-a-service application has nothing to do with your equipment. It is ingestion, storage, logins, one account per customer and alerting — and whoever builds it has to maintain it forever.

Building from scratch You pay for all of it

Before anyone builds the usage report your first customer 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 equipment makers

Custom software for selling what your machines do

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

Usage metering and billing data

Run hours, cycles, throughput or output measured on the machine and rolled up per unit, customer and contract, so billing comes from data both sides can see rather than from estimates.

  • Usage per unit and per contract
  • Plans, allowances and billing periods
  • Billing-ready exports to your ERP

Customer portals under your brand

Each customer gets its own space to see its machines, usage and service history, with your logo, colours and domain, and users and roles it manages itself.

  • One organisation per customer
  • Your brand, your domain
  • Customer users and roles

Uptime and service-level tracking

Availability per unit measured against what each contract commits to, so you know where you stand before the customer asks, and the monthly report writes itself.

  • Availability per unit
  • Targets per contract
  • Monthly service reports

Remote service and diagnostics

Your service team sees what a machine was doing before it stopped, from the office, so the technician who goes arrives with the right part — or doesn't need to go at all.

  • Remote diagnostics per unit
  • Alerts to your service team
  • Service history per machine

Installed-base view for your team

Every unit at every customer in one place: where it is, how hard it works and which accounts are growing into a bigger plan or quietly using less.

  • Installed base by customer and region
  • Usage trends across the fleet
  • Renewal and upsell signals

Industrial AI across your installed base

Agents that keep an eye on every unit, write each customer's monthly summary and answer questions like “which customers are close to their plan limit?” through Channels like WhatsApp.

  • Monthly summaries per customer
  • Questions answered from live data
  • Actions through Connectors
Connectivity

Connect every unit, at every customer

Your machines run on someone else's site, behind someone else's network. We work with the controllers and modules your equipment already has, or specify what it needs. Hardware is specified, not supplied.

CELLULAR

Independent of the customer's network

LTE-M, NB-IoT or 4G modules, so a unit reports from day one without waiting on the customer's IT department.

CONTROLLERS

The machine's own PLC

Run hours, cycles, states and faults read from the controller through an edge gateway, over Modbus or MQTT.

FIRMWARE

Devices you build

Your own electronics publish straight to the platform's API over MQTT or HTTP, with the endpoints in your firmware.

SYSTEMS

Billing, ERP and CRM

Your billing, ERP, CRM or field-service software, connected by API or webhook and scoped as its own work package.

Connectivity:LTE-M / NB-IoTMQTTHTTP / RESTModbus via gatewayLoRaWANWebhooks
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.

Engagements in delivery

What this looks like in practice

Two equipment makers turning their hardware into a connected product, described by what was asked and how it is being built.

Equipment manufacturer · white-label platform

An indoor air quality manufacturer building its own platform

They arrived with a finished requirements document and one real question: not "can you build this", but "how much of this do we have to build at all?"

220requirements classified
89.5%deliverable on the platform
~25work packages

145 requirements ship through configuration and 52 through the extension layer. A working prototype was built on the real platform, not in a design tool, and became a delivery asset in its own right.

Enterprise white-label licence closed August 2026 · delivery under way

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.

FAQ

Questions equipment makers ask first

What is equipment as a service?

Equipment as a service is selling what a machine does — hours of operation, cycles, output or uptime — by subscription or by usage, instead of selling the machine outright. The manufacturer keeps ownership, so it needs reliable data on how each unit is used and how it is running, to bill for it and to service it. Custom software fits that to your machines, your contracts and your customers.

What is servitization?

Servitization is the shift by manufacturers from selling products to selling services built around them: monitoring, maintenance, uptime commitments and pay-per-use. Equipment as a service is one form of it. All of them depend on connected equipment and on software your customers can actually use.

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.

Does the software send the invoices?

No. It meters usage per unit, customer and billing period and produces billing-ready data; your billing system or ERP issues the invoice. Connecting the two is scoped as its own work package, so usage reaches billing without anyone retyping it.

Can each customer see only their own machines, under our brand?

Yes. Each customer gets its own organisation with its own users and roles, and the application carries your logo, colours and domain. Your team sees the whole installed base; each customer sees only theirs.

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 equipment-as-a-service 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 what you want to sell by the hour

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)