The 4 Types of IoT: Consumer, Commercial, Industrial and Infrastructure

The 4 types of IoT compared: consumer, commercial, industrial (IIoT) and infrastructure. Who owns each, what a failure costs, and why the technology overlaps.

Agustin Pelaez
· 13 min read
Send by email
Diagram of the four types of IoT: consumer, commercial, industrial and infrastructure, with example sectors for each

There are four types of IoT: consumer IoT, commercial IoT, industrial IoT (IIoT) and infrastructure IoT. What separates them is who owns the system and what a failure costs, not the technology. The same networks, protocols and even devices appear in several types, so technology cannot be the dividing line.

The type decides most of a project's design: the uptime target, the hardware rating, the integration work and who pays when a device stops reporting. A thermostat and a tank-level sensor both send a number to the cloud, but they share little else.

What are the main types of IoT?

The main types of IoT are consumer, commercial, industrial and infrastructure IoT, and each one is defined by who owns it. Consumer IoT belongs to a household or individual, the scope NIST uses in its consumer IoT baseline (NIST IR 8425, September 2022), and commercial IoT belongs to a business, building operator, hospital or fleet operator. Industrial IoT belongs to manufacturers and operators of production assets, on the plant floor or in the field. Infrastructure IoT belongs to a city, utility or public agency.

Many guides list only three types and fold infrastructure into industrial IoT. Infrastructure IoT gets its own type here because its owner is public, and a failure lands on everyone who depends on the service.

The table summarizes each type by owner, typical devices, networks, protocols and the cost of a failure.

TypeWho owns itTypical devicesNetworksProtocolsCost of a failure
Consumer IoTA household or individualThermostats, smart locks, smoke detectors, voice assistants, fitness and health wearables, connected carsWi-Fi, Bluetooth LE, Zigbee, Thread, cellularMatter, proprietary cloud APIsInconvenience at best; privacy breaches, home safety risks, devices hijacked into botnets
Commercial IoTA business, building operator, hospital, or fleet operatorEnergy meters, occupancy sensors, HVAC controllers, asset tags, cold-chain monitors, hospital equipment trackers, fleet telematicsWi-Fi, Ethernet, Bluetooth LE, LoRaWAN, LTE-M, NB-IoT, LTEBACnet, Modbus, MQTTHigher utility bills, tenant complaints, spoiled inventory, lost assets, compliance fines, patient safety in clinical settings
Industrial IoT (IIoT)Plant floor: a manufacturer or plant operator.
Field: a mining, oil and gas, construction, or agricultural operator
Plant floor: PLCs, vibration and level sensors, energy meters, gateways.
Field: heavy equipment telematics, tank and pump monitors, wellhead sensors, barn and irrigation monitors
Plant floor: Ethernet, RS-485, Wi-Fi, private LTE/5G.
Field: cellular, LoRaWAN, satellite, private LTE
Plant floor: Modbus, OPC UA, MQTT, Profinet, EtherNet/IP.
Field: MQTT, Modbus RTU, DNP3
Lost production, equipment damage, unplanned downtime, costly site visits, spills, crop or livestock loss, safety or environmental incidents
Infrastructure IoTA city, utility, or public agencyWater-level sensors, smart water and power meters, traffic counters, environmental stations, substation monitors, public transit vehiclesLoRaWAN, NB-IoT, LTE-M, cellular, fiberDNP3, IEC 61850, Modbus, MQTTService disruption for the public, flooding or outage risks to public safety

Categories overlap: the same device or use case (an energy meter, a vehicle tracker, a pump monitor) can sit in different rows depending on who operates it and what a failure costs.

Why are the types of IoT defined by owner, not technology?

The types of IoT are defined by owner and cost of failure because the technology overlaps too much to separate them. LoRaWAN, a long-range network, appears in commercial, industrial and infrastructure IoT. Modbus and MQTT, two protocols that run on top of networks, appear in the same three types. A vibration sensor, an energy meter or a GPS tracker does not reveal its type; the organization that runs it, and what that organization loses when the device goes quiet, does.

The matrix maps four common use cases to the types of IoT they appear in.

Use caseConsumer IoTCommercial IoTIndustrial IoT (IIoT)Infrastructure IoT
Vehicle telematicsPersonal connected carsDelivery fleetsHeavy equipment (field)Public transit vehicles
Energy meteringRare; the home meter usually belongs to the utilityBuilding and tenant metersMachine and line meters (plant floor)Utility power and water meters
Environmental and gas sensingSmoke and carbon monoxide detectorsIndoor air-quality sensorsGas detectors at plants and wellheadsEnvironmental stations
Remote pump and tank monitoringRareRareTank and pump monitors (field)Water and wastewater pumping stations

