Skip to content
DT Nova
Services

IoT software development for connected products and devices

IoT software development, or internet of things software development, for companies that make, install or operate connected devices: sensors, meters, machines, chargers, building equipment and consumer products. We build the software that turns a device into a product: secure provisioning, a cloud backend that receives and stores device data, over-the-air updates, mobile and web apps for your customers and dashboards for your team. The EU rules that now apply to connected products, the Cyber Resilience Act and the Data Act, are built into the design rather than added later. The code and the cloud accounts are in your company's name.

  • You see the result before it goes live
  • Fixed price for the agreed scope, in writing before work starts
  • Source code, domain and accounts in your company's name

Request a quote

The layers of an IoT product

Most connected products fail on the software around the device, not on the device itself. A sensor that measures well is of little use if it cannot be set up in two minutes, updated safely or shown to the customer in a way they understand. IoT in software development terms means designing these layers together:

LayerWhat it doesWho builds it
Device firmwareReads sensors, controls actuators, connectsYour electronics team or partner; we agree the interface with them
Gateway or edge softwareCollects local devices, buffers offline, pre-processes dataWe build it on embedded Linux or a gateway platform
Provisioning and identityGives each device a unique identity and credentials at the factory or at set-upWe build it
Cloud backendReceives messages, stores time series, runs rules and alertsWe build it
Update serviceSigns, stages and rolls out firmware and software updatesWe build it, with your firmware team
Apps and dashboardsSet-up, live status, history, alerts and control for users and your support teamWe build them
IntegrationsERP, CRM, service and billing systemsWe build them

Hardware design and radio certification stay with your electronics team or partner. We build the parts above the firmware, and we write the interface with your firmware team down before either side starts.

IoT platform: buy, build or combine

An IoT platform is the cloud layer that connects devices, receives and stores their data, manages identities and updates, and exposes the data to apps and other systems. The large cloud providers and specialist vendors sell ready-made IoT platform services, and open-source brokers and frameworks exist for teams that want to run their own. For most connected products we combine: a managed broker and device registry from an EU cloud region for the commodity parts, and our own code for what makes the product yours, such as the data model, rules, customer apps, billing and integrations. That keeps the platform replaceable, which matters both for cost and for the switching rights the Data Act gives cloud customers.

Protocols and data

For most products, devices talk to the cloud over MQTT, a publish and subscribe protocol designed for constrained devices and unreliable networks. MQTT 5.0 has been an OASIS Standard since 7 March 2019 (read 11 November 2026), and every major cloud and message broker supports it. HTTP fits devices that report a few times a day. Industrial sites often bring their own protocols, such as Modbus or OPC UA, which a gateway translates.

Device data is time series: many small readings, each with a timestamp. We store it in a database built for that, keep raw data as long as you need it and summaries for longer, and design topics and message formats so a new device model can be added without rebuilding the backend. Devices queue readings when the connection drops and send them later, and the backend accepts late and duplicate messages without double counting.

Security from the factory to the field

A connected device is a computer on someone else's network, for years. Security is designed in from the first device:

The Cyber Resilience Act

The EU Cyber Resilience Act, Regulation (EU) 2024/2847, sets security requirements for products with digital elements placed on the EU market, which covers most connected devices and the software that comes with them. According to its Article 71, the Regulation applies from 11 December 2027, but the reporting obligations in Article 14 apply from 11 September 2026. From that date, a manufacturer must send an early warning of an actively exploited vulnerability in its product within 24 hours of becoming aware of it, through the single reporting platform. The essential requirements in its first annex ask, among other things, that products are made available without known exploitable vulnerabilities, that security updates are provided, separately from functionality updates where technically feasible, and that security is tested regularly. The recitals expect a support period of at least five years in most cases. (Read 11 November 2026.)

The Radio Equipment Directive's own cybersecurity rules, Delegated Regulation (EU) 2022/30, have applied since August 2025. The European Commission's Radio Equipment Directive page explains that they are repealed with effect from 11 December 2027, the date the Cyber Resilience Act takes over, to avoid overlapping requirements.

What this means for the software we build: a software bill of materials for each release, a vulnerability handling process with a contact point, an update service that can deliver a security fix to the whole fleet quickly, and logs that let you know which devices are affected. Conformity assessment and the legal decisions are yours and your advisers'; we make sure the software supports them.

