Give your automation eyes it can query.
LabVision is an autonomous vision layer for the lab — cameras with intelligence behind them. Your automation methods, Workflow Wizards, and LIMS ask LabVision what it sees and make decisions from the answer: liquid volumes, sample presence, tip counts, hardware status, and more.
Shipping
In production today
Queryable
Your stack acts on it
Standard
Cameras, no custom rigs
Wizard › "Volume remaining in Reservoir A?"
LabVision → ~12 mL · enough for the next 3 steps
The difference
Your automation is precise.
Now it can see, too.
Liquid handlers execute exactly what they're told — but they run blind to the physical state of the deck. LabVision adds a vision layer the rest of your stack can interrogate. Instead of assuming, a method can ask what's actually there and decide what to do next.
-
It answers questions
"How much is left?" "Did the sample go in?" "How many tips remain?"
-
Your stack acts on the answer
Methods, Wizards, and LIMS branch on what LabVision reports.
-
It keeps a visual record
When something goes wrong, the captured deck state shows what happened.
A vision layer the rest of your stack can query
Illustrative. LabVision answers to your methods, Wizards, and LIMS.
What it sees
Capabilities your stack can query
LabVision turns standard cameras into answers your automation, Wizards, and LIMS can act on.
Volume estimation
Read how much liquid remains in a reservoir, trough, or well — so your method can branch on what is actually there.
Sample-presence verification
Confirm a sample was actually added to the wells before the run continues, instead of assuming it.
Tip counting
Count the tips on the deck so the next step knows whether it has what it needs.
Hardware & object status
Check the state of things in the lab — freezer doors, labware presence and orientation, deck state — and report what it sees.
Deck-error capture
Record what the deck looked like when something went wrong, so post-run troubleshooting starts with evidence, not guesswork.
Barcode reading
Read barcodes on tubes and plates to confirm the right labware is in the right position.
In practice
How labs put LabVision to work
Branch on real volumes
A method asks LabVision how much reagent is left and adjusts its plan instead of running dry.
Confirm sample addition
Verify samples actually landed in the wells before committing the rest of the protocol.
Check tip inventory
Count available tips before a step that needs them, so the run does not stall mid-protocol.
Validate deck state
Confirm required labware is present and correctly oriented before a run begins.
Troubleshoot from evidence
Review the captured deck state after an error to see what actually happened.
Check object status
Query the state of freezer doors, racks, and other objects the rest of your stack cares about.
Why teams use it
A vision layer, not a webcam feed
Shipping
In production today
A real product running in labs now — not a roadmap item.
Queryable
Your stack makes the call
Automation methods, Wizards, and LIMS ask LabVision what it sees and act on the answer.
Standard
Cameras, not custom rigs
Works with standard cameras — no specialized hardware to install.
Integrated
Part of the platform
Feeds a central dashboard and connects to GeNovu LIMS and Workflow Wizards.
Easy integration
Works with your existing equipment
LabVision uses standard cameras and connects to the infrastructure you already run. No proprietary hardware, no extensive modifications.
- Standard webcams, USB cameras, or IP cameras
- Hamilton, Tecan, Beckman, and more
- Queryable by GeNovu LIMS and Workflow Wizards
- Scale incrementally as your lab grows
Simple architecture
Camera
Camera
Camera
LabVision Hub
Vision processing + query API
Automation
methods
Wizards
in-run checks
LIMS
records
Add eyes to your automation
Bring a workflow where knowing the physical state of the deck would change what your automation does. We'll show you what LabVision can answer.