Fluid assembles a machine per workload with Hive provisioning warm VMs and Drive keeping storage detached; Functions run as IO-bound small VMs, many requests share an instance, and Active CPU pricing bills only while code runs.

Functions get the same warm-VM instant-start path as builds and sandboxes, and pay-for-CPU billing changes the cost math for workloads that mostly wait on databases or models.

Vercel Fluid Compute Now Powers Functions Alongside Builds and Sandboxes

Q: What shipped?

Vercel revealed Fluid Compute — the single execution layer that already ran builds and sandboxes — now also powers Functions, announced September 1, 2026.

What shipped

Vercel revealed Fluid Compute — the single execution layer that already ran builds and sandboxes — now also powers Functions. Announced September 1, 2026 in "Compute that takes any shape."

What changed

Fluid assembles a machine to fit each workload instead of locking a job to one compute primitive. Hive provisions isolated VMs (usually already warm, so work starts instantly), Drive keeps storage detached from machines, and many requests share a single instance. Functions run as IO-bound workloads on small VMs that load code the instant a request lands.

Billing shifts to Active CPU pricing: you pay for CPU only while your code is working, not while it waits on a database or a model. Scale numbers: 15 million builds a day, 25 million sandboxes a week, a trillion requests a month.

Why a builder cares

Functions inherit the same warm-VM, instant-start path as builds and sandboxes, and the pricing model changes the cost math for API and agent workloads that mostly wait on I/O — idle CPU no longer gets billed.

What shipped

What changed

Why a builder cares

Related reading