# kinora > kinora is an open-source dashboard for Playwright test reports across projects and over time, with an embedded trace viewer. CI runs push their results to kinora; it tracks pass rates, trends, and flaky tests, and opens the full Playwright trace inline for any failure. Playwright ships a great HTML report for a single run on one machine. kinora sits one level up: it ingests every run from CI, keeps history, and lets you compare runs, watch pass-rate trends, and surface flaky tests over time. The Playwright trace viewer is embedded directly in the dashboard, so a red test is one click from its full trace. kinora runs two ways: self-host the full dashboard and trace viewer for free (FSL-1.1 license, single-origin Docker Compose bundle, no account), or use the hosted cloud (free tier plus paid plans). It is CI-agnostic: results are pushed either through the @kinora/reporter or the kinora CLI, over a plain REST ingest API authed by an API key, so any CI provider or a curl command works. ## Links - [Home](https://kinora.dev): product overview, features, pricing, setup - [Live demo](https://demo.kinora.dev): the dashboard with seeded data - [App](https://app.kinora.dev): sign up / log in to the cloud - [GitHub](https://github.com/Kinora-dev/kinora): source code, issues, releases - [Docs](https://docs.kinora.dev): guides, reference, and self-hosting - [Self-host guide](https://docs.kinora.dev/self-hosting/): Docker Compose bundle - [Desktop app](https://github.com/Kinora-dev/kinora/releases/latest): local trace viewer + account dashboard - [Agent setup](https://kinora.dev/llms/setup.md): paste-and-go Playwright reporting setup for coding agents - [Full text](https://kinora.dev/llms-full.txt): every use case, comparison, and FAQ in one file ## Use cases - [A Playwright report with history](https://kinora.dev/playwright-report-with-history): Playwright's HTML report shows one run on one machine. kinora keeps every run, so you get a Playwright report with full history: pass-rate trends, run-over-run comparison, and flaky detection across projects. - [A flaky test dashboard for Playwright](https://kinora.dev/playwright-flaky-test-dashboard): kinora is a flaky test dashboard for Playwright: it watches every run and surfaces the tests that pass and fail without code changes, so you can find, rank, and fix them instead of hitting retry. - [The Playwright trace viewer, online](https://kinora.dev/playwright-trace-viewer-online): Drop a trace.zip and it opens right here, in your browser. No install, no account, and the file never leaves your machine. - [Playwright CI failures, in your coding agent](https://kinora.dev/playwright-mcp-coding-agents): kinora ships an MCP server. Point Claude Code, Cursor, or any MCP client at it and your agent pulls the failing test, its trace, and flaky history straight into the chat, then works the fix. Local over stdio, against the cloud or your own self-host. - [Playwright reports for GitHub Actions](https://kinora.dev/playwright-report-github-actions): Add the reporter to your workflow and every GitHub Actions run lands in kinora with its commit, branch, and run link. Pull requests get a summary comment, and the trace for any failure opens in the browser. - [A self-hosted Playwright dashboard](https://kinora.dev/self-hosted-playwright-dashboard): kinora self-hosts with one docker compose: Postgres, the dashboard, and the embedded trace viewer on a single origin. Free forever, every feature unlocked, and your traces stay on your own storage. ## Comparisons - [All comparisons](https://kinora.dev/vs): how kinora compares to the other Playwright reporting tools - [kinora vs Playwright HTML report](https://kinora.dev/vs/playwright-html-report): Playwright's HTML report shows you one run on one machine. kinora shows you every run: history, trends, and flaky tests across projects, with the same trace viewer embedded inline. - [kinora vs Currents](https://kinora.dev/vs/currents): Currents is a cloud-only paid dashboard that also orchestrates your test runs. kinora is open source, self-hostable for free with a free cloud tier, and focuses on the reporting dashboard and embedded trace viewer. - [kinora vs Allure Report](https://kinora.dev/vs/allure-report): Allure Report generates a portable static report per run for 50+ frameworks. kinora is a persistent, Playwright-native dashboard that keeps history across runs and embeds the Playwright trace viewer, with no CI history plumbing. - [kinora vs ReportPortal](https://kinora.dev/vs/reportportal): ReportPortal is a framework-agnostic reporting platform with ML failure analysis and a heavier stack. kinora is Playwright-native, lightweight to self-host, with an embedded Playwright trace viewer and transparent pricing. ## Key facts - License: FSL-1.1-MIT. Server, web, and desktop are FSL-1.1 (source-available, converts to MIT after 2 years); the embeddable libraries (reporter, CLI, core, ui) and the trace viewer are MIT. - Ingest: add @kinora/reporter to playwright.config, or upload results.json with the kinora CLI from CI. Both derive the same cross-run test identity, so history stays stable regardless of upload path. - Artifacts: trace.zip files are stored on local disk by default, or in any S3-compatible store (AWS, Cloudflare R2, MinIO, Hetzner). Self-hosted, everything stays on your own infrastructure. - Alerts: per-project notifications on new failures and regressions via Slack, email, and webhook. - GitHub PR comments: on a pull_request run, the reporter/CLI post a summary comment on the PR (pass/fail, tests newly failing vs the base branch, link to the run) using the CI job's GITHUB_TOKEN, so no credentials are stored; works self-host and cloud. - Desktop: an Electron app that is a local Playwright trace viewer (no account) plus an account dashboard; it can re-run a failing test locally with your repo's own Playwright and open the resulting trace inline. - Pricing: self-host is free forever. Cloud has a free tier (2,500 test results/month, 1 project, 7-day retention) and paid plans from $49/month billed by test results, with unlimited seats on every plan.