Edge vs a single European region: which is faster in 2026?

If your visitors and your database are both in Europe, one European region is usually as fast as the edge, and often faster for pages that read data. Edge compute wins when your audience is spread across continents and a request can be answered without a trip to a central database. Cloudflare Workers fits that worldwide case, while Eurobase fits a European audience whose app and data live in one place.

Edge and regional hosting at a glance

Platform	Where your code runs by default	Can you choose a region?	Where the data sits
Eurobase	European infrastructure run by Scaleway, a French provider	No, Europe only	SQLite databases for apps on V8 isolates, in your project
Cloudflare	The data center closest to where the request arrived, in 348 cities	Yes, with Placement hints or Smart Placement	D1 keeps one primary; read replicas are optional
Vercel	Functions in Washington, D.C., iad1	Yes: 1 region on Hobby, 5 on Pro	Your own database provider
Netlify	Functions in Ohio, cmh; Edge Functions at the location closest to each user	Yes, for functions on Pro and Enterprise	Your own database provider

Defaults are from each provider's own docs, checked on 10 November 2026.

Where the time actually goes

A page request has two legs. The first runs from the visitor to your code. The second runs from your code to everything it calls: a database, an auth service, a payment API. Edge hosting shortens the first leg. It does nothing for the second, and it can make it longer.

Cloudflare's own Placement docs give the example of a visitor in Sydney using a Worker that makes several round trips to a database in Frankfurt. Each of those trips crosses the world, so Cloudflare moves the Worker next to the database instead. The general rule follows from that: count how many sequential calls a page makes to its backend. One call or none favours the edge. Three, five or ten favour putting the code beside the data.

Static files are a separate question. A CDN can cache them close to visitors in front of either model, so they don't decide the choice. See European CDN providers.

What to check before you decide

• Where your visitors are. Look at your analytics by country. If almost all traffic comes from Europe, one European location already sits close to most of it.
• Where your data lives. A database has one primary for writes. Cloudflare's D1 docs say every write still goes to the primary, even with read replication on.
• How many backend calls a page makes. Multiply that number by the distance between your code and your data.
• What the default is. Vercel and Netlify both start functions in the United States. A European team that never changes the setting pays a transatlantic trip on every query to a European database.
• Cold starts. Code that has been idle has to start again, wherever it runs. Check how long your platform keeps an idle app warm.
• Legal location, not only speed. Running code in hundreds of cities means your requests are handled in many countries. Read EU region vs EU company if that matters to you.

1. Eurobase

Eurobase is a regional host. It runs Next.js, Astro, Nuxt and other frameworks on V8 isolates, and servers in Node.js, Python, Go and more as containers, all on European infrastructure run by Scaleway, a French provider. Apps on V8 isolates get SQLite databases in the same project, so queries don't leave Europe. When one of those apps marks a response as cacheable, later requests get the stored copy without running your code, and you can purge by tag, path or everything. See the cache docs.

• Best for: European audiences, and apps whose data has to stay in Europe.
• Price: free to start, with paid plans at €10 and €20 a month + VAT covering the whole workspace. Nothing is billed by usage today: past a limit, new work is refused, apps on V8 isolates and Functions stop until the monthly reset, and containers and static sites keep serving.
• What it lacks: a worldwide edge network, a region picker, managed Postgres, and preview deployments. An app on V8 isolates stops after 15 minutes without requests, and container apps scale to zero, so the next request waits for a start.

The company behind it is registered in Warsaw, Poland. ISO 27001 and SOC 2 certification is under way and not yet awarded. See Workers docs and Eurobase vs Cloudflare.

2. Cloudflare Workers

Cloudflare lists data centers in 348 cities and says 95% of the world's internet users are within 50 ms of one. By default a Worker runs in the data center closest to where the request arrived. Placement changes that: Smart Placement moves a Worker toward the backend it calls most, and explicit hints let you name a cloud region, a database host or an API hostname. Smart Placement is on all Workers plans, and static assets are always served from the location nearest the visitor.

