PR comments, status checks, and line annotations on every pull request. Works with any CI — your source never leaves it.
No credit card · 5-min setup · Free for public repos
How it works
Add one line to your CI pipeline. OtterWise handles the rest.
Step 01 — CI
Add a single curl step after your tests run. Works with every major CI provider and every coverage format.
Step 02 — Ingest
We read the coverage artifact your tests already produce, like lcov, cobertura, jacoco, and more. Your source never leaves your runner.
Step 03 — Read
Coverage trends, cycle time, and churn risk, all in one place. Post results back to GitHub, or pull them anywhere via the API.
Treemap coverage
Treemap tiles sit side by side so you can spot hot spots instantly. Size reflects lines of code; color reflects coverage. The bigger and warmer the block, the higher the risk.
Coverage trends
See how coverage moves across every branch: who's pushing it up, where code is slipping through untested, and which trends to act on before they become problems.
#123 Add new feature for import & export of user data
Status checks
Status checks automatically fail PRs when coverage drops or complexity spikes. Set your own quality thresholds and let automation enforce them. No more “looks good to me” merges that introduce untested code.
Everything else
We never access your source. We only store coverage metrics and the minimal service data needed to run OtterWise. Read about our code privacy efforts.
All plans (including free) offer unlimited collaborators at no extra charge. You can invite your entire engineering department, designers, PMs, and stakeholders.
Watch coverage move over time in the dashboard, or pull the same numbers into your own with the API.
All paid plans include priority chat support, and we can help you get running even if you have no CI pipeline yet.
Configure which files to ignore, when to fail CI, how coverage is calculated, and more. It bends to your setup, not the other way around.
Per-line coverage, type coverage, and CRAP scores point you at the code most likely to break, so you test what matters first.
Runs anywhere
Any CI that can run tests and upload a coverage report. Official guides for GitHub Actions and ChipperCI; everything else via the bash uploader. Use it with JavaScript, Go, Ruby, .NET, PHP, and any other language.
… plus any CI that can run the uploader
Why OtterWise
Coverage report · +2.4%
Free for public repos. Set up in 5 minutes. No credit card required.
FAQ
Something not covered here? Email [email protected] and we'll help you out.
No. By default, our servers can't reach your repository code at all.
We rely on GitHub annotations and the coverage files your tests already produce, so you get everything a coverage service offers without us ever reading your source.
Your organization can opt in to temporary code access if you want coverage rendered per line inside OtterWise. You can read about our code privacy efforts here.
Any of them. OtterWise is language- and framework-agnostic; the only requirement is that your code is on GitHub.com and your test framework can output a Clover XML or LCOV file.
Most can: PHPUnit has it built in (via PCOV or Xdebug), and in JavaScript you get it through Istanbul/nyc. Our setup guides walk you through it.
None. There's no minimum commitment, cancel anytime from your account and billing stops immediately. You keep access until the end of the cycle.
After that we move you to the free plan and adjust automatically, for example disabling private repos over the free limit. Your data stays put.
Free forever, with unlimited collaborators and unlimited builds. We only charge for private repos.
Two ways to try it:
Yes. On your organization's billing page, switch between yearly and monthly and hit Update plan, it applies instantly and prorates the difference. Or email [email protected] and we'll sort it.
Yes, no questions asked. Email [email protected] and we'll sort it out.
Login runs entirely through GitHub, so your existing GitHub access controls apply. Remove someone from your GitHub organization and they lose OtterWise access automatically.
Yes, coverage across the whole repository, not just the diff, on every plan.
Yes, coverage of just the lines your pull request or commit changed, on every plan. It shows exactly which new lines aren't tested before you merge.
GitHub today, plus any CI that can run the uploader.
OtterWise tracks line coverage, branch coverage, patch coverage, type coverage, complexity, and CRAP.
Free plans keep 6 months of history; Pro plans keep it indefinitely. Either way you can view past reports and track trends over time.
Yes. Pull your coverage, metrics, and history out through the API anytime, or ask support for an export.
Authentication runs through GitHub, traffic is encrypted in transit, and code access is off by default and opt-in only, so your source stays private unless you choose otherwise.
Weekly and monthly digests, leaderboards, coverage trends, and per-file breakdowns. Pro plans add deeper history and analytics.
Yes, unlimited collaborators on every plan, including free. Manage access through your GitHub organization, and work from shared PR comments and line annotations.
Any framework that can output a Clover XML or LCOV report, including PHPUnit, Jest, Cypress, RSpec, and PyTest.
No, coverage reports only.
PR comments, status checks, line annotations, and trends, all without code access. Free for public repos; per-repo pricing for private repos.
