SaaS Ranking
Menu

Upwind: what they publish

upwind.io · Container and cloud workload security · checked 2026-10-16

43/100DBand D

Rank 4 of 26 in Container and cloud workload security, where the median is 22.

Public transparency score, not a product or security rating. Latest check: 2026-10-16. How the score works.

Evidence at a glance

Choose a check to see its source, date and scope.

Not found means not found at the addresses we checked. Not measured means we could not complete the check.

Start a vendor reviewDownload evidence (CSV)

Overview

3 days since the newest dated result, 3 since the oldest. 12 of 12 criteria have a measured result in the last 30 days. Failed checks and undated results are excluded.

Evidence freshness is a statement about our measurement and is kept apart from the transparency score, which is frozen at v1. How good our own measurement is.

Transparency labelsaas-ranking.com

Upwind

upwind.io · Container and cloud workload security

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

Published commitments5 of 9 found

Measured behaviour0 of 3 found

Checked 2026-10-16. 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.

Downloads include all checks, source URLs, dates and the snapshot ID for your procurement file. We do not issue badges.

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 Upwind has no such document.

Where Upwind sits in Container and cloud workload security

  1. A0 0%
  2. B0 0%
  3. C0 0%
  4. D4 15%
  5. E7 27%
  6. F15 58%
26 vendors with a score; 2 more without a score because we could measure too little. Bands have fixed thresholds, see how the score works.

The band of Upwind is marked. Vendors without a score are the ones where we could measure too few criteria to rank them – a gap on our side, counted separately.

What Upwind states

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

✗

Data location: where they say data is hosted

weight 3 of 3

No statement about data location found.

Checked 7 addresses on 2026-10-16.

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

Is this wrong? Send us the URL

Across the market: Data location stated in Container and cloud workload security: 9 of 26 companies

✗

Public pricing with figures

weight 2 of 3

No public pricing with figures found.

Checked 5 addresses on 2026-10-16.

Show the 5 addresses we checked
  1. https://upwind.io/pricing – reached, no match (HTTP 404)
  2. https://upwind.io/pricing/ – reached, no match (HTTP 404)
  3. https://upwind.io/plans – reached, no match (HTTP 404)
  4. https://upwind.io/en/pricing – reached, no match (HTTP 404)
  5. https://upwind.io/pricing-plans – reached, no match (HTTP 404)

Is this wrong? Send us the URL

Across the market: Public pricing in Container and cloud workload security: 6 of 26 companies

✗

HTTPS enforced with HSTS

weight 2 of 3

No enforced HTTPS with HSTS found.

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

    max-age=31536000; includeSubDomains

    Read at https://upwind.io/
  • HSTS options includeSubDomains.
    Show the exact wording

    max-age=31536000; includeSubDomains

    Read at https://upwind.io/

Checked 2 addresses on 2026-10-16.

Show the 2 addresses we checked
  1. http://upwind.io/ – HTTP 301, no redirect to HTTPS
  2. https://upwind.io/ – HSTS max-age=31536000

Is this wrong? Send us the URL

Across the market: HTTPS enforced with HSTS in Container and cloud workload security: 22 of 28 companies

✗weight 2 of 3

Third-party requests seen on the first load, before any interaction.

Checked 1 address on 2026-10-16.

Show the 1 address we checked
  1. https://upwind.io/ – third-party requests before any interaction: api-na2.hubapi.com, cdn-cookieyes.com, cdn.jsdelivr.net, fonts.googleapis.com, fonts.gstatic.com, forms-na2.hscollectedforms.net, forms-na2.hsforms.com, ip2c.org, js-na2.hs-analytics.net, js-na2.hs-banner.com, js-na2.hs-scripts.com, js-na2.hsadspixel.net, js-na2.hscollectedforms.net, log.cookieyes.com, p.typekit.net, pagead2.googlesyndication.com, px.ads.linkedin.com, region1.google-analytics.com, snap.licdn.com, use.typekit.net, www.clickcease.com, www.googletagmanager.com

Is this wrong? Send us the URL

Across the market: No third-party tracking before consent in Container and cloud workload security: 2 of 28 companies

✗

Notice before subprocessors change

weight 2 of 3

No commitment to give notice before subprocessors change found.

Checked 8 addresses on 2026-10-16.

Show the 8 addresses we checked
  1. https://upwind.io/legal/subprocessors – reached, no match (HTTP 404)
  2. https://upwind.io/subprocessors – reached, no match (HTTP 404)
  3. https://upwind.io/sub-processors – reached, no match (HTTP 200)
  4. https://upwind.io/legal/dpa – reached, no match (HTTP 404)
  5. https://upwind.io/dpa – reached, no match (HTTP 200)
  6. https://upwind.io/legal/data-processing-agreement – reached, no match (HTTP 404)
  7. https://upwind.io/trust/subprocessors – reached, no match (HTTP 404)
  8. https://upwind.io/legal/sub-processors – reached, no match (HTTP 404)

Is this wrong? Send us the URL

Across the market: Notice before subprocessors change in Container and cloud workload security: 2 of 26 companies

✗

security.txt (RFC 9116)

weight 1 of 3

No security.txt found.

Checked 1 address on 2026-10-16.

