Vendors · Comparison
Baseten vs CoreWeave
Only Baseten documents SOC 3, ISO 27001 and HIPAA BAA. Pricing, compliance, regions and residency compared, every fact sourced and dated.
Last verified (older of the two profiles) How we verify
Analysis
What separates them
These sit at different layers. Baseten runs your models as managed dedicated deployments. CoreWeave rents GPU infrastructure: its security page says every CoreWeave Kubernetes Service node is single-tenant, and you run the serving stack yourself.
Billing follows the layer. Baseten bills compute down to the minute. CoreWeave publishes per-hour on-demand and spot GPU prices and offers up to 60% off on-demand rates for committed usage.
Residency evidence differs. Baseten’s regional deployments let GPU model deployments select a region (US and European Union among the values), a Stated product control. CoreWeave’s residency is not verified here: no contractual or stated region commitment was found in its sources.
Both are US companies. CoreWeave’s terms of use are governed by New York law; Baseten contracts as Baseten Labs, Inc. under its terms. For a buyer the question is whether you want a managed inference product or isolated hardware to operate.
Last verified (every source below) How we verify
Sources (6)
- https://www.coreweave.com/security (checked 2026-10-22)
- https://www.baseten.co/pricing (checked 2026-10-22)
- https://www.coreweave.com/pricing (checked 2026-10-22)
- https://docs.baseten.co/deployment/regional-deployments (checked 2026-10-22)
- https://docs.coreweave.com/policies/terms-of-service/terms-of-use (checked 2026-10-22)
- https://www.baseten.co/terms-and-conditions/ (checked 2026-10-22)
From the data
Key differences
- Pricing Baseten: Per 1M tokens (Model APIs); per-minute GPU/CPU instances for dedicated deployments (published pricing). CoreWeave: Per-GPU-hour on-demand and spot; reserved capacity at up to 60% discount (published pricing).
- Category Both are Dedicated GPU offerings.
- Compliance Both document SOC 2 Type II and GDPR DPA. Only Baseten documents SOC 3, ISO 27001 and HIPAA BAA.
- Data residency Baseten states data residency on its own pages (not contractual); CoreWeave's data residency is not verified.
- Jurisdiction Both parent companies are under United States jurisdiction.
Generated from the verified vendor data below; sources and dates on each vendor profile.
Baseten
Dedicated deployments and an enterprise self-hosted option position Baseten for single-tenant use. Trust centre lists ISO 27001:2022, SOC 2 Type 2 and SOC 3. Regional deployments pin replicas to the US or EU, but no contractual data-residency guarantee found; trust centre lists subprocessors across multiple clouds. Egress allow-lists of IP ranges and domains (Truss egress_restrictions; support-enabled) restrict outbound traffic.
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.
Side by side
Capabilities compared
| Baseten | CoreWeave | |
|---|---|---|
| Pricing model | Per 1M tokens (Model APIs); per-minute GPU/CPU instances for dedicated deployments | Per-GPU-hour on-demand and spot; reserved capacity at up to 60% discount |
| Public pricing | Yes | Yes |
| Category | Dedicated GPU | Dedicated GPU |
| Deployment models | Dedicated deploymentSelf-hostedHybrid | Bare metalManaged KubernetesOn-demandSpotReserved capacity |
| Regions | United States, EU/EEA | United States, United Kingdom, EU/EEA |
| Compliance | SOC 2 Type IISOC 3ISO 27001HIPAA BAAGDPR DPA | SOC 2 Type II (stated)GDPR DPA |
| Data residency evidence | Stated | Not verified |
| Parent jurisdiction | United States | United States |
| Sovereign for | Not recorded | Not recorded |
| Analyst note | Dedicated deployments and an enterprise self-hosted option position Baseten for single-tenant use. Trust centre lists ISO 27001:2022, SOC 2 Type 2 and SOC 3. Regional deployments pin replicas to the US or EU, but no contractual data-residency guarantee found; trust centre lists subprocessors across multiple clouds. Egress allow-lists of IP ranges and domains (Truss egress_restrictions; support-enabled) restrict outbound traffic. | 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. |
Where they diverge
Deployment differentiation
Only Baseten
Both
No overlap in deployment models.
Only CoreWeave
Read the full profiles