
Live perception for connected devices.
Capture video, audio, and sensor streams. Process them at the edge. Compose real-time workflows and return intelligence to operators or devices.
- 30 fps
- Live video
- 42 ms
- Relay latency
- 6 surfaces
- Device targets
Three launch surfaces
One intelligence layer.
Different ways into the world.
SecondSee works like a spatial studio: begin with the edge, shape the system around the launch, then deliver it through the right hardware and interface.
Commercial systems
Put perception inside the operation.
Launch real-time viewing, tracking, recording, and operator workflows around the work already happening at the edge.- Live operations
- Workflow orchestration
- Multi-publisher rooms
Developer platforms
Compose intelligence instead of rebuilding it.
Start with device clients, a binary relay protocol, and a visual workflow engine spanning local vision, audio, models, and outputs.- Composable DAGs
- Device SDK surfaces
- Developer tools
Consumer experiences
Make the interface disappear into the moment.
Build camera, microphone, speaker, and display experiences around wearable form factors people already understand how to use.- Natural capture
- Audio interaction
- Wearable display
The system
A live loop from the world
to intelligence and back.
Bring your own compute hub. SecondSee connects capture, perception, orchestration, and output without forcing the whole experience into one device.
Capture
See and hear
H.264 · PCM · sensorsPerceive
Process at the edge
Vision · Core ML · OC-SORTOrchestrate
Compose the workflow
FRLY · FRAU · FRSEDeliver
Return intelligence
Web · device · displayINSIDE THE STUDIO
Watch the system think.
A live camera signal moving through detection, tracking, OCR, and an operator-facing viewer.
Stream from supported wearable publishers or a desktop camera through the shared relay and into the web viewer.
YOLO detection, OC-SORT tracking, OCR — chain nodes into a live pipeline that runs while you stream.
Compose detection, tracking, models, triggers, recordings, and outputs as a live graph shared by device and web surfaces.
A working system,
not a concept reel.
The core surfaces already exist across devices, local processing, relay infrastructure, workflow orchestration, and operator tools.
Wearable capture
Stream camera and audio from Ray-Ban Meta on iOS, INMO on Android, or a desktop camera into the same relay model.
On-device perception
Enhance frames, run Vision and Core ML, detect objects, track identities, classify scenes, and record locally.
Visual workflows
Compose sources, processors, triggers, models, and outputs as a live DAG instead of hard-coding one assistant.
Live relay + rooms
Move video, audio, and sensor signals through a shared binary protocol with multi-publisher room support.
Speech + audio
Route phone and glasses microphones, transcription, audio classification, synthesized speech, and playback.
Operator platform
Monitor live streams, edit workflows, inspect telemetry, manage recordings, and work with developer tools on the web.
Build for the surface
that fits the launch.
SecondSee separates the intelligence layer from the frame on someone's face. Shipping integrations stay distinct from development and evaluation work.
One signal layer.
Different capture bodies.
Smart glasses
Hands-free capture from supported wearable cameras, with audio and device-side perception sharing the same relay contract.






What SecondSee is.
And what it does not pretend to be.
Implementation status and hardware validation matter. These answers describe the current system without turning experiments into promises.
SecondSee is a system for capturing live camera, audio, and sensor streams from wearable and conventional devices, relaying those streams to browser operators, and composing perception and output workflows around them.
The repository includes iOS, macOS, Android, visionOS, browser, and XR work at different levels of implementation and validation. The device field above separates current integrations from development, probe, and evaluation surfaces instead of treating every experiment as shipping support.
No. Capture, codec, perception, audio, sensor, and output capabilities vary by publisher and hardware. SecondSee normalizes the system around shared streams and workflow contracts, but a workflow definition is not automatically a compatibility claim for every device.
It depends on the workflow. Processing can run on the publishing device, a nearby compute hub, the SecondSee relay stack, or a configured external model service. The system is designed to keep those stages composable rather than forcing the entire experience onto one device.
Deployments can use authenticated sessions, access controls, share tokens, gateway isolation, TLS termination, and configurable object storage. Exact retention, encryption, data-region, and compliance guarantees depend on deployment configuration and are not implied by the landing page.
SecondSee is for teams building a commercial system, developer platform, or consumer experience around live cameras, microphones, sensors, perception, and operator feedback. The best starting point is a specific device, signal, and outcome—not a generic smart-glasses rollout.
What device sees it?
What should happen next?
Bring a specific camera, microphone, sensor, workflow, or operator problem. We'll map the capture path, where perception runs, and how the result returns to people or devices.
Include the target hardware and the live signal you need to use.