IoT Platform Cost: A Five-Year TCO Model for Integrators

IoTITermIoT (Internet of Things)The IoT (Internet of Things) is the network of physical objects with sensors, software and connectivity that collect and exchange data and act autonomously.View profile platform cost is rarely just the license line on a quote: over five years, data, connectivity, and operations can add up to more than the software.

Elena is a product manager at a company that makes cold-room monitoring units. In 2023 she compared two ways to add software to her hardware. One quote charged a monthly fee per device. The other was an open source platform her team would host, with no license at all. The second option looked free, and she chose it.

By the third year the free platform had a cloud bill, half of an engineer's time, two security audits, and a mobile app nobody had budgeted. None of those costs was a mistake. They just weren't on the comparison sheet.

Elena's case is common. Cisco's 2017 IoT survey found that 60% of IoT initiatives stalled at the proof of concept stage, and only 26% of companies considered one of their IoT projects a complete success. Budget overruns were among the five challenges respondents cited most, together with time to completion and limited internal expertise.

This guide breaks IoT platform cost into the lines that matter over five years, gives you a total cost of ownership (TCO) model to reuse, and lists the questions to ask before you sign. It's written for integrators and device manufacturers who have to price these projects for their own clients. If your project is still moving from pilot to rollout, the guide to taking an IoT prototype to production covers the cost per device at that stage.

What IoT Platform Cost Includes Over Five Years

A platform decision usually outlives the hardware generation it was chosen for. Five years is a sensible horizon: long enough to include a battery cycle, a few firmware updates, and at least one change in the client's requirements.

These are the six layers of cost to include:

The recurring lines matter more as the fleet grows. In its State of IoT 2025 report, IoT Analytics counted 21.1 billion connected IoT devices worldwide, 14% more than a year earlier. Fleets get bigger, and every euro per device per month gets multiplied.

Connectivity Depends on the Radio

Connectivity is the line that changes most with the technology, and the platform choice doesn't remove it. Cellular devices on NB-IoTProtocolNB-IoT3GPP-standardized cellular LPWAN — carrier coverageView profile or LTE-MLProtocolLTE-MCellular IoT with mobility and voiceView profile carry a SIM with a monthly or annual data plan, so the cost grows with every device. LoRaWANProtocolLoRaWANOpen long-range, low-power LPWANView profile moves most of the spending to the start: gateways, installation, and a network server fee that depends more on the number of gateways than on the number of sensors. Devices on the client's existing Wi-Fi or Ethernet cost almost nothing to connect, but they depend on an IT department that may change its rules.

Mixed fleets are normal. A water utility can read meters over LoRaWAN, while its pumping stations report over cellular. Model each group separately and add them up.

Underneath all these lines sits the build versus buy question. The article on whether to buy or build an IoT platform covers the strategic side. This guide puts numbers on it.

License Models and the Terms That Change the Price

Platform vendors price in different units, and the unit decides how your cost grows.

• Per device. Simple to forecast and easy to pass on to a client. Check how many variables each device may report.
• Per variable or data point. Fairer when devices differ a lot, but harder to predict when a client adds sensors.
• Per message. Cheap for devices that report rarely. It becomes expensive when a client asks for one-minute data instead of 15-minute data.
• Per instance. A fixed fee for a dedicated environment, common for large clients or on-premise installations.
• Per user. Less common in IoT, and it discourages the client from sharing dashboards with the people who need them.

The Fine Print Behind the Monthly Fee

Two quotes with the same monthly price can end up far apart. These terms explain most of the gap:

• How much history is included, and what longer retention costs.
• The maximum reporting rate, for example one data point per minute per variable.
• Whether support is included, and with what response time.
• Setup fees for a dedicated or on-premise instance.
• Discounts for annual payment and for volume tiers.
• What happens when you go over the device or variable limit.

At Cloud Studio IoT, plans are based on the number of devices and variables, with shared or dedicated instances and different support levels. The pricing page shows the current plans. For clients who need to run everything on their own servers, the comparison of on-premise vs. cloud IoT platforms explains what changes in cost and responsibility.

Data Volume, Retention, and Exit Costs

Data volume grows faster than intuition suggests, so do the multiplication early.

Take 2,000 devices, each reporting five variables every five minutes. That's 288 reports per device per day, or 2,880,000 readings per day across the fleet. Over a year, it comes to about 1.05 billion readings, and over five years, more than five billion.

A capable platform stores that without trouble. The questions are who pays for it and for how long. Three decisions set the storage bill:

1. Retention. Raw data for how long? Many projects keep full resolution for a year and hourly or daily aggregates after that.
2. Granularity. Does the client need one reading per minute, or does every 15 minutes answer the same question at a fifteenth of the volume?
3. Backups. How many copies, in which region, and how long does a restore take?

Plan the Exit Before You Enter

Leaving a platform has a cost too: exporting history, moving devices, and rebuilding dashboards and rules. In the European Union, the Data Act lowers part of that barrier. According to the European Commission's Data Act explainer, providers of data processing services can charge only the costs linked to switching and data egress until 12 January 2027. After that date, switching charges disappear entirely.

The rules help with cloud services, but they don't rebuild your alarm rules or your client's dashboards. Ask for export formats in writing, and keep your own register of device identifiers and keys. The guide to IoT platform migration explains how to move without losing data.

Operations: The IoT Platform Cost Nobody Quotes

