Iteration velocity is now set by how quickly you can provision the computer your app or agent needs.

Workloads differ in how long they run, how much memory they take, and how much of the environment they control. That previously meant a different compute primitive for each job, so product iterations required provisioning infrastructure, not just working on a feature.

We built Vercel so that none of this has to be your problem. The compute layer is a single system with a simple job. Take any workload, assemble the machine it needs, swap configuration on the fly, and absorb burst capacity in real time.

We call this Fluid.

Builds ran on it first, then sandboxes, and now functions.…