Follow the request.
Understand the system.

A living map of an imaginary document service. Switch environments, follow a route, and break something safely.

FICTIONAL TOPOLOGY
SIMULATED TRAFFIC · ZERO NETWORK CALLS

Selected environmentPRODUCTION10.42.0.0/16 · fictional

Route stateHEALTHYAll selected paths available

Application replicas6 / 4API / worker replicas · model settings

Highlighted edges9Click a line to inspect its connection

Production / network map
Click a component or connection. On mobile, swipe the map.

Web / APIAsync messagesData / storageInterruptedAnimated dots are illustrative, not measured rates.

Experiment safely

What happens when the path breaks?

Try “Create an export,” stop the workers, then trace the request. The API can accept work while delivery is stuck.

Request journal

A trace is worth a thousand arrows.

Select a flow, then choose Trace request. No real request is sent.

Inspect the embedded topology JSON

This is the data driving this page. The separate topology.json is an editable reference copy; changing it does not automatically rebuild this HTML.

This entire explorer is one HTML document.

The moving packets, environment switches, inspectors, and simulated traces run in your browser. No cloud account or backend deployment is needed to try this example. Keep the explanation and topology beside the interactive page in one Marke.st collection.

Build and publish an artifact like this ↗Play Queue Rescue ↗Explore the full gallery ↗