IoT testing services
An IoT product is never one piece of software. It is firmware on a device, a radio link that drops, a mobile app, a cloud service, and a setup flow that has to make sense to someone who will never read the manual. Each part can pass its own tests while the product still fails, because most of the defects users see live in the joins. We test the whole chain, end to end, the way it is actually used.
We are an independent testing company. We have tested other people's software since 2018, including connected devices for cold chain monitoring and for baby care, where a wrong reading or a leaked record is not a small bug. 50+ engineers, in Cluj-Napoca, Romania.
Two weeks, free if you are not happy with what we deliver. We invoice from week three.
What we test
- The device and its firmware. Functional behaviour, firmware updates and rollback, power loss in the middle of a write, and long soak runs that find the leak a one-day test cannot. For the deeper firmware work, see embedded software testing.
- Connectivity. Pairing, weak signal, dropped links and, above all, what happens on reconnect: is queued data sent once, twice or never? Bluetooth Low Energy, Wi-Fi and cellular each fail differently, so we test the ones your product uses.
- The companion app. Setup and pairing, live readings, alerts and notifications, on a real matrix of phones and operating system versions. See mobile app testing.
- The cloud and its APIs. Device-to-cloud messages, the APIs the app depends on, and whether the data that arrives is the data the device sent. See API testing.
- Security and privacy. How devices pair and authenticate, what travels unencrypted, what the APIs expose, and how personal data is handled under GDPR. See security testing.
- Load and reliability. Thousands of devices reporting at once, a fleet reconnecting in the same second after an outage, and behaviour over weeks rather than hours. See performance testing.
- Compatibility across versions. A fleet is never on one firmware version. The app has to work with the current release, the previous one and whatever an old batch is still running.
- Setup for real people. The out-of-box experience is where most returns start. See usability testing.
Where connected products actually break
The device passes. The app passes. The product still fails, and the user blames the device.
The app shows a reading from nine hours ago with today's timestamp. A device that was offline for a day reconnects and sends its backlog twice, so the chart doubles. A firmware update succeeds and the app still expects the old message format. None of these shows up when each team tests its own layer, which is why we test the seams between them on purpose.
Work we have done
Cold chain monitoring. Devices that track temperature and humidity for industries such as pharmaceuticals. We tested the firmware, the Bluetooth connectivity and whether the readings that reached the system matched what the device measured.
Baby care health monitoring. Devices sending a baby's health readings to a parent app in real time. We tested data transmission under unreliable networks, the security of very sensitive data, endurance under long use, and a setup flow that had to work for tired parents who are not technical. We brought in simulators to reduce dependence on physical devices, and ran two bug scrub meetings per sprint so problems were triaged early.
More detail in how we adapt testing for IoT devices and IoT in healthcare.
How we work without owning your hardware
If units can be shipped to Cluj-Napoca, that is simplest, and it is what we would usually propose. Where you have a rig or a lab, we design the tests and your engineers run the hardware. Where devices are scarce, we use simulators and emulators for the device side and test directly against the app, the APIs and the cloud for everything above it.
Every defect is reported with the device model, firmware version, app version and phone it happened on, plus the logs, because an IoT bug without its versions cannot be reproduced. Test cases and results live in BugBoard, so you can trace each requirement to the test that covers it. Where it pays off, we automate the app and API regression with Flows.
What it costs
$25 to $45 an hour.
The rate moves with the seniority of the engineer, how long you commit for, and the mix of manual, automation and specialist work. Longer commitments move down the range. Our tools come with the engagement, with no separate licence cost.
An engineer can be working on your product in about two weeks. We start the same way on every engagement. Two weeks, free if you are not happy with what we deliver. We invoice from week three.
When we are not the right answer
We would rather say this here than on the third call.
Hardware certification. EMC, radio type approval, ingress rating, drop and thermal testing belong to an accredited lab. We test the software and the system around it.
A certificate of conformity. Where your product needs sign-off under a safety or radio standard, that comes from a notified body or an accredited assessor. We produce test evidence. We do not issue the certificate.
An engineer next to the hardware every day. If the devices cannot be shipped or reached remotely, an on-site supplier is the right answer and we are not it.
Why us
We are independent. We did not build the device, the app or the cloud, so we have no reason to assume the layer we did not write is someone else's problem.
We built our own tools. BugBoard for test management and traceability, Flows for automation, Auditi for WCAG, GDPR and FDA auditing, BetterFlow for visibility into the hours, and our AI Security Toolkit. They come with the engagement.
Four ISO certificates, all current to 05.12.2027: ISO 9001:2015, ISO/IEC 27001:2022, ISO 13485:2016 and ISO 14001:2015. ISO 13485 matters if your device is a medical one.
4.9 on Clutch, from more than 65 reviews. Written by clients, not by us. Founded in 2018, 50+ engineers.
Common questions
Do you need our devices?
Ideally, yes: a handful of units shipped to Cluj-Napoca is the simplest setup. If that is not possible, we work with your rig remotely or use simulators for the device side and test the app, APIs and cloud directly.
Which connectivity do you test?
Whatever your product uses. Bluetooth Low Energy, Wi-Fi and cellular come up most often. Tell us yours on the first call and we will say how we would test it.
How is this different from embedded software testing?
Embedded testing goes deep on the firmware. IoT testing covers the whole system: device, connectivity, app, cloud and the seams between them. Most connected products need both, and we scope them together.
Do you include security testing?
Yes. Pairing, authentication, data in transit and the APIs behind the app are part of the test plan, and our AI Security Toolkit comes with the engagement.
How soon can you start?
About two weeks to have an engineer working on your product. The first two weeks are free if you are not happy with what we deliver, and we invoice from week three.
Talk to us
Tell us what the device does, how it connects, how it gets updated, and what the last field failure was. We will tell you which layer we would test first, and if part of it is a job for a hardware lab rather than for us, we will say so.