One platform, from the sensor to the decision.
Parallax is four parts that are designed together: models, a runtime, a desktop app and an SDK. Each one assumes the others are there, which is how a whole perception graph fits inside 8 ms.
Four pieces, one frame budget.
Use them together, or bring your own model and use the Runtime and SDK on their own.
Parallax Runtime
The engine. Compiles a perception graph for one chip and runs it one frame at a time, every frame.
How the Runtime works →Depth models
Detection, masks, tracking, pose, stereo depth and event motion, sized to fit on-chip memory.
See the models →Parallax Studio
A desktop app to add cameras, draw zones, watch detections live and read traces frame by frame.
Inside Studio →SDK
Swift, Kotlin, C++ and Python. The same session, camera and event types in every language.
Read the docs →A runtime that treats every frame as a deadline.
Inference servers wait for a batch. The Runtime does not wait for anything. It compiles one schedule per chip and keeps the answer on time, even when a node runs long.
Late answers are worse than no answer.
So the Runtime never delivers one. If a node overruns, its last good result is handed on and marked stale.
On time
Every frame gets a decision inside its budget. Overruns are handled by policy, never by a queue.
7.8 ms median · 9.6 ms p99 on dock-03Per chip
Schedules are compiled for the exact chip, so fusion and memory layout fit the hardware, not a framework.
5 chip familiesOffline
No licence check, no telemetry, no model download at run time. It works in airplane mode.
0 frames leave the deviceSee what the device sees, while it sees it.
Studio connects to a camera over the local network or USB and shows the graph running on the device itself.

- Live feed with tracked boxes, labels and per-frame timing.
- Zones and rules drawn on the image, pushed to the device in one click.
- Traces that show where each frame spent its budget.
- Works fully offline. Nothing in Studio needs a network connection to the camera.
Built for machines that move, and cameras that watch.
The same Runtime and models ship on every device class. Only the compiled schedule changes.
The video never has to leave the building.
Parallax sends events, not pixels. What leaves the device is the decision, in a few hundred bytes.
- Frames are processed in memory and discarded unless you choose to record.
- Events carry boxes, tracks and labels, not images.
- Models and schedules are signed and verified on the device.
- Runs on isolated networks with no outbound connection at all.
Put real-time vision on your device.
Install the SDK, point it at a camera and see your first detections in an afternoon.