# Pricing: Free for Open Source, Seats for Teams

- Section: Pricing
- Canonical: https://covdbg.com/pricing/

---

There is one download for everyone and no license key. Open source and personal use are free. A team pays per developer, which covers every repository and every pipeline.

## Plans

### Free: $0

For personal use and open source.

- Unlimited public repositories
- One private repository at a time
- Switch repositories at any time at app.covdbg.com
- Public CI: no secret on GitHub Actions, elsewhere a project token from your personal team
- Email support tickets

[Download covdbg](/download.md); covdbg 1.5.1 is out, see the [covdbg 1.5.1 announcement](/announcing-covdbg-1-5-1.md). Need the full team model for a public project? See the [open source program](/company/programs/open-source-program.md).

### Team: $12 per user per month

For teams: all repositories and CI.

- Unlimited private repositories, no lock
- CI project tokens cover every seated commit author
- Invite by email, manage seats and tokens in one place
- Priority email support, one business day
- Up to ten teams per owner

Buy seats at https://app.covdbg.com/pricing. USD, plus applicable tax. Billed monthly; cancel any time. A team of one is fine.

### Enterprise: let's talk

For larger organizations: volume pricing, purchase orders and annual invoicing. [Request a quote](/pricing/request-quote.md); we reply within one business day.

Every plan includes the CLI, VS Code extension, MCP server and GitHub Action, plus HTML, Cobertura, LCOV and GCOV export, merge and baseline coverage. View your runs on your own dashboard and work offline for weeks between checks.

## How licensing works

There is no license key. Each run carries your sign-in, or a project token in CI, and the license service checks whether it is covered. A public repository on GitHub Actions needs no token: covdbg presents the job's own GitHub workflow token, granted with `id-token: write`. Public repositories are free, a signed-in developer gets one private repository, and a seat covers everything else. What covdbg sends to decide that, and nothing more, is listed on the [Data and Telemetry](/docs/reference/data-and-telemetry.md) page.

1. **Download and sign in.** Install covdbg and run `covdbg login` once per machine. The sign-in lives in the Windows Credential Manager, not in a file.
2. **Run on any repository.** covdbg names the repository's git remote to the service. A public repository is free; the first private one becomes your personal lock.
3. **Create a team when you need it.** Create a team at app.covdbg.com, buy seats, and invite colleagues by email. Team seats cover all repositories without a personal repository lock.
4. **Give CI a project token.** For unattended runs, set `COVDBG_PROJECT_TOKEN`. It covers every commit author who holds a seat in that team.

## Common questions

**Is there a trial?** Every download is the full product, and there is no time limit. Use it free on public repositories and on one private repository for as long as you like. Buy seats when you need a second private repository, a team, or CI for private code.

**What counts as a user?** A developer who holds a seat in a team. Seats are attributed by the commit author's email, so a seat follows the person, not the machine. Bots such as Dependabot or Renovate are never counted.

**What happens in CI when an author has no seat?** The coverage run continues. The author is listed on the team's page as unseated so an owner can invite them, and their runs keep full reports for ten days before the report is gated to a sample.

**Can two people lock the same private repository under personal use?** Yes. The lock belongs to the person. Two colleagues each lock the same repository in their own slot. What personal use does not cover is that repository's CI, which needs a team's project token.

**Does covdbg work offline?** Yes. The service's decision is cached for seven days and reused; if the service cannot be reached, the last decision keeps working for up to three weeks.

**What does covdbg send to your servers?** For the license check: the repository's git remote URL, the email address in your git configuration, and your sign-in, project token, or the job's GitHub workflow token. After a run, if you leave telemetry on: the covdbg version, the Windows version, how long the program ran, and its exit code. Never source code, file names, paths, or coverage data.

**How do I pay?** By card at app.covdbg.com, monthly per seat. For purchase orders, annual invoicing, or volume discounts, [request a quote](/pricing/request-quote.md).

**What happens when I add or remove seats?** You preview the charge or credit before confirming. Seats added during a billing month are charged for the rest of that month now, and your renewal date stays the same. Reducing purchased seats credits unused time toward future invoices. Removing a member alone does not change your bill. The [Licensing FAQ](/docs/reference/licensing-faq.md) has a worked example.

The full licensing details are in the [Licensing FAQ](/docs/reference/licensing-faq.md).
