SaaS Ranking
Menu

RunPod

runpod.io · MLOps and model serving · checked 2026-09-05

52/100DBand D

Rank 3 of 33 in MLOps and model serving, where the median is 26.

We measured 12 of 12 criteria for RunPod on 2026-09-05. We found 7 with a source and did not find 5 at the addresses we checked. That is a transparency score of 52 out of 100, band D.

Overview

Transparency labelsaas-ranking.com

RunPod

runpod.io · MLOps and model serving

  1. A
  2. B
  3. C
  4. D
  5. E
  6. F
D 52of 100 Rank 3 of 33

Published commitments5 of 9 found

Measured behaviour2 of 3 found

Checked 2026-09-05. Every line links the page we found it on. A cross means we found nothing at the addresses we checked, not that the vendor has no such document. A transparency score, not a product rating.

The evidence pack carries every criterion with its source, the addresses we checked, the date and the data snapshot id – the four things a procurement file needs and a screenshot loses. We do not issue badges: a badge is the first step towards a paid placement, and there is none here.

The label is the whole measurement in one object: every criterion with its weight, the band, and the date. Public transparency score, not a product or security rating.

Every line in it links the page we found the result on, or lists the addresses we checked. A cross means we found nothing there, not that RunPod has no such document.

What they state

The exact figures and names we read off the pages linked below, with the sentence they stand in. This is what they publish, not what we verified about their systems.

Gaps, heaviest first

✗

Subprocessor list

weight 3 of 3

No subprocessor list found.

Checked 7 addresses on 2026-09-05.

Show the 7 addresses we checked
  1. https://runpod.io/legal/subprocessors – reached, no match (HTTP 404)
  2. https://runpod.io/subprocessors – reached, no match (HTTP 404)
  3. https://runpod.io/sub-processors – reached, no match (HTTP 404)
  4. https://runpod.io/legal/sub-processors – reached, no match (HTTP 404)
  5. https://runpod.io/trust/subprocessors – reached, no match (HTTP 404)
  6. https://runpod.io/privacy/subprocessors – reached, no match (HTTP 404)
  7. https://runpod.io/legal/subprocessor-list – reached, no match (HTTP 404)

Is this wrong? Send us the URL

✗

Data location stated

weight 3 of 3

We found this behind a sign-in, so it is not published openly.

Seen at https://www.runpod.io/legal/compliance · checked 2026-09-05

Show the 7 addresses we checked
  1. https://runpod.io/security – reached, no match (HTTP 404)
  2. https://runpod.io/trust – reached, no match (HTTP 404)
  3. https://runpod.io/legal/privacy – reached, no match (HTTP 404)
  4. https://runpod.io/privacy – reached, no match (HTTP 200)
  5. https://runpod.io/privacy-policy – reached, no match (HTTP 200)
  6. https://runpod.io/compliance – found, but behind a sign-in
  7. https://runpod.io/legal/privacy-policy – reached, no match (HTTP 200)

Is this wrong? Send us the URL

✗

Status page with history

weight 2 of 3

No public status page found.

Checked 3 addresses on 2026-09-05.

Show the 3 addresses we checked
  1. https://status.runpod.io/ – The name "status.runpod.io" could not be resolved.
  2. https://runpod.io/status – reached, no match (HTTP 200)
  3. https://runpod.io.statuspage.io/ – Could not be fetched: fetch failed.

Is this wrong? Send us the URL

✗

No third-party tracking before consent

weight 2 of 3

No consent-free first load found.

Checked 1 address on 2026-09-05.

Show the 1 address we checked
  1. https://runpod.io/ – third-party requests before any interaction: cdn.jsdelivr.net, cdn.prod.website-files.com, d3e54v103j8qbb.cloudfront.net, geo.cookie-script.com, www.googletagmanager.com

Is this wrong? Send us the URL

✗

Uptime SLA with a figure

weight 1 of 3

No uptime figure found.

Checked 6 addresses on 2026-09-05.

Show the 6 addresses we checked
  1. https://runpod.io/legal/sla – reached, no match (HTTP 404)
  2. https://runpod.io/sla – reached, no match (HTTP 404)
  3. https://runpod.io/legal/service-level-agreement – reached, no match (HTTP 404)
  4. https://runpod.io/trust/sla – reached, no match (HTTP 404)
  5. https://runpod.io/uptime – reached, no match (HTTP 404)
  6. https://runpod.io/legal/uptime-sla – reached, no match (HTTP 404)

Is this wrong? Send us the URL

Evidence

The full source lists sit behind these two groups, so that the answer above stays readable.

Published, with a source 7
✓

Data processing agreement

weight 3 of 3

Published and readable without a login.

Source: https://www.runpod.io/legal/data-processing-agreement · checked 2026-09-05

✓

Public pricing

weight 2 of 3

Actual numbers on a public page.

Source: https://www.runpod.io/pricing · checked 2026-09-05

✓

HTTPS enforced with HSTS

weight 2 of 3

HTTP redirects to HTTPS and the HSTS header is set.

  • HSTS max-age 31536000 seconds (365 days).
    Show the exact wording

    max-age=31536000

    Read at https://runpod.io/

Source: https://runpod.io/ · checked 2026-09-05

✓

Notice before subprocessors change

weight 2 of 3

The vendor commits publicly to giving notice before the list changes.

Source: https://www.runpod.io/legal/data-processing-agreement · checked 2026-09-05

✓

Certifications named

weight 1 of 3

SOC 2 or ISO 27001 named on a public page.

Source: https://www.runpod.io/legal/compliance · checked 2026-09-05

✓

security.txt (RFC 9116)

weight 1 of 3

Served at /.well-known/security.txt.

Source: https://runpod.io/.well-known/security.txt · checked 2026-09-05

✓

Named privacy contact

weight 1 of 3

A data protection officer or a dedicated privacy address is named.

Source: https://www.runpod.io/legal/privacy-policy · checked 2026-09-05

History

Not enough completed runs yet to draw a line. The next runs fill this in.

Compare

A shortlist holds up to six vendors across categories and lives entirely in the address of its page: share the link, bookmark it, put it in a ticket. Nothing is stored, so we do not know it exists.