Cloudflare — Engineering Performance
Avg. perf / dev / mo (ETV)
−20.4%
1.20 → 0.96
Active contributors
−13.4%
142.0 → 123.0
Growth
+0.7pp
34.5% → 35.2%
Fixes
−4.7pp
21.3% → 16.6%
Cloudflare vs. 500 OSS Performance Index
Per-engineer ETV for Cloudflare plotted against the pooled 500 OSS Performance Index. Both series are 90-day trailing rolling averages scaled to a 30-day month, so the curves sit on the same scale (ETV / dev / mo) and can be compared point-for-point. Latest reading: Cloudflare is 55% below the index (0.96 vs 2.12 ETV/dev/mo). Baseline gap was 34% below.
Monthly reports
No monthly reports available yet.
Repositories
Active repositories ranked by average performance per developer per month (over the last 90 days). The chart shows monthly performance composition — each repo as a stacked layer, with the top of the stack representing total org performance per month. Top 9 repos shown; the remainder is aggregated as “Other”.
| Repository | ||||
|---|---|---|---|---|
| agents | 6 | 171 | 9.5 | +1294%since Q2 2025 |
| sandbox-sdk | 5 | 22 | 1.4 | +348%since Q2 2025 |
| workers-sdk | 28 | 89 | 1.1 | +142%since Q2 2025 |
| foundations | 2 | 4 | 0.7 | +2313959%since Q2 2025 |
| workers-rs | 1 | 1 | 0.5 | +47%since Q2 2025 |
| pingora | 6 | 8 | 0.5 | +114%since Q2 2025 |
| containers | 1 | 1 | 0.3 | −80%since Q2 2025 |
| cloudflare-docs | 84 | 49 | 0.2 | −5%since Q2 2025 |
| cloudflared | 4 | 2 | 0.2 | −9%since Q2 2025 |
| lol-html | 1 | 0 | 0.2 | −5%since Q2 2025 |
| telescope | 2 | 1 | 0.1 | +396%since Q4 2025 |
| workerd | 17 | 4 | 0.1 | +16%since Q2 2025 |
Company total12 repositories | 123unique devs | 353ETV total | 0.96ETV / dev / mo | +85%since Q2 2025 |
| Performance (ETV) is the sum of every repository above. Active devs at the company level counts unique contributors across all repos, so a contributor working in multiple repos is counted once here but appears in each repo's row (the per-repo column will sum higher). ETV / dev / mo = Company ETV ÷ unique devs ÷ 3 mo. The "Since start" column compares each repo's Q1 2026 quarterly performance to the first quarter it had any activity — for repos that existed in Q2 2025 (when this index began), that's Q2 2025; for younger repos it's the quarter they actually started. The company row uses Q2 2025 as the baseline since the index itself began then. | ||||
Performance Growth vs Active Contributors
Shows how engineering performance scales relative to team growth. Left axis shows total performance score, right axis shows active contributor count. The gap between curves represents productivity gains — more delivered per person, not just more people. Unit: Engineering Throughput Value (ETV).
Cost per Performance Unit
−40%
If performance per engineer grew 65%, each unit of engineering performance now costs approximately 40% less than at the baseline 90-day window (ending 2025-06-29). This is a directional estimate — the exact figure depends on fully-loaded engineer cost, but the direction is unambiguous.
Effective Capacity Added
+80 engineers
At today's productivity, the current 123-person team delivers the performance equivalent of 203 engineers at the baseline 90-day rolling window (ending 2025-06-29). That's roughly 80 engineers worth of capacity added through productivity gains, not hiring.
Performance Composition
Stacked bars show total complexity performance split into Growth (new value), Maintenance (sustaining systems), and Fixes (rework). The yellow line overlays performance per contributor — rising line means each engineer is delivering more, regardless of team size changes. Unit: Engineering Throughput Value (ETV).
CapEx vs OpEx
Monthly CapEx vs OpEx split. CapEx (capitalizable investment) is Growth — new features and capabilities. OpEx (operating expense) is Maintenance plus Fixes — keeping the lights on and reworking what's already shipped. The yellow line is the CapEx share, a quick read on how much of the month went into building new vs sustaining existing. Unit: Engineering Throughput Value (ETV).
Hours per Repository
Trailing 90-day window (64 working days). Org-level capacity is allocated to each repo by its share of org performance, then split CapEx / OpEx by that repo's own Growth vs Maintenance + Fixes mix.
| foundations | 81.8% | 18.2% |
| pingora | 70.9% | 29.1% |
| telescope | 59.1% | 40.9% |
| workerd | 51.5% | 48.5% |
| sandbox-sdk | 48.8% | 51.2% |
| workers-sdk | 36.0% | 64.0% |
| workers-rs | 35.9% | 64.1% |
| agents | 33.6% | 66.4% |
| lol-html | 26.5% | 73.5% |
| cloudflare-docs | 22.9% | 77.1% |
| cloudflared | 9.1% | 90.9% |
| containers | 0.0% | 100.0% |
| Total | 35.2% | 64.8% |
Fix Burden Distribution
Monthly rework volume broken down by who did it. Top contributors carry their named slice; everyone else is rolled into Others. Use this to spot whether fix work is concentrated on a small group (bus-factor risk) or distributed across the team.
Quarterly Summary
The raw numbers behind the charts: commits analyzed, active contributors, total performance, performance per developer, and the Growth / Maintenance / Fixes split for each quarter.
| Quarter | ||||||||
|---|---|---|---|---|---|---|---|---|
| Q2'25 | 2,510 | 130 | 227.99 | 0.6 | 31.3% | 57.1% | 11.6% | — |
| Q3'25 | 2,754 | 137 | 256.52 | 0.6 | 30.2% | 51.5% | 18.4% | +13% |
| Q4'25 | 2,410 | 130 | 253.18 | 0.6 | 27.4% | 51.8% | 20.8% | −1% |
| Q1'26 | 2,670 | 139 | 422.77 | 1 | 36.1% | 38.1% | 25.8% | +67% |
Top Contributors
Contributors ranked by performance per month (Growth + Maintenance + Fixes), over the last 90 days normalized to a 30-day calendar month.
The best way to measure AI efficiency
SampleA preview of the Navigara engine running on a sample organization. The numbers below are illustrative, not part of the OSS500 benchmark above.
Measure
Score every commit by depth
GitHub commits are weighted by what it took to write them, not by lines of code. The result is ETV per developer per month.
SourceGitHub
Spend
Tie ETV to cost
AI token bills and seat costs are pulled per team and divided by the ETV produced. The result is your true cost per unit of work.
SourceToken usage + finance
Map
Tie work to objectives
Each ETV is mapped to your Jira epics and labels, so you can see what's key-aligned, aligned, or unmapped capacity.
SourceJira
Performance
ETV delivered per developer / month
9.4ETV / dev / month
5.6 below target- Non-AI 5.8
- AI 3.6
AI Efficiency
AI spend per ETV unit delivered
$4.20
$0.60 over target- Cost / ETV $4.20
Objective Alignment
Share of work mapped to key objectives
51%
24 pts below target- Key-aligned 28%
- Aligned 23%