100 IoT Platforms to Research, Grouped by Use Case
“Best” is a difficult label in the Internet of Things. A platform that suits a manufacturer connecting industrial equipment may be a poor fit for a small team tracking shipments, operating smart buildings, or launching a consumer device. Connectivity options, edge requirements, data residency, device lifecycle management, integrations, and pricing structure all change the answer.
Rather than treating this as an objective ranking, use the following as a non-ranked research list. It includes full IoT platforms alongside relevant connectivity, edge, device-management, and protocol foundations. That breadth matters: many real-world IoT stacks combine more than one product. Product packaging and availability can change, so teams should confirm current support, regional coverage, and commercial terms during evaluation.
How to compare IoT platforms
Before making a shortlist, define the job the platform must do. A useful starting point is the path from a physical device to a business decision: how devices connect, how identities and permissions are managed, where data is processed, and who acts on the resulting alert or workflow.
- Device fit: Confirm supported hardware, operating systems, protocols, and offline behavior.
- Connectivity: Consider cellular, Wi-Fi, Ethernet, LPWAN, satellite, or a combination.
- Operations: Review provisioning, monitoring, remote configuration, and software-update processes.
- Data architecture: Decide what needs real-time processing at the edge and what can move to the cloud.
- Security and governance: Review authentication, access control, auditability, and data-location requirements.
- Team fit: A developer-led build, a low-code workflow, and an industrial deployment can call for very different tools.
A short proof of concept with representative devices and network conditions usually reveals more than a feature checklist alone.
100 IoT platforms and foundations to research
Cloud and enterprise IoT platforms
- AWS IoT
- Microsoft Azure IoT
- Alibaba Cloud IoT Platform
- Tencent Cloud IoT Explorer
- SAP IoT
- Siemens Insights Hub
- PTC ThingWorx
- Cumulocity IoT
- Hitachi Lumada
- Bosch IoT Suite
Application enablement and low-code options
- Particle
- Blynk
- Ubidots
- Losant
- TagoIO
- Thinger.io
- Arduino Cloud
- Datacake
- Akenza
- Leverege
Open-source and open ecosystem projects
- ThingsBoard
- Kaa IoT
- Mainflux
- OpenRemote
- Eclipse Kapua
- FIWARE
- EdgeX Foundry
- openBalena
- Home Assistant
- openHAB
Messaging, protocol, and device-service foundations
- EMQX
- HiveMQ
- Eclipse Mosquitto
- VerneMQ
- NanoMQ
- Aedes
- Eclipse Californium
- Eclipse Leshan
- NATS
- RabbitMQ
LoRaWAN and LPWAN platforms
- The Things Stack
- ChirpStack
- Actility ThingPark
- LORIOT
- Senet
- Everynet
- Helium
- MachineQ
- TEKTELIC
- Kerlink Wanesy
Cellular connectivity and IoT SIM management
- Soracom
- 1NCE
- em nify
- Eseye
- Aeris
- KORE
- Wireless Logic
- Hologram
- Twilio Super SIM
- Cisco IoT Control Center
Industrial edge, operations, and analytics
- Litmus Edge
- ClearBlade
- Inductive Automation Ignition
- HighByte Intelligence Hub
- Kepware
- Tulip
- Seeq
- Braincube
- Telit deviceWISE
- Crosser
Device lifecycle and connected-product platforms
- Mender
- balenaCloud
- Memfault
- FoundriesFactory
- Eclipse hawkBit
- Airbiquity OTAmatic
- Sibros Deep Connectivity Platform
- Ayla IoT Platform
- Nabto Edge
- Exosite Murano
Smart home and smart building ecosystems
- Samsung SmartThings
- Tuya IoT Platform
- Amazon Alexa Smart Home
- Apple HomeKit
- Google Home Developer Center
- Schneider Electric EcoStruxure
- Honeywell Forge
- Johnson Controls OpenBlue
- Hubitat Elevation
- Homey
Fleet, asset, and logistics platforms
- Samsara
- Geotab
- Wialon
- Tive
- Roambee
- Nexxiot
- Verizon Connect
- Trimble Transportation
- Azuga
- Fleet Complete
Turning a long list into a practical shortlist
Start by eliminating platforms that do not match the required network, device type, or deployment geography. Then identify whether the project needs a single integrated service or a composable stack. A small team with a limited hardware footprint may value managed services and faster setup. A business with existing operational technology may prioritize industrial protocols, edge deployment, and integration with established systems.
It is also worth separating a demo from an operating model. Ask who provisions the next thousand devices, investigates an offline unit, approves an over-the-air update, and responds when an alert is generated at night. These questions make ongoing ownership visible early.
For solo founders and small teams, the most useful platform is rarely the one with the longest feature list. It is the one that supports the required device workflow, leaves room for growth, and can be operated confidently with the people and processes available.