Services Pricing and Limits
Vercel bills Services across the compute each service runs on, the requests services make to each other, and the data services return.
Each service runs on Vercel's compute and is billed the same as Vercel Functions: Active CPU, provisioned memory, and invocations. Fluid Compute applies, so concurrent requests can share an instance.
When one service calls another over a binding, each call counts as one service request. Requests that arrive from the public internet are not service requests.
Service requests are regionally priced, like other Managed Infrastructure resources, and are billed separately from CDN requests. A service-to-service call does not incur a separate Edge Request or Fast Data Transfer charge.
Resource | Hobby Included | Pro Included | On-demand Rates |
|---|---|---|---|
| N/A | N/A | Regional |
See Pricing for plan details and included credits.
The bytes a service returns are billed as Fast Origin Transfer, the same as other origin traffic on Vercel, whether the response is a static file or comes from a function.
The same function limits apply to each service, such as memory and maximum duration.
Was this helpful?