Skip to main content

Industry of Things Platform

The platform is the stack you stand on when you deploy a device. Five layers, each with incumbents, each with DePIN challengers.

Regulatory Landscape

Hardware networks cross borders. The rules are jurisdictional.

DomainIncumbent RuleFriction for DePIN
Radio spectrumNational telecom regulatorsMesh networks need spectrum licences
Customs / originWCO, national customsCustody events cross borders mid-journey
Data protectionGDPR, CCPA, APPIDevice data may be personal data
Consumer goodsFDA, EU CE, MPIAttestation may fall short of certification
Financial settlementLocal money transmitterPer-scan micropayments hit MSB thresholds

The industry needs jurisdiction-aware contracts. See Verifiable Intent for the delegation model that bounds cross-border action.

Physical Resources

What the industry runs on — before any chip is mounted.

ResourceCurrent SourceBottleneck
Silicon fabsTSMC, Samsung, IntelGeopolitics, lead times
RFID inlaysAvery Dennison, SML, ArizonConsolidated supply
BatteriesCATL, LG, PanasonicLi/Co supply, cycle life
Rare earth magnetsChina-dominatedExport controls
ConnectivityLoRa, cellular, sat-IoTSpectrum and roaming

The DePIN thesis works only when hardware cost drops faster than network payments grow. Physical supply is the floor.

Tools and Machinery

The six-layer hardware stack, mapped to who sells what today.

LayerCategoryExample VendorsDePIN Challengers
IdentityRFID / NFC / tagsAvery Dennison, Impinj, NXPDevin Labs, Baxus
SensingEnvironmental, GPSBosch, Sensirion, u-bloxWeatherXM, GEODNET
InterrogationReaders, scannersZebra, Honeywell, RedBiteDevin Labs operator networks
Edge computeGateways, SBCsAdvantech, Dell, NVIDIA JetsonPeaq-registered gateways
ActuationRobots, valvesABB, KUKA, FanucOpen-source robot stacks
ConnectivityLoRa, cellular, satSemtech, Quectel, IridiumHelium, XNET

See DePIN Devices for the buyable catalogue. See DePIN Tokens for the economic layer.

Software and Coordination

AI and orchestration are the soft layer on top of the hardware.

FunctionWhat It DoesWhere It Lives
Device provisioningIssue identity, enrol in networkPeaq DID, custom onboarding flows
Fleet orchestrationMonitor health, push updates, rotate keysBalena, AWS IoT, W3bstream
Event aggregationCollect signed events, normalise, forwardOracle networks, custom middleware
Inference at edgeClassify readings, trigger local actionNVIDIA Jetson, Coral, Hailo
Settlement triggersRead events, call smart contractsChain-specific (Solana, Peaq, IoTeX, Sui)

Tightness Score: 4/5

Platform is the most mature P. Hardware exists, catalogues are public, DePIN stacks are shipping. The gap is not "can you buy a reader" — it is "can you wire five vendors into one signed event." Integration is the binding constraint, not availability.

Context

Questions

Which layer — identity, sensing, interrogation, edge, actuation, or connectivity — is the binding constraint for the next million verified events?

  • Is the bottleneck hardware cost, integration complexity, or standards fragmentation?
  • What does the first five-vendor interop demo look like?