Reflex Dev Kit

Two boards on your bench.
One learns. The other already knows.

The kit is the smallest fleet there is: two NVIDIA Jetson Orin boards, two cameras, and the reflex layer already installed beside whatever perception you run. Show the first board something your detector gets wrong. Then watch the second board catch it, without a label, without a retrain, and without a server in between.

It is the same layer we build for aircraft and ground robots, on the board you would use anyway. You keep your detector, your flight or drive stack, and your image. We add one process.

BOARD A your detector reflex BOARD B your detector reflex one small signed message THE NODE what was it? raccoon Board A meets something new and raises it. Board B has it before it looks. The node asks; you answer.

What is in the kit

Everything needed to see it happen
on the first afternoon.

01 — TWO BOARDS

NVIDIA Jetson Orin, twice

Two is the point. One board learning is a demo of a detector. Two boards, where the second inherits what the first met, is a demo of a fleet. Developer tier ships on the Jetson Orin Nano developer kit. Defence tier ships on an NDAA-compliant Orin Nano bundle from a US board vendor; you buy the board from them, we put the layer on it.

02 — TWO CAMERAS

Jetson-native cameras, ready on arrival

Each board arrives with a camera the layer has already been brought up on. Point them at the same scene, or at two different ones. The layer reads the same frames your detector reads, nothing else.

03 — THE LAYER, INSTALLED

One package beside your stack

Reflex installs as its own process on the image the board already runs. Your detector stays yours; swap it later and the layer does not care. The kit licence covers both boards talking to each other, signed, with no central node. One key works on the kit desk and on the API, with 90 days of the Reflex Planning LLM included.

NVIDIA Inception Program

Univault Technologies LLC is a member of the NVIDIA Inception program.

04 — THE RECORD

Every kit keeps its own record

Each board writes down what it met, what it learned, and what it passed to the other, in a form an independent assessor can read. That record is the start of a certification path, not an afterthought: the procedure that decides what a fleet may learn in the field is something an authority can approve once and leave running. The kit is where you start building that record.

Price

Under a thousand dollars,
on purpose.

A lab card, not a purchase order. Developers know what a Jetson developer kit costs, so what you are paying for is visible: the layer, the licence and the record, on two boards. After the kit, a per-unit licence on the board you already buy.

FULL KIT
$999
one kit, everything in the box
  • 2 × NVIDIA Jetson Orin Nano developer kit
  • 2 × camera, brought up on the layer
  • 2 × storage, pre-flashed, ready to boot
  • The reflex layer, installed beside your detector
  • Two-board licence, signed transfer
  • The record, yours, as plain files
Reserve the full kit
BRING YOUR OWN BOARDS
$449
you already own two Jetson Orin boards
  • 2 × camera, brought up on the layer
  • 2 × storage, pre-flashed for your boards
  • The reflex layer, installed beside your detector
  • Two-board licence, signed transfer
  • The record, yours, as plain files
  • 90 days of Reflex Planning, 10,000 answers
  • Ships within 10 business days · full refund before shipment
Reserve the BYO kit
DEFENCE TIER
By quote
NDAA-compliant Orin Nano, US board vendor
  • You buy the compliant boards from the vendor
  • We put the layer on them, remotely
  • Same kit, same record, same licence
  • Selectable cryptographic backend
Ask for a quote
REFLEX PLANNING LLM
$0.01 an answer
first 1,000 free
  • The language layer for the machine, not a chatbot: what you pay for is what the labs do not sell
  • Talks with the person, picks one of your numbered actions, reports to the record
  • Every answer carries a line: confident, or not; not confident = the unit does not move
  • 1,000 answers free; kit tenants get 90 days
  • Fleets: we host it for you, or it runs in your account; by quote
Request a key

Why you cannot talk it out of its rules

A chatbot's rules are a prompt, and a prompt is a request. Tell a coding assistant "never touch that file" and one day it does, because the rule was a sentence weighed against the next sentence. Anyone who can talk to it can talk it out of the rule. That is fine for a reader; it is not fine for a body.

