CI cost per contributor

CI cost per contributor is total CI spend over a period divided by the number of people who actively contributed code in that period — a normalization that makes CI costs comparable across teams of different sizes and across time as a team grows.

How it is measured

The numerator is whatever you count as CI cost: the provider invoice, an estimated compute cost built from job durations, or a fuller figure that includes the cost of failed builds in engineer wait time. The denominator is where definitions diverge: an active contributor is usually a distinct author who pushed commits or opened pull requests inside a rolling window, but the choices underneath — how long the window is, whether bots are excluded, whether the same person on two providers counts once or twice — move the number materially. Any comparison between two teams' per-contributor costs is only as good as the match between their two definitions.

The pricing pattern

Per-active-contributor pricing has become an industry pattern for CI analytics tools, for the same reason the metric works: CI usage scales with the number of people writing code, not with seats provisioned in an admin panel. Datadog prices CI Pipeline Visibility at $8 per active Git committer per month on an annual commitment ($12 on-demand, as of 2026-07-28), defining a committer as someone with three or more commits that month; Mergify charges $21 per seat per month on its Max plan (as of 2026-07-28), where a seat is anyone who opened a pull request or pushed commits in the last 30 days. TrimCI bills on the same basis — per active contributor rather than per seat — with the current prices, the exact counting rules, exclusions and trial terms answered canonically on the pricing page. Side-by-side breakdowns live in the Datadog and Mergify comparisons.

Why it matters

Absolute CI spend rises with headcount, so a growing bill is ambiguous on its own: it can mean the team got bigger, or that pipelines got wasteful. Cost per contributor separates the two. If the team doubled and per-contributor cost held flat, CI scaled cleanly; if per-contributor cost is climbing on stable headcount, something specific changed — a slower suite, a rising retry tax, or minute rounding overhead from a fan-out refactor. The metric also frames tooling decisions in like units: a per-contributor analysis tool against per-contributor waste, which the loss calculator puts numbers on.

TrimCI counts active contributors directly from synced pipeline data — the settings page shows exactly who counts in the current window — and on paid plans the report executive summary sets estimated failure cost against plan cost on the same per-contributor basis.