Remote pump and tank monitoring shows the principle most clearly. An oil and gas operator's tank monitor and a water utility's pump-station monitor both connect over cellular or LoRaWAN. Both read sensors over Modbus RTU and publish the values over MQTT. Only the owner differs, and with it the type: industrial IoT for the operator, infrastructure IoT for the utility.

What is consumer IoT?

Consumer IoT is the set of connected devices a household or individual buys and runs: thermostats, door locks, smoke detectors, voice assistants, fitness and health wearables, and connected cars. NIST's consumer profile (IR 8425) scopes these as products for home or personal use and lists the cybersecurity capabilities manufacturers should build into them.

Consumer devices connect over Wi-Fi, Bluetooth LE, Zigbee, Thread and cellular. Newer home products use Matter, the Connectivity Standards Alliance standard that runs over Wi-Fi and Thread and uses Bluetooth LE for commissioning, while many others talk only to their maker's cloud API.

A consumer IoT failure can cost far more than an inconvenience. A connected door lock or smoke detector that stops working is a home safety problem. Compromised consumer devices have also been turned against everyone else: the Mirai botnet took over home routers, network cameras and digital video recorders in 2016 and used them for some of the largest DDoS attacks recorded at the time, according to CISA alert TA16-288A.

What is commercial IoT?

Commercial IoT is IoT run by a business, building operator, hospital or fleet operator in the places people work, shop, stay and receive care: offices, hotels, retail stores, hospitals and warehouses, plus the vehicles that serve them. In buildings, the market is often sold as smart building technology. A commercial system measures energy, occupancy, temperature and assets so the operator can cut utility costs, keep occupants comfortable and stay compliant.

Inside buildings, controls speak BACnet, the building automation standard published as ANSI/ASHRAE 135 (current edition 135-2024), over Ethernet and Wi-Fi. Sensors spread across a site or a fleet connect over LoRaWAN, LTE-M or NB-IoT instead.

A commercial failure costs more than a higher utility bill. A missed cold-chain excursion spoils inventory, a gap in records brings compliance fines, and in hospitals a failure can affect patient safety.

AIS Technology, a systems integrator in Malta, cut energy costs and automated billing for a multi-tenant building with commercial IoT. Edge devices with 4G and Ethernet read the electricity, water and gas meters and send the data over MQTT to the Ubidots platform, which produces each tenant's utility report. AIS Technology reports about 30% less staff time lost to manual work and a 5% lower carbon footprint for its client.

An office building, hotel or retail store is therefore a commercial IoT project. The owner is a business, the devices sit in occupied spaces, and a failure costs money, compliance or comfort rather than production.

Industrial IoT (IIoT): connecting production assets that already run

Industrial IoT (IIoT) connects the production assets of manufacturers and operators to software that monitors them, either on the plant floor or in the field. A failure means lost production, damaged equipment or a safety incident, and that cost is what sets IIoT apart. NIST's Guide to Operational Technology Security (SP 800-82 Rev. 3, September 2023) treats these systems separately from IT because they act on the physical environment and carry their own performance, reliability and safety requirements.

Prospect Control brought IoT to an industrial company in Australia this way. For an agricultural chemicals manufacturer, the Melbourne engineering firm used Senquip Orb gateways to read radar level sensors over 4-20 mA or Modbus and send tank levels over MQTT to Ubidots across two sites. Prospect Control reports operational savings of $50,000 to $60,000 per year per site.

Plant floor: factories and process plants

Plant-floor IIoT is usually added to legacy equipment that is already running, such as PLCs, drives and meters installed more than a decade ago. These assets sit on wired networks, mainly Ethernet and RS-485, with Wi-Fi and private LTE or 5G where cables cannot reach. An industrial gateway translates their data, often with edge computing to buffer readings when the connection drops.

The plant floor speaks industrial protocols. Modbus, published by Modicon in 1979, remains common on meters and PLCs, and OPC UA, released by the OPC Foundation in 2008 and standardized as IEC 62541, carries structured machine data. Drives and controllers also use Profinet and EtherNet/IP, and MQTT 5.0, an OASIS Standard since March 7, 2019, moves the data to the cloud.

For what this looks like on the plant floor, see these five industrial IoT applications with real examples, from OEE monitoring to energy efficiency.

Field and remote assets: mining, oil and gas, construction and agriculture

Field IIoT connects production assets outside any building: mine sites, oil and gas wells, construction equipment, and farms with barns, irrigation and greenhouses. The devices are rugged, outdoor and often battery or solar powered, and they connect over cellular, LoRaWAN, satellite or private LTE. On top of those networks they usually speak MQTT, Modbus RTU or DNP3. A failure often means a costly site visit, a spill, or lost crops and livestock.

Being outdoors changes the tech stack, not the category. A pump on a well pad and a pump in a process plant are both IIoT, because production stops when either one does.

What is infrastructure IoT?

