Vendors · Comparison
Azure OpenAI Provisioned Throughput (PTU) vs CoreWeave
Only Azure OpenAI PTU documents ISO 27001, C5 and FedRAMP. 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 Azure OpenAI Provisioned Throughput (PTU): Per PTU per hour; Azure Reservations discount with 1-month or 1-year terms (published pricing). CoreWeave: Per-GPU-hour on-demand and spot; reserved capacity at up to 60% discount (published pricing).
- Category Azure OpenAI Provisioned Throughput (PTU) is a Hyperscaler dedicated offering; CoreWeave is Dedicated GPU.
- Compliance Both document SOC 2 Type II and GDPR DPA. Only Azure OpenAI Provisioned Throughput (PTU) documents ISO 27001, C5, FedRAMP and HIPAA BAA.
- Data residency Azure OpenAI Provisioned Throughput (PTU) commits to data residency in its contract terms; 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.
Azure OpenAI Provisioned Throughput (PTU)
Provisioned throughput is now a Microsoft Foundry (formerly Azure AI Foundry) deployment type billed hourly per PTU, with 1-month or 1-year Azure Reservations. Global, Data Zone (US, EU or APAC), and Regional options set where prompts are processed; stored data stays in the customer-designated geography. FedRAMP scope names Azure OpenAI; SOC 2, ISO 27001, and C5 attest the Azure platform.
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
| Azure OpenAI Provisioned Throughput (PTU) | CoreWeave | |
|---|---|---|
| Pricing model | Per PTU per hour; Azure Reservations discount with 1-month or 1-year terms | Per-GPU-hour on-demand and spot; reserved capacity at up to 60% discount |
| Public pricing | Yes | Yes |
| Category | Hyperscaler dedicated | Dedicated GPU |
| Deployment models | Global provisionedData-zone provisionedRegional provisioned | Bare metalManaged KubernetesOn-demandSpotReserved capacity |
| Regions | Global, United States, EU/EEA, Asia-Pacific | United States, United Kingdom, EU/EEA |
| Compliance | SOC 2 Type IIISO 27001C5FedRAMPHIPAA BAAGDPR DPA | SOC 2 Type II (stated)GDPR DPA |
| Data residency evidence | Contractual | Not verified |
| Parent jurisdiction | United States | United States |
| Sovereign for | Not recorded | Not recorded |
| Analyst note | Provisioned throughput is now a Microsoft Foundry (formerly Azure AI Foundry) deployment type billed hourly per PTU, with 1-month or 1-year Azure Reservations. Global, Data Zone (US, EU or APAC), and Regional options set where prompts are processed; stored data stays in the customer-designated geography. FedRAMP scope names Azure OpenAI; SOC 2, ISO 27001, and C5 attest the Azure platform. | 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 Azure OpenAI Provisioned Throughput (PTU)
Both
No overlap in deployment models.
Only CoreWeave
Read the full profiles