A second product on the same app and cloud: that's when you want Groundrun
Your first product shipped, and it sold. Now you want a second one on the same app and the same cloud.
Blog
From the ground
Patterns, scenarios, and lessons on developing connected products with AI agents, validated on real hardware.
Hardware in the loop brings speed, flow validation brings confidence
Put the hardware in the loop and development moves at the speed the agent works. It flashes the build, walks the flow, reads what the product did, and goes again. That's the first half of putting the real device inside the agent's loop.
Why AI agents need hardware in the loop
Put the hardware in the loop. An AI coding agent working on a connected product should be able to run its change on the real device while it works, then read back what the device did.
Be bold, with confidence: why people choose Groundrun
Groundrun is the validation step inside agent-driven development of a connected product. Your flows run on your own hardware, with your app and your test cloud in the run, and the AI coding agents invoke them from inside the loop where they work.
Vibe coding vs. agentic engineering for products that span cloud, app, and firmware
Vibe coding is a way to find out whether an idea is worth building. Agentic engineering is a way to build a product that has to keep working for years.
How to start using AI coding agents in connected product development
An AI coding agent can turn a paragraph into a working web app. Getting the same kind of useful first result on a real connected product codebase is a harder problem, and a different one.
In-loop validation runs the tests your team already owns
A connected product team already tests at several levels: unit tests on each module, full-system scenarios that walk a real device through a real flow, and a final quality assurance pass before a release reaches customers.
In-loop validation is what makes agent-driven development of connected products work
Every change to a connected product has to answer one question: does the whole product still work? The firmware passes its tests, the app passes its own, the cloud deploys green, and the flow a customer actually walks through crosses all three and answers to none of them.
Three passing test suites and a broken onboarding screen
Three green checkmarks. Zero cross-domain coverage.
The speed of AI stops at the testing gate
What happens when an AI agent finishes a firmware change in an hour, but the verification queue holds it for three days?
Your engineering leadership matters more when AI writes the code
You watch an agent produce a code change that would have taken a senior engineer two days. The code is clean, the tests pass, and the commit message reads like a senior engineer wrote it.
Every connected product company just became a software company
An AI agent picks up a firmware task on a connected product: cut the time a device takes to reconnect after a Wi-Fi drop. As it works, it runs the cross-domain scenario suite, flashing the build to a test device, dropping the network, and checking that telemetry and the app both come back online.