About Knilb¶
Knilb is an early-stage company working on a specific problem: the workflow gap that opens up when teams building connected products have to validate the whole system (device, firmware, cloud, and physical interfaces) together, under conditions that resemble how the product actually gets used.
We're approaching this from inside the work. The team has spent years shipping connected products, building in-house test rigs, watching them turn into the kind of fragile, person-dependent infrastructure that everyone recognizes and no one wants to maintain.
Why we started¶
The same conversation kept happening. A team finishes a product. The software side is clean enough. There's CI, there's coverage, there's discipline. The hardware side works in the lab. But when the whole system has to be exercised end to end, the work falls back to one or two people doing it by hand. Releases slow down. Field defects sneak through. The team's response is usually to hire another tester or build another rig, which buys time but doesn't fix the underlying workflow.
The tools exist. The gap is in the workflow between them, and that's what we're working on.
How we work¶
Right now, we spend most of our time talking to engineering leaders, test engineers, and product managers about how their teams actually validate systems today. Not what the process diagrams say. What the calendar says.
If you've been close to this work, we'd like to hear what your version of it looks like. The conversation goes both ways: we share what we're seeing across industries, you tell us where it lines up and where it doesn't.