INSIGHT · AMBIENT IoT

Ambient IoT vs RAIN RFID.

Ambient IoT is a real technical development and a heavily marketed term, and the two do not describe the same thing. This is what it means, who is using the phrase for what, and where it genuinely beats passive RFID.

Book a 30-minute scoping call

The term does not have one meaning

Before comparing anything, it is worth knowing that ambient IoT has no single accepted definition, and the three groups using the phrase mean different things by it.

The Ambient IoT Alliance defines it as devices primarily powered by harvesting ambient energy — radio waves, light, motion, heat. That is a technically useful boundary. Its founding members include Atmosic, Infineon, Intel, PepsiCo, Qualcomm, VusionGroup and Wiliot.

Wiliot uses the term prominently and frames it more broadly, as a new class of connectivity built into everyday things themselves. That is a product framing rather than a technical boundary.

3GPP uses the term for something different again: a cellular specification for battery-free backscatter devices read by a base station.

So the first question in any vendor conversation is which of those three they mean. They are not interchangeable.

The cellular version, and why it is not imminent

3GPP studied ambient IoT in Release 19. What it standardises is narrow: Device 1 only, meaning fully passive backscatter at roughly one microwatt, read by a base station, on licensed FR1 spectrum, with minimal protocol layers and no mobility.

The more capable device classes — reflection amplifier and very-low-cost active — are deferred to Release 20, whose stage-3 freeze is targeted for March 2027.

Our reading: with Release 20 protocol work not due to freeze until 2027, we would not plan on commercial cellular ambient IoT deployments before about 2028. If a roadmap presented to you depends on it sooner, ask which release it is built on.

Battery-free Bluetooth versus passive RAIN RFID

This is the comparison that actually matters today, because both are purchasable now.

	RAIN RFID (passive UHF)	Battery-free BLE
Read range	A few centimetres to several metres (RAIN Alliance)	Vendor-stated up to 40 m broadcast; energising range considerably shorter, around 3 m at 2.4 GHz
Read rate	Up to 1,000 items per second (RAIN Alliance)	Not comparable — event driven, not bulk inventory
Tag cost	Mature multi-vendor supply	Vendor-stated from around 10 cents at high volume
Infrastructure	Readers, antennas, portals	Energiser bridges plus gateways or phones
Sensing	Limited; temperature via specific sensor ICs	Temperature, humidity, light
Data	Identifier plus user memory, no compute	On-tag compute, cloud-mediated event stream

Read the cost row carefully. The 10 cent figure is a vendor claim at high volume. We could not find an independent 2026 benchmark for RAIN pricing and published figures vary widely, so we will not quote a number we cannot stand behind. Get both quoted, at your volume, for your item.

Where each genuinely wins

RAIN RFID wins decisively on cost per tag, bulk read rate, dock door and portal throughput, mature multi-vendor supply, and item-level tagging economics at retail scale. If you need to read a pallet of items in one pass, nothing else is close.

Ambient IoT genuinely adds autonomous sensing and near-continuous state reporting without anyone pointing a reader — cold chain condition, dwell time, environmental exposure. If the value is in what happened to this item over time rather than is this item here now, that is a real capability difference, not a marketing one.

The two are not substitutes for each other as often as either camp implies. A number of sensible designs use RAIN for inventory and a much smaller population of sensing tags for the items where condition matters.

Gen2v3 and Gen2X: know which is a standard

Two names come up in RAIN conversations and only one is a standard.

Gen2v3 is the GS1 EPC UHF Gen2 air interface standard, current release 3.0.1 ratified February 2026. Version 3.0 (2023) was developed against GS1’s Gen2v3 business requirements; the specification includes commands such as QueryX/QueryY for tag filtering and ReadVar for memory reads. This is an open standard.

Gen2X is Impinj's vendor-defined extension. Standards-compatible, but not a GS1 or ISO standard. Impinj describes extended read range, tag selection at the start of an inventory round, Protected Mode and cryptographic authentication; Impinj and Zebra material notes that the advanced features need both Gen2X-enabled readers and Gen2X-capable tag chips.

That is worth knowing before it appears in a specification. Requiring Gen2X in an RFP is requiring one manufacturer, whether or not that is your intention.

What we would advise

Decide what you need to know about each item, and how often. Identity at read points is a solved, cheap problem and RAIN RFID solves it. Condition over time is a different problem with different economics, and it is where ambient IoT earns its premium — on the subset of items where condition actually changes a decision.

Be sceptical of any proposal to replace a RAIN estate with sensing tags wholesale. The cost difference is real, and most items in most estates do not need to report anything except that they are present.

We sell no tags, readers or platforms, and hold no partner tier with any vendor named on this page.

Sources

Vendor and standards facts on this page come from the public sources below, checked on 25 September 2026. Vendor statements are reported as the vendor’s own claims.

Last updated: 25 September 2026