Compute provider terms: comparison matrix

Published reserved/committed-capacity vehicles exist: EC2 Reserved Instances, Savings Plans, Dedicated Host Reservations, On-Demand Capacity Reservations, and Capacity Blocks for ML. Reserved Instances/Savings Plans/Dedicated Host Reservations are noncancellable, nonrefundable, and charged for full term even if Agreement terminated (pro rata refund only if AWS terminates other than for cause). Capacity Blocks for ML cannot be canceled or modified and are fully nonrefundable. On-Demand Capacity Reservations and Capacity Blocks cannot be resold. Enterprise-specific commitment terms negotiated privately, not published.

Public docs describe On Demand Capacity Reservations for VMs and Capacity Blocks (reservation of compute capacity for a specified duration), each with their own SLA. Broader enterprise commitment vehicles (e.g. Enterprise Agreement pricing/commitments) negotiated, not published. Cancellation may incur fee per Product Terms.

Committed Units (non-cancellable committed-use, paid whether used or not, auto-renew, no resell/transfer); Compute Engine future reservations subject to Google approval; enterprise financial commitments in Order Form/addendum negotiated, not published

not specified in public docs; commitment terms negotiated, not published

Public terms reference only Orders and published pricing; no reserved-instance, committed-use, take-or-pay or cancellation terms published. Meaningful commitment terms are negotiated, not published (per-Order).

Not specified in public documents; no reserved instances, committed-use, savings plans, take-or-pay or cancellation terms appear. Pricing incorporated by reference to external URL. Enterprise commitment terms appear negotiated, not published.

Subscriptions auto-renew for same-duration terms; no prorated refund on cancellation (use-it-or-lose-it flavor). No published reserved-instance/committed-use terms; enterprise commitment terms negotiated, not published.

not specified. Terms describe on-demand rental of hosting from independent providers and purchase of credits; no reserved/committed-use terms published.

Default for core services: AWS will not access or use Your Content except to provide the Services or comply with law; will not use Your Content to compete with your products/services. Base position does not train on customer content. However, many named AI/ML services (e.g., CodeGuru, Comprehend, Rekognition, Transcribe, Amazon Q Developer Free Tier, etc.) MAY use AI Content to develop/improve the service and AWS/affiliate ML/AI technologies, with a per-service or AWS Organizations AI-services opt-out. Bedrock/custom models: AWS will not access or use your customized model except to provide the service.

Does not train on customer data by default: Microsoft Generative AI Services will not use Customer Data to train any generative AI foundation model except per Customer's documented instructions. Output Content is Customer Data; Microsoft does not own it.

Does not train on customer data: 'Google will not use Customer Data to train or fine-tune any AI/ML models without Customer's prior permission or instruction'; Customer Data processed only per Cloud Data Processing Addendum

not specified; no language on using/training on customer data (governed by referenced Privacy Policy/TOS not provided)

No explicit AI/ML training statement. Provider may process Customer Property to provide Services and may use aggregated/anonymized 'Usage Information' to improve Services; no opt-out stated. Default: may use anonymized/aggregated data to improve services.

Does not use customer data for other purposes. Crusoe accesses/uses Customer Data only to provide the Services and TSS or as instructed, and will not use it for any other Crusoe products, services, or advertising. No AI/ML training language; no opt-in/opt-out stated.

May access/use Your Content to provide Service, and use it in aggregated and anonymized form to update and improve Service and Runpod's products. No explicit AI/ML model-training statement; no opt-out stated.

not specified re AI training. Governed by Privacy Policy/DPA; Feedback is assigned to Company for any use. Data-use rights not detailed in these terms.

AWS may suspend immediately upon notice if it reasonably determines: (a) use poses security risk / could adversely impact systems or other customers / could subject AWS or third parties to liability / could be fraudulent; (b) material breach of Agreement; (c) breach of payment obligations; or (d) customer insolvency/bankruptcy. Notice required ('immediately upon notice to you'), but not advance/prior notice.

