Ovyaro local-first hardware layer
Device Mesh
Your camera, wearables, spatial avatar and local AI—under your control.
Permissions happen on this device, Edge Core listens only on your computer, pairing tokens stay in memory, and the robot boundary starts in simulation. Nothing is silently connected.
Private Local AI
Ovyaro Edge Core + Ollama + an installed local model
Camera Assistant
Browser camera permission; a local vision model for semantic answers
Wearables & Smart Devices
Web Bluetooth, Web Serial or WebUSB compatible hardware
AR / VR Avatar
WebXR-compatible browser/headset for immersive mode
Robot Vehicle Boundary
Simulation is built in; physical motion needs a robot-specific certified adapter
Private core
User-controlled local AI
Ollama inference runs on this PC. The pairing token is erased when this page closes.
Wearable bridge
Smart-device connections
Direct browser transports; permission is always shown by the browser. Health data is not read until a device-specific schema is added.
Local camera
Camera-based assistant
Frames never leave this browser unless you explicitly ask the paired local model.
Light
0%
Contrast
0%
Motion
0%
Color
balanced
Spatial presence
AR / VR avatar
The animated avatar and operating-system voice need no provider API. Immersive mode needs a compatible WebXR headset/browser and HTTPS or localhost.
WebXR support: checking · active session: none
Fail-safe physical AI
Robot / vehicle integration
This console validates commands through Edge Core but never sends motor output. It is the safe contract for a future hardware-specific adapter.
Simulation boundary ready. No motor output is enabled.
What still needs a vendor or hardware integration?
Base Device Mesh uses no paid API. A wearable that hides its data behind Apple, Google, Garmin or another private cloud needs that vendor's approved SDK/API. Semantic camera answers need a local vision model in Ollama. Real robot motion needs a robot-specific driver, hardware E-stop, independent safety controller and qualified engineering review. WebXR needs compatible hardware. Remote access outside this computer needs a separately secured relay; it is intentionally not enabled here.