What is snapshot fork?

A snapshot fork creates a new environment from an already-warm one that has finished installing and building, so it costs milliseconds rather than seconds.

The alternative is booting a machine, cloning a repo, installing dependencies and building it: 60 to 100 seconds of identical work, repeated on every episode. A fork skips all of it. The parent is already built, already warm, and the copy starts from there.

A Promigence copy is ready for its first command 39 ms in, and a hundred at once still land at 122 ms.

Warm start

This is one of the terms in the Promigence glossary.

Run your own workload on it, free

Send a repo and the command you run against it, whatever that is: an eval suite, an RL rollout, a CI job, a queue of coding tasks. We build the environment once, run it a thousand times, and send back the timings, the failures and an exact price. Free, once, on your real workload.

1,000 runs of your own command, on your own repo
What each one cost in wall clock, and anything that failed
Whether a failure was your code or the environment
An exact price for your real volume

Not ready to hand over a repo? Read the quickstart or check the numbers first.