Vendors · Comparison
CoreWeave vs RunPod
Only RunPod documents SOC 3 and ISO 27001. Pricing, compliance, regions and residency compared, every fact sourced and dated.
Last verified (older of the two profiles) How we verify
From the data
Key differences
- Pricing CoreWeave: Per-GPU-hour on-demand and spot; reserved capacity at up to 60% discount (published pricing). RunPod: Per GPU-hour (per-second display available); reserved clusters via sales (published pricing).
- Category Both are Dedicated GPU offerings.
- Compliance Both document SOC 2 Type II and GDPR DPA. Only RunPod documents SOC 3 and ISO 27001.
- Data residency CoreWeave's data residency is not verified; RunPod states data residency on its own pages (not contractual).
- Jurisdiction Both parent companies are under United States jurisdiction.
Generated from the verified vendor data below; sources and dates on each vendor profile.
CoreWeave
Security page states every CKS node is single-tenant; CKS runs Kubernetes directly on bare-metal nodes without a hypervisor. SOC 2 Type II scope covers Bare Metal and CKS. Trust centre shows ISO 27001/27017/27018 badges but the security page uses "aligned with" wording, so ISO 27001 is excluded (https://www.coreweave.com/security). Terms name CoreWeave, Inc. under New York law.
RunPod
Secure Cloud runs in T3/T4 data centres for enterprise and production workloads; Community Cloud uses vetted peer-to-peer providers. Terms make no residency commitment; the trust centre states workloads can be placed by jurisdiction. A HIPAA programme is stated, but no BAA was found. This site has an affiliate relationship with RunPod.
Side by side
Capabilities compared
| CoreWeave | RunPod | |
|---|---|---|
| Pricing model | Per-GPU-hour on-demand and spot; reserved capacity at up to 60% discount | Per GPU-hour (per-second display available); reserved clusters via sales |
| Public pricing | Yes | Yes |
| Category | Dedicated GPU | Dedicated GPU |
| Deployment models | Bare metalManaged KubernetesOn-demandSpotReserved capacity | Secure CloudCommunity CloudReserved clusters |
| Regions | United States, United Kingdom, EU/EEA | United States, EU/EEA, Asia-Pacific |
| Compliance | SOC 2 Type II (stated)GDPR DPA | SOC 2 Type IISOC 3ISO 27001GDPR DPA |
| Data residency evidence | Not verified | Stated |
| Parent jurisdiction | United States | United States |
| Sovereign for | Not recorded | Not recorded |
| Analyst note | Security page states every CKS node is single-tenant; CKS runs Kubernetes directly on bare-metal nodes without a hypervisor. SOC 2 Type II scope covers Bare Metal and CKS. Trust centre shows ISO 27001/27017/27018 badges but the security page uses "aligned with" wording, so ISO 27001 is excluded (https://www.coreweave.com/security). Terms name CoreWeave, Inc. under New York law. | Secure Cloud runs in T3/T4 data centres for enterprise and production workloads; Community Cloud uses vetted peer-to-peer providers. Terms make no residency commitment; the trust centre states workloads can be placed by jurisdiction. A HIPAA programme is stated, but no BAA was found. This site has an affiliate relationship with RunPod. |
Where they diverge
Deployment differentiation
Only CoreWeave
Both
No overlap in deployment models.
Only RunPod
Read the full profiles