A simulation studio for infrastructure
Some things only make sense when you watch them fail.
We build honest simulations of the mechanisms behind infrastructure behaviour — the retry storm that does not stop when you stop retrying, the percentile that was never about your service, the GPU that is full and idle at the same time. Playable on the page. Rendered to video you can post.
02 — The work
Three mechanisms, built end to end. Each one runs in the page — take the control and try to undo the failure yourself.
03 — Commission
We pick the mechanism
One thing your system does that people get wrong — the retry storm, the allocator, the number your dashboard is not really measuring. Not a product tour. The mechanism underneath it.
We simulate it
Physics, not animation. Requests arrive, contend for something finite, and fail the way they fail in production. Nothing on the frame is drawn by hand; every number came out of the simulation that produced it.
You get the assets
A page your readers can play with, and silent captioned video in three shapes — wide for the docs, square and tall for the feed. Yours to post under your own name.
04 — Method
These are made for an audience that will check them. So the things that make a simulation trustworthy are built in rather than promised.
The simulation is the source
The video is a recording of the same code this page runs. There is no separate animation to drift out of step with the model.
Deterministic and seeded
The same specification renders the same frames on any machine. The parameters and the seed are printed on the frame, so a reader can check the run.
It has to earn the claim
Every piece is run against twelve checks before it ships — that the fix is real, that the loop closes, that the number moves, that the constants are sourced. Anything traded away is written down on the artifact.
If your system does something subtle, it deserves better than a diagram.