OpenClover is maintained by volunteers in their spare time. Every feature added, every bug fixed, and every compatibility update for a new Java or build tool release is unpaid work driven by passion for code quality. If OpenClover saves you time or improves the quality of your software, please consider giving something back.
I have been maintaining OpenClover as a volunteer for a decade. I genuinely love this project, but love alone does not pay the bills. Running OpenClover costs real time and money every year:
None of this has ever been sponsored or reimbursed. Every cent has come from my own pocket because I believe OpenClover is worth it. If you do too, a small donation helps me keep the lights on and spend more of my spare time writing code rather than worrying about costs.
OpenClover is a fork of Atlassian Clover®, which was one of the most advanced commercial code coverage tools on the market before Atlassian open-sourced it. When it was still sold commercially, Atlassian Clover® licences started at:
You are getting a professional-grade tool at no cost. A one-time €5 coffee is a token of appreciation many of us can afford.
Just a single test optimization feature alone can cut the time spent waiting for tests to complete dramatically. Here is a conservative estimate for a single developer:
| Annual developer salary | $100,000 |
| Working days per year | 220 |
| Cost per minute of developer time | ≈ $0.95 |
| Test suite runs per day | 5 |
| Average test suite duration | 5 minutes |
| Time in tests per year | 92 hours |
| Time saved with 70% optimization | 64 hours ≈ $3,600/year |
And the OpenClover offers way more features - heat maps, top risks, quick wins, class-to-test mapping, code metrics - just to name a few!
Accurate, per-test coverage reports reveal redundant tests and coverage gaps. Teams that act on this data routinely reduce test count by 10–30% while improving overall coverage — cutting both CI time and maintenance burden.
Uncovered code is where bugs hide. Research consistently shows that a bug found during coding costs 5–10× less to fix than the same bug discovered in production. OpenClover makes uncovered code impossible to ignore.
A live coverage map gives teams the confidence to refactor aggressively, knowing exactly which paths are exercised and which are not. Better code structure means lower long-term maintenance cost.
OpenClover has thousands of active users, based on downloads statistics. If just 1 in 10 bought a single cup of coffee once a year, that would be enough to sponsor one full-time engineer dedicated to OpenClover development. Imagine what that engineer could build for the whole community.
You can make a wire transfer using your banking app to the following Euro account. Pick any amount you want, the ones below is my proposition.
Thank you for using OpenClover and for considering a donation. Your support makes a real difference.