Free test analytics for GitHub
Test analytics for GitHub
Track each test's performance across commits to detect regressions.
Live DemoGet Started
Regressions vs FlakesSeparate regressions from flakes<br>Every result is tied to the commit and environment it ran on. Flakiness.io can tell whether a failure is new in the PR, already broken on main, or flipping on the same commit. Never land a regression again.
Pull RequestsTest Results<br>Refactor auth middlewareHas Regressions<br>#1409
Update ClickHouse clientMergeable<br>#1407
Fix snapshot collisionMergeable<br>#1406
Vendor isolation policyMergeable<br>#1402
Test Health Calendarmain<br>Dec<br>Jan<br>Feb<br>Mar
Mon
Wed
Fri
RegressionFailureFlakyPassingNo data
Test RunnersAny test, any runner<br>Frontend in Vitest. E2E in Playwright. Backend in Pytest or JUnit.<br>Flakiness.io gathers all tests in one place, with high-quality reporters for the major runners, a JUnit XML bridge for everything else, and a Node.js SDK for custom integrations.
PlaywrightPytestVitestJestCucumberJSBunRustJUnit XML
Test OrchestrationFaster CI from balanced shards<br>A sharded run is only as fast as its slowest shard. Splitting tests by count leaves some shards overloaded and others idle, so the whole run waits on a straggler.<br>Flakiness.io records how long every test takes, and compatible test runners can use that information to balance shards by real duration.
Random shardingwall-clock 20m 00s<br>shard 1/4
16m 00s<br>shard 2/4
20m 00s<br>shard 3/4
9m 00s<br>shard 4/4
15m 00s
Split by test count
Balanced shardingwall-clock 15m 01s<br>shard 1/4
14m 58s<br>shard 2/4
15m 01s<br>shard 3/4
15m 00s<br>shard 4/4
15m 01s
Split by test duration history
Supported runnersPlaywrightMore runners coming
CI & ShardingAny CI, one report<br>Works with any CI provider. Flakiness.io ingests results as they land, automatically merges shards, and keeps staging and production histories separate.
GitHub ActionsOIDC authenticated
Shard 1/4312 tests
Shard 2/4308 tests
Shard 3/4315 tests
Shard 4/4311 tests
env: production
Unified Report<br>Shard 1Shard 2Shard 3Shard 41,246<br>tests
ReportsZoom in, Zoom out<br>Test reports range from a week-level overview across every environment down to a single test in a single run.<br>Slice results with the Flakiness Query Language, group failures into error bins, and read system telemetry alongside the test waterfall.
Test Results<br>1,246<br>tests
Passing87%<br>Failed8%<br>Flaky5%
Test Waterfall1,246 tests · 4 workers · 2m 48s<br>CPU<br>Memory<br>worker #1
worker #2
worker #3
worker #4
0s30s1m1m 30s2m2m 30s
Errors:TimeoutError × 4AssertionError × 2Flaky × 1
ArtifactsKeep evidence attached<br>Logs, screenshots, videos and traces upload alongside every report. Powerful built-in viewers handle image diffing and Playwright traces in the browser.<br>Configurable data retention lets you keep what matters and prune the rest.<br>See a report with attachments
Videos<br>Images<br>Playwright Traces<br>HTML Attachments<br>Terminal Logs
Access ControlGitHub-native access<br>Flakiness.io follows your GitHub repository permissions. People with access to a repository can see its test analytics; people without can't.<br>You do not need to recreate users, teams, permissions, or single sign-on (SSO) inside Flakiness.io. Access stays where your engineering team already manages it: GitHub.
acme/apiCollaborators<br>alexAdmin<br>tallyWrite<br>saraWrite<br>jamieRead<br>marcoRead
flakiness.io · acme/apisynced<br>alexHas access<br>tallyHas access<br>saraHas access<br>jamieHas access<br>marcoHas access
AI AgentsCompact context for coding agents<br>Raw CI output is expensive context for coding agents. Flakiness.io turns a failed run into a compact record: what failed, whether it regressed, how it behaved on main, and which logs and artifacts matter.<br>Agents spend fewer tokens gathering context and less time fixing problems.
Claude Code<br>Codex<br>Cursor
claude<br>> Hey Claude, fix failures in PR #219<br>● Pulling test history from flakiness.io…<br>● 3 regressions found in billing/*.spec.ts<br>● Analyzing flip rate on main…<br>● Drafting fix for race condition in billing.ts:142
Pricing ModelWe charge for storage,<br>not tests or seats<br>Most platforms charge per test run, per dashboard user, or both. Flakiness.io charges for stored data. Run more tests and let everyone with GitHub access view the results — without per-run or per-seat fees.
Typical providers<br>$ / test run<br>$ / user<br>× Penalty for writing more tests<br>× Surprise bills at scale
Flakiness.io<br>$ / storage<br>✓ Run as many tests as you want<br>✓ Predictable bills at scale
Platform pricingChoose your plan<br>Starts free — no credit card required.
MonthlyYearly<br>MonthlyYearly
Free<br>$0USD<br>/ month
no credit card required<br>Create free organization<br>Core test analytics
1 GB artifacts storage
90 days data retention
Unlimited test runs
Unlimited users
Public projects
Private projects
Slack Notifications
Self-hosting
Audit log
Standard support
Startup<br>$49USD<br>/ month
billed monthly<br>Continue with Startup<br>Core test analytics
10 GB artifacts storage
180 days data...