singletenant.ai

Vendors · Comparison

Amazon Bedrock Provisioned Throughput vs RunPod

RunPod 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). RunPod: Per GPU-hour (per-second display available); reserved clusters via sales (published pricing).
  • Category Amazon Bedrock Provisioned Throughput is a Hyperscaler dedicated offering; RunPod is Dedicated GPU.
  • Compliance Both document SOC 2 Type II, SOC 3, ISO 27001 and GDPR DPA. Only Amazon Bedrock Provisioned Throughput documents HIPAA BAA, C5 and FedRAMP.
  • Data residency Amazon Bedrock Provisioned Throughput 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.

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.

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

Amazon Bedrock Provisioned Throughput RunPod
Pricing model Per Model Unit (MU) per hour; no-commitment, 1-month, or 6-month terms Per GPU-hour (per-second display available); reserved clusters via sales
Public pricing No Yes
Category Hyperscaler dedicated Dedicated GPU
Deployment models Provisioned throughputCustom model (provisioned) Secure CloudCommunity CloudReserved clusters
Regions United States, United Kingdom, EU/EEA, Asia-Pacific United States, EU/EEA, Asia-Pacific
Compliance SOC 2 Type IISOC 3ISO 27001HIPAA BAAC5FedRAMPGDPR 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 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. 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 Amazon Bedrock Provisioned Throughput

Provisioned throughputCustom model (provisioned)

Both

No overlap in deployment models.

Only RunPod

Secure CloudCommunity CloudReserved clusters