A pilot starts with the demonstrations you already have: teleop episodes, video with control logs, telemetry. You get back the generated episodes, the evals, and a trained action model, via API or as weights on your hardware.
Request a pilot ↗Custom action models for any task. A world model built from your demonstrations generates the failure cases you could never stage, then trains and tests the policy. Your data, your weights, via API or on your hardware.
Real-world collection prices an episode in teleop hours and broken hardware. A world model prices it in GPU-seconds: a recent pilot's 40 missing episodes cost $2.32 to generate. That inversion is the entire company.
The episodes a policy needs most are the ones a real robot can least afford to produce: drops, near-misses, collisions. Inside the world model they cost cents and nobody calls maintenance.
The same world that generates training data is an evaluation range. Policies run against the generated failure cases before they touch your hardware, and the readout ships with the weights, whichever way it goes.
API labs meter imagination, which is ruinous at training scale and impossible where data can't leave the building. We deliver trained weights on your data, on your cluster if you want. Your simulator is your moat.
NVIDIA released Cosmos 3 Edge on July 20 with no public path to fine-tune it for a robot other than their own. Ten days later ours ran on an SO-101, for $342.
a dreamed episode: one real photograph plus 240 commanded actions in, sixteen seconds of imagined pick-and-place out.
Play the live demo ↗When General Intuition and Kyutai released MIRA, the first open multiplayer world model, we rebuilt it from scratch in the week that followed: codec, model, four-player fine-tune. MIRA Mini.
four players, one world model: MIRA Mini, our one-week reproduction of General Intuition & Kyutai's MIRA (open release, demo only).
Play it live ↗Local weights are a promise about hardware, so we spend real effort making models smaller and faster. An 18M-parameter policy runs on the factory cell; the curve below is the same discipline applied to our world models, measured:
real output from our first multiplayer local world model, released in March 2026.
Play the live demo ↗One task per pilot: world model built from your demonstrations, missing episodes generated, policy trained and tested, weights delivered. First contract signed.running
Every pilot returns a deployed action model, and teams that train their own models take the data and evaluation layer alone. Ten paid pilots delivered end to end is the bar.in progress
Order certified episodes and train policies inside our worlds through the API, without talking to us. The first lab already trains through it today.first users live
Success is measured one way: your policy, trained on real plus ours, beats real-only on your own eval.
A pilot starts with the demonstrations you already have: teleop episodes, video with control logs, telemetry. You get back the generated episodes, the evals, and a trained action model, via API or as weights on your hardware.
Request a pilot ↗Your model is your moat; keep it. We supply the data and evaluation layer: the edge cases your fleet logs are thin on, and a gauntlet every model update runs before it ships. When a task falls outside your stack, the same pipeline hands back a full policy.
Start the conversation ↗the world model engine · by the team serving world models in production at play.alakazam.gg