Link to headingFrom servers to serverless

In the early days of cloud computing, teams ran long-lived servers. You had to manage provisioning, handle scaling manually, and decide what happens during traffic spikes. Over-provisioning cloud resources was common, and idle time meant wasted money.

Serverless changed that. It abstracted away infrastructure configuration and introduced automatic scaling. Each request triggered its own isolated instance.

But this came with trade-offs. These instances were single-purpose and short-lived. Powerful, but ephemeral. That led to cold starts, duplicated overhead, and underutilized compute. Once again, teams were paying for resources they didn't fully use.

Link to headingFrom serverless to Fluid compute

Fluid compute breaks away from the traditional one-to-one serverless model. Instead of spinning up a separate instance for each invocation, Fluid compute intelligently orchestrates compute across invocations. Multiple concurrent requests can share the same underlying resources, eliminating cold starts and reusing idle time. This allows I/O bound workloads like AI to run more efficiently.

The impact was visible immediately. Fluid became the default for AI on Vercel, powering over one trillion invocations. Teams saw up to 90% cost savings by sharing compute across workloads intelligently.

Link to headingFluid with Active CPU

Fluid improved performance and cost, but there was still room to optimize. Even with high concurrency, there could still be moments where all invocations are waiting on external responses and no code is actively running. During these idle periods, functions stay in memory, doing no work, yet still incur CPU cost.

Active CPU pricing solves this. It's a new pricing model that charges for CPU only when your code is actively using the CPU. Building on existing Fluid gains, this brings additional cost savings of up to 90% for workloads with high idle time, like AI inference.

This aligns pricing with actual usage. Compute costs scale with real work, not just with the time a function is alive.

Link to headingThe Active CPU pricing model

Fluid compute now charges based on three key metrics, each designed to reflect actual resource usage:

1. Active CPU reflects the compute time your code is actively executing on a virtual CPU (vCPU). It’s measured in milliseconds, calculated as the number of vCPUs allocated multiplied by the time they’re actively used. Pricing starting at at $0.128 per hour

2. Provisioned Memory covers the memory required to keep a function alive while it's running. It’s measured in GB-hours and billed at a much lower rate (less than 10% of Active CPU), thanks to Fluid’s ability to reuse memory across multiple concurrent invocations. Pricing starting at at $0.0106 per GB-Hour

3. Invocations are counted per function call (just like in traditional serverless) and remain part of the overall pricing

This pricing model in action:

A function running on a Standard machine size at 100% active CPU would now cost ~$0.149 per hour (1 Active CPU GB-Hour + 2 GB of provisioned memory). Previously, this would have cost $0.31842 per hour (1.7 GB Memory × $0.18).

Link to headingBuilt for the way modern apps run

Fluid is our proprietary compute platform, built for modern workloads.

It simplifies cloud infrastructure while preserving flexibility and performance. Developers can use standard runtimes like Node.js and Python, making it easy to run existing code without changes.

Fluid powers core product experiences across our platform, including Functions, and recently announced Sandbox. All of them run on the same compute engine, optimized for concurrency, reuse, and efficiency, with unified billing across the stack.

Link to headingAvailable today

Active CPU pricing is now enabled by default for all Hobby, Pro, and new Enterprise teams. For existing Enterprise customers, availability depends on your current plan configuration. Most teams will have access right away. Reach out to your Vercel account representative to learn more and enable the new pricing model.

With Active CPU, Fluid compute automatically optimizes your costs to match actual usage. It reduces waste, scales with real usage, and reflects the way modern apps actually run.