If your site loads fast in your office but your agents in Dubai or Riyadh say it drags on their phones, this is for you. It is not for a team without real visitor numbers yet: measure first, then change the setup.
What does the CDN do for a visitor in Dubai?
It answers from the nearest point of presence when the page is cached, and sends the request on to a compute region when it is not. The second half is where Gulf visitors lose time.

- 01The visitor's request reaches the nearest of Vercel's points of presence: over 126 in 51 countries, its regions page says.
- 02The firewall and DDoS checks run. Vercel says this mitigation is unmetered and on every deployment at no extra cost.
- 03Routing rules run: redirects, rewrites and headers.
- 04If the page is in the cache, it goes straight back. If not, the request travels over Vercel's private network to a function in your compute region.
- 05The response can be cached so the next visitor gets it from the cache.
Vercel does not publish the city list for its points of presence, so we cannot tell you whether one sits in Dubai or Riyadh. What it does publish is the compute region list: 19 regions, none in the UAE, Saudi Arabia or the Middle East. Mumbai (bom1) is the nearest.
So a cached page skips the trip to a compute region. An uncached one goes to India, Europe or, by default, Washington, D.C. The search results for "vercel cdn" on 16 October were almost all Vercel's own pages, and none of them said where an uncached Gulf request goes.
Which pages can the CDN answer on its own?
More than most teams cache today. Vercel's CDN is framework-aware: with a supported framework, the caching rules come out of the build, so nobody writes cache headers by hand.

Incremental Static Regeneration (ISR) is the middle row's tool. It serves the cached page and regenerates it in the background, and Vercel handles the purging for Next.js, SvelteKit, Nuxt and Astro. Tag-based invalidation lets you clear only the pages for one project or one building when its price changes.
The regions page explains why this works: by keeping "fewer, dense regions", Vercel says it raises the chance that a popular page is already in a region's cache.
Where should the uncached part run?
Next to the data it reads, not next to the visitor. A form that runs in Mumbai and then calls a database in Frankfurt crosses two seas. Vercel's regions page says the same: run functions in the same region as your database.
- 01List what each function calls: your CRM, a database, a payment provider, an AI model.
- 02Find where the one it calls most lives.
- 03Set the function region to the nearest of Vercel's 19. Never leave it on the iad1 default by accident.
- 04If the data has no fixed home and your visitors are in the Gulf, bom1 Mumbai is the nearest region.
This also answers the data question. The CDN does not make Vercel a place to keep records that must stay in the UAE. Vercel's compliance page says data may be transferred to the United States. The form collects; the record lives in a system that keeps it in the country.
What does a listings site look like on it?
Here is a sample plan, not a client. A Dubai brokerage runs a site with 400 listing pages, each with photos and a payment plan, and a lead form that creates a Salesforce lead.
The only part that has to leave the Gulf is the submit. Browsing, photos and the payment plan come from the cache. For the shape of this work, see Mindcat for real estate brokers.
What does the CDN cost on Pro?
A fixed amount, as long as traffic stays inside a tier. Pro includes the lowest Flat Rate CDN tier at no extra cost.

Vercel says 1 million requests a month is about 33,000 a day, and a single busy day does not change the bill. If a whole month goes over, it moves you up a tier at the next cycle. On demand, outside Flat Rate, Fast Data Transfer costs $0.15 to $0.35 a GB and is priced by the region the requests come from.
Hobby includes 1 million CDN requests and 100 GB of Fast Data Transfer a month, but Hobby is for non-commercial use only. A business site is on Pro.
How do you know it is fast for your visitors?
Measure the people who use it, not a test from your office. Vercel's Speed Insights reports real-user Core Web Vitals, and the usage dashboard can filter data transfer by region. Look at your Gulf visitors on phones, on the pages that matter: the listing, the offer and the form.
If you have no traffic numbers yet, do not tune the CDN. Launch with the cache-or-run rule above, then change it with a month of real data.
What happens on the first call?
We call the method Preview every change, and cache rules are part of the change: Vercel scopes every CDN change to a branch and a preview link, so you test caching before production. On the call you tell us which pages matter, where your data lives and where your visitors are. The written assessment is free and lists what caches, what runs where, and the expected tier.
The first build week is a fixed AED/SAR 14,900, and Run plans watch the cache and the bill after go-live. See everything we build at Vercel, then send us the site.

