ico
The replay lab

Launchers

How the replay restarts your engine under other flags, set per replica.

A launcher stops a replica's engine and starts it again with other flags. The replay does nothing else to your engine. Health checks, timeouts and restoring the original are the same whichever launcher you use. Set it per replica under launcher in the config the replay reads.

For vLLM running in a Docker container. The simplest one.

launcher:
  kind: docker
  container: vllm      # the name of the engine's container

Each config runs in a copy of the engine's container: the same image, GPUs, volumes, environment, ports and networks, with only the engine's flags changed. The flags in production are read from the running container itself. The original container is only stopped, never changed or removed, so restoring it is starting it again: it comes back with whatever it was started with.

The replay needs access to the Docker socket, so run it as a user in the docker group or as root.

Kubernetes is not supported yet: there is no launcher that restarts a Deployment under other flags.
Copyright © 2026