Kaizen — the platform
改善 — change for the better.
Kaizen is a centralized test management SaaS in the spirit of Allure TestOps, Qase.io, and TestRail — built around the same Kensho v1 schema your CI pipelines already produce.
What it adds on top of Kensho
| | Kensho (OSS) | Kaizen (SaaS) | |---|---|---| | Single-run report | yes | yes | | Multi-run history & flake detection | no | yes | | Defect linking (Jira / GitHub / Linear) | no | yes | | Manual test cases & test plans | no | yes | | Live runs from CI | no | yes | | RBAC, SSO, audit logs | no | yes | | AI clustering of failures | no | yes | | Account required | no | yes |
The contract is one-way: Kaizen ingests Kensho. Anything you can produce locally with the OSS report tool is something the platform can correlate over time.
Core surface
- Workspaces — the top-level account (your company)
- Projects — one per app/repo. Access mode
open·team·project - Runs — one per
kensho pushor one per upload. Closed runs become history - Test cases — auto-created from run cases via stable IDs; merge with manual cases for hybrid coverage
- Test plans — bundles of cases with execution sessions (manual + automated)
- Defects — linked from runner annotations or attached manually; rolls up across cases & runs
- Flaky board — rolling pass-rate per case, surfaced when it crosses a threshold
- Live runs — websocket-tailed pipeline output from your CI; final report ingest is automatic
- Migration — bring manual tests in from TestRail/Zephyr/Xray; auto-link to automated cases by name match
Get started
- Sign up — Google, GitHub, Okta, or email
- Create a project
- Upload your first Kensho run — CLI, GitHub Action, or browser drag-and-drop
- Watch the dashboard light up
Where the data flows
your CI ──► Kensho adapter ──► kensho-results/ ──► kensho push ──► Kaizen API
│
▼
kensho generate ──► static HTML you keep on your CDN
The Kensho viewer is also embeddable inside the Kaizen platform for single-run views — same component, same URL routing, same keyboard shortcuts.