Grounds: material breach (non-payment), AUP/Code of Conduct violation, security risk, trade-law risk. 30 days' notice before suspension normally, but immediate suspension if payment declined or to prevent unauthorized access / protect systems. AUP violations suspended only to extent reasonably necessary with reasonable notice unless immediate needed.

AUP violation: notice + 24 hours to cure before suspension. Immediate suspension for security/infrastructure protection, suspected unauthorized access, legal compliance, or breach of Restrictions/Service Specific Terms. Also for late payment.

May suspend or terminate use of Services for AUP violation, even if unintentional/unauthorized; at sole discretion, no notice requirement stated. Payment issues may suspend/cancel Transaction.

Grounds: breach of Agreement/AUP, non-payment, excessive utilization affecting availability, suspected unauthorized access, legal/court/regulatory requirement. Suspension may be immediate ('immediately suspend, throttle or terminate').

AUP violations: notice + 24-hour cure before suspension. Other grounds (adverse impact on Services/network, suspected unauthorized access, legal compliance, breach of Restrictions/Service Specific Terms): immediate suspension. Non-payment: may suspend if overdue. Notice of basis given at Customer's request as soon as reasonably possible.

May suspend/terminate immediately and without notice for material breach, undue system stress, or legal requirement; non-payment may lead to suspension. Grounds: AUP breach, non-payment, legal process, security/harm.

Grounds: non-payment/chargebacks, false info, export-law violation, AUP/breach, or any/no reason; may be immediate and without notice.

Termination for convenience: customer any time by closing account; AWS any time on at least 30 days' advance notice. For cause: either party on 30-day uncured material breach; AWS may terminate immediately in defined situations. Post-termination data retrieval: during the 30 days following the Termination Date AWS will not remove Your Content and allows retrieval if all amounts paid (does not apply if AWS terminated under 5.2(b)).

Termination for convenience: either party on 60 days' notice. Post-termination data retrieval: for non-renewed Online Services, access continues 30 days after expiration; disabled account gives Customer 90 days to extract Customer Data.

Customer may terminate for convenience anytime on prior written notice (subject to commitments); Google may terminate GCP for convenience on 30 days' notice. On termination all access to Customer Data terminates unless otherwise stated; no specified general post-termination retrieval window (EU Data Act adds 30-day Data Recovery Period).

No termination-for-convenience or post-termination data retrieval window specified. Right to use CoreWeave Sites ceases immediately on breach.

Termination for convenience: either party may terminate when no Orders in effect; for-cause with 30-day cure. Post-termination data retrieval: no window guaranteed - Lambda may delete Customer Property upon termination without liability.

Termination for convenience: Customer any time on prior written notice; Crusoe any time with 30 days' prior written notice. On termination all rights and access to Services terminate including access to Customer Data; no defined post-termination data-retrieval window (data export must occur during the Term).

Runpod may terminate for convenience at any time upon notice; customer may terminate by notice and closing Account. No post-termination data-retrieval window specified; Runpod may delete account/content at any time.

Either side may terminate at any time for any reason; Company may terminate without notice and delete content. No post-termination data retrieval window; Company has no obligation to retain data.

AWS may modify the Agreement at any time by posting a revised version or notifying by email; modified terms effective upon posting (or as stated in email). Continued use = acceptance. Specific commitments: at least 90 days' advance notice for adverse SLA changes; at least 12 months' notice before discontinuing material functionality; 30 days' notice for fee increases on existing services.

Microsoft may update the Agreement. General Terms/other terms: at least 60 days' notice, effective on renewal. SLA: at least 90 days' notice for adverse material changes. Product Terms: Material Adverse Changes apply at renewal; other changes effective on posting. No changes during initial subscription term for SLA.

Google may update the Agreement; material updates to GCP terms effective 30 days after posting; updates for new functionality or legal compliance effective immediately. Continued use = consent.

Provider may update terms in sole discretion; changes effective immediately on posting, no advance notice

Lambda may update Agreement unilaterally; updated version binding at start of next billing cycle. (Website Terms: changes effective 10 days after posting.)

