Skip to content
All tool news

Tool desk · Updated daily

Tool news·Netlify·

Netlify Moves Every Edge Function Into Firecracker MicroVMs.

Netlify now runs each Edge Function in a Firecracker MicroVM, cutting median warm invocations to 5–6 ms and speeding logs 5×.

CW

Create With tool desk

4 sources checked · 2 min read · 3 sections

ShareLinkedIn
Netlify Moves Every Edge Function Into Firecracker MicroVMs

Netlify Firecracker MicroVMs now run every Edge Function inside the company’s edge network. The infrastructure change required no action from customers, while cutting median warm invocation times and delivering logs more quickly.

According to the LinkedIn post, Netlify handles about a billion Edge Function runs each day. Every invocation now runs in its own Firecracker MicroVM within the edge network.

Daily Edge Function runs
About 1 billion
Median warm invocation
5–6 ms
previously 25–40 ms
Log delivery
5× faster

Firecracker MicroVMs Require No Migration

Customers did not need to update their functions, change configuration or redeploy projects to receive the infrastructure upgrade. Existing Edge Functions moved to individual MicroVMs without changes to customer code.

Median warm invocation time fell from a range of 25 to 40 milliseconds to 5 or 6 milliseconds. This measurement covers warm invocations, where the function is already available to handle the request.

The other improvement is in observability. Logs now arrive five times faster, reducing the wait between an Edge Function running and its output appearing in the logs. The change applies alongside the runtime migration rather than through a separate logging setup.

What Changes for Edge Function Workflows

The update changes the infrastructure beneath existing Edge Functions, rather than introducing a new function type or deployment process. Projects continue to use the same functions while gaining the lower median warm invocation time.

Builders debugging production behaviour also receive function logs sooner. No new logging command, dashboard or customer-side configuration was announced as part of the change.

Frequently asked questions

What are Netlify Firecracker MicroVMs?

They are individual MicroVMs that now run each Netlify Edge Function inside its edge network. The migration happened without customers changing their functions.

How fast are Netlify Edge Functions now?

Netlify reports median warm invocation times of 5 or 6 milliseconds. The previous range was 25 to 40 milliseconds, while logs now arrive five times faster.

Which Netlify plan includes Firecracker MicroVMs?

The post says every Edge Function now runs in its own Firecracker MicroVM. It does not give separate pricing or plan details for the change.

Sources

4 checked

How we cover tool news: Create With's tool desk drafts these reports with AI from the sources listed above and checks them against those sources before publishing.

Worth passing on?

ShareLinkedIn

Latest tool news

What else changed this week.

All tool news

The Create With Briefing

Don't watch forty changelogs. Read one email.

Every Tuesday: the tool changes worth knowing, real business use cases, and what's on near you. Free, unsubscribe any time.