We're here to help

Integration support

Evaluating QRIoT, prototyping with the reference firmware, or shipping a product built on top of it? Tell us where you're stuck and we'll help you get unblocked.

✉️

Email us

Fastest route to a human. We reply within one working day for integration questions, evaluations, and support on the reference apps.

support@qriot.io
🤝

Partnerships & integration

Want to deploy QRIoT on your own IoT product? We'd love to hear what you're building and walk you through how the pieces fit.

hello@qriot.io

FAQ

Common questions

What is QRIoT, exactly?

QRIoT is a reference platform for IoT device makers who want frictionless Bluetooth pairing for their products. The firmware, iOS / Android / web apps, and backend you'll find on this site are a working demo — the goal is to help you ship the same experience on your own hardware. It's not a consumer product you buy off the shelf.

What hardware does it work with?

Any Bluetooth LE device. Our reference firmware runs on an ESP32 (M5Stack Core2 specifically) but the protocol is stack-agnostic and sits on top of standard BLE advertising and GATT. If you're evaluating hardware for your product, get in touch and we'll help you map the pattern to your platform.

Do we use the reference apps, or build our own?

Either. You're welcome to fork the reference iOS / Android / PWA apps as a starting point, or integrate the onboarding protocol into an existing companion app you already ship. The protocol is designed to be a thin layer you can drop in without rewriting your BLE stack.

I'm testing the demo app and something's broken

If you're trying the QRIoT reference app from the App Store or Play Store, the most common issues are Bluetooth permissions on the phone and the device needing to display its QR code (it only advertises while the QR is visible on screen). If it still won't pair, email support@qriot.io with a short description and we'll take a look.

How do we talk about integrating QRIoT into our product?

Drop us a line at hello@qriot.io with a short description of your product and where you are in development. We'll set up a call to discuss the fit, the reference architecture, and the rollout path.