Vendors · Comparison
Azure OpenAI Provisioned Throughput (PTU) vs Baseten
Only Azure OpenAI PTU documents C5 and FedRAMP; only Baseten documents SOC 3. 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). Baseten: Per 1M tokens (Model APIs); per-minute GPU/CPU instances for dedicated deployments (published pricing).
- Category Azure OpenAI Provisioned Throughput (PTU) is a Hyperscaler dedicated offering; Baseten is Dedicated GPU.
- Compliance Both document SOC 2 Type II, ISO 27001, HIPAA BAA and GDPR DPA. Only Azure OpenAI Provisioned Throughput (PTU) documents C5 and FedRAMP. Only Baseten documents SOC 3.
- Data residency Azure OpenAI Provisioned Throughput (PTU) commits to data residency in its contract terms; Baseten 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.
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.
Side by side
Capabilities compared
| Azure OpenAI Provisioned Throughput (PTU) | Baseten | |
|---|---|---|
| Pricing model | Per PTU per hour; Azure Reservations discount with 1-month or 1-year terms | Per 1M tokens (Model APIs); per-minute GPU/CPU instances for dedicated deployments |
| Public pricing | Yes | Yes |
| Category | Hyperscaler dedicated | Dedicated GPU |
| Deployment models | Global provisionedData-zone provisionedRegional provisioned | Dedicated deploymentSelf-hostedHybrid |
| Regions | Global, United States, EU/EEA, Asia-Pacific | United States, EU/EEA |
| Compliance | SOC 2 Type IIISO 27001C5FedRAMPHIPAA BAAGDPR DPA | SOC 2 Type IISOC 3ISO 27001HIPAA BAAGDPR 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. | 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. |
Where they diverge
Deployment differentiation
Only Azure OpenAI Provisioned Throughput (PTU)
Both
No overlap in deployment models.
Only Baseten
Read the full profiles