Crusoe may change the Agreement/URL Terms and pricing. Material changes effective 30 days after posting; changes for new functionality, DPST, or legally required are effective immediately. At least 90 days' advance notice for materially adverse SLA changes. Continued use = consent.

May modify Terms at sole discretion; notice given only by updating 'Last Updated' date; changes effective on posting via continued use. No fixed advance-notice period (pricing changes get 'reasonable advance notification').

Company may modify at any time; changes effective on posting; user waives right to specific notice; continued use = acceptance.

Governing law and forum vary by AWS Contracting Party. For Amazon Web Services, Inc. (US): Washington State law, King County, WA courts. Disputes are subject to binding arbitration (AAA commercial rules) and a class-action waiver (individual basis only).

Governing law: State of Washington and US federal law. Venue: if Customer sues (non-Europe Affiliate) King County, WA; if Microsoft sues, Customer's HQ; Europe = Ireland. Binding arbitration: no (court venues specified). Class-action waiver: not specified.

Governing law: California (excl. conflict rules); venue: state/federal courts of Santa Clara County, CA; binding arbitration: no; class-action waiver: not specified

Governing law: New York; venue: courts in New York, NY; arbitration: optional at Company's discretion (AAA, NY law); class-action waiver: yes

Governing law: California. Forum if not arbitrated: N.D. Cal. or Santa Clara County state court. Binding arbitration: yes (AAA, FAA; 30-day opt-out). Class-action waiver: yes.

Governing law: New York law (excluding conflict rules). Forum: exclusive federal/state courts of Denver County, Colorado. Arbitration: no (litigation). Class-action waiver: not specified.

Governing law: Delaware. Venue: NJ courts (Burlington County for severed/void-arbitration matters). Binding arbitration: yes (NAM, opt-out within 30 days). Class-action waiver: yes.

Governing law: California. Forum: JAMS arbitration, Los Angeles, CA. Binding arbitration: yes. Class-action waiver: yes.

EC2 dual commitment: Region-Level SLA (instances across 2+ AZs/regions) = 99.99% Monthly Uptime Percentage; Instance-Level SLA (single instance) = 99.5% Monthly Uptime Percentage. Basis: both instance-level and region-level. 'Unavailable' = no external connectivity.

instance-level and cluster/throughput-based (varies by service); VM in Availability Zones 99.99%, Availability Set/Dedicated Host Group 99.95%, Single-Instance VM 99.9% (Premium SSD); AKS API server 99.95% (AZ) / 99.9% (non-AZ); Capacity Blocks capacity-availability based

instance-level and region-level: Monthly Uptime Percentage. Instances in Multiple Zones >=99.99% (Premium); Single Instance Memory Optimized >=99.95%; other Single Instance >=99.9%; Load balancing >=99.99%; Standard Tier >=99.9%

no SLA / uptime not committed; site provided 'as is, as available'

no SLA / uptime not committed; Services provided 'AS-IS', no warranty of uninterrupted service

instance-level (per single GPU-enabled VM) and per-volume/per-resource. Commitments: 99.5% GPU VM, 99.5% Persistent Disks, 99.5% Shared Disks, 99.9% Container Registry, 99.9% Managed Kubernetes control plane. Measured as Monthly Uptime Percentage.

no SLA / uptime not committed. For Community Cloud, expressly no uptime warranty; Service provided 'as-is and as-available'.

no SLA / uptime not committed. Terms state Company cannot guarantee availability and disclaims liability for downtime.

Region-Level: <99.99% but >=99.0% = 10%; <99.0% but >=95.0% = 30%; <95.0% = 100%. Instance-Level: <99.5% but >=99.0% = 10%; <99.0% but >=95.0% = 30%; <95.0% = 100%. Max credit = 100% of monthly bill for affected service/region. Credits are sole and exclusive remedy; applied against future payments; issued only if >$1.

Tiered by service; e.g. VM Availability Zones: <99.99%=10%, <99%=25%, <95%=100%. Standard tier VMs <99.9%=10%, <99%=25%, <95%=100%. Max credit 100% of monthly fees for affected resource. Service Credits are sole and exclusive remedy.

