How much does it cost to build an IoT platform in 2026
How much does it cost to build an IoT platform in 2026
Building an IoT platform in 2026 typically costs $80,000 to $1,000,000+ to ship a real V1. A single-product device fleet runs $80k to $200k. A multi-tenant platform that hosts other companies' devices runs $250k to $1M. Industrial or regulated IoT (medical, energy, automotive) starts at $1M and grows from there, mostly on certification, not engineering.
Most cost guides hand you a single number and a generic feature list. This one names the actual stack picks at each tier, and budgets the line item nobody else admits to: device certification routinely costs more than the software.
What actually goes into an IoT platform
An IoT platform is not one product. It is roughly nine moving parts, and each one has its own cost curve.
- Device firmware. Embedded code in C, Rust, or Zephyr RTOS. Runs on the microcontroller (ESP32, nRF52, STM32). Has to handle power, retries, and OTA updates without bricking.
- Connectivity. WiFi, BLE, LoRaWAN, or cellular (LTE-M / NB-IoT). Each has different range, power, and per-device cost trade-offs. Cellular adds a SIM bill of $1 to $5 per device per month.
- Device-to-cloud bridge. Almost always MQTT today. The broker is either managed (AWS IoT Core, Azure IoT Hub, HiveMQ Cloud, EMQX Cloud) or self-hosted (Mosquitto, EMQX, HiveMQ Community).
- Time-series data ingest. Sensor data is dense and append-only. TimescaleDB, InfluxDB, or ClickHouse handle this far better than vanilla Postgres.
- Stream processing. Kafka or AWS Kinesis if you have real-time alerts. Skip it until you do.
- OTA firmware updates. Buy this. Memfault, Mender, or Balena will save you three months versus rolling your own.
- Fleet management UI. Internal admin to provision, monitor, and decommission devices.
- Customer dashboard plus mobile companion app. What the end user actually sees.
- Security. Per-device certificates, secrets provisioning during manufacture, and a credible answer to the OWASP IoT Top 10 (2024 update).
A note on platform risk: Google Cloud IoT Core was decommissioned in August 2023, forcing thousands of platforms to migrate mid-flight. If you build on a managed IoT-specific service, treat deprecation exposure as real. Founders today default to AWS IoT Core, Azure IoT Hub, or self-hosted MQTT with portable message schemas.
Three scope tiers and what each really costs
Every honest IoT cost conversation starts here. The differences are huge.
Tier 1: single-product device fleet ($80k to $200k). You make one product (a smart sensor, a connected thermostat, a fitness wearable). You sell it to end users. The platform serves your devices only.
- Build time: 4 to 6 months
- Team: 2 engineers (1 firmware, 1 cloud + frontend) plus a designer
- Stack: ESP32 or nRF52 + Mosquitto or HiveMQ Cloud + Postgres with TimescaleDB extension + Next.js dashboard
Tier 2: multi-tenant platform ($250k to $1M). You host other companies' devices. Think a SaaS where customers bring their own hardware and you handle the broker, ingest, dashboards, and APIs. This is roughly a 4x cost jump because tenancy, billing, RBAC, and data isolation all become first-class.
- Build time: 9 to 12 months
- Team: 4 to 6 engineers (firmware SDK author, 2 cloud, 1 frontend, 1 DevOps, 1 mobile)
- Stack: AWS IoT Core or self-hosted EMQX cluster + ClickHouse or Timescale + Kafka for fan-out + multi-tenant Postgres for app data
Tier 3: industrial or regulated IoT ($1M+). Medical devices, smart-grid endpoints, automotive, industrial control. Engineering is the small part. Certification, audits, and field service own the budget.
- Build time: 12 to 30 months including cert cycles
- Team: 6+ engineers plus a regulatory lead and a hardware lead
- Stack: hardened Zephyr RTOS firmware + private MQTT cluster + on-prem or sovereign cloud + signed OTA + IEC 62304 / 21 CFR Part 11 / ISO 27001 audit trail
If you're not sure which tier you're in, the test is simple: do you ship the hardware, host other people's devices, or get audited by a regulator?
Cost breakdown by approach
Hiring shape moves the bill more than tooling does. Here's what each path looks like for a 6-month Tier 1 build:
| Approach | Cost | Timeline | Pros | Cons |
|---|---|---|---|---|
| US full-time IoT engineer | $160k-$240k/yr + 30% benefits | 6-12 weeks to hire | Deep ownership, IP retention, on the cap table | Long hire cycle, single point of failure, hard to fire |
| IoT dev agency (US/EU) | $120-$250/hr; $200k-$1M project | 4-8 weeks to start | Multi-skill team, accountable contract | High markup, often weak in firmware specifics, locks you to their stack |
| Freelancer (Upwork) | $25-$120/hr | 1-2 weeks to start | Cheap entry, fast | Wildly variable quality, few firmware + cloud generalists, ghost risk |
| Toptal | $60-$200/hr | 2-3 weeks | Vetted, established brand | Premium markup, monthly minimums, slower to replace |
| Cadence | $500-$2,000/wk | 48-hour trial then ship | AI-native baseline, weekly billing, replace any week, voice-vetted | Less suited to enterprise procurement that wants a master services agreement |
Cadence sits at the bottom by design. Founders book engineers by the week against a four-tier rate card: junior $500/wk for cleanup and integrations with good docs, mid $1,000/wk for end-to-end shipping of standard features, senior $1,500/wk for architecture and edge-case work, and lead $2,000/wk for systems design and fractional-CTO scope. Every engineer on the platform is AI-native by default, vetted on Cursor, Claude, and Copilot fluency in a founder-led voice interview before they unlock bookings. The pool sits at 12,800+ engineers with a 27-hour median time to first commit.
Stack picks at each tier (named, with current pricing)
This is the section the other top-10 results skip. Vendor-agnostic advice is useless when you're sizing a budget.
Brokers
| Broker | Hosting | Cost | When to pick |
|---|---|---|---|
| Mosquitto | Self-host | Free | Tier 1, under 1,000 devices, you have a Linux box |
| HiveMQ Cloud | Managed | Free up to 100 connections; from $0.04/connection/mo | Tier 1 to early Tier 2, you want zero broker ops |
| EMQX Cloud Serverless | Managed | From $0.18/hr metered | Tier 2, bursty load, multi-region |
| AWS IoT Core | Managed | $1.00 per million minutes connected + $1.00 per million messages | Tier 2, already on AWS, want IAM-native auth |
| Azure IoT Hub | Managed | From $10/month for 400k messages | Tier 2 to Tier 3, you live in the Microsoft stack |
Rule of thumb: managed broker until you have 50,000+ connected devices. Past that, self-hosted EMQX or HiveMQ on your own VMs cuts the bill 40-70%, but you own broker uptime.
Time-series databases
- TimescaleDB: Postgres extension. Self-hosted free; Cloud from $25/mo. Best pick if your team already knows SQL.
- InfluxDB: Purpose-built. Cloud Serverless from $0.002/MB ingest. Best pick for high-cardinality device data.
- ClickHouse: OLAP-grade compression. Self-host free; Cloud from $193/mo. Best pick when you need analytical queries over billions of rows.
Cloud bridge
If you're building greenfield, default to AWS IoT Core for Tier 1 and 2. The combination of IAM auth, device shadows, and Lambda triggers is hard to beat for the first 50,000 devices. Move to a self-hosted EMQX cluster only when the AWS bill crosses what a DevOps engineer costs.
OTA tooling
Do not roll your own. Memfault is $0.50 to $2 per device per month. Mender is open source with a paid tier. Balena bundles OTA with device management. Three weeks of in-house OTA work costs more than five years of Memfault for a 5,000-device fleet.
For a deeper read on managed-cloud trade-offs at this layer, our writeup on migrating from Heroku to AWS walks through the same managed-vs-self-host decision tree at the application layer.
The line item nobody else budgets: certification and compliance
For Tier 1 consumer IoT, certification is real but bounded. For Tier 3 industrial, it's the dominant cost. Here are the rough numbers per SKU:
- FCC certification (any radio sold in the US): $5,000 to $30,000
- CE marking (EU market entry): €3,000 to €15,000
- UL listing (safety-critical, US): $10,000 to $50,000+
- HIPAA (medical data): $20,000 to $100,000+ for audit, controls, BAA paperwork
- IEC 62304 (medical device software): $50,000 to $250,000+
- ISO 27001 (B2B procurement gate): $30,000 to $80,000 first year
For an industrial IoT platform with three SKUs targeting US, EU, and medical-adjacent markets, certification routinely costs 2x to 5x the engineering build. Founders who skip this in their pitch deck either haven't sold to a hospital yet or are about to learn an expensive lesson.
Two adjacent reads: building a healthcare app covers the HIPAA / SOC 2 layer in detail, and our Stripe integration cost breakdown is a useful reference for the billing surface most multi-tenant IoT platforms eventually need.
How to keep the bill honest
Five rules that have saved founders six figures more than once.
- Use a managed broker until you have 10,000+ devices. HiveMQ Cloud or AWS IoT Core. The "we'll just self-host Mosquitto" plan eats 200 hours of your senior engineer's year on uptime.
- Self-host time-series only if you have a DBA. TimescaleDB Cloud or InfluxDB Cloud Serverless will be cheaper than the engineer-time to keep a self-hosted cluster running until you cross roughly $1,500/mo in managed bills.
- Buy OTA, don't build it. Memfault, Mender, or Balena. The bricked-device blast radius from a homemade updater is too high.
- Ship one verticalized product before going multi-tenant. Tier 2 cost is 4x Tier 1 because tenancy is invasive. Validate with one customer's hardware first.
- Book weekly, not quarterly. IoT scope changes constantly between firmware, cloud, and dashboard. Long agency contracts price in that volatility. Weekly billing lets you re-shape the team as the bottleneck moves.
If you want help running the numbers on which approach fits your scope, book a 48-hour trial with a senior engineer on Cadence and have them sketch the architecture and a phased budget before you commit to a stack.
The fastest path from prototype to production
A clean three-step plan for founders who already have a hardware prototype and need to get to paying customers.
Step 1: lock the stack on paper before you write code. Pick the broker, the time-series store, the cloud bridge, and the OTA vendor. This decision drives 70% of your monthly bill. A senior engineer can do this in three days.
Step 2: ship a working fleet of 10 devices end-to-end. Firmware, broker, ingest, dashboard, OTA. Real devices in real conditions. This is the build that tells you what's actually broken in your assumptions. Budget 6 to 8 weeks with two engineers.
Step 3: hire incrementally with weekly billing. Once the 10-device fleet is live, you'll know exactly which role you need next: more firmware depth, a dedicated frontend, a DevOps engineer to harden the broker. Hire that exact role, not a "full-stack IoT engineer."
For the third step, the on-demand path is faster than recruiting. Cadence will shortlist four engineers in 2 minutes against your spec, and the 48-hour free trial means you can drop anyone who doesn't fit before the first invoice. If you'd rather see what other founders shipped first, the recruiting platform cost breakdown is a useful comparison for what a full-cycle hire costs in time and dollars.
Try it on your own scope. Tell Cadence what you're building. Get a 4-engineer shortlist with rates in 2 minutes, run a 48-hour free trial, and ship. Replace anyone the next week if the fit is wrong. Start your shortlist.
FAQ
How long does it take to build an IoT platform in 2026?
A single-product device fleet ships in 4 to 6 months with two engineers. A multi-tenant platform takes 9 to 12 months with 4 to 6 engineers. Industrial IoT with certification cycles adds 6 to 18 months on top of that.
Is it cheaper to use AWS IoT Core or self-hosted MQTT?
AWS IoT Core is cheaper until roughly 50,000 connected devices. Past that, self-hosted EMQX or HiveMQ on your own VMs typically cuts the bill 40 to 70%, but you take on broker uptime yourself. For most early-stage platforms, the managed bill never reaches the threshold where a self-host migration pays back.
Why did Google Cloud IoT Core shut down and what does that mean?
Google decommissioned IoT Core in August 2023, forcing thousands of platforms to migrate. The lesson is platform risk. If you build on a managed IoT-specific service, your deprecation exposure is real. Many founders now default to AWS IoT Core, Azure IoT Hub, or self-hosted MQTT with portable message schemas so they can move brokers without rewriting firmware.
What does device certification really cost?
FCC for a US radio runs $5,000 to $30,000 per SKU. CE marking is €3,000 to €15,000. UL listing for safety-critical devices is $10,000 to $50,000+. HIPAA controls and audits start at $20,000 and climb to $100,000+. For regulated industrial IoT, certification often costs 2x to 5x the engineering build.
Can I build an IoT MVP solo as a non-technical founder?
You can prototype on a Raspberry Pi or ESP32 with a managed broker like HiveMQ Cloud and a no-code dashboard like Tinybird or Grafana Cloud. To ship to paying customers you need at least one firmware-fluent engineer and one cloud engineer. Booking a senior on Cadence for two weeks is a faster way to find out what the production-grade build actually requires than reading another cost article.