Vendors · Comparison
Amazon Bedrock Provisioned Throughput vs CoreWeave
CoreWeave 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). CoreWeave: Per-GPU-hour on-demand and spot; reserved capacity at up to 60% discount (published pricing).
- Category Amazon Bedrock Provisioned Throughput is a Hyperscaler dedicated offering; CoreWeave is Dedicated GPU.
- Compliance Both document SOC 2 Type II and GDPR DPA. Only Amazon Bedrock Provisioned Throughput documents SOC 3, ISO 27001, HIPAA BAA, C5 and FedRAMP.
- Data residency Amazon Bedrock Provisioned Throughput 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.
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.
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
| Amazon Bedrock Provisioned Throughput | CoreWeave | |
|---|---|---|
| Pricing model | Per Model Unit (MU) per hour; no-commitment, 1-month, or 6-month terms | Per-GPU-hour on-demand and spot; reserved capacity at up to 60% discount |
| Public pricing | No | Yes |
| Category | Hyperscaler dedicated | Dedicated GPU |
| Deployment models | Provisioned throughputCustom model (provisioned) | Bare metalManaged KubernetesOn-demandSpotReserved capacity |
| Regions | United States, United Kingdom, EU/EEA, Asia-Pacific | United States, United Kingdom, EU/EEA |
| Compliance | SOC 2 Type IISOC 3ISO 27001HIPAA BAAC5FedRAMPGDPR 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 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. | 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 Amazon Bedrock Provisioned Throughput
Both
No overlap in deployment models.
Only CoreWeave
Read the full profiles