Hardware & IoT

Beta platform for teams shipping a physical product

A connected device beta has nothing running underneath it. If a tester does not tell you the hub dropped off the network on day three, nothing else will. What testers tell you is the main signal, which makes a quiet tester the most expensive thing in the program.

Schedule a demo Compare the alternatives

What a device program needs

Seven things a hardware beta needs that a software beta can usually do without. Each one is a reason teams outgrow the spreadsheet.

How do you keep an unreleased device confidential?

NDA acceptance is enforced before a tester sees anything, with a per-tester bypass for the cases that need one. Nothing about the device is visible until the agreement is in.

Simplify your NDA agreements

How do you test two hardware versions at once?

Labels. Tag testers by version, firmware build, region or install type, then put the same labels on tasks. A task shows up only for the testers it applies to, so one program covers several groups of devices without splitting it in two.

Segment tasks using beta labels

How do you give different testers different flows?

The same labels. Screening rules read an applicant's answers, on any question or their email address, and suggest which labels that person should get. A manager checks and applies them on the way in. From then on each group sees its own path through the program, and a manager can change someone's labels later to move them.

Collect and screen beta applicants

How do you run a test that lasts six weeks?

Each task has a date it opens on, so a day-1 setup task, a day-7 check-in and a day-45 wear-and-tear report unlock on their own instead of being three emails you have to remember to send.

Control task availability by date

How do you capture what a device actually did?

File upload steps take photos of the install, video of the failure and log files pulled off the device, attached to the task they belong to instead of scattered across a shared inbox. Rating, ranking, choice and free-text steps make answers easy to compare across testers.

Capture qualitative tester feedback

How do you know who has gone quiet?

The funnel shows invited, accepted and completed at a glance. Fourteen days after launch, every tester who has done nothing gets an automatic email telling them how long is left. Seven days before the end, testers and managers both get a reminder. A pending invite can be sent again in one click.

Track tester engagement

How do you find testers who own the device?

Publish a screening form that anyone can fill in without an account, read the answers, then shortlist, reject or invite. It turns your own audience, your waitlist, your existing customers or your field techs, into a list of testers.

Qualify testers using custom fields

AI in Stomio, and your own assistant

Two pieces run inside the product. The AI task builder drafts a full task set from a description of the device, which is how a program gets from nothing to reviewable in an afternoon. AI Canvas sits in the manager view and answers questions over your own beta data: who has gone quiet, what testers on firmware 2.1 are reporting, what the last round found.

Stomio is also a remote MCP server, which means claude.ai, Claude Desktop, Claude Code and ChatGPT connect to your workspace directly. Connect from Workspace settings, choose read-only or read and write when you connect, and cut it off whenever you want.

More than eighty tools are available, covering beta projects, tasks and steps, tickets, testers, announcements and applicant screening. In practice a program manager can ask their assistant to draft the week-two task set from the last version's program, find every tester on firmware 2.1 who reported a connection problem, or write the mid-beta announcement, without leaving the conversation. A manager can also leave their assistant to check the ticket queue on a schedule and triage what came in overnight.

Anything that would reach a tester or an applicant is shown to you in the conversation and waits for you to approve it. AI features are turned on per beta project, so a program can stay out of it entirely.

What Stomio does not do

We do not recruit testers
There is no panel to rent, but the tools are here: publish a screening form anyone can fill in without an account, then set rules on the answers that pick who to shortlist, reject or label.
We do not ship devices
Getting units out stays with you, but a beta project can require every tester's address before they start, and labels let you mark who already has one.
We do not pay out rewards
Paying out stays with you, but the top performers list names the testers who finished everything, labels group them, and a targeted announcement tells them.