If it hasn't passed sim,
it doesn't ship.
The Simulator runs your build manifest through million-step physics scenarios with hard pass/fail gates. A model that hasn't passed cannot be deployed — safety is enforced by the platform, not by policy documents.
Scenario presets
warehouse-dense-v2, sidewalk-crowd, home-kitchen, field-mud — battle-tested environments with parameterized difficulty, or bring your own scene.
Hard gates
Set maxCollisionRate and the run fails above it. Gates are recorded with the result, so a PASS means something specific — not a vibe.
Deterministic seeds
Every run is seeded. Reproduce a failure exactly, bisect a regression between two manifest versions, replay the same crowd crossing a thousand times.
CI-friendly
createRun + waitForRun from the SDK blocks your pipeline until a terminal state. Red build if the robot can't behave. Green if it provably can.
Faster than realtime
Runs execute at up to 400× realtime on the compute network. A million steps of warehouse traffic finishes before your coffee does.
Result diffing
Compare two runs side by side — collision heatmaps, intervention counts, energy budgets. See exactly what your last commit did to behavior.
Gate your first deploy.
Wire the simulator into CI with three SDK calls and never ship an unvalidated build again.