• Best for: worldwide audiences and logic that needs little or no central data, such as redirects, auth checks or personalised headers.
• Price: a free plan with 100,000 requests a day, then Workers Paid from $5 a month per account.
• What it lacks: writes close to every user. D1 keeps one primary, and its read replicas need the Sessions API before they serve any queries. Your contract is with Cloudflare, Inc. of San Francisco, and California law governs it.

3. Vercel

Vercel caches static content in its CDN, which has 126 PoPs, and runs functions in 19 compute regions. Five are in Europe: Stockholm, Paris, Dublin, Frankfurt and London. New projects run functions in Washington, D.C. unless you change the region. Vercel's Edge runtime does run near the visitor, but Vercel's docs now recommend moving from edge to Node.js for better performance and reliability, and say Next.js 16.3 no longer supports runtime = 'edge'.

• Best for: Next.js teams who will set fra1 or another European region next to their database.
• What it lacks: more than one function region on Hobby; Pro allows 5. Routing Middleware runs in all regions whatever you choose.

4. Netlify

Netlify splits the two models. Edge Functions run on Deno at the network location closest to each user. Regular functions run in exactly one region, Ohio by default, and Netlify's docs call that default deliberate. You can switch to Dublin, Frankfurt or London in the dashboard, while Paris and Milan need a request to support.

• Best for: sites that want light edge logic in front of one regional backend.
• What it lacks: a region choice on lower plans; changing the function region is a Pro and Enterprise feature. A function can't be deployed to several regions for geo-routing.

How to measure it for your app

Don't decide from a map. Deploy the same build twice, once at the edge and once in a European region next to your data, and time a page that reads from the database:

1. Run curl -o /dev/null -s -w '%{time_connect} %{time_starttransfer}\n' https://your-app.example/page from a few places where your users are.
2. Compare time_starttransfer, the time to the first byte of the answer, not time_connect. A nearby edge location connects sooner, but visitors wait for the answer, not the connection.
3. Repeat after a long pause with no traffic to catch a cold start, then again straight away to see a warm one. On Eurobase, an app on V8 isolates stops after 15 minutes without requests.
4. Check a cached page separately. For an app on V8 isolates on Eurobase, the Cache-Status header shows whether the response came from the cache.

Frequently asked questions

Is edge hosting always faster?

No. It's faster for the first leg of the request and for pages that need no central data. When a page makes several database calls and the database sits in one region, code next to the database answers sooner. Cloudflare built Smart Placement for exactly that case.

Do I need edge hosting if all my users are in Europe?

Usually not. Distances inside Europe are short compared with a trip across the Atlantic, and a response cache on a regional host absorbs repeat traffic. What matters more is keeping your code and your database in the same place.

Why does Vercel run my functions in the US by default?

Vercel says it picks Washington, D.C. so functions sit close to most external data sources, which it says are hosted on the US East Coast. If your database is in Europe, set a European region such as fra1 in your project settings.

Can I put a CDN in front of a regional app?

Yes. A CDN caches static files and cacheable pages near visitors and forwards everything else to your region. That gives a worldwide audience fast assets while your dynamic pages stay next to the data. European CDN providers compares the options.

Does running at the edge affect GDPR?

It can. An edge network handles requests in many countries, and the provider's home country affects which other laws can reach the data. Check the provider's data location controls and where the company is based, and see the GDPR hosting checklist.

Sources

• Cloudflare Workers Placement, Cloudflare network and D1 read replication
• Cloudflare Workers pricing and Cloudflare terms
• Vercel function regions, Vercel regions and Vercel Edge runtime
• Netlify function configuration and Netlify Edge Functions
• Eurobase cache docs, Eurobase Workers docs, Eurobase containers docs, Eurobase plans and Eurobase subprocessors