Vercel Flat Rate CDN reaches general availability with fixed monthly billing for Pro teams

Vercel has moved its Flat Rate CDN plan to general availability for Pro teams, replacing metered CDN billing with a fixed monthly fee, team-level capacity, and spike protection switched on by default. According to the Vercel blog, the goal is to eliminate the surprise invoices that traffic bursts, viral launches, or bot activity can produce under usage-based pricing.

The launch, announced in a blog post and changelog entry both dated September 8, follows a limited beta that Vercel says began in May. New Pro teams get the flat-rate plan automatically, while existing teams can switch over in Billing settings and can opt back out at any time.

What the fixed fee covers

One monthly payment bundles the four CDN-related resources Vercel previously billed by consumption: CDN requests, Fast Data Transfer, Blob Data Transfer, and observability events generated by CDN requests. None of these are metered individually on the plan, so a temporary surge in any of them does not add to the bill.

Capacity is set at the team level rather than per project, meaning a spike on one project draws on the allowance that covers every project the team runs. Vercel's changelog also confirms that spike protection is active by default: requests that push a team past its tier's ceiling keep being served at normal performance and do not add to the invoice, subject to Vercel's fair use guidelines.

Tiers and pricing

The base tier, Flat Rate CDN 1M, ships with Pro at no extra cost and covers 1 million requests and 1 TB of data transfer per month. Paid tiers add capacity:

• Flat Rate CDN 10M — $20 per month for 10 million requests and 50 TB of transfer
• Flat Rate CDN 50M — $100 per month for 50 million requests and 50 TB
• Flat Rate CDN 150M — $300 per month for 150 million requests and 50 TB

A tier stays fixed for the duration of a billing period, and Vercel sends notifications when usage approaches the tier's limit.

How spikes are handled

Vercel argues that flat-rate offers elsewhere in the infrastructure market typically cap usage once capacity runs out, causing rejected requests and quickly degrading performance. Its alternative works in two parts: the company says it detects short-lived spikes and leaves them out of the calculation that compares usage against tier capacity, and it resizes the tier each month to match sustained usage.

If a team runs materially above its tier over time, Vercel may shift those projects to a separate Flex CDN tier and adjust the flat-rate subscription when the next billing cycle begins. The company says traffic keeps flowing without interruption and without extra charges in the meantime.

Vercel's own illustration involves a team whose ordinary usage fit the $20 tier; days later a viral product launch would have driven a usage-based invoice into the tens of thousands of dollars, while the flat-rate month cost $20. Vercel also maintains that the cheaper predictability does not come with cheaper bandwidth, saying requests still run on its premium network, including private fiber routing that the company claims can lift performance by as much as 60 percent.

What beta teams reported

Customers quoted in Vercel's announcement said the predictability changed how they operate. One team said the plan cut the time spent monitoring bot activity through observability tools, a chore that had grown alongside rising AI crawler traffic. Another said fixed CDN costs made caching-heavy Next.js patterns more attractive, since extra cache traffic no longer carries a direct cost penalty. Vercel also cites Yasuyuki Matsumoto, an engineering lead at Newt Travel, who said the team no longer keeps a close eye on CDN-related costs.

Why it matters

Metered egress and request billing remain among the least predictable line items in web infrastructure, and Vercel itself points to billing surprises that played out publicly on social media as a motivating factor. Flat Rate CDN trades that variance for a subscription, which matters most to agencies and product teams running many sites on shared capacity who cannot forecast client-driven or seasonal spikes.

The fine print deserves attention: "no overages" is defined by Vercel's fair use guidelines, sustained over-capacity usage can be migrated to the Flex CDN tier, and the dramatic savings figures come from Vercel's own examples rather than independent benchmarks. Even so, for teams with steady traffic profiles the plan turns delivery costs into a known number, and it sets a predictability benchmark that other CDN and hosting providers may eventually have to answer.