Summary

  • Vercel's regional rate table prices four adjacent rows in four different denominators: CDN Requests | 1,000,000 Requests for $2.00 - $3.20, Fast Data Transfer per 1 GB, ISR Writes per 1,000,000 Write Units and ISR Reads per 1,000,000 Read Units.
  • The rendered price page prints "per 1M" on three of those rows — $0.40 for ISR Reads, $4 for ISR Writes, $0.60 for Function Invocations — and only the invocation row's million counts a request; the size of the ISR unit is defined on a third document as 8 KB of cache.

The table that names its own units

The regional rate table is the one place in the corpus where the noun sits next to the number. CDN Requests | 1,000,000 Requests for $2.00 - $3.20. Fast Data Transfer | 1 GB for $0.15 - $0.35. ISR Writes | 1,000,000 Write Units for $4.00 - $6.40. ISR Reads | 1,000,000 Read Units for $0.40 - $0.64.

Read that column and the architecture is visible at once. The platform bills one wall of its business by counting events, another by counting bytes on the wire, and a third by counting cache blocks. Three physical quantities, one table, one currency, two rows of whitespace between them.

Now open the page most buyers reach first.

The page that drops the noun

On vercel.com/pricing the ISR rows read "1M / month included" and then "Starting at $0.40 per 1M" and "Starting at $4 per 1M". Function Invocations reads "1M / month included" then "$0.60 per 1M". Three instances of one expression, on one page.

For the invocation row the expression is exact. Vercel's functions documentation defines an invocation as "Counts each request to your function - Billed per incoming request", and its legacy pricing page fixes the perimeter: successful and errored invocations both count, cache hits do not. A May 2026 changelog prints the same rate twice, as $0.0000006 per invocation and as $0.60 per 1M — two denominations, one number.

For the two ISR rows the expression is a shape with nothing in it. The price page glosses the operations, saying an ISR read reads cached data from the global Vercel Cache and an ISR write writes to it, which tells you what the software does and nothing about what the million counts. The noun lives one document over, which prints "1M read units" and "1M write units" beside the same rates. What a unit weighs lives one document further, in a sentence short enough to quote whole: Read unit: One read unit equals 8 KB of data read from the ISR cache, and the matching line for writes.

Everywhere else in the corpus the request counter is defined by its perimeter rather than its size. The CDN usage page calls a CDN Request simply "Requests the CDN processes"; Vercel's own training lesson says every incoming request counts whether the response is served from cache or generated dynamically. That is a counter with no denominator problem, because the denominator is the event.

Eight kilobytes, and what it does to $0.40

Multiply. One million read units at 8 KB is 8,000,000 KB, which is 8 GB in decimal kilobytes. At $0.40 per million units, cache reads come to $0.05 a gigabyte. Do the same on the write row: one million write units is 8 GB, so $4.00 per million write units is $0.50 a gigabyte written.

Lay that against the transfer row at $0.15 a gigabyte. Writing a gigabyte of ISR cache costs 3.33 times what moving a gigabyte to a visitor costs. Reading it back costs one third.

All of that is my division of Vercel's printed rates by Vercel's printed unit size. The company prints none of the three per-gigabyte figures and owes nobody the comparison. But the comparison is the only way to see what the row actually prices — and it is the reason a reader who stops at the price page cannot know.

Then take the ambiguity seriously. Read "1M ISR reads" as a million requests and each read as 1 KB, and a million reads is 125,000 read units, so the bill is $0.05. Read each read as 64 KB, and a million reads is 8,000,000 read units, so the bill is $3.20. Same phrase, same page, same $0.40 headline. The spread is 64×, and the only payload at which the two readings agree is exactly 8 KB — the size the third document prints.

Three meters on one request, two on one page

The request does not carry one number. The CDN usage page adds CDN Request CPU duration as a separate billable resource, metered in 10 ms increments, with requests of 10 ms or less free and the rest at $0.30 an hour, one hour included on Pro. That line is not on the rendered price page.

