Ubidots
Vibration analysis software development

Custom vibration analysis software, from sensor to spectrum

You own the application; we keep everything underneath it running. We build the vibration trends, spectra and fault alerts your analysts and technicians work from — for motors, pumps, fans and gearboxes — 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 vibration analysis application has nothing to do with vibration. It is ingestion, storage, logins and alerting — and whoever builds it has to maintain it forever.

Building from scratch You pay for all of it

Before anyone builds the spectrum view your analyst 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 vibration programs

Custom software for every machine that turns

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

Wireless vibration monitoring

Triaxial wireless sensors on every measurement point, reporting velocity, acceleration and temperature on a schedule, so the machines between routes are watched too.

  • Velocity and acceleration RMS
  • Severity limits per machine class
  • Trends per measurement point

Spectrum and waveform analysis

FFT spectra and time waveforms, where the sensor captures them, viewed in the app with the machine's fault frequencies marked, and compared against last month's.

  • Spectra per measurement point
  • 1×, 2× and bearing frequency markers
  • Spectrum comparisons over time

Fault rules for bearings, imbalance and misalignment

Rules written per fault type, on the features the sensors send, so an alert says what probably changed and attaches the data an analyst needs to confirm it.

  • Rules per fault type
  • Bearing defect frequency tracking
  • Alerts with the evidence attached

Route and online data in one place

Readings from portable analysers on a route land next to the online sensors, on the same machine and the same timeline, instead of in a separate program.

  • Route data uploaded by API or file
  • One timeline per machine
  • Measurement points matched to assets

Apps for analysts and technicians

A review queue for analysts and branded iOS and Android apps for technicians — built as a customisation of an existing app, so login, navigation and push alerts are reused, not rebuilt.

  • Analyst review queue
  • Machine condition reports
  • Push alerts and acknowledgements

Industrial AI across your vibration data

Agents that keep an eye on every measurement point, summarise what changed overnight and answer questions like “which machines moved into a higher severity band this month?” through Channels like WhatsApp.

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

Connect every measurement point

Vibration data comes from wireless sensors, permanently installed systems and portable analysers. We work with what your plant already has, or specify what it needs. Hardware is specified, not supplied.

WIRELESS

Wireless vibration sensors

Battery-powered triaxial sensors over LoRaWAN or a local gateway, mounted on the machine with no cabling to the panel.

ONLINE

Installed monitoring systems

Overall levels and alarms from systems already wired to your critical machines, read through an edge gateway over Modbus or MQTT.

PORTABLE

Route-based analysers

Readings and spectra exported from portable analysers, loaded by API or file and matched to the same measurement points.

SYSTEMS

CMMS and ERP

Your maintenance and asset systems, connected by API or webhook and scoped as their own work package.

Connectivity:LoRaWANModbus via gatewayMQTTHTTP / RESTFile import via APIWebhooks
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 current engagements, 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 reliability teams ask first

What is vibration analysis?

Vibration analysis is measuring how a machine vibrates — overall levels, frequency spectra and waveforms — to find out whether it is healthy and, if not, what is wrong: imbalance, misalignment, looseness or a failing bearing. Custom software fits it to your machines, your measurement points and the way your analysts and technicians work.

What's the difference between vibration monitoring and vibration analysis?

Vibration monitoring trends overall levels and raises an alarm when they cross a limit; it tells you that something changed. Vibration analysis looks at the spectrum and waveform to work out why. Most programs need both: monitoring on every machine, analysis on the ones that alarm.

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.

Do wireless sensors send full spectra?

Most send features computed on the sensor — velocity, acceleration, temperature and a few peak frequencies — because that is what a battery and a low-power network can carry. Some can also capture a spectrum or waveform on a schedule or on demand. We specify sensors for what each machine needs, and the application handles both kinds of data.

Do you provide vibration analysts?

No. We build the software; the analysis stays with your reliability team or the service provider you already work with. What changes is that they review data from every machine in one place, with the evidence attached to each alert, instead of collecting it on a route first.

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 vibration analysis 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 machines you measure today, and how

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)