Show the 1 address we checked
  1. https://upwind.io/.well-known/security.txt – reached, no match (HTTP 404)

Is this wrong? Send us the URL

Across the market: security.txt (RFC 9116) in Container and cloud workload security: 2 of 26 companies

✗

Named privacy contact (DPO or privacy address)

weight 1 of 3

No named privacy contact found.

Checked 7 addresses on 2026-10-16.

Show the 7 addresses we checked
  1. https://upwind.io/legal/privacy – reached, no match (HTTP 404)
  2. https://upwind.io/privacy – reached, no match (HTTP 404)
  3. https://upwind.io/privacy-policy – reached, no match (HTTP 200)
  4. https://upwind.io/legal/privacy-policy – reached, no match (HTTP 404)
  5. https://upwind.io/legal/privacy-notice – reached, no match (HTTP 404)
  6. https://upwind.io/trust/privacy – reached, no match (HTTP 404)
  7. https://upwind.io/datenschutz – reached, no match (HTTP 404)

Is this wrong? Send us the URL

Across the market: Named privacy contact in Container and cloud workload security: 10 of 26 companies

Evidence

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

Published, with a source 5
✓

Data processing agreement (DPA)

weight 3 of 3

Published and readable without a login.

Source: https://www.upwind.io/data-processing-addendum · checked 2026-10-16

Across the market: Data processing agreement in Container and cloud workload security: 3 of 26 companies

✓

Subprocessors: the published list

weight 3 of 3

The actual list is published, not just a promise to keep one.

Source: https://www.upwind.io/sub-processors · checked 2026-10-16

Across the market: Subprocessor list in Container and cloud workload security: 2 of 26 companies

✓

Status page with incident history

weight 2 of 3

A public status page with incident history.

Source: https://status.upwind.io/ · checked 2026-10-16

Across the market: Status page with history in Container and cloud workload security: 4 of 27 companies

✓

Certifications named (SOC 2, ISO 27001)

weight 1 of 3

SOC 2 or ISO 27001 named on a public page.

  • Named on that page FedRAMP (not counted: the sentence does not carry it), ISO/IEC 27001 (not counted: the sentence does not carry it), SOC 2 Type II (not counted: the sentence does not carry it). The sentence we kept does not carry this finding on its own, so it counts in no list and no figure.
    Show the 3 exact wordings

    2 ISO/IEC 27001:2022 GDPR AWS Advanced Technology Partner AWS Security Software Competency Partner FedRAMP High Upwind is reviewed and trusted by BILL Wix Siemens Waste Management Peloton Agoda ClickU...

    Read at https://trust.upwind.io/

    Compliance SOC 2 Type 2 ISO/IEC 27001:2022 GDPR AWS Advanced Technology Partner AWS Security Software Competency Partner FedRAMP High Upw

    Read at https://trust.upwind.io/

    Compliance SOC 2 Type 2 ISO/IEC 27001:2022 GDPR AWS Advanced Technology Partner AWS Security Software Competency Par

    Read at https://trust.upwind.io/

Source: https://trust.upwind.io/ · checked 2026-10-16

Across the market: Certifications named in Container and cloud workload security: 8 of 27 companies

✓

Uptime SLA with a figure

weight 1 of 3

An availability commitment with a figure.

  • Highest uptime figure on that page 99.9 %.
    Show the exact wording

    Upwind provides ninety-nine point nine percent (99.9%) uptime commitment for the Core Services (as defined below) as well as some priority support featur

    Read at https://www.upwind.io/service-level-agreement

Source: https://www.upwind.io/service-level-agreement · checked 2026-10-16

Across the market: Uptime SLA with a figure in Container and cloud workload security: 2 of 26 companies

History

100 0 2026-10-09: 43 of 1002026-10-16: 43 of 100 2026-10-09 2026-10-16
Score over the last 2 runs we measured Upwind in: 43 (2026-10-09), 43 (2026-10-16).

Prepare your vendor review

A source is a starting point. Check the product, plan, legal entity and date before treating it as evidence for your purchase. These questions do not change the transparency score.

Upwind

5 found · 7 not found · 0 not measured across 12 public checks.

12 of 12 criteria have a measured result from the last 30 days. Oldest dated result: 2026-10-16.

Investigate 7 open evidence questions
  1. Data location stated

    Which locations apply to our primary data, backups and support access? Which region can we select for this plan?

    Inspect this check
  2. Public pricing

    Please confirm the total cost for our seats and usage, including minimum commitments, add-ons, overages and renewal terms.

    Inspect this check
  3. HTTPS enforced with HSTS

    How is HTTPS enforced on the product and sign-in domains we will use? Please distinguish those domains from the public website.

    Inspect this check
  4. No third-party tracking before consent

    Which third-party requests occur before a visitor makes a choice, and for what purpose? Please distinguish the public website from the product.

    Inspect this check
  5. security.txt (RFC 9116)

    Where should we report a vulnerability, and what acknowledgement and follow-up process should we expect?

    Inspect this check
  6. Notice before subprocessors change

    How will you notify us before a subprocessor changes, with how much notice, and what response options apply to our contract?

    Inspect this check
  7. Named privacy contact

    Which privacy contact handles requests for our account, and what escalation path should we use?

    Inspect this check

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.