Skip to content
All tool news

Tool desk · Updated daily

Tool news·Netlify·

Netlify Adds Per-Function Compute Controls for Memory, CPU, and Regional Execution.

Netlify now lets developers configure memory, CPU, and execution region per function to optimize performance for large workloads and AI inference.

CW

Create With tool desk

1 source checked · 2 min read · 2 sections

ShareLinkedIn
Netlify Adds Per-Function Compute Controls for Memory, CPU, and Regional Execution

Netlify rolled out per-function compute controls last week, giving developers granular control over how serverless functions execute. The update targets teams deploying larger apps and workloads that demand more resources, including AI inference tasks and APIs handling heavy payloads.

The new configuration options let developers set three parameters directly in code: execution region, memory allocation (1–4 GB), and CPU allocation (0.5–2 vCPU). Memory and CPU scale together automatically, so developers can specify whichever metric makes the most sense for their use case and Netlify adjusts the other proportionally.

Why Regional and Resource Controls Matter

Regional execution addresses two core needs: performance and compliance. Deploying a function closer to users or the databases and services it depends on reduces latency, particularly for latency-sensitive workloads like real-time APIs or data-heavy operations. For teams subject to data sovereignty or compliance requirements, regional controls ensure functions process data in specific geographies.

Memory and CPU controls address a different bottleneck. Default serverless functions allocate 1 GB of memory and 0.5 vCPU, sufficient for lightweight tasks but restrictive for compute-intensive jobs. AI inference, large file processing, and complex data transformations routinely exceed these limits. Netlify's new settings let developers scale up to 4 GB of memory and 2 vCPU per function, defined at the function level rather than site-wide.

This approach follows a broader industry shift toward giving developers infrastructure control without leaving the serverless model. Vercel and other platforms have adopted similar patterns, recognizing that one-size-fits-all resource limits no longer match real-world workloads.

Configuration and Validation

All compute settings live in code, which means they version with the rest of the project and get validated in deploy previews before reaching production. This prevents resource misconfigurations from impacting live traffic. The configuration format integrates with Netlify's recent push toward typed function definitions, part of their Agent Experience overhaul.

Developers on credit-based plans (Pro and above) can access per-function memory and CPU controls immediately. Regional execution is available across all plans that support function configuration.

The timing aligns with Netlify's broader repositioning around AI-native development. The platform recently added support for Agent Runners and event handlers, infrastructure specifically designed for agentic workflows. Per-function compute controls extend that capability by giving AI workloads the resources they need to run efficiently at scale.

Netlify Functions interface
Netlify Functions interface

For teams already running complex serverless architectures, the update removes a longstanding friction point. Instead of architecting around fixed resource limits or migrating compute-heavy tasks to separate infrastructure, developers can now tune individual functions to match their workload. The result is fewer workarounds and more predictable performance for resource-intensive tasks.

Sources

1 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
VercelDigest

What Vercel Shipped in Late October

Vercel shipped quicker static deployments, four AI Gateway models, more free domain choices and new CLI controls in late October. The changes cover developers testing sites…

Vercel

Vercel Adds Submit_feedback to Its MCP

submitfeedback is a new Vercel MCP tool that lets agents and harnesses send bug reports, friction reports and feature requests directly to the Vercel team. Feedback can include…

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.