InfiIoT Labs

Engineering claims should survive a physical test.

Each report begins with a failure mode or a tradeoff we can test. Measurements include their conditions, and claims stay labelled until the physical work supports them.

Field insight · flagship

The six failure modes that actually break IoT products

Protocol seams, decision latency, sensor drift, fleet OTA, operator adoption, and offline survival, examined through standards and destructive tests.

Read the field report →
Field insight

One meter, three radios: what NB-IoT, BLE and LoRa actually cost you

The same gas meter on NB-IoT, BLE, and LoRa, with power budgets, gateway costs, and recurring fees drawn from a shipped architecture.

Read the field report →
What-if

What if a transformer could order its own oil test?

A transformer-pilot thought experiment that follows one health threshold into evidence, approval, and an oil-test work order.

Read the field report →
Teardown · in test

Three vibration sensors, one spindle, 30 days

Publication follows the 30-day physical test and includes the measured results.

Connected-product assessment

Bring one product. Leave with a clear next step.

Use 30 minutes to test the fit around one product and one blocked decision. If there is a fit, we will outline the two-week Product Blueprint.

30-minute fit callOne productNo prepared deck