Developer Tools · Simarium

DevTools

Creator — soloApr 2026 – Presentdevtools.simarium.in ↗

Starting point

Started from an empty repository

Nothing was here before — I set up the repository and built the whole thing.

What I owned

Designed
Built
Shipped
Operated

The moving parts

What talks to what — clients, services, data, and the boundaries between them.

Web appClients

Simulation engineModelled state

2D canvasRendering

Push to prod

The checks a change has to pass before it ships, and what watches it after.

Source

DeployFE · BE

Node detail

Pick a box

Tap any box in the diagrams to see the tools behind it and what each one did on this project. Tap again to let go.Hover any box in the diagrams to see the tools behind it and what each one did on this project. Click to keep it open; Esc lets go. On a touch screen, tap.

The product

Interactive simulations of the systems developers rely on daily, run against modelled state in the browser.

What I built

Full ownership as a solo developer — frontend and deployment, under his own Simarium banner (the whole system runs client-side, so there is no backend to operate). The Git visualizer is live and runs real graph operations; the simulation engines are written to mirror how the underlying systems actually behave rather than replaying a canned animation.

Everything I did here

Git visualizer, live today: add, commit, merge, rebase and cherry-pick against a simulated repository.
Runs a real commit-graph model, not a scripted animation.
Kafka playground live: design topics, then push events through producers, partitions and consumer groups.
JavaScript internals live — the event loop, call stack and queues, stepped through as code runs.
Docker, AWS, database and web-communication playgrounds in progress.
Simulation engines written to mirror how the real system behaves, so the semantics hold up under inspection.
Everything runs client-side against simulated state — no backend to keep alive.