Follow the request like a line on a map

A request through your stack is a journey: browser to edge, edge to API, API to queue, queue to worker, worker to database. Most tools show you each stop in a different app with a different query language and a different bill. We built Traceway so you can follow the whole line on one map.

One map, six lines

Logs, traces, metrics, session replay, exceptions, and AI spans are lines on the same map. They interchange: open an exception and the session replay is already there, source-mapped, tied to the span that died. Tail a log line and transfer straight to its trace. Context-switching is the bug.

MIT, no asterisks

The whole line is MIT licensed. Every Cloud feature is on the self-host build — Cloud is convenience, not a gated platform. Point OTLP at it and you're in:

$ git clone github.com/tracewayapp/traceway
$ cd traceway && docker compose up -d
✓ dashboard at http://localhost:3000

No BSL. No open-core bait. If you outgrow Cloud, we help you export and stand up your own depot.

Where the line goes next

We ship most days — watch the releases board, star the repo, and tell us where the map is missing a stop on Discord.