IoT App Development Cost in 2026: Apps, Cloud, Firmware and Cost per Device

IoT app development cost in 2026: the short answer

"IoT app" means three different projects in the briefs we get. A hardware company with a finished Bluetooth device that needs an iPhone and Android app. A startup building a connected product where the app, the cloud and the firmware all start from zero. And an operator with thousands of sensors in buildings, vehicles or factories that needs a platform to manage them. Same keyword, budgets that differ by ten times.

These ranges come from our own estimates and the competing proposals clients bring to first calls. Rates match what we track in our software development rates by region article. They cover software: mobile apps, cloud backend, dashboards and the firmware parts that talk to them. Electronics design, enclosures, tooling and manufacturing are a separate budget, often as large as the software one.

For scale: IoT Analytics counted about 21 billion connected IoT devices worldwide at the end of 2025 and expects close to 40 billion by 2030. Most new devices are not built by giants. They come from mid-size hardware companies that know their product very well and software much less well, which is exactly where IoT budgets tend to break.

Where the money goes: the four layers of an IoT product

Every IoT estimate we write splits the work into the same four layers. The app screens founders show us in the first call cover only one of them, and not the most expensive.

The device layer is firmware on a microcontroller: reading sensors, managing power, holding a secure identity, talking Wi-Fi, Bluetooth Low Energy or cellular, and accepting updates without bricking. If the hardware team already owns firmware, app developers only need a clear protocol. If not, embedded engineering becomes the largest single line in the estimate.

The link layer is the onboarding moment: the phone finds the device over BLE, passes Wi-Fi credentials, the device connects to the cloud and gets claimed by the right user account. It looks like four screens. In practice it is the flow behind most one-star reviews of connected products, because it depends on routers, phone permissions, 2.4 GHz versus 5 GHz networks and captive portals nobody tested.

The cloud layer receives telemetry over MQTT, keeps a registry and a "shadow" or "twin" of each device's state, stores time-series data, sends commands, runs OTA campaigns and exposes APIs to the apps. Managed platforms like AWS IoT Core and Azure IoT Hub handle the broker and device identity; the rest is ordinary backend work with unusual traffic patterns.

The apps show data, control the device and handle accounts, sharing, notifications and support. A web dashboard for installers, fleet operators or your own support team often matters as much as the consumer app.

Feature-by-feature cost

Hours include iOS and Android on one cross-platform codebase with native Bluetooth modules, the backend, admin screens and testing. Cost uses a blended $55 per hour, typical for Central and Eastern Europe in 2026. Embedded engineers usually bill 10–20% above that blend. Multiply by 2.5–3 for a US agency.

"v1?" is our view. Firmware work is not in this table because it depends on whether the hardware team owns it. Adapting a chip vendor's SDK and reference firmware for connectivity, provisioning and OTA typically takes 350–600 hours; writing custom firmware for a new board takes 1,000–1,800 hours before power optimization. If the subscription is sold inside the app, store fees apply: Apple takes 15% under its Small Business Program (first $1 million a year) and 30% above, and Google Play in the US takes 10% on the first $1 million and on subscriptions, 20% above, plus about 5% when you use Play Billing. Our mobile app development cost guide covers the app store side in more detail.

IoT cost calculator: build and monthly cloud

This calculator estimates both bills: the effort and build cost for your scope, connectivity, firmware and security level, and the monthly cloud cost for your fleet and message rate. Change the message rate first. It moves the running cost more than anything else.

Two experiments worth running. First, move messages per device per hour from 60 to 360 (one every 10 seconds): the build does not change, the cloud bill grows almost six times. Most products do not need that rate; they need to send changes, not samples. Second, switch connectivity to cellular. The platform cost barely moves, but the data plan becomes the largest line on the monthly bill.

What cloud IoT platforms cost per device and message

Cloud IoT pricing is cheap per unit and confusing in total, because it is billed on several meters at once. The 2026 list prices we use in estimates:

Vendors change these prices. Check the current pricing pages before you sign. And remember that platforms can disappear: Google retired Cloud IoT Core in August 2023, and every customer had to migrate. Keep your device-side protocol standard (MQTT with your own topic structure) and the cloud-specific code thin.

A worked example: 10,000 devices that stay connected around the clock and each send one 2 KB message a minute.

• Connectivity: 10,000 devices x 43,800 minutes a month = 438 million connection minutes. At $0.08 per million, about $35.
• Messages: 438 million messages at $1.00 per million, about $440.
• Rules: one rule triggered with one action per message, 438 million each at $0.15 per million, about $130.
• On Azure IoT Hub: about 14.6 million messages a day needs three S2 units, about $750, rules and routing included.