Here the rules that decide what moves are not in the prompt. The model may pick one of the numbered lines you wrote, or none; it cannot invent an action. Not confident holds the unit in code, not in a sentence. Stop and the safety rules run on the unit, outside the model, and nothing learned can lower them. You can talk to it all day; it will never do a thing you did not put on the list.

And this is what "correct" means in the paper. Every question carries a note written before any answer existed: the substance a correct answer must contain, and one thing it must not do. An answer that does the forbidden thing is scored not correct, however good the rest of it is. A chatbot can be right and still break the rule. Here, breaking the rule is being wrong; and in the layer that moves, breaking it is not possible.

What it says can still be argued with, like any model. What it does cannot.

The BYO kit is a checkout: one payment, built to order, ships within 10 business days, full refund any time before it ships. The full kit and the defence tier are still by quote — reserving those holds a place and charges nothing, and we confirm the price, the board and your ship window by email. Under a thousand dollars on purpose: a lab card, not a purchase order. The Planning LLM is sold for machines that act on what it says, so it is held to a standard a chatbot is not: a wrong answer is not allowed to become a movement.

The first afternoon

Three steps.
No retraining anywhere.

STEP 1

Power both boards. Open the page each one serves on your bench network. Your detector runs as it always did; the layer sits beside it and raises the frames where the two disagree.

STEP 2

Show board A something your detector handles badly. A printed decoy, an odd angle, a thing it was never trained on. Confirm the catch on board A's page.

STEP 3

Show the same thing to board B. It has it. One small signed message travelled between them; nothing in your detector or your image changed. That is the fleet property, on two boards, on a desk. Today this is measured with board B fed board A's frames; two-camera transfer is the open item in the ledger below.

Two units, and you

Three learners on your bench.
Two of them are machines.

The units catch what the detector missed and teach each other. You are the third learner. Every catch the kit makes is written to a record you keep, as plain files, on your own machine. Read it there with the Prompt Board node: small AIs on your computer that never write anything for you. They read a line and ask what you meant, and your answer is what the next unit learns from.

What the units learned is recorded. What you decided is recorded. That record is the thing an assessor reads, and it is yours, not ours.

Then two boards become twenty, and a fleet inherits what one unit learned. The specialists trained on your own journal, the way you label and the way your shop works, are carried onto the same boards. You own the school; the fleet attends it. And because every lesson was recorded with who said what, an outside assessor can read how the fleet learned and approve the procedure once, instead of re-approving every change.

That is the first taste of how this works: two boards, a desk, and you. Machines that learn with you. AI that keeps you the author.

The node is free to install and pairs with the kit. For a team, this is the after-action loop in one place: the machines catch, you decide, your assistant writes the note, the bees check it against the record.

See the Prompt Board node

Who it is for

Builders who want to see it
before they believe it.

Drone and robot builders on Jetson, university labs and courses, integrators evaluating a second detection channel for a site or a fleet, and anyone who would rather test a claim on their own bench than read about it. If your platform is not on Jetson, reserve anyway and say so; it changes what we build next.

What is true today

Nothing above this list
claims more than this list.

  • TRUEThe layer runs as one process beside your detector on a Jetson Orin, reading the camera, and raises the frames it disagrees on.
  • TRUEOn our bench, a unit shown a new object passes it to a second unit that has no camera, over a socket, as one signed message; the second unit raises on it, and a signed revocation takes it back.
  • TRUEThe record names who taught what, and a write budget bounds what any one person can teach.
  • NOT MEASUREDTransfer between two different cameras or two different boards. Kits ship with matched cameras until it is.
  • NOT YET PASSEDA stranger installing it from the box without us in the room. We are running that test in public at the next event.
  • NOT YETThe two-board video, the golden image, and the docs page.
  • NOT PUBLICCheckout. Today a reservation is a place in the queue; nothing is charged until we confirm with you.

Reserve a kit

Nothing is charged
until we confirm it with you.

This is a reservation, not a checkout. Tell us which tier and how many. We come back by email to confirm the price, the board it ships on, and your ship window, and only then do you decide. First kits ship in order of reservation. The founder reads every one of these and replies to it.

No card. No charge. Goes straight to the founder.