The Data Act and device data

The EU Data Act, Regulation (EU) 2023/2854, has applied since 12 September 2025. Its Article 3(1) requires connected products to be designed so that the data they generate, with the metadata needed to interpret it, is accessible to the user by default, easily, securely, free of charge and in a machine-readable format where relevant and technically feasible. Under Article 50, that design obligation applies to connected products placed on the market after 12 September 2026 (read 11 November 2026).

In practice we build a data export and an interface for users from the first version: their readings, events and settings, in a documented format, with access controlled by the account. Designing it in from the start takes far less work than adding it to a fleet already in the field.

For the rest of the Regulation, including third-party sharing, unfair data terms and cloud switching, see our EU Data Act guide.

Apps and dashboards

For the end user, the product is the app. Set-up should take minutes: scan the code on the device, connect it to the network over Bluetooth or a local hotspot, name it and see the first reading. After that, the app shows live status and history, sends alerts that matter and lets the user control the device where that is safe. Your support team gets its own view of the fleet: which customer, which device, which version, which error, so a support question is answered without a site visit. We build the apps for iPhone and Android from one codebase where that fits; see cross-platform app development. For the analytics side, see dashboard development. When a device alarm should become a service job, for example a failing heat pump or chiller, see HVAC scheduling software. When running hours or a measured condition should trigger planned service on your own equipment, see preventive maintenance scheduling software.

How we build it

  1. Architecture workshop. Devices, connectivity, volumes, users and the rules that apply. The interface with your firmware team written down.
  2. Scope and fixed price in writing. Layers, integrations and what the first version leaves out.
  3. A thin slice end to end. One device, provisioned, sending data, updated over the air and visible in the app, before the fleet features are built.
  4. Pilot fleet. A few dozen devices in real conditions, with update and recovery tested on purpose.
  5. Production and handover. Documentation, runbooks, vulnerability handling and the maintenance plan for the support period.

You own it

As a standard term, the source code is in your company's repository, and the cloud accounts, signing keys and device records are in your company's name. Hosting runs in an EU data region under a written data processing agreement. You can keep us for maintenance, run it yourself or hand it to another team. Connected devices sold in the EU fall under the Cyber Resilience Act, explained in our Cyber Resilience Act guide.

For production planning around your devices, see production scheduling software. For chargers, batteries, heat pumps and meters that take part in the energy market, see energy software development. For a review of an existing product, see security audit services. For the wider build, see custom software development and cloud migration consulting. For SIM-based products and operator network APIs, see our guide to telecom software development. For machinery and field sensors on farms, see agriculture software. For the technician visit that follows an alarm, see field service management software. See prices.

Questions we get

Do you design the hardware or the firmware?

Circuit board design and radio certification stay with your electronics team or partner. We build the software around the device: the cloud backend, the provisioning and update service, the mobile and web apps, dashboards and integrations, and gateway or embedded Linux software where a device runs a full operating system. For microcontroller firmware and hardware we work with your electronics team or partner, against a written interface.

Which protocol should our devices use?

For most connected products, MQTT is a good default: it is an open OASIS standard, light on bandwidth and power, and supported by every major cloud. HTTP suits devices that report rarely, and some industries have their own protocols, such as Modbus or OPC UA in industrial settings. We choose with your device constraints in front of us.

Does the Cyber Resilience Act apply to us?

If you place a product with digital elements on the EU market, very likely yes. Its reporting duties for actively exploited vulnerabilities apply from 11 September 2026 and the main requirements from 11 December 2027. We build the software side to support them: secure defaults, security updates, a software bill of materials and vulnerability handling. Your conformity assessment is your own or your notified body's.

How are device updates delivered?

Over the air, from an update service that signs each release, rolls it out in stages, checks the device came back healthy and can roll back. Security updates are kept separate from feature updates where technically feasible, which is also what the Cyber Resilience Act asks for.

Who owns the code and the device data?

Your company owns the code, the cloud accounts and the device fleet records. Under the EU Data Act, users of connected products also have rights to the data their product generates, so we design data access for users from the start.

Get a written quote

Tell us in a few lines what you need. We reply within one working day with a written quote: scope, timeline and a fixed price or an hour estimate. Asking is free and commits you to nothing.

See every price · Contact details

Request a quote