Repeatability
One validated module that travels with the machine, across series and sites.
For machine builders
For machine builders who ship vision as a repeatable machine function: stable modules, strong APIs/SDKs, documentation and product choices that survive OEM revision cycles.
What you want to achieve
You build machines for tasks such as packaging, sorting, recycling, logistics or internal transport. Vision is part of what you ship, not a station bolted on later.
One validated module that travels with the machine, across series and sites.
A focused set of cameras, optics, lighting and software you can keep for the long term.
Interfaces and product choices that do not break field machines years later.
Technical needs
High-performance PC-based systems with application software, plus smart cameras where the job is standard, always with optics and LED lighting matched to the process.
| Job on the machine | Typical stack | What we protect |
|---|---|---|
| Core machine function | PC-based + stable SDK / library | Documented interfaces, version discipline |
| Standard station on the machine | Smart camera | Fast deploy, limited custom code |
| Robot guidance cell | PC and/or 3D | Pose, variation, closed loop to controller |
| Optics & lighting | Selected with the camera | Never an afterthought on OEM lines |
Select a durable product set. Detect in PoC on your samples. Control into your machine software with APIs you can ship worldwide, full service for new modules, VAR when your team owns integration.
Architecture, FOV, lighting and interfaces before metal is cut.
Classical vs AI called correctly, no hype demos.
Product choices that survive OEM revision cycles.
Patterns we see
Dairy automation, egg grading, fruit sorting, logistics automation and robotic packaging share the same need: vision that behaves like a productised machine function.
Bring performance targets, cycle time and how vision sits in your software stack.