Infrastructure IoT is IoT owned by a city, utility or public agency to run water, power, traffic, public transit and environmental monitoring. The devices include water-level sensors, utility water and power meters, traffic counters, environmental stations, substation monitors and transit vehicles, spread across a city or region. A failure disrupts a service the public depends on, and a flood or power outage puts public safety at risk.

Infrastructure networks use LoRaWAN, NB-IoT, LTE-M, cellular and fiber. Grid and substation equipment speaks DNP3 and IEC 61850, while newer sensors use Modbus and MQTT.

Peclet, a Sydney team that works with Australian city councils, builds infrastructure IoT. At Coogee Beach in Sydney, which draws more than 8,000 visitors per day, meshed sensors on a LoRaWAN network through The Things Network feed Ubidots dashboards with weather, beach and safety conditions. Utility networks follow the same model, as in this IoT water infrastructure monitoring of pumping stations.

Where do healthcare, agriculture and vehicles fit among the types of IoT?

Healthcare, agriculture and connected vehicles are industries, not types of IoT, so each one splits across the four types by owner. Treating them as separate categories would hide the differences inside each industry: a fitness wearable and a hospital equipment tracker share an industry but not an owner, an uptime target or a cost of failure.

  • Healthcare: wearables and home monitoring are consumer IoT. Hospital equipment tracking and clinical environments are commercial IoT.
  • Agriculture: farms, barns, irrigation and greenhouses are industrial IoT in the field, because a failure means lost crops or livestock. A hobby greenhouse is consumer IoT.
  • Connected vehicles: a personal car is consumer IoT, a delivery fleet is commercial IoT, heavy equipment is industrial IoT in the field, and public transit is infrastructure IoT.
  • Mining, heavy machinery, oil and gas: industrial IoT, even outdoors.

IoT vs IIoT: what is the difference?

The difference between IoT and IIoT is who owns the system and what a failure costs. IoT is the umbrella term for any connected device that sends data over the internet; IIoT is the subset owned by producers, where a missed reading can stop a line, overflow a tank or breach a safety limit. IIoT hardware is therefore rated for heat, dust, vibration or weather and stays in service for years. Consumer and commercial failures can be serious too, but they rarely stop production.

The table compares consumer IoT, commercial IoT and IIoT on the attributes that change a project's design.

AttributeConsumer IoTCommercial IoTIndustrial IoT (IIoT)
OwnerHousehold or individualBusiness, building, hospital or fleet operatorManufacturer or operator of production assets
EnvironmentHomes, personal devices, carsOccupied buildings, vehiclesPlant floor (heat, dust, vibration, electrical noise) or field (weather, remote sites, battery or solar power)
NetworksWi-Fi, Bluetooth LE, Zigbee, Thread, cellularWi-Fi, Ethernet, Bluetooth LE, LoRaWAN, LTE-M, NB-IoT, LTEEthernet, RS-485, private LTE/5G on the plant floor; cellular, LoRaWAN, satellite in the field
ProtocolsMatter, proprietary cloud APIsBACnet, Modbus, MQTTModbus, OPC UA, MQTT, Profinet, EtherNet/IP, DNP3
IntegrationNew devices, set up by the ownerNew sensors plus existing building controlsExisting PLCs and legacy equipment through gateways
Uptime expectationBest effortBusiness hours to 24/724/7; downtime stops production
Security guidanceNIST IR 8425 consumer profileNIST IR 8425 also guides small-business purchasesNIST SP 800-82 Rev. 3
Cost of a failurePrivacy breaches, home safety risks, botnet recruitmentSpoiled inventory, compliance fines, patient safetyLost production, equipment damage, safety or environmental incidents

How do you tell which type of IoT a project is?

The type of IoT a project belongs to follows from two questions about owner and consequence, plus a third for industrial projects. Starting from the technology does not work, because a LoRaWAN sensor fits three of the four types. A household facing a safety or privacy risk is running consumer IoT; a producer facing lost output is running industrial IoT.

  1. Who owns and operates the system? A household, a business, a producer, or a public agency.
  2. What does a failure cost? Home safety and privacy, money and compliance, production, or a public service.
  3. For industrial projects, where do the assets sit? On a plant floor with wired networks, or in the field on cellular, LoRaWAN or satellite.

When a project spans two types, such as a manufacturer with a plant, an office and a delivery fleet, design each part for its own type and the shared platform for the strictest one.

Why do consumer-grade IoT devices fail in industrial environments?

Consumer-grade IoT devices fail in industrial environments because plants and field sites expose them to conditions and integration demands they were not designed for. A plant floor adds heat, dust, moisture, vibration and electrical noise from motors and drives, and a field site adds weather and no one nearby to reset a device. Industrial-grade electronics are specified for wider temperature ranges than consumer parts, and Wi-Fi built for a home struggles across steel structures and long distances.

