Skip to main content
Runpod offers custom pricing plans for large scale and enterprise workloads. Contact our sales team to learn more.
Serverless offers pay-per-second pricing with no upfront costs. You’re billed from when a worker starts until it fully stops, rounded up to the nearest second.

​
Worker types

​
What you’re billed for

Your total cost includes compute time and storage:

​
Compute cost breakdown

Workers incur charges during three phases:
  1. Cold start: From when the worker starts until your handler is ready, mostly your handler loading models into GPU memory. Pulling the container image and downloading cached models normally happen while the worker is scaled down and are not billed. Minimize with FlashBoot or model caching.
  2. Execution time: Processing requests. Set execution timeouts to prevent runaway jobs.
  3. Waiting (idle timeout): After its last job, a worker keeps running and waits for new requests for up to the idle timeout (default: 5 seconds) before it scales down. Configure in endpoint settings.
A worker that has scaled down, shown as Idle in the console, is not billed. See worker lifecycle.
For high-volume workloads with significant storage needs, use network volumes to share data across workers and reduce per-worker storage costs.

​
Account limits

Spend limit: Default limit of $80/hour across all resources. Contact support to increase.

​
Billing support

If you believe you’ve been billed incorrectly, contact support, including the following information in your ticket:
  • Endpoint ID
  • Request ID (if applicable)
  • Approximate time of the issue
Last modified on October 15, 2026