Netlify has described an infrastructure rebuild behind Edge Functions. Requests now run in Firecracker microVMs on its own edge network rather than being sent to a separate hosted execution service.
The provider says existing URL imports, npm packages, Node built-ins, configuration and local-development workflows continue to work as before.
What changes for developers
The update mainly changes how Netlify executes a deployed function, rather than asking application teams to adopt a new API. Netlify also reports lower invocation latency from its measurements.
Those figures describe the provider’s observed platform behavior, not a guaranteed speedup for every application. Teams can keep their existing code and measure their own request path, including external API or database calls that may dominate response time.