Vendors · Comparison
Azure OpenAI Provisioned Throughput (PTU) vs RunPod
Only Azure OpenAI PTU documents C5, FedRAMP and HIPAA BAA; only RunPod documents SOC 3. Pricing, compliance and residency compared, with sources.
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). RunPod: Per GPU-hour (per-second display available); reserved clusters via sales (published pricing).
- Category Azure OpenAI Provisioned Throughput (PTU) is a Hyperscaler dedicated offering; RunPod is Dedicated GPU.
- Compliance Both document SOC 2 Type II, ISO 27001 and GDPR DPA. Only Azure OpenAI Provisioned Throughput (PTU) documents C5, FedRAMP and HIPAA BAA. Only RunPod documents SOC 3.
- Data residency Azure OpenAI Provisioned Throughput (PTU) commits to data residency in its contract terms; 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.
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.
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
| Azure OpenAI Provisioned Throughput (PTU) | RunPod | |
|---|---|---|
| Pricing model | Per PTU per hour; Azure Reservations discount with 1-month or 1-year terms | Per GPU-hour (per-second display available); reserved clusters via sales |
| Public pricing | Yes | Yes |
| Category | Hyperscaler dedicated | Dedicated GPU |
| Deployment models | Global provisionedData-zone provisionedRegional provisioned | Secure CloudCommunity CloudReserved clusters |
| Regions | Global, United States, EU/EEA, Asia-Pacific | United States, EU/EEA, Asia-Pacific |
| Compliance | SOC 2 Type IIISO 27001C5FedRAMPHIPAA BAAGDPR DPA | SOC 2 Type IISOC 3ISO 27001GDPR DPA |
| Data residency evidence | Contractual | Stated |
| 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. | 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 Azure OpenAI Provisioned Throughput (PTU)
Both
No overlap in deployment models.
Only RunPod
Read the full profiles