Q4 FY26 operating evidence by product line, and supplemental context.
Public usage and event data are directional evidence, not disclosed product revenue. Sources: npm Registry, GitHub, W3Techs, PeeringDB, Cloudflare Radar, SEC filings.
Share and traffic mix indicate whether Cloudflare's core public-web footprint is still expanding.
Recent share gain is the key near-term signal. Cloudflare gained share while legacy competitors continued to lose relevance.
Non-human traffic is now structurally important. Every bot request still requires inspection, enforcement, and policy controls.
Cloudflare's share has increased over a decade while Akamai has steadily declined. This supports the structural migration thesis.
Akamai's declining share is useful competitive context because it shows where part of Cloudflare's footprint growth is coming from.
Cloudflare Tunnel client activity is the main product-specific public signal for Zero Trust deployment. Network footprint is moat context for the same act.
cloudflared is the client used to create Cloudflare Tunnel connections. Each bar sums the GitHub Releases downloads of every version published that month; a month with no release is a true zero. Read the shape, not the levels: a download count is cumulative since the release was published, so older months have had years to accumulate and the newest has had weeks. This is a rough adoption proxy, not MAU.
PeeringDB prefix data is moat context. It supports Cloudflare's distribution advantage, but it is not a direct product revenue signal.
Wrangler CLI downloads measure Workers platform usage; Workers AI SDK downloads capture early AI integration activity.
Wrangler is the command-line tool used to build and deploy Cloudflare Workers. Download growth is a strong usage signal; it includes CI/CD automation.
@cloudflare/ai captures early Workers AI integration activity. It is best read as an emerging product signal, not proof of current-quarter revenue.
These charts test whether Workers growth is broad-based and whether Cloudflare widens the platform gap vs Fastly.
YoY growth removes some seasonality and helps distinguish a real usage step-up from monthly noise.
Month-to-month growth is a momentum check. It is useful for timing, but less reliable than YoY growth.
Miniflare, Cloudflare SDK, Vitest Workers pool, and next-on-pages test whether usage is broad-based.
Wrangler CLI downloads versus Fastly's JavaScript Compute package show relative developer mindshare and ecosystem momentum.