nought
EN FR
Design partner

The most expensive bug is the one your customer finds.

Reliable tests on your own hardware, at every commit, without depending on a hand-built bench or on one person.

Become a design partnerfree, selective Or reserve early access, CHF 1 000

Not ready yet? Join the waitlist and follow the progress.

In service on two Crispy hardware-CI benchesYour pipeline stays in chargeIn your lab or hosted by Nought

How a hardware-in-the-loop run works

One run, from lease to clean state. Select a step to follow what changes on the bench.

bench clean, ready for a run

A Nought bench, part by part An isometric drawing of a Nought bench, read from left to right. A controller is linked to a PoE switch. From the switch, one cable goes to each of three nought machines: Raspberry Pi boards with a PoE HAT, each on its mount and each wired to its own embedded system. The first machine, the one a run leases, is drawn in detail: two USB leads go from the Raspberry Pi to a plate carrying an RP2040 target board and its SWD probe, joined by three SWD wires. The second machine tests a larger board, the third a small enclosed device tapped by a Glasgow digital probe. On a commit the pipeline asks the controller for a machine, its parts seat, it powers up and boots from the network, the target is flashed and tested, a verdict goes back to the pipeline, then the target is erased and the machine powers off. Glasgow Raspberry Pi 3 Model B RP2040 target SWD probe 1controller2PoE switch3nought machine4PoE HAT5target plate6your embedded system7SWD probe8digital probe lease API firmwaresha256 9f2a…deviceserial 0048testssuite v1.4verdictPASSFAILsignature, on the roadmapclean staterun in progressPASSFAIL
A Nought bench: one controller, one switch, one machine per embedded system. The run shown here is an illustration.

  1. Your pipeline requests a bench

    nought: lease acquired by ci runner

  2. Diskless boot.

    booting from ram, no disk attached

  3. Full power cycle.

    dut: power cycle, rail A off → on, cold start

  4. Verified reference image.

    provision: reference image written, readback verified

  5. Run your tests over SSH.

    ssh: test session open, serial and signals captured

  6. The result returns to your pipeline

    verdict: PASS, returned to ci runner

  7. Erase. Power off. Ready again.

    swd: target erased, power off

Test it against your bench: become a design partner Reserve a bench from the first batch

Keep your tools. Let the bench run itself.

Works with your existing CI
Use GitHub, GitLab, Jenkins or your own tooling to reserve a bench, run tests and collect results. Your pipeline stays in charge.
First green in days, not months
If your test scripts already exist: wire your target, point your CI at the lease API, run.
No framework, no Kubernetes
Standard Raspberry Pi plus off-the-shelf probes. No proprietary boards.

Release with confidence, not a hope that the bench was right.

A green check matters only when it supports a release decision. Nought starts each run from a known state, so your team can reproduce failures and release with confidence, not guesswork.

Catch defects before customers do

A test you cannot trust becomes a field failure. Real-hardware tests find it before release, where it is cheaper to fix.

The Milbank Quarterly, FDA data

Your bench should not depend on one person

Replace one person’s setup and know-how with a workflow the whole team can run the same way.

A green check you can trust

A passing result reflects your firmware and tests, not whatever state the bench was in that day.

In service on Crispy.

Two benches run the hardware CI of Crispy, our open-source A/B bootloader: boards, pipeline and control portal.

On the roadmap: a signed record of every run for audit evidence. See what it will contain.

Watch Nought in under 30 seconds on YouTube.

The first test bench: a Raspberry Pi with its PoE hat on a black mount, next to a plate holding the RP2040 target and its SWD debug probe
The first bench: a Nought machine on its PoE mount, the RP2040 target and its SWD probe on the plate.
The control portal: one bench ready with SSH up and its boot trace, one bench free, and an SSH console opened with the boot's ephemeral key
Every bench at a glance: state, boot trace, and a console opened with the key generated at each boot.
A green CI run on the bench: the pipeline leases a bench, builds the firmware, flashes it over SWD, runs protocol tests on the target and releases the lease
From lease to release in one pipeline: firmware built, flashed over SWD, protocol tests on the target, then the bench frees itself for the next job.

Does this look like your bench?

Show us your target and your CI. We are validating Nought with a small number of embedded teams.

Become a design partner, free and selective

Built because we needed it.

After 20+ years across IT, software and firmware, I kept seeing the same gap: software is automated; real-hardware tests remain bespoke and manual.

At ADNT, Crispy made it concrete. We built the bench our CI needed: one it can reserve, boot clean and reset after every run. Nought is the bench I kept wishing I had.

Three ways to get involved.

Shape Nought with us, reserve a place in the first batch, or follow its progress.

We built it for our bench. Now we want to test it against yours.

Help us validate Nought against your board and workflow.

Design-partner access is free and selective. We read every application and reply personally.

  1. Sep 2026 launch gathering, 2 months, consolidation
  2. Dec 2026 roadmap published early-access influence
  3. Jan 2027 development starts development
  4. for early-access users first batch

early-access sign-ups open until the end of 2026

Early access

CHF 1 000

One-time deposit, deducted from your first bench

100% refundable

Your email first, so we can reach you about your access and any refund. We’ll then take you to SumUp for your name and payment.

  • Get priority access to the first hardware batch.
  • Your CHF 1 000 are deducted from the price of your first bench.
  • Help shape the roadmap.
  • No budget risk: the deposit is fully refunded if Nought never ships.

Waitlist

Interested, keep me posted.

Every run leaves a record.

On the roadmap: a signed record linking firmware, device, tests and verdict. Audit evidence, not a screenshot.

Roadmap item. No run is signed today.

Questions

Compared with other tools

Why not Jumpstarter or labgrid?

They solve remote access to hardware, and they do it well. What they don't do is make the test host itself disposable. Nought does. Think of it as an extension of your CI, not a replacement for your tools.

How is it different from Lager or BenchCI?

They wrap your bench and ship your tests to it. Nought does one thing: it makes the test host itself ephemeral, so reproducibility comes from the machine, not from how carefully someone wrote the teardown script. Run it next to them, or on its own.

Getting started

How long until my first green pipeline?

If your test scripts already exist: a few days. Wire your target, point your CI at the lease API, run. No lab to build, no Kubernetes, no IT project. Framework-based labs quote weeks to months per embedded system.

Does it need Kubernetes?

No.

What hardware does it run on?

Standard Raspberry Pi plus off-the-shelf probes. No proprietary boards.

Stage and price

What stage is the product at?

The bench is in service: it runs our own hardware CI on Crispy. What we're defining now is the public product. This phase is about collecting the concerns and needs of embedded teams; we'll then publish a roadmap listing the features that will be implemented. Design partners and early-access users shape it directly.

How much will a bench cost?

The final price isn't announced yet. Early-access users pay a CHF 1 000 deposit, deducted from the price of their first bench and fully refunded if Nought never ships.

When does it ship?

It's in development. Early-access users get the first batch and set the priorities.

What if it never ships?

Full refund, no questions asked.