Multi-zone/LB tiers: 99.00-<99.99% =10%, 95-<99% =25%, <95% =100%. Single Instance: 95-<threshold =10%, 90-<95% =25%, <90% =100%. Max credit = amount due for affected Covered Service. Stated sole and exclusive remedy.

not specified; no service-credit structure in provided documents

No service-level uptime credit regime. Only discretionary credits (coupons, promos, prepaid, fee adjustments) expiring 12 months from issuance; no tiers, no sole-remedy language for uptime.

Tiered credit of monthly bill for the affected Covered Service. GPU VM/Persistent/Shared Disks: 95-99.5%=10%, 90-95%=25%, <90%=100%. Container Registry/Kubernetes: 99-99.9%=10%, 95-99%=25%, <95%=100%. Max credit capped at amount due for affected Covered Service that month. Stated as sole and exclusive remedy.

not specified; no service-credit structure in the document. Liability capped at lesser of 6-month fees paid or $100.

not specified; no service-credit structure. Payments are final and no refunds; refunds on unspent credits at sole discretion.

Customer must file a claim by opening a case in AWS Support Center. Window: request must be received by end of the second billing cycle after the incident occurred. Cannot combine Region- and Instance-Level claims. Evidence: specific subject line, dates/times/affected region (and AZ for instance), resource IDs, and request logs documenting/corroborating the outage. Failure to provide info disqualifies the claim.

Customer must submit a claim to Microsoft customer support with detailed description, time/duration of downtime, affected resource names, number/location of affected users, and error description. For Azure, claim must be received within 60 days of the Incident.

Customer must request credit: notify Google technical support within 60 days of becoming eligible, and provide log files showing Downtime Periods with date and time; failure forfeits credit.

not specified; no SLA credit claim process in provided documents

not specified (no SLA credit claim process; credits are discretionary and not claim-based)

Customer must request. Must notify Crusoe within 30 days from becoming eligible, and provide log files or monitoring data showing loss of connectivity with date and time of errors. Failure to comply forfeits the credit.

not specified; no SLA credit claim process. Billing disputes directed to help@runpod.io.

not specified. No SLA claim process; note a 1-year limitation period applies to any claim/cause of action.

Present: force majeure / factors outside reasonable control; external network/ISP issues (beyond demarcation point); customer fault/misuse (actions or inactions, failure to respond); customer equipment/software/technology; unavailability arising from suspension/termination. Also (Service Terms): beta/preview services and Beta Regions excluded; Services running locally on AWS Outposts excluded.

Present: force majeure/outside reasonable control; external network/ISP/third-party; single-datacenter non-geo-resilient; customer fault/misuse; beta/preview/trial; throttling/abuse; exceeding quotas; scheduled/maintenance windows; customer-initiated operations (restart, scale). Performance degradation without unavailability excluded.

Present: pre-GA/beta features, features excluded in Documentation, factors outside Google's reasonable control (force majeure-type), customer/third-party hardware/software, AUP/Agreement violations (misuse), system quotas. Cloud VPN downtime excluded.

not specified; no SLA present, though disclaimer notes failures beyond control (acts of God, comms line failure)

No SLA exists. Related risk-shifting present: force majeure; customer fault/misuse; scheduled/emergency maintenance ('planned downtime for upgrades and maintenance'); beta/preview services; external network/ISP issues; throttling.

Present: force majeure (factors outside Crusoe's reasonable control); customer fault/third-party hardware/software; scheduled or emergency maintenance; beta/preview (pre-general availability features); AUP/agreement violations; quotas/throttling (quotas applied by system). Not addressed: single-AZ, external ISP.

No formal SLA. Related disclaimers present: force majeure ('cause beyond our reasonable control'); customer fault/misuse; interruption/cessation of transmission; Community/beta-type offerings disclaimed.

No SLA exists. Related disclaimers present: force majeure (cause beyond reasonable control) and maintenance/interruptions; no service-level exclusions listed.