Now
Working- Describe, Simulate and Validate, working end to end.
- Manufacturing files for boards you bring, with the Checks Ledger inside the archive.
- A signable Design Check Record that lists the checks that did not run.
Describe a sensing problem in plain English. Bluewright turns it into a specification, runs the physics, checks your board, and states exactly what it verified and what it did not.
A spark of imagination, engineered into reality.
Describe, simulate and validate work today. Last checked October 2026, early access.
Seven stages, run in a fixed order by code. Each one states where it stands today, the same way a result states its evidence.
Brief Bluewright in plain English, the way you would brief a colleague. It returns a structured, machine-readable specification your team can review and correct.
Link-budget, coverage and antenna field physics run against the specification. Where a number cannot be computed, Bluewright reports “not evaluated” rather than inventing one.
An AI model generates the circuit board from the specification. It never labels its own work: Bluewright’s checks judge it, and you approve it before it enters your design. Until then, bring your own KiCad board.
Electrical and design rule checks run on the board, and the Checks Ledger records what passed, what raised issues and what did not run. The result is a Design Check Record someone can sign.
Production files for the board: Gerbers, drill, placement and bill of materials, with the Checks Ledger inside the archive. Generated boards follow once Design ships.
Firmware is drafted from the specification, signed and flashed over a serial connection, with progress streamed back to the app. The flash path is built end to end and now in testing. Until it is proven on real hardware, firmware stays DRAFT.
Upload measurements from your own lab, network-analyser S-parameter files first. Code checks each file and compares it with the prediction. Only then can a result read MEASURED, naming who uploaded it.
In hardware, an unchecked assumption becomes a board respin. So labels are set in code, by the checks and simulations that actually ran, and never claim more than those show.
Sensing first, then the wider physical world. Sensing systems need everything at once: physics, circuit design, firmware and proof, which makes them the proving ground. Plans carry no promised dates.
Bluewright is available by invitation. Tell us what you need to sense or build, and we will set up a walkthrough.
Please keep confidential or export-controlled details out of your first email.