Skip to content

CONCEPT Cited by 1 source

Platform limit lifting

When an internal customer (dogfood workload) hits a platform limit during production use, the platform team raises the limit for everyone rather than granting a private exception. The internal workload serves as proof that the limit is too conservative.

Definition

Platform limits (subrequest caps, step counts, concurrency ceilings) are set conservatively at launch. When the platform's own team encounters them in a real production workload, this is treated as evidence that external customers will too. The fix is universal, not a private bypass.

Canonical instance

cdnjs hit two Cloudflare platform limits during migration: (1) 1,000 subrequests per Worker invocation and (2) 1,024 steps per Workflow. Rather than working around them silently, Cloudflare asked the Workers and Workflows teams to raise them — subrequests now go to 10 million on paid plans; Workflows now default to 10,000 steps, configurable to 25,000 (Source: sources/2026-07-30-cloudflare-dogfooding-at-scale-migrating-cdnjs-to-cloudflares-developer-platform).

Why it matters

"The limits we hit are limits we lifted for everyone. If the Cloudflare Developer Platform can serve 9 billion requests a day and publish packages with hundreds of thousands of compressed, minified files, it can probably run whatever you're building."

Seen in

Last updated · 604 distilled / 1,840 read