01
Visibility is the product
Oplut should make hidden physical behavior visible without forcing builders onto proprietary hardware.
Company
Making physical data visible
Oplut starts as software hardware builders install on existing robots, boards, and rigs so hidden behavior becomes visible enough to improve, repair, and trust.
The foundation is simple: one unit worked, Oplut captured it, something changed, and the builder knew what to do next.
First proof
Raspberry Pi camera plus ESP32-S3/BNO085 IMU
Near term
Python runtime, SDK, dashboard, and local evidence
Long term
A dedicated board only if the software earns it
What we believe
Visibility is the product
02
The first loop must be undeniable
One unit worked, Oplut captured it, something changed, and the builder knew what to do next.
03
The baseline is local truth
Camera latency, IMU sample quality, wiring symptoms, and component attachment belong in local Oplut evidence first.
04
Diagnosis should be readable
The output should tell a builder what physically changed and what to inspect next.
Now
Make one Raspberry Pi runtime prove the first foundation loop.
Phase 0
Prove camera and IMU baseline capture, intentional drift checks, and builder-readable diagnosis.
Later
Consider a dedicated board only after users want a pre-flashed always-on runtime.