Netlify Edge Functions
Deno-based functions at Netlify's edge. Web-standard APIs, a generous free allowance, tight Netlify build integration.
VISIT NETLIFY EDGE FUNCTIONSQuick facts
- CategoryV8 isolate
- LanguageDeno / TS
- PricingFreemium
- LicenseProprietary
- Created2022
- GitHub starsclosed
- Cold startinstant
- PoPs—
- Node-compatNo
What it is
Netlify Edge Functions run JavaScript or TypeScript on Deno at the network edge, close to the visitor. They expose web-standard APIs (fetch, Request, Response) rather than the full Node surface, and are built for middleware-style work: redirects, geolocation, locale routing, A/B tests, auth, and streaming. The free tier includes 1,000,000 edge function invocations a month, well above the 125,000 serverless function invocations.
Further reading
Best for
- Redirects, geolocation, locale routing, and A/B tests at the edge
- Teams already deploying their site on Netlify
- Streaming and personalisation close to the user
When not to pick it
Skip Netlify Edge Functions for API and backend work that needs npm packages or Node built-ins, where regular Netlify Functions fit better. Skip Netlify entirely if your site is not hosted there; the value is in the integration.
My take
Netlify Edge Functions are the Deno-flavoured counterpart to Vercel Edge and Cloudflare Workers. If you are already on Netlify, the generous free edge allowance and the build integration make them an easy default for middleware. Cloudflare still wins on raw scale and PoP count.
Links
Similar tools you should also consider
Deno Deploy
V8 isolates from the Deno team. Web-standard APIs, cleaner runtime than Node.
Read the take →Cloudflare Workers
V8 isolates on 300+ PoPs. Sub-millisecond cold starts, lowest cost at scale, the edge default.
Read the take →Vercel Edge
V8-isolate Edge runtime inside Vercel. Tight Next.js integration, now runs on Vercel Functions after the 2025 Edge Functions deprecation.
Read the take →If Netlify Edge Functions is your pick — the next conversation is short
The 30-min call is where your edge runtime choice becomes a real architecture, an integration plan with your data layer + auth + build pipeline, and a price range you can take to your stakeholders.