--- source_url: "https://vercel.com/docs/functions/usage-and-pricing" title: Fluid compute pricing mirrored_at: 2026-08-11T13:02:22.329Z host: vercel.com cited_in_42a: true mirror_canonical: "https://index.42a.ai/vercel.com/docs/functions/usage-and-pricing" --- > **Original source:** https://vercel.com/docs/functions/usage-and-pricing Vercel prices Functions on fluid compute based on your plan and resource usage. Hobby includes monthly allowances for Active CPU, Provisioned Memory, and Invocations. Vercel bills Pro usage on demand, and your monthly Pro usage credit can offset those charges: Resource Hobby Pro [**Active CPU**](#active-cpu) 4 hours included N/A _On-demand Active CPU_ \- Costs vary by [region](#regional-pricing) [**Provisioned Memory**](#provisioned-memory) 360 GB-hrs included N/A _On-demand Provisioned Memory_ \- Costs vary by [region](#regional-pricing) [**Invocations**](#invocations) 1 million included N/A _On-demand Invocations_ \- N/A Enterprise plans have custom terms. Speak to your Vercel account representative for details. - This is the CPU time your code actively consumes in milliseconds - You are only billed during actual code execution and not during I/O operations (database queries, like AI model calls, etc.) - Billed per CPU-hour - Pauses billing when your code is waiting for external services For example: If your function takes 100ms to process data but spends 400ms waiting for a database query, you're only billed for the 100ms of active CPU time. This means computationally intensive tasks (like image processing) will use more CPU time than I/O-heavy tasks (like making API calls). - Memory allocated to your function instances (in GB) - Billed for the entire instance lifetime in GB-hours - Continues billing while handling requests, even during I/O operations - Each instance can handle multiple requests with [optimized concurrency](https://vercel.com/docs/fluid-compute#optimized-concurrency) - Memory is reserved for your function even when it's waiting for I/O - Billing continues until the last in-flight request completes For example: If you have a 1GB function instance running for 1 hour handling multiple requests, you're billed for 1 GB-hour of provisioned memory, regardless of how many requests it processed or how much of that hour was spent waiting for I/O. - Counts each request to your function - Billed per incoming request - Hobby includes 1 million invocations per month - Vercel bills Pro invocations on demand - Counts regardless of request success or failure For example: If your function receives 1.5 million requests on a Pro plan, Vercel bills those invocations at $0.60 per million, subject to your monthly Pro usage credit. The following table shows the regional pricing for fluid compute resources on Vercel. The prices are per hour for CPU and per GB-hr for memory: Fluid compute regional pricing Region Active CPU (per hour) Provisioned Memory (per GB-hr) Cape Town, South Africa (cpt1) $0.200 $0.0166 Cleveland, USA (cle1) $0.128 $0.0106 Dubai, UAE (dxb1) $0.185 $0.0153 Dublin, Ireland (dub1) $0.168 $0.0139 Frankfurt, Germany (fra1) $0.184 $0.0152 Hong Kong (hkg1) $0.176 $0.0146 London, UK (lhr1) $0.177 $0.0146 Montreal, Canada (yul1) $0.147 $0.0122 Mumbai, India (bom1) $0.140 $0.0116 Osaka, Japan (kix1) $0.202 $0.0167 Paris, France (cdg1) $0.177 $0.0146 Portland, USA (pdx1) $0.128 $0.0106 San Francisco, USA (sfo1) $0.177 $0.0147 São Paulo, Brazil (gru1) $0.221 $0.0183 Seoul, South Korea (icn1) $0.169 $0.0140 Singapore (sin1) $0.160 $0.0133 Stockholm, Sweden (arn1) $0.160 $0.0133 Sydney, Australia (syd1) $0.180 $0.0149 Tokyo, Japan (hnd1) $0.202 $0.0167 Washington D.C., USA (iad1) $0.128 $0.0106 A function instance runs in a region, and its pricing is based on the resources it uses in that region. The cost for each invocation is calculated based on the Active CPU and Provisioned memory resources it uses in that region. When the first request arrives, Vercel starts an instance with your configured memory. Vercel bills Provisioned Memory continuously until the last in-flight request finishes. Vercel bills Active CPU only while your code is actually running. If the request is waiting on I/O, CPU billing pauses but memory billing continues. After all requests complete, the instance is paused, and no CPU or memory charges apply until the next invocation. This means, you pay for memory whenever work is in progress, never for idle CPU, and nothing at all between requests. Suppose you deploy a function with 4 GB of memory in the São Paulo, Brazil region, where the rates are $0.221/hour for CPU and $0.0183/GB-hour for memory. If one request takes 4 seconds of active CPU time and the instance is alive for 10 seconds (including I/O), the cost will be: - CPU: (4 seconds / 3600) × $0.221 = $0.0002456 - Memory: (4 GB × 10 seconds / 3600) × $0.0183 = $0.0002033 - Total: $0.0002456 + $0.0002033 = $0.0004489 for each invocation.