So the IoT platform is around $600–$750 a month, or 6–8 cents per device. The time-series database, stream processing, API servers, logs and monitoring usually add as much again or more. In our estimates, a typical telemetry product lands at $0.10–$0.50 per device per month all-in. Products that stream high-frequency sensor data or store everything forever go far above that. Our cloud cost optimization article covers what to do when the bill grows faster than the fleet.

From what we see in first calls: hardware teams often worry about the platform price per message, which is the smallest number in the model, and forget the data plan. A cellular IoT plan of $1–$3 per device per month is ten to fifty times the IoT platform cost. If the device lives in a home with Wi-Fi, use it.

Built by Gilzor

Results we’ve shipped

70+products launched

98%delivered on time

85%clients come back

Retail · Startup700+stores aggregatedMobile application for Grocery shops→Food delivery3.5 moto MVP launchOptimizing and controlling delivery for a Pizzeria Chain→EdTech4 moto a full iOS app on the App StoreA mobile app to develop brain functions→

Talk to the people who build it. Tell us about your project and get a free estimate of scope, timeline and cost.

See how we’d approach yours →

Firmware, BLE and MQTT: where IoT schedules slip

The protocol contract. The app team, the cloud team and the firmware team meet at two documents: the BLE GATT profile (services, characteristics, data formats, error codes) and the MQTT topic and payload specification. When those documents do not exist, every change in firmware breaks the app and nobody finds out until a tester picks up the device. We ask for both documents, or write them, before any estimate becomes a commitment.

Bluetooth on phones. iOS and Android handle Bluetooth differently: background scanning limits on iOS, permission models that changed several times on Android, vendor-specific Bluetooth stacks on cheap Android phones, and connections that drop when the app goes to the background. Cross-platform frameworks work well for IoT apps, but the Bluetooth layer always needs native code and a device lab. Our Flutter cost guide and React Native cost guide compare the two most common choices.

Provisioning. The flow has to survive a router with an unusual password, a 5 GHz-only network, a phone that switches to cellular mid-setup, and a user who resets the device halfway. Budget twice what the screen count suggests and test with a box of real routers.

OTA updates. An update mechanism is the only way to fix a security hole in a device that is already in someone's home. It needs a bootloader with two firmware slots, signed images, a rollback if the new firmware fails to boot, staged rollouts to 1%, 10% and then everyone, and reporting. Skipping OTA in v1 saves 250–450 hours and creates a product you cannot repair remotely.

The Standish Group's CHAOS research has reported for years that only about a third of software projects finish on time, on budget and with the planned scope. IoT adds hardware revisions to the usual risks. A new board revision can change pins, power behavior or the radio, and the firmware and app tests have to run again.

Security and compliance: what it costs now

Security used to be the line item that disappeared from IoT budgets. That is changing on three fronts.

• US Cyber Trust Mark. The FCC created this voluntary label for consumer IoT devices in 2024. The program paused in 2025 when UL Solutions withdrew as lead administrator, and the FCC selected the ioXt Alliance as the new lead administrator in April 2026. The criteria build on NIST's IoT cybersecurity baseline: unique credentials, secure updates, data protection, vulnerability disclosure and a stated support period.
• State and foreign rules. California's IoT security law (SB-327) has required "reasonable security features," including no shared default passwords, since 2020. The UK's PSTI regime has banned default passwords and required a published support period and a vulnerability disclosure contact since April 2024.
• EU Cyber Resilience Act. If you sell in the EU, manufacturers of connected products must report actively exploited vulnerabilities and serious incidents since September 11, 2026 (early warning within 24 hours), including for products already on the market. The full requirements, with conformity assessment and security updates through the support period, apply from December 11, 2027.

For a connected product v1, a security baseline (TLS everywhere, per-device certificates, signed OTA, no default passwords, encrypted local storage) adds about 120–200 hours if designed in from the start. Readiness for the Cyber Trust Mark or the European ETSI EN 303 645 standard adds documentation, penetration testing and a disclosure process: 300–450 hours plus outside testing fees. Retrofitting the same controls after launch usually costs two to three times more, because devices in the field need an update path that may not exist. Tick what you already have planned:

Who builds it: team rates by region

For a connected product v1 of about 4,100 hours (Wi-Fi provisioning, adapted vendor firmware, cloud OTA, web dashboard, Cyber Trust Mark readiness), the build cost at typical 2026 blended vendor rates:

Latin American teams are nearshore for US companies and share most of the working day. Gilzor's teams in Poland and Cyprus are offshore for US clients: Warsaw is six hours ahead of New York, which leaves two to four shared hours with the East Coast when both sides shift a little, and very little with the West Coast. For IoT work, a bigger practical question than time zones is hardware logistics: who holds the prototypes, how fast new board revisions reach the app and QA team, and whether the vendor keeps a device lab with the phones your customers use. Ask that in every vendor call. If you are comparing specialist vendors, our list of IoT mobile app development companies is a starting point.

Quiz: what kind of IoT project is yours?

The category decides the architecture, and the architecture decides most of the budget. Six questions we ask in first calls about connected products.

Hidden costs that rarely appear in a quote

• Maintenance: 15–20% of the build cost per year. Every iOS and Android release can change Bluetooth, background and permission behavior. Cloud SDKs, certificates and security patches come on top. For a $200,000 build that is $30,000–$40,000 a year. Our software maintenance cost guide breaks this down.
• Support for the device's whole life. Phones get replaced every few years; thermostats and sensors stay on the wall for ten. Your app and cloud must keep supporting old firmware versions, and the security rules above expect a stated support period.
• Certification. FCC equipment authorization for the radio (much cheaper when you use a pre-certified module), Bluetooth SIG qualification at $12,000 per design for Adopter members since March 2026, and Connectivity Standards Alliance membership and per-product fees if you want the Matter logo. Every new hardware revision can trigger retesting.
• Connectivity. Cellular data plans of roughly $1–$3 per device per month, SIM management, and roaming rules if devices travel.
• A device lab. Dozens of phones, routers, prototypes from each board revision, and network simulation. Our QA team treats hardware-in-the-loop testing as its own suite, separate from app testing.
• Factory provisioning. Loading unique certificates and serial numbers onto every unit on the production line needs a tool, a process and a partner who follows it.
• Store and developer fees. $99 a year for the Apple Developer Program, a one-time $25 for Google Play, and commissions on any subscription sold in the app.

Where IoT budgets blow up

These are the patterns we see in estimates and in connected products that come to us after another team.

1. No protocol document between firmware and appBoth teams interpreted the same bytes differently. Every firmware build broke the app, and weeks went into finding out which side was wrong.
2. OTA was postponed to "after launch"The first field bug needed a firmware fix, and the only way to apply it was a recall or a USB cable. The update mechanism then had to be built under pressure, for devices that lacked the bootloader to support it.
3. Provisioning tested only on the office routerCustomers had mesh networks, 5 GHz-only bands and guest portals. Returns and support tickets arrived before reviews did.
4. Sampling instead of reporting changesDevices sent a reading every few seconds whether anything changed or not. The cloud bill grew with every device sold, and battery life fell short of the box claims.
5. Security added for the first big retailerA buyer asked for a penetration test and a support period. Shared default passwords and unsigned firmware turned a checkbox into a redesign.

How to reduce the cost without breaking the product

• Use a pre-certified radio module and the chip vendor's SDK. It cuts firmware hours and certification costs. Custom radio designs pay off only at high volumes.
• Write the protocol documents first. GATT profile and MQTT topics, versioned, before the app or firmware sprint starts. Then build the app against a simulator while hardware catches up.
• One cross-platform app with native Bluetooth modules. It saves roughly 20–30% of client effort compared with two native apps.
• Buy the broker, build the product. Managed MQTT and device identity are commodities. Spend hours on onboarding, the dashboard and the features that make your device worth buying.
• Send events, not samples. Report on change, batch readings, and keep raw high-frequency data on the device or at the edge. It lowers cloud cost and saves batteries.
• Keep OTA and the security baseline in v1. Cut a dashboard report or a voice assistant integration instead. Those can ship later; a missing update path cannot be shipped later to devices already sold.
• Run a short discovery. Two to four weeks of business analysis turns "a smart device with an app" into a protocol, a provisioning flow, a cloud architecture and a cost per device, which is what makes an estimate hold.

If your connected product handles patient data or is a medical device, our healthcare app development cost guide covers HIPAA and FDA cost drivers. Already have an IoT app with bad reviews about pairing, disconnects or battery drain? A rebuild is not automatically the answer; a fixed-price mobile app audit shows what is worth keeping.

FAQ

Where Gilzor fits

We build mobile apps and their cloud backends from Poland and Cyprus for startups, hardware companies and product teams. On an IoT project, we start with the decisions that set both bills: how the device connects, who owns the firmware, how updates reach the field, which security rules apply in your markets, and what each device costs to run per month. Our tech stack page lists the tools we work with.

More than 70 projects launched, and 85% of our customers come back for the next one. Send us your device, your connectivity and your fleet size, and we'll show you what the app, cloud and firmware work costs and what each device will cost to serve.