Buildings are files
Height is lines of code. A 3,000‑line module is a tower; a config stub is a shed. Watch a file grow floor by floor as it’s edited.
Your codebase is a city.
Watch it get built.
Every file is a building. Every folder a district. Height is lines of code. Press play and the city rises one building at a time, commit by commit, through your repo’s entire history.
No signup. Paste any public repo and watch it build.
Four rules, and the whole repo makes sense
Districts are folders
A squarified treemap zones the ground by directory, and the gaps it leaves become the street grid. Structure before detail.
Type picks the form
Twelve massing types. Source code builds offices and towers, docs build churches and civic halls, config builds depots and utility yards.
Every commit, replayed
One frame per commit — not a sampled approximation. Scrub the full history and see exactly when each building appeared.
Paste a URL. Get a city.
Paste any public repo
Drop in a GitHub URL. No signup, no install, no access token.
We replay the git log
One pass of git log --numstat reconstructs every file’s line count at every commit — without ever checking one out.
The city rises
Buildings break ground one at a time, in commit order, until the repo stands at HEAD.
0commits replayed, unsampled
0buildings in one scene
0draw calls, any repo size
0frames per second
Built to survive real repositories
One draw call, any size
Every building of a given shape lives in a single InstancedMesh. A 10,000‑file repo costs the same handful of draw calls as a 10‑file one.
Streamed git parsing
The log is parsed line by line as it arrives, so a repo with hundreds of megabytes of history never lands in memory at once.
Real materials
Ground‑truth ambient occlusion, an environment probe for glazing, and procedural facades with window reveals — so buildings read as solid, not as boxes.