Blog

Notes from the edge

Engineering deep-dives, deployment stories, and the occasional strong opinion about Physical AI.

AI agent pipeline visualization

From camera to agent: forklift safety in 30 minutes

A step-by-step build of the pipeline everyone asks about — person detection, zone rules, Slack alerts, and auto-generated incident reports.

Read article →
Robot perceiving a room as a point cloud

Why Physical AI starts with spatial intelligence

LLMs read the internet. Robots have to read rooms. The case for depth as the first-class citizen of embodied AI.

Read article →
Staged OTA rollout wave across a camera fleet

Staged OTA for 100 cameras without a single bricked device

How the fleet runtime rolls out updates in waves, verifies health, and rolls back automatically.

Read article →
iToF phase wave vs dToF photon pulses

iToF vs dToF: choosing the right depth technology

Range, sunlight, resolution, power — an honest engineering comparison across our own lineup.

Read article →

From camera to agent: forklift safety in 30 minutes

Every warehouse we visit has the same poster on the wall: "STAY CLEAR OF FORKLIFTS." And every warehouse has near-misses anyway, because posters don't watch aisles. Here's the full build of a system that does — using one Spatial Robot LiDAR, the forklift-safety model, and a ten-line agent.

1. Mount and enroll

The Spatial Robot's SPAD dToF covers 8 m of choke point — the intersection where near-misses actually happen — from a single pole mount, unfazed by skylight glare. One cable, then visionlibra fleet enroll cam-047 and it appears in the dashboard.

2. Load the model

The forklift-safety model classifies forklifts and people from pure depth, tracks both, and emits a person_near_forklift event when trajectories converge. It runs on-device in real time.

3. Write the agent

Subscribe to the event; wire three actions: Slack the safety channel, log a structured record to Postgres, and generate an incident report with the depth clip attached. That's the whole program — it's the exact code on our Developer page.

4. Watch it work

Events land in Slack in under a second. The dashboard heatmap shows convergence hotspots by aisle, which — in every deployment so far — moved a pallet staging area within the first week. That's the difference between AI and an AI agent: the first one sees, the second one changes the building.

Why Physical AI starts with spatial intelligence

Language models learned from the internet's text. But the physical world doesn't come annotated — a robot's first problem isn't reasoning, it's knowing where things are, in meters, right now. That's spatial intelligence, and it's the substrate every embodied capability is built on.

RGB cameras give you pictures of space; depth sensors give you space itself. A depth frame is already structured data — distances, volumes, trajectories — which is why a 40 × 30 dToF array can drive obstacle avoidance that a 4K camera can't, at a hundredth of the compute.

Our bet with VisionLibra: the winning stack for Physical AI looks like the winning stack for GPUs — hardware, a developer-loved SDK, a model ecosystem, and a platform that operates fleets. Depth is where it starts, not where it ends.

Staged OTA for 100 cameras without a single bricked device

Firmware updates are where camera fleets go to die. Our rollout engine updates in waves — 10%, then 50%, then all — with automatic health verification between stages. A device that fails post-update checks rolls back to the previous image on its own; the stage halts and the dashboard flags the diff.

The A/B partition scheme means there is no unbootable state, and the fleet CLI makes the whole process one command: visionlibra ota rollout v2.4.2 --stage 10%. The result across our pilot fleets: 3,000+ device-updates, zero truck rolls.

iToF vs dToF: choosing the right depth technology

Indirect ToF measures phase shift; direct ToF times photons with SPADs. The practical differences decide your product:

  • Resolution: iToF wins — Spatial Vision delivers 320 × 240 for gesture and people analytics.
  • Sunlight: dToF wins — Spatial Robot ranges 8 m outdoors where iToF washes out.
  • Integration: all-in-one iToF (Spatial Home) does the depth processing on-module — 100 × 100 room-scale sensing with zero host-side pipeline.
  • Power: single-zone dToF (Spatial Mini) idles in microamps — the only choice for battery products.

Rule of thumb: interaction → iToF, navigation → dToF, drop-in simplicity → all-in-one, battery → single-zone. And since all four run the same SDK, a wrong first guess costs you a purchase order, not a rewrite.