Nothing to install
Drop a trace.zip on the page and it opens. No show-trace, no download step, no sign-up.
[ Trace viewer ]
Drop a trace.zip and it opens right here, in your browser. No install, no account, and the file never leaves your machine.
The Playwright trace viewer is normally something you run locally: download trace.zip from CI, then playwright show-trace. kinora runs the real viewer as a web page instead, so a trace opens the moment you pick it, with the full timeline, DOM snapshots, network, console, and source. The zip is read in your browser by a service worker, so nothing is uploaded anywhere. Connect your CI later and the same viewer opens every failure straight from your run history.

Drop a trace.zip on the page and it opens. No show-trace, no download step, no sign-up.
The zip is read locally in your browser, never uploaded, so traces from a private project stay private.
Timeline, DOM snapshots, network, console, and source, vendored straight from Playwright, so everything behaves as you expect.
Send your runs to kinora and the same viewer opens on any failure, from any past run, with no artifact dance.
Yes. Drop a trace.zip on the viewer and it opens in your browser, with no install, no account, and nothing to configure.
No. The zip is read locally in your browser by a service worker, the same way the viewer reads a remote trace. It never reaches a kinora server.
Yes. The trace viewer is vendored from Playwright, so the timeline, snapshots, network, and console tabs behave exactly as you expect.
Yes. Send your runs with @kinora/reporter or the CLI, and every failure opens its trace inline in the dashboard, for any run kinora has kept.
Yes. The kinora desktop app is a standalone Playwright trace viewer that opens traces from your file manager, also without an account.
Add the reporter, point it at a kinora server, and watch the history build itself.