Coveralls

Overview

Coveralls is a test-coverage service for teams that want to find untested code and follow coverage across builds. It is strongest for projects that put coverage results into pull-request review and merge decisions; the cloud plans make private-repository capacity the key buying constraint.

Key features

A dashboard pairs current project coverage with trend graphs, and repository views drill from aggregate results through sub-projects and files to individual lines. That detail helps teams locate gaps rather than relying on a single headline percentage. Coveralls tracks line and branch coverage and accepts formats including LCOV, SimpleCov, Cobertura, JaCoCo, Gcov, Pytest-Cov, and Clover XML.

Build history follows coverage across branches and builds, including pull requests. Pull-request summaries and annotations bring results into code review, while coverage criteria can allow or block merges. Slack and webhook notifications can flag changes. Together, these features suit teams that want coverage to affect review decisions, not just produce an archive of reports.

Coveralls says it works with any CI service and offers more than 30 community-created integrations, as well as a GitHub Action and CircleCI Orb. Its supported languages include .NET, C/C++, Go, Java, JavaScript, PHP, Python, Ruby, Scala, and others. The API can add repositories programmatically and return recent-build statistics, useful for teams automating coverage workflows.

For cloud privacy, Coveralls says it reads code through an SCM OAuth token, accesses repositories read-only, and does not store or cache private code. Detailed file coverage is retained for 12 months on paid repositories and six months on public ones; aggregated build-level coverage is retained indefinitely. The self-hosted enterprise installation can run within a customer's existing security controls and without outbound network access, a meaningful option for organizations with tighter infrastructure requirements.

Pricing

Open-source and public repositories are free. For private cloud use, the Starter plan costs $10 a month, billed $10/mo, for one private repository and a 30-day free trial. It is a low-cost entry for a single private project, but not a broad team allocation.

Org costs $50 a month, billed $50/mo, for 10 private repositories and unlimited users; Org+ costs $100 a month, billed $100/mo, for 20 private repositories and unlimited users. Pro costs $200 a month, billed $200/mo, for 40 private repositories and unlimited users. These tiers scale repository capacity without imposing a seat cap. Unlimited costs $400 a month, billed $400/mo, for unlimited private repositories and users, fitting larger portfolios that do not need the stated premium-support package.

Cloud Premium costs $800 a month, billed $800.00/mo, for unlimited private repositories, premium support, custom SLA terms, and multi-org billing. Enterprise Cloud costs $35 a month, billed $35/user/mo, and includes unlimited organizations, repositories, and users, secure private infrastructure, guaranteed performance, and premium support; its 40-seat minimum makes the starting total $1,400/mo. It is aimed at larger organizations prepared for that minimum rather than smaller teams.

The Usage add-on costs $30 a month, billed $30/mo, for 3,000 additional uploads per month and priority processing, is repository-scoped, and combines with any Cloud Plan. The Support add-on costs $200 a month, billed $200/mo, for premium support, priority response, and live chat, and also combines with any Cloud Plan. These add-ons address upload volume and support needs, not repository-count expansion. Cloud pricing therefore ranges from a one-repository foothold to high-capacity plans, with seats, repository limits, and add-ons shaping the actual fit.

Platforms

Coveralls supports API, Linux, self-hosted, and web use. Its range of report formats and language integrations makes it relevant across varied development stacks, while self-hosting is available for organizations that need coverage analysis inside their own security controls.

Who it's for

Coveralls is a good fit for open-source maintainers and development teams that want coverage history, line-level investigation, and pull-request checks in one workflow. Teams with a handful of private repositories can start at the lower cloud tiers, while organizations needing unlimited repositories or private infrastructure have higher-tier options. It is less compelling for a small private project that does not need review integration, or for teams whose repository count exceeds a cheaper tier's cap.

Pros and cons

• Pro: Coverage detail reaches individual code lines, making project summaries actionable when teams need to find specific gaps.
• Pro: Pull-request reporting and coverage gates connect results to review and merge decisions.
• Pro: Open-source and public repositories are free, and paid plans retain detailed file coverage for 12 months.
• Con: Private-repository limits rise by tier; the Starter plan covers just one repository.
• Con: Enterprise Cloud's 40-seat minimum sets a $1,400/mo floor, which is a substantial commitment for smaller teams.
• Con: Public repositories retain detailed file coverage for six months, shorter than the paid-repository period.

Alternatives

Test Coverage Tools is a useful place to compare options. Choose OpenClover if you want a free coverage tool with no usage limits. SimpleCov is a free, MIT-licensed option for Ruby coverage. Choose cargo-llvm-cov for free Rust coverage under Apache-2.0 or MIT licensing, or Coverage.py for an open-source Python coverage tool with an enterprise subscription available through Tidelift.

Coverlet is a free, MIT-licensed option for modern .NET SDK-style projects. EclEmma is a free Eclipse plug-in for Java coverage. Choose gcov when working with code compiled using GCC and coverage instrumentation. gofmt is included with Go and is used from the command line.

Verdict

Choose Coveralls if your team needs coverage trends and line-level detail tied directly to pull requests and merge criteria, especially for open-source projects or private portfolios that fit its repository tiers. Look elsewhere if you need a free private-repository workflow or cannot justify the seat minimum on Enterprise Cloud.