The WAF page subtracts the other way: traffic denied, challenged or rate-limited by the firewall, plus DDoS mitigation, Attack Mode, IP blocking and persistent actions, incurs neither CDN Requests nor Fast Data Transfer, while a request that passes a challenge and continues counts normally.

The observability page multiplies: a cached response is one CDN Request event, while a dynamic one can be a CDN Request plus Middleware plus a Function Invocation plus two external API calls plus an AI Gateway request — six events from one page view.

None of that is a contradiction. Each is a printed boundary on a different meter, and the price page carries one of them.

The rename that tells you what the vendor thinks a rename is

On 30 September 2026 Vercel renamed the request meter. Edge Requests became CDN Requests, and the changelog says: This is a naming change only: pricing, limits, and how usage is measured are all unchanged.

An honest, useful sentence, and it marks the boundary of what a reader can conclude from it. It establishes that one rename on one date did not move measurement. It establishes nothing about the size of a unit that was never named on the price page, and it does not tell a buyer whether the next rename will be as cheap.

Where the printed surface ends

Three things do not appear in the thirteen Vercel pages I read.

First, a rounding rule. The ISR page says a unit is 8 KB and never says whether a 1 KB read bills as one full unit or as one eighth of one. That single sentence would move the effective rate by eight times for a small-payload workload, and it is not in the corpus. I looked for the document that would carry it; I did not find one. That is a stop, not a finding that the rule does not exist.

Second, a payload distribution. Even with the 8 KB unit in hand, nobody holding these pages can turn an invoice line in read units back into a request count, because the average cache payload belongs to the application, not to the vendor.

Third, a reconciliation of Pro's included request volume. This is the one place where the corpus contradicts itself cleanly. The rendered price page shows Pro's CDN Requests row as "Included in Flat Rate CDN". The Flat Rate CDN documentation puts the Pro-included tier at 1M requests and 1 TB. And a machine-readable rendering of the same price page, surfaced in the same search, prints "10M / month included; then starting at $2 per 1M". Three copies, three answers, no page reconciling them.

What the same gigabyte costs inside a tier

Flat Rate CDN is the Pro default and replaces per-unit CDN billing with monthly capacity: the $20 tier carries 10M requests and 50 TB. Fifty terabytes is 50,000 GB, so $20 across that capacity is $0.0004 a gigabyte, against $0.15 a gigabyte past the included 100 GB on demand. A factor of 375, mine, from two printed numbers.

The covered list is worth reading rather than skimming: the tier covers CDN requests, Fast Data Transfer, Blob Data Transfer, Sandbox Data Transfer and observability events generated from CDN requests. ISR reads and ISR writes are not on that list. The list is a list and not an exclusion clause, so I will not say the cache rows sit outside the tier — only that no retained page puts them inside it.

The ledger, read correctly

Put the pieces where they belong. The request counter counts events. The transfer counter counts bytes as the network sees them — the page says the calculation uses "the full size of each HTTP request and response... the body, all headers, the full URL and any compression" — a larger quantity than the payload a developer thinks they are shipping. The two cache counters count 8 KB blocks of stored content. Four rows, four physical things, one table.

That is not a scandal. It is a design, it is documented, and the documentation is short enough to quote whole. It is also a trap for the reader who takes the price page as the whole of the pricing. The page prices three things "per 1M" and only one of those millions is a request. The CDN row has stopped printing a rate at all for Pro. A second meter on the same request sits on a third page. The number that governs a month's bill is not the number most readers carry away.

Why the package also carries a Fast Origin Transfer line at $0.06 per 1 GB, and why the pricing documentation likewise prints Runtime Cache reads and writes in 8 KB units, is worth one sentence: the 8 KB idea is not a quirk of the ISR page. It is the platform's house unit for cache, printed in the place where the noun already exists, and absent from the place where the rate does. The gap between those two places is the ordinary condition of cloud pricing rather than an exception: the vendor publishes the rate on one page and the size of the thing the rate multiplies on another, and the join is left to whoever reconciles the invoice.