What Engineering Analytics Platforms Actually Cost

Most vendors in this category hide pricing. Here's what buyers report paying, where the figures disagree, and how to read a quote before you sign one.

Most vendors in this category don't publish pricing. You book a demo, describe your organisation, and receive a number weeks later with no way to tell whether it's reasonable.

This page collects what's publicly verifiable, with sources and dates attached. It's updated as new figures come in, including from readers. Undated pricing data is worthless in a market that reprices this often.

How to read this page. Figures below come from three source types, kept separate: vendor-published pricing, third-party buyer datasets, and reported quotes. Where they disagree, we say so rather than averaging them into a single misleading number.

Vendors that publish pricing

Vendor	Published price	Notes
Koalr — Growth	$39 / seat / month	DORA, PR cycle time, review analytics, CODEOWNERS enforcement
Koalr — Business	$55 / seat / month	Adds deployment risk scoring and AI chat
GitKraken Insights	$9–19 / contributor	Lower end of the market
Apache DevLake	Free	Self-hosted, infrastructure cost only

Self-serve pricing is itself a signal. Vendors publishing rates are generally targeting teams that want to evaluate quickly without a sales cycle. Vendors hiding rates are generally targeting buyers whose procurement expects a negotiation.

Jellyfish: what the data says

Jellyfish is the clearest case, because enough buyer data exists to triangulate.

No list price, no free trial, no self-serve signup. You cannot evaluate it without talking to sales. For a team wanting to compare several tools quickly, that's a real cost measured in weeks.

Reported figures, by source:

Figure	Source type	Notes
$35,920 median annual contract	Vendr buyer dataset, 91 purchases, July 2026	Deals observed starting near $16,500
$50,000–$120,000 / year	Vendr analysis	For 50–150 engineering seats, annual terms
~$49 / contributor / month	Reported per-seat	Top of the observed band
$20–40 / developer / month	Third-party reports and reviews	Wider, older range

These disagree, and the disagreement is informative. A $35,920 median sits well below the $50,000–$120,000 range quoted for 50–150 seats, which suggests the median is pulled down by smaller contracts. If you're a 50-person team being quoted six figures, the data says push back.

Discounts are real. Volume commitments and multi-year terms commonly reduce per-seat cost by 15–30%. Assume the first number is not the last number.

Setup takes 4–8 weeks. Budget for it. A platform that goes live in the last month of a quarter contributes nothing to that quarter.

Pricing is based primarily on engineering seats — contributors whose work is tracked — and contract length, with a minimum that varies by organisation size and deployment complexity. Unlike some competitors, Jellyfish does not generally charge per integration.

The rest of the field

LinearB, Swarmia, DX and Faros all price per contributor and none publishes complete rates. Practical guidance rather than invented numbers:

Get three quotes minimum. Not for leverage theatre — because you cannot tell whether a number is reasonable without comparison, and in this category the spread between vendors for equivalent scope is wide.

Ask what counts as a seat. Definitions vary: all engineers, active contributors in the period, anyone whose commits are ingested. On a 200-person org the difference between these definitions can be tens of thousands of dollars.

Ask about integration charges separately. Some vendors bundle, some don't. This is where quotes that looked comparable stop being comparable.

Price the exit. Data export on termination, and whether historical metrics leave with you. Flow customers are learning this lesson in 2026 — the product retires 31 December 2027 and API access goes with it.

What should you actually budget?

A rough frame, assuming a commercial platform rather than self-hosted:

Under 30 engineers: the market barely serves you. Free tooling or a published-price vendor.
30–100 engineers: $15,000–50,000 a year is the realistic band for a mainstream platform.
100–300 engineers: $50,000–120,000, with real negotiating room.
300+: six figures, and the per-seat rate should drop meaningfully.

Add to any of these: 4–8 weeks of setup, and internal time for integration configuration and data validation. The internal time is routinely underestimated and is frequently larger than people expect.

Contribute a data point

If you've bought in this category, send the vendor, your seat count, the annual figure and the month. We publish ranges and never identify a company or individual. More data points make this page more useful for the next buyer negotiating against a number they can't sanity-check.

Frequently asked

Why doesn't anyone publish pricing? Because enterprise sales in this category depends on discovering budget before quoting. It's a commercial choice, not a technical constraint — and the vendors that do publish demonstrate that.

Is the median a good benchmark for my quote? Only alongside your seat count. A median across 91 purchases spans very different organisation sizes. Compare against the band for your size, not the midpoint of everyone.

How much negotiating room is there? Observed discounts of 15–30% for volume and multi-year commitments. Whether that applies to you depends on timing, seat count and how close the vendor is to quarter end.

Is a free or self-hosted option viable? For pure DORA metrics, yes. The gap opens when you need developer experience surveys or reporting across many teams, neither of which the open-source stack handles.

Figures on this page carry their source and date. Vendor pricing changes; verify current rates before making a decision on them.