The largest line in most self-hosted projects is people, and it rarely appears in the first comparison.

A platform that runs 24 hours a day needs someone to watch it. That work includes operating system and database updates, certificate renewals, backup tests, capacity planning, and an on-call rotation for the night the database fills up. Hiring a team for it, or using an existing one, is the question behind the article on a software team vs. an off-the-shelf IoT platform.

Security adds its own line. Under the EU Cyber Resilience Act, manufacturers of products with digital elements have to set a support period and handle vulnerabilities throughout it, as the Commission's CRA summary explains. The main obligations apply from 11 December 2027. If your product includes the platform under your brand, those updates are part of your cost for as long as you support the product.

Field Visits Count Too

Some operating costs happen outside the data center. Each visit to replace a battery, reset a gateway, or swap a failed sensor costs a technician's time and travel. A platform that shows battery levels, silent devices, and weak signals lets you group those visits by route instead of sending someone out for each alarm. In the guide to industrial IoT implementation, the question of who runs the system after the project ends appears for the same reason.

Want to know which operations the platform takes off your team's hands? The IoT platform page summarizes what comes included.

A Five-Year TCO Model You Can Reuse

The table below compares two options for the 2,000-device fleet from the previous section: a self-hosted open source platform and a managed commercial platform. The figures are illustrative. Replace each one with the quotes and salaries of your own project.

These are the assumptions behind each line:

• Licenses at €1 per device per month for the managed option: 2,000 devices over 60 months.
• An initial build of dashboards, alarms, user management, and a mobile app for the self-hosted option, against configuration work on the managed one.
• Hosting at €900 per month for the self-hosted option.
• Half an engineer at a loaded cost of €60,000 per year to run the self-hosted platform, against a tenth of one for the managed option.
• An annual penetration test and security work at €10,000 for the self-hosted option, and €2,000 for the managed one.
• Connectivity at €1 per device per month in both cases.

Where the Model Changes Its Answer

People and licenses move the result most. At 50,000 devices, the same license assumption becomes €3 million over five years, while a platform team doesn't grow at the same pace as the fleet. At that scale, an in-house platform or an on-premise license can make sense, and so can negotiating volume pricing.

The opposite also happens. A company with 300 devices and no software team pays for the self-hosted option in salaries long before it saves on licenses.

Elena's team ran this model in its third year, with real invoices instead of estimates. The self-hosted platform came out at a little over €4 per device per month once the mobile app and the audits were included. They moved the next hardware generation to a managed platform and kept the old units where they were until their batteries ran out.

Build Your Own Version in Five Steps

1. List the fleet by group: device type, connectivity, reporting rate, and expected growth per year.
2. Ask each vendor for a quote over 60 months, with the terms from the previous sections in writing.
3. Put a salary figure on every task your team would take on, including nights and holidays.
4. Add one-time costs in the year they happen, not spread across the term.
5. Divide the total by device-months, and compare that figure with what your client is willing to pay.

Turning TCO Into a Price Your Client Accepts

For an integrator, the TCO model is also a sales tool. Clients compare the upfront price. You win when you show them what each option costs over five years.

Pablo runs an integration firm that bid for a council contract to monitor 600 water tanks. A competitor offered a lower installation price, with the platform "at no extra cost." Pablo's proposal included a five-year table like the one above, with a fixed monthly price per tank that covered the platform, connectivity, monitoring, and battery replacements.

The council's technical team compared both bids over the full contract term. Pablo's came out cheaper, because the other bid left hosting, updates, and field visits to be quoted later. He won the contract, and he now has five years of recurring revenue.

From Cost per Device to Price per Device

The model gives you a cost per device per month. Your price adds your own service: monitoring, support, reports, and field work. Two practices make that price easier to defend:

• Show the breakdown. A client who sees what the monthly fee covers is less likely to compare it with a bare license.
• Spread fixed costs. With a multi-tenant platform, a dedicated instance or a support plan serves many clients at once, so each new client lowers your cost per device.

Serving several clients under your own brand is what a white-label IoT platform is built for.

Six Questions Before You Sign

Ask every vendor the same questions, and keep the answers with the proposal.

1. Billing unit. What do you charge for, and what happens when I go over the limit?
2. History and granularity. How much data is included, at what resolution, and what does more cost?
3. Support. What does support cover, and what is the response time for a critical incident?
4. Setup fees. Is there a one-time fee for a dedicated or on-premise instance?
5. Exit. In what format do I get my data, devices, and configuration if I leave?
6. Price review. How and when does the price change each year?

Key Takeaways

• IoT platform cost covers six layers: licenses, connectivity, infrastructure and data, build and integration, operations, and exit. Budget all of them over five years.
• The billing unit decides how cost grows. Read the terms on retention, granularity, support, and overage before comparing monthly fees.
• Data volume adds up quickly: 2,000 devices with five variables every five minutes produce more than a billion readings a year.
• People are usually the largest hidden line in a self-hosted platform, and EU rules such as the Cyber Resilience Act add ongoing security work.
• A clear TCO model helps integrators win bids and turn projects into recurring revenue.

Cloud Studio IoT gives integrators and device manufacturers a platform priced by devices and variables, with dashboards, alarms, mobile apps, and multi-tenant management included, in the cloud or on the client's own servers. Check the pricing plans, and if you want help building the five-year model for a real project, talk to the team. To resell the platform under your own brand, see the partner program.