LOCAL REQUEST FLIGHT RECORDER
Watch one Node.js request cross your app, inspect the TypeScript declaration behind every proven hop, and replay the causal path — locally, without a hosted observability stack.
GUIDED PRODUCT WALKTHROUGH
Route, middleware, services, databases, queue, and external calls appear in execution order—not as an aggregate diagram.
THE OPERATING MODEL
Static analysis explains what the application declares. Runtime events prove what one recent request did. Runtime Atlas keeps the distinction visible.
Discover literal routes, middleware, services, databases, caches, queues, and external calls.
atlas.service({ id, label }, handler)
Use the first-party SDK or existing OTLP/HTTP JSON exporters without blocking requests.
trace → parent span → child span
Resolve explicit node IDs, code provenance, HTTP routes, then bounded runtime-only evidence.
static node ⇄ measured span
Select history, scrub ordered events, inspect source context, export, or clear retained traces.
26 / 26 events · 483 ms
PRODUCT EVIDENCE
The built-in local demo models checkout, search, and a dependency failure with simulated downstream delays. It demonstrates the workflow without pretending to call real third-party systems.
SOURCE-DERIVED MAP
Literal TypeScript declarations become an explorable graph immediately. The map stays honest about what was proven statically and what appeared only at runtime.
SOURCE INSPECTOR
Inspect an analyzer-approved source window alongside last latency, mean latency, call count, runtime state, and safe metadata.
NARROW VIEWPORT
Scenario controls, topology, focus states, and navigation remain available on a Pixel 7-sized viewport verified in Chrome.
BRING YOUR OWN TRACE EVIDENCE
Both paths feed the same bounded in-memory runtime. Binary protobuf and gRPC are intentionally outside the supported collector surface.
FIRST-PARTY
Framework-neutral wrappers and Connect/Express middleware preserve parent-child context through concurrent promises. Transport queues, retries, and timeouts are bounded.
const ordersDb = atlas.database(
{ id: "db.orders", label: "Orders DB" },
async () => saveOrder(),
);
const createOrder = atlas.route(
{ id: "route.orders", label: "POST /orders" },
async () => ordersDb(),
);STANDARDS PATH
Send complete OpenTelemetry spans to the exact traces endpoint. Runtime Atlas retains only a small allowlist of routing, service, code, database, and messaging evidence.
curl --request POST \
http://127.0.0.1:4319/v1/traces \
--header 'content-type: application/json' \
--data-binary @examples/otlp-trace.jsonLOCAL-FIRST BY CONSTRUCTION
Runtime Atlas binds to loopback by default, keeps traces in process memory, and ships without accounts, analytics, cookies, advertising, or a persistent telemetry database.
Read the privacy modelRequest bodies, database statements, query strings, URL fragments, credentials, arbitrary OTLP attributes.
Trace history, event buffers, events per trace, aggregate events, request bodies, SDK queues, and viewer count.
Source inspection and trace clearing can be disabled; bearer authentication protects shared ingest.
This is not a durable tracing database, metrics platform, or public multi-tenant service.
FIRST RUN
The pinned Node.js version and locked dependencies make the built-in demo reproducible. Open the URL printed by Vite, then launch POST /checkout, GET /search, or FAIL /payment. A 14-node topology appears before the first request; the captured path then animates across it.
$ git clone https://github.com/OthmaneBlial/Runtime-Atlas.git
$ cd Runtime-Atlas
$ nvm install && nvm use
$ npm ci && npm run devRUNTIME ATLAS / MIT