Integration is the second failure point. A factory's PLCs and SCADA system were installed to run the process, not to share data, and many speak only Modbus or a vendor protocol. Connecting them is harder than a commercial rollout because the integrator must read data from a running system without disturbing its control logic, often across equipment from several vendors and decades.

The usual fix is a gateway that reads the PLC alongside SCADA instead of replacing it. The gateway polls registers over Modbus TCP or OPC UA and publishes the values over MQTT to a cloud platform such as Ubidots, leaving the control system untouched. One walkthrough shows how to send PLC data to the cloud with Node-RED and Modbus TCP, another configures a Siemens SIMATIC S7 PLC as a Modbus TCP server, and this list compares industrial IoT and edge gateways by protocol and price.

How many IoT devices are connected today?

IoT Analytics projected 21.1 billion connected IoT devices worldwide by the end of 2025, up 14% from 2024, and forecasts 39 billion by 2030, according to its State of IoT 2025 report (October 28, 2025). The count excludes computers, laptops, phones and consumer tablets, so it measures IoT devices rather than all connected electronics. IoT Analytics does not split the headline figure between consumer and enterprise devices, so any consumer-versus-industrial share quoted without a named source is an estimate.

Where does AI fit across the types of IoT?

AI adds the most value where a failure costs the most, which makes industrial and infrastructure IoT its natural fit. A dashboard shows a reading only when someone opens it; an AI agent reads the live data, explains what changed and acts before a missed reading becomes downtime, a spill or a service outage. Machine-learning models handle the numbers, such as anomaly detection and forecasting, while a large language model (LLM) reasons over their results, as these five prompts that break an LLM, and the ML tool-calling that fixes them show.

A general-purpose AI assistant cannot see a machine because it has no telemetry, so the agent belongs inside the platform that collects the data, which is how industrial AI agents are deployed in practice. Industrial AI and IoT platforms like Ubidots build that layer from four parts:

  • Agents reason over live and historical data, answer operational questions in plain language and carry out actions.
  • Watchers trigger that analysis on a schedule or an event, such as a device that stops reporting, without anyone having to ask.
  • Connectors reach outside systems in both directions: outward to open a work order in an ERP, inward to bring data back.
  • Channels deliver the result where the team already works, such as the web console or WhatsApp.

The four parts work the same way in every type of IoT; what changes is the cost of the failure they catch. In a commercial building, a Watcher that flags an HVAC unit drawing more power than usual saves money. On a plant floor, the same pattern applied to vibration data is IoT predictive maintenance, and a Connector opens the work order before the machine stops.

Choosing among the types of IoT for a project

The types of IoT differ less in their sensors than in their owners and the cost of a failure. Consumer IoT optimizes for quick setup and safe defaults, commercial IoT for operating cost and compliance across buildings and fleets, industrial IoT for uptime on equipment that already runs, and infrastructure IoT for public service across a region.

IoT platforms like Ubidots collect data from all four types over MQTT and HTTP, including readings that gateways pull from Modbus and OPC UA equipment, and put them in the same dashboards, alerts and agents. Try the Ubidots IoT platform with your own devices.

Frequently asked questions about the types of IoT

Is IIoT part of IoT?

IIoT is part of IoT: the Industrial Internet of Things is the subset of IoT that connects production assets such as PLCs, meters, pumps and heavy equipment. IIoT uses the same building blocks as other IoT, including sensors, networks and cloud software, but adds industrial protocols like Modbus and OPC UA and stricter uptime and safety requirements.

What are the 4 types of IoT?

The four types of IoT are consumer, commercial, industrial (IIoT) and infrastructure IoT, separated by who owns the system and what a failure costs. Consumer IoT belongs to households, commercial IoT to businesses, hospitals and fleets, IIoT to producers on the plant floor or in the field, and infrastructure IoT to cities, utilities and public agencies.

Is a smart home device consumer IoT?

A smart home device is consumer IoT when a household buys it for personal use, as with a thermostat, door lock or voice assistant. The same sensor becomes commercial IoT when a business installs it in a hotel or office and runs it for occupants. The owner decides the type of IoT, not the hardware.

What connectivity does commercial IoT use?

Commercial IoT runs on Wi-Fi and Ethernet inside buildings, Bluetooth LE for asset tags, and LoRaWAN, LTE-M, NB-IoT or LTE across sites and fleets. Over those networks, building controls speak BACnet (ANSI/ASHRAE 135), meters often speak Modbus, and a gateway translates both into MQTT for the cloud platform that stores and charts the data.

Does industrial IoT need the cloud?

Industrial IoT does not require the cloud for control, which stays in PLCs and SCADA on site. Edge computing on a gateway filters, buffers and acts on data locally, so a dropped connection does not stop the process. The cloud adds remote dashboards, alerts and history across sites, which is where IoT platforms receive the data over MQTT.