Skip to main content
A Simulation is a runtime instance of one ready Simulator. It has isolated state, a virtual clock, and a data-plane endpoint.

Create a repeatable run

The seed and clock start pin injected randomness and virtual time. Use the same Simulator revision and inputs when you need repeatable behavior. The create response includes a data-plane token once. List and get operations never return that token again.

Control the lifecycle

Stop a Simulation to freeze its state. Start it later to continue from that state.
Fork a running Simulation to explore another path without changing the source. You can fork the current head or a recorded step.
Use the API reference for exact Simulation routes and schemas.

Choose a Simulator

Select the behavior that the Simulation runs.

Connect Simulations

Start related systems as one World.