Ubidots
Smart city software development

Custom smart city software, from street to control room

You own the application; we keep everything underneath it running. We build the monitoring, alerts and public views your operators and citizens rely on — for street lighting, water, air quality and roads — 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 smart city application has nothing to do with the city. 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 control-room 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 cities

Custom software for the systems a city runs on

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

Smart street lighting

Connected luminaires and lighting controllers from one or several vendors in a single view, with failures, dimming schedules and energy per district or corridor.

  • Luminaire status and failures
  • Dimming schedules and energy
  • Several vendor platforms in one view

Water and wastewater networks

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

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

Air quality and environmental monitoring

Particulates, gases and noise from stations across the city, with limits per station and public dashboards residents can check for themselves.

  • PM2.5, PM10, NO₂ and noise
  • Limits and alerts per station
  • Public dashboards

Parking, traffic and roadside equipment

Parking occupancy, traffic counts and the equipment that keeps roads running — generators, UPS units, signs and equipment rooms — watched from the same place.

  • Parking occupancy
  • Traffic counts per corridor
  • Roadside power and equipment rooms

Waste and public assets

Fill-level sensors on containers so collection follows what is actually full, and status for the public assets crews otherwise check by driving past.

  • Container fill levels
  • Collection by need, not by schedule
  • Public asset status

Industrial AI for the control room

Agents that keep an eye on every system, write the overnight summary for the control room and answer questions like “which corridors had lighting failures this week?” through Channels like WhatsApp.

  • Overnight summaries for operators
  • Questions answered from live data
  • Actions through Connectors
Connectivity

Connect every system, whoever made it

A city's infrastructure comes from many vendors, installed over many years. We work with what is already on the street, or specify what is needed. Hardware is specified, not supplied.

CITY-WIDE

Low-power sensors

Air quality, parking, level and fill sensors over LoRaWAN or NB-IoT, battery-powered and spread across the city.

VENDOR PLATFORMS

Lighting, parking and meters

Systems that already have their own platform, connected through their API so their data lands in the same view.

ON SITE

Stations and equipment rooms

Generators, UPS units, pumps and controllers, read through an edge gateway over Modbus or MQTT.

SYSTEMS

GIS, work orders, open data

Maps, maintenance systems and open-data portals, connected by API or webhook and scoped as their own work package.

Connectivity:LoRaWANLTE-M / NB-IoTMQTTHTTP / RESTModbus 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 city water network running on the platform today, and one road-infrastructure project our team has specified.

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.

Highway concessionaire · road infrastructure

One control room for lighting, power and roadside equipment

A toll-road operator was watching its corridor through five separate vendor platforms: smart streetlights, backup generators, solar inverters, UPS units and the air conditioning in its equipment rooms.

181smart streetlights, growing to 1,000+
14backup generators

The design brings every system into one monitoring centre. The operator's team feeds on-site equipment through its own gateway; we connect the lighting vendor's platform by API and build the interface on top.

Specified and estimated; proposal under review. No figures from operation yet.

FAQ

Questions cities and operators ask first

What is a smart city?

A smart city uses sensors and connected equipment to see how its infrastructure is running — street lighting, water networks, air quality, parking, traffic and waste — and to act on it from one place instead of waiting for complaints. Custom software fits that to the systems a city or operator already has and to the people who run them.

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 bring together systems from different vendors?

Yes, and that is usually the point. Lighting, parking and metering vendors each have their own platform; we connect them by API, and equipment on site through an edge gateway, so operators work from one view. The vendor systems stay in place; nothing has to be ripped out.

Can citizens see the data?

Yes, where you want them to. Public dashboards — air quality, parking availability, service status — can sit on your website or open-data portal, while operational views stay behind a login with roles per department or contractor.

Can integrators and concessionaires deliver it under their own brand?

Yes. Each city, client or concession 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 infrastructure.

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 smart city 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 city systems you need to see in one place

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)