OpenBeam Open the app Start free

Scaling world-model physics.Video shows what happened. OpenBeam records why: state, load, controls and repeatable scenarios.

OpenBeam Cloud runs soft-body physics on our servers at a fixed 2 kHz timestep, so you need no GPU. Each run records its video together with the controls and engine data behind it, and AI agents can drive the whole loop over MCP. The data is yours.

Sent. Check your email for your link.

Become a design partner

14-day free trial with 3 simulation hours. No card needed.

Every scene in this reel is soft-body physics running on OpenBeam Cloud. A Saturn V launch, a freight train, a helicopter, a race start, heavy machinery, a robot welding cell and a wrecking ball through a brick wall. Each was generated and filmed in the cloud with its telemetry recorded: the controls and engine data on the same clock as the video.

The training gap

A robotics team can collect hours of video of a task. The model still lacks the force, stress, contact state and controls behind it. When a run goes wrong, the team can’t ask what changed in the physics, so each round of iteration takes weeks.

Video alone

Shows what a task looks like, frame by frame. It can’t tell a model why a grip slipped or a beam gave way.

What’s missing

Force, stress, contact state and the controls that produced the motion, on the same clock as the pictures.

What OpenBeam adds

Runs you control and can repeat, with their state and inputs recorded beside the video. Change one parameter and see what changed in the physics.

The closed loop

World-model work is becoming interactive. An agent acts, the world responds, the model reads ground truth, and the next run comes from what the model got wrong. OpenBeam Cloud speaks MCP, so an agent can drive the whole loop with no person in it.

Observe

The agent watches the stream and reads telemetry: speed, position, nodes, beams and broken beams.

Act

It loads maps, spawns vehicles and robots, sends controls or runs a test script inside the engine.

Simulate

The node-and-beam solver steps at a fixed 2 kHz on our servers. Parts bend, slip and break.

Evaluate

The run’s telemetry and recording show what happened. The agent changes a part or a parameter and goes again.

Connect Claude, Codex or any MCP client. It uses the same tools you do: create and upload a vehicle, robot, prop or map, start runs, change parameters and read the results. Connect over MCP.

Scale it

The loop repeats: generate variants, run them, package the traces, train or evaluate, then generate the next sweep.

Sweep

An agent or script varies worlds, assets, terrain and controls. Scenarios are repeatable, with versioned setup.

Parallel sessions

Each variant runs in its own cloud session. An account runs one session at a time, so a team runs one per seat, side by side.

Labeled traces

Every run comes back as video, controls, engine data and metadata in open formats.

Model loop

Train or evaluate on the traces, find where the model fails, and aim the next sweep there.

Physics data grows with compute, not field-collection headcount.

Pricing

Start free. Choose a plan when you need more simulation hours.

Plan Free trialEvery new account PersonalResearchers, students, agent builders TeamsStartup and lab teams EnterpriseCommitted annual usage
Price $0 $30 / month $150 / seat / month Custom
Simulation hours 3 in your first 14 days, then 30 minutes a month free 30 a month included 100 a month per seat included Committed annual usage
What you get The full solver, telemetry export and MCP Everything in the free trial, plus private model storage Everything in Personal for each seat, paid by invoice SSO and private deployment
Get started Start free trial Start free, upgrade anytime Book a demo Book a demo

Paid plans are open. Every new account starts on the free trial (3 simulation hours over 14 days, no card), then gets 30 free minutes a month. Founding price: the first 100 Personal subscribers who subscribe by November 1 keep $30 a month for 12 months. Hours are counted per session: five one-hour sessions use five hours. Time waiting for a GPU isn't counted; a session counts until it ends (on paid plans, from December 1, 2026), so press Leave when you're done. Metering for usage past the included hours, with spend alerts and caps, is coming. Until it starts, usage past the included hours isn't charged, and we'll tell you before it does. Team plans can pay by invoice. Enterprise plans can also include OpenBeam for your desktop, so you can run tests on your own machine before sending them to the cloud.