Vendors · Comparison
CoreWeave vs Together AI
Only CoreWeave documents GDPR DPA; only Together AI documents HIPAA BAA and ISO 27001. Pricing, compliance and residency compared, with sources.
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). Together AI: Per 1M tokens serverless; per GPU-hour for dedicated endpoints and clusters (published pricing).
- Category Both are Dedicated GPU offerings.
- Compliance Both document SOC 2 Type II. Only CoreWeave documents GDPR DPA. Only Together AI documents HIPAA BAA and ISO 27001.
- Data residency CoreWeave's data residency is not verified; Together AI 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.
Together AI
Dedicated endpoints are explicitly single-tenant GPU instances with public per-hour pricing. The dedicated endpoints page says customers choose the deployment region for data residency; the terms make no geographic commitment, so residency is Stated. ISO 27001:2022 certified by A-LIGN, an ANAB-accredited body. Reserved dedicated capacity is also sold in throughput units (PTUs).
Side by side
Capabilities compared
| CoreWeave | Together AI | |
|---|---|---|
| Pricing model | Per-GPU-hour on-demand and spot; reserved capacity at up to 60% discount | Per 1M tokens serverless; per GPU-hour for dedicated endpoints and clusters |
| Public pricing | Yes | Yes |
| Category | Dedicated GPU | Dedicated GPU |
| Deployment models | Bare metalManaged KubernetesOn-demandSpotReserved capacity | ServerlessDedicated endpointGPU clusters |
| Regions | United States, United Kingdom, EU/EEA | Not verified |
| Compliance | SOC 2 Type II (stated)GDPR DPA | SOC 2 Type II (stated)HIPAA BAA (stated)ISO 27001 |
| 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. | Dedicated endpoints are explicitly single-tenant GPU instances with public per-hour pricing. The dedicated endpoints page says customers choose the deployment region for data residency; the terms make no geographic commitment, so residency is Stated. ISO 27001:2022 certified by A-LIGN, an ANAB-accredited body. Reserved dedicated capacity is also sold in throughput units (PTUs). |
Where they diverge
Deployment differentiation
Only CoreWeave
Both
No overlap in deployment models.
Only Together AI
Read the full profiles