Buy If / Skip If
Quick decision guide. PromptQuorum's verdict: a strong default for renting GPUs by the second, as long as you manage storage and credits actively.
- Choose RunPod if:
- You want per-second GPU billing with no contract
- You need a wide GPU choice, from 24 GB consumer cards to H100, H200 and B200
- You want an autoscaling inference endpoint that scales to zero
- You want a documented vLLM worker with an OpenAI-compatible API
- You can run non-sensitive workloads on Community Cloud, or pay for Secure Cloud
- Skip RunPod if:
- You need refundable credits or invoiced billing at small volumes (credits are non-refundable)
- You need documented data-center locations per region (the docs name only "European data center regions")
- You process sensitive personal data and need Community Cloud security guarantees (the docs do not describe them)
- You only run a 7B model occasionally and a local GPU already covers it
RunPod Scorecard
PromptQuorum assessment, based on RunPod's own pricing page and documentation checked 2026-11-22 — not a hands-on lab test of the service. Scores reflect fit for running or fine-tuning open-weight LLMs.
Price
- Score:
- 8/10
- Why:
- Community Cloud and per-second billing are cheap; idle storage adds up
Reliability
- Score:
- 7.5/10
- Why:
- Secure Cloud in T3/T4 data centers; Community Cloud is peer-supplied
Ease of setup
- Score:
- 9/10
- Why:
- Prepaid credits, Pods and a documented vLLM worker
GPU choice
- Score:
- 9.5/10
- Why:
- Pricing page lists RTX 3090 up to B300
Support and docs
- Score:
- 8.5/10
- Why:
- Detailed docs on billing, storage and Serverless
Overall
- Score:
- 8.5/10
- Why:
- Flexible GPU rental; manage storage, credits and data sensitivity
These scores are PromptQuorum's editorial assessment derived from RunPod's published pricing and documentation (see "How We Evaluate" below). They are not the result of PromptQuorum running benchmarks or long-term tests on the service.
Verdict: Who Should Use RunPod
Use RunPod if you want to rent a specific GPU by the second, and you are willing to watch storage charges and your credit balance. Its pricing page, checked 2026-11-22, lists GPUs from the RTX 3090 to the B300, and Community Cloud puts an RTX 4090 at $0.34/hr. For a one-off fine-tuning run or a weekend of testing, per-second billing means you pay for the minutes you use.
RunPod is not the right choice because it is cheapest on every line; it is the right choice when GPU variety, per-second billing and a documented serverless vLLM path matter more than a refund policy. Credits are non-refundable, and the docs do not describe Community Cloud security, so keep sensitive data on Secure Cloud or off the platform.
If the main question is price against a peer-to-peer marketplace, read the RunPod vs Vast.ai pricing comparison before topping up credits.
How RunPod Works: Pods, Serverless and Cloud Tiers
RunPod has two compute products and two hardware tiers: Pods or Serverless, on Secure Cloud or Community Cloud. Per the docs, Pods and Serverless workers each run in their own container with separation from other workloads, and both are billed by the second.
- Pods vs Serverless: use a Pod for interactive work, fine-tuning and long-running servers; use Serverless when requests arrive in bursts and idle time should cost nothing.
- Cold starts: a worker is billed during cold start and during its idle timeout. RunPod documents FlashBoot as retaining worker state after spin-down for faster revival; the docs give no timing numbers, and say it works best on endpoints with consistent traffic.
- Active workers: the default is 0. Setting 1 or more removes cold starts but, per the docs, incurs charges continuously, including when there are no jobs. Defaults checked: idle timeout 5 seconds (console), max workers 3.
- vLLM on Serverless: RunPod documents a vLLM worker deployable from the RunPod Hub, described as a drop-in replacement for the OpenAI API (change the endpoint URL and API key). Setup details are in the RunPod vLLM worker docs. For background on the engine, see vLLM explained.
- Network volume: keeps model weights outside any single Pod, so you do not re-download them each time.
Option | What it is |
|---|---|
| Pod | GPU container you control; billed while it runs |
| Serverless | Workers that scale to zero; billed while workers run |
| Secure Cloud | T3/T4 data centers, aimed at production use |
| Community Cloud | Vetted individual compute providers, lower prices |
| Container disk | Temporary; lost when the Pod stops or is deleted |
| Volume disk | Persists across stop/reboot; mounted at /workspace |
| Network volume | Independent storage attachable to Pods or endpoints |
Pricing and Real Costs
Pods are priced per GPU per hour and billed per second; Community Cloud is lower than Secure Cloud on every GPU in the table. All prices are USD from RunPod's pricing page, checked 2026-11-22, and can change.
- Serverless (per hour, same page): 24 GB GPUs (L4, A5000, 3090) $0.75; 4090 $1.34; 48 GB L40/L40S/6000 Ada $1.89; A100 80 GB $2.99; H100 80 GB $5.89. The page does not show separate flex and active per-second rates.
- Storage: container disk $0.10/GB/month; volume disk $0.10 while running and $0.20 while idle; network storage $0.07/GB/month under 1 TB and $0.05 above (high-performance $0.14).
- Arithmetic, not a quote: an 8-hour RTX 4090 session is 8 × $0.89 = $7.12 on Secure Cloud or 8 × $0.34 = $2.72 on Community Cloud. A 100 GB network volume at $0.07 is $7.00 per month whether or not a Pod is running.
- Credits: prepaid; the billing docs say you can start with as little as $10, prepaid cards must deposit at least $100 per transaction, and a new Pod needs at least one hour of credits. Credits are non-refundable and cannot be withdrawn.
- Zero balance: running Pods are stopped. A Pod with a network volume keeps its data; a Pod without one is terminated and its data cannot be recovered. Network volume storage keeps accruing while Pods are stopped.
- Traffic and limits: the docs state no ingress or egress fees. The default spending limit is $80 per hour across all resources and rises with account history.
- For hourly rates across providers, see cloud GPU cost per hour.
RTX 3090
- Secure:
- $0.50/hr
- Community:
- $0.22/hr
RTX 4090
- Secure:
- $0.89/hr
- Community:
- $0.34/hr
RTX A6000
- Secure:
- $0.69/hr
- Community:
- $0.33/hr
L40S
- Secure:
- $1.09/hr
- Community:
- $0.79/hr
A100 PCIe
- Secure:
- $2.09/hr
- Community:
- $1.19/hr
H100 SXM
- Secure:
- $4.39/hr
- Community:
- $2.69/hr
H200
- Secure:
- $5.29/hr
- Community:
- $3.59/hr
Which Models Fit Which GPU
A single 24 GB card covers models up to roughly 32B at Q4, and a 70B model at Q4 needs about 44 GB of VRAM, so it needs a 48 GB card or more. Sizes come from PromptQuorum's DeepSeek-R1 distill VRAM cheatsheet (Q4_K_M). Speed in tokens per second is not stated because it was not measured for this review.
- PromptQuorum assessment: a 70B model at Q4 leaves little memory for context on a 48 GB card; an 80 GB card gives headroom for longer prompts.
- The Serverless table lists A100 and H100 at 80 GB and L40/L40S at 48 GB, so those are the entry points for 70B on endpoints.
- To check any other model, use the VRAM guide for local LLMs. To compare renting with owning, use the build vs rent cost calculator.
- On a Pod, you can install Ollama or vLLM yourself; PromptQuorum has not benchmarked either on RunPod hardware.
7B–8B
- VRAM needed:
- ~5.5–6 GB
- RunPod GPU class:
- Any 16–24 GB card (A4000, L4, 3090)
14B
- VRAM needed:
- ~9.5 GB
- RunPod GPU class:
- 16–24 GB card
32B
- VRAM needed:
- ~20.5 GB
- RunPod GPU class:
- 24 GB card (4090, tight) or 32–48 GB
70B
- VRAM needed:
- ~44 GB
- RunPod GPU class:
- 48 GB card (tight) or A100/H100 80 GB
What You Can Build With It
RunPod suits work where you need a GPU for hours or days, or an endpoint that sits idle between bursts.
- Good fit: fine-tuning runs, experiments with 7B–32B models, and batch jobs billed only while they run. See best cloud GPU for fine-tuning under $1 per hour.
- Good fit: an inference API on Serverless with the vLLM worker when traffic is bursty. For production-scale server choices, see enterprise LLM inference servers.
- Limited: always-on endpoints, where active workers bill continuously and a dedicated Pod may be simpler.
- Poor fit: workloads with sensitive personal data on Community Cloud, or anything that needs refundable prepaid balances.
Risk and Trust
Facts only, from RunPod's documentation checked 2026-11-22: payment is prepaid credit, Secure Cloud is hosted in T3/T4 data centers, and Community Cloud uses individual compute providers. PromptQuorum has not audited RunPod or its hosts.
- Billing model: prepaid credits; per-second billing for compute and storage; credits are non-refundable and cannot be withdrawn; auto-pay needs a saved card.
- Where hardware comes from: Secure Cloud runs in T3/T4 data centers. Community Cloud connects individual compute providers to users through what RunPod calls a vetted, peer-to-peer system.
- Isolation: the docs say each Pod or worker runs in its own container with strict separation from other workloads.
- Host access: RunPod's terms prohibit hosts from inspecting Pod or worker data; the docs do not say how this is technically enforced.
- Certifications: the docs state that Secure Cloud infrastructure partners meet SOC 2, ISO 27001 and PCI DSS. This is attributed to the partners, not stated as RunPod's own certification. The docs do not describe Community Cloud security.
- GDPR: the docs state GDPR compliance for data processed in European data center regions and list no specific locations. The privacy policy covers website data and says RunPod is headquartered in the United States.
- Refunds and credits: none beyond the non-refundable statement above; no savings-plan terms were found on the billing page.
- Practical rule (PromptQuorum assessment): keep sensitive personal data off Community Cloud and review RunPod's data processing terms before using it for regulated data. This is not legal advice; whether a given use is lawful is for you and your data-protection adviser to decide.
Pros & Cons
RunPod trades refund flexibility for GPU variety and per-second billing. Balanced view below.
- Pros
- Per-second billing with no commitment and no ingress or egress fees
- Wide GPU range, from RTX 3090 to B300 on the pricing page
- Community Cloud prices well below Secure Cloud on every listed GPU
- Serverless scales to zero; a documented vLLM worker exposes an OpenAI-compatible API
- Network volumes keep weights independent of any Pod
- Cons
- Prepaid credits are non-refundable
- Idle volume disk costs $0.20/GB/month; network storage accrues even with no Pod running
- A Pod without a network volume is terminated at zero balance and its data cannot be recovered
- Community Cloud security is not described in the docs; data-center locations are not listed
- FlashBoot has no published timing numbers
Where to Sign Up
Create an account on runpod.io, add prepaid credits, then pick a Pod template or deploy a Serverless endpoint. Check the live prices before you commit; the figures here were checked 2026-11-22.
- Step 1: create a RunPod account and add credits (the docs say you can start with as little as $10; prepaid cards need $100 per transaction).
- Step 2: decide Secure Cloud or Community Cloud based on data sensitivity, then pick a GPU from the model-fit table above.
- Step 3: attach a network volume if you want weights or checkpoints to survive a Pod being stopped or terminated.
- Step 4: set a low-balance email alert in billing, so a zero balance does not stop a Pod unexpectedly.
- Step 5: for Serverless, deploy the vLLM worker from the RunPod Hub and keep active workers at 0 unless you need to remove cold starts.
Alternatives to Consider
Pick by billing model and data sensitivity, not by headline price alone.
- Peer-to-peer marketplace with on-demand and interruptible pricing → Vast.ai review.
- Crypto-denominated GPU marketplace → Clore.ai review; read its risk section before deciding what data to send.
- Large-provider GPU instances → see AWS, Google Cloud and Lambda directly; prices were not compared here.
- Own the hardware instead → compare with a local card using the cost calculator linked above, since steady daily use can favor owning.
How We Evaluate
This review was not hands-on tested by PromptQuorum. PromptQuorum did not rent GPUs, run benchmarks, or measure tokens per second or cold-start times for this page. It is built from RunPod's own pages, fetched 2026-11-22.
- Provider-stated: prices, billing granularity, storage types, defaults and security statements from RunPod pricing, billing docs, Pods overview, Serverless endpoint configuration, security and compliance docs and the privacy policy.
- PromptQuorum assessment: the scorecard, model-fit judgments and buy/skip advice, applied to the provider-stated facts above. VRAM sizes come from the PromptQuorum cheatsheet linked in the model-fit section.
- Not verified: data-center locations, Community Cloud security posture, per-second Serverless rates and cold-start timings.
- Criteria scored: price, reliability, ease of setup, GPU choice, support and docs.
Frequently Asked Questions
What is RunPod?
RunPod is a cloud service that rents NVIDIA GPUs billed per second. It offers Pods (a GPU container you control) and Serverless (autoscaling workers that scale to zero), on Secure Cloud and Community Cloud tiers.
How much does an RTX 4090 cost on RunPod?
The RunPod pricing page, checked 2026-11-22, lists the RTX 4090 at $0.89 per hour on Secure Cloud and $0.34 per hour on Community Cloud. Serverless lists 24 GB class GPUs separately; the 4090 is $1.34 per hour there. Prices can change, so check the live page.
What is the difference between Secure Cloud and Community Cloud?
Per RunPod's docs, Secure Cloud runs in T3/T4 data centers aimed at production use, while Community Cloud connects individual compute providers to users through a vetted, peer-to-peer system at lower prices. The docs do not describe Community Cloud security, so keep sensitive data off it.
How does RunPod bill?
Compute and storage are billed per second from prepaid credits, with no ingress or egress fees. The billing docs say you can start with as little as $10, prepaid cards must deposit at least $100 per transaction, and credits are non-refundable.
What happens when my RunPod balance reaches zero?
Running Pods are stopped. A Pod with a network volume keeps its data; a Pod without one is terminated and its data cannot be recovered. Network volume storage keeps accruing while Pods are stopped, so set a low-balance alert.
Does RunPod Serverless support vLLM?
Yes. RunPod documents a vLLM worker you can deploy from the RunPod Hub or customize from the worker-vllm repository. The docs describe it as a drop-in replacement for the OpenAI API: change the endpoint URL and API key.
What does FlashBoot do?
The docs say FlashBoot reduces cold starts by retaining worker state after spin-down, allowing faster revival than a fresh boot. It works best on endpoints with consistent traffic. RunPod publishes no timing numbers, and PromptQuorum did not measure any.
Do active workers cost money when idle?
Yes. The docs say active workers incur charges continuously, including when they have no jobs. The default is 0 active workers; setting 1 or more removes cold starts but adds a constant cost.
Is RunPod storage free?
No. The pricing page lists container disk at $0.10 per GB per month, volume disk at $0.10 while running and $0.20 while idle, and network storage at $0.07 per GB per month under 1 TB, $0.05 above, as checked 2026-11-22.
Can RunPod run a 70B model?
Yes, on a card with enough memory. A 70B model at Q4 needs about 44 GB of VRAM per PromptQuorum's cheatsheet, so use a 48 GB card (tight) or an 80 GB A100 or H100. Speed was not measured for this review.
What does RunPod's documentation say about GDPR?
RunPod's security and compliance page states GDPR compliance for data processed in European data center regions, without listing locations. PromptQuorum has not audited this; review the data processing terms before using personal data. Whether your use is compliant depends on your own lawful basis, a data processing agreement and any transfer mechanism, because RunPod is headquartered in the United States.
Can I get a refund for unused RunPod credits?
The billing docs say credits are non-refundable, cannot be withdrawn once deposited, and can only be used for RunPod services. Add only what you expect to use.
