Vendors · Comparison
Amazon Bedrock Provisioned Throughput vs Baseten
Baseten publishes its prices; Bedrock Provisioned Throughput has no full public price list. Pricing, compliance and residency compared, with sources.
Last verified (older of the two profiles) How we verify
From the data
Key differences
- Pricing Amazon Bedrock Provisioned Throughput: Per Model Unit (MU) per hour; no-commitment, 1-month, or 6-month terms (no published pricing). Baseten: Per 1M tokens (Model APIs); per-minute GPU/CPU instances for dedicated deployments (published pricing).
- Category Amazon Bedrock Provisioned Throughput is a Hyperscaler dedicated offering; Baseten is Dedicated GPU.
- Compliance Both document SOC 2 Type II, SOC 3, ISO 27001, HIPAA BAA and GDPR DPA. Only Amazon Bedrock Provisioned Throughput documents C5 and FedRAMP.
- Data residency Amazon Bedrock Provisioned Throughput 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.
Amazon Bedrock Provisioned Throughput
Provisioned Throughput reserves per-model capacity in Model Units (MUs), billed hourly with no-commitment, 1-month, or 6-month terms; required for serving customised models. AWS states Bedrock content is stored at rest in the Region of use and not shared with model providers. Example per-MU rates are published for some models; most quotes require an AWS account team.
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
| Amazon Bedrock Provisioned Throughput | Baseten | |
|---|---|---|
| Pricing model | Per Model Unit (MU) per hour; no-commitment, 1-month, or 6-month terms | Per 1M tokens (Model APIs); per-minute GPU/CPU instances for dedicated deployments |
| Public pricing | No | Yes |
| Category | Hyperscaler dedicated | Dedicated GPU |
| Deployment models | Provisioned throughputCustom model (provisioned) | Dedicated deploymentSelf-hostedHybrid |
| Regions | United States, United Kingdom, EU/EEA, Asia-Pacific | United States, EU/EEA |
| Compliance | SOC 2 Type IISOC 3ISO 27001HIPAA BAAC5FedRAMPGDPR 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 reserves per-model capacity in Model Units (MUs), billed hourly with no-commitment, 1-month, or 6-month terms; required for serving customised models. AWS states Bedrock content is stored at rest in the Region of use and not shared with model providers. Example per-MU rates are published for some models; most quotes require an AWS account team. | 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 Amazon Bedrock Provisioned Throughput
Both
No overlap in deployment models.
Only Baseten
Read the full profiles