SaaS Ranking
Menu

Zesty

zesty.co · Container and cloud workload security · checked 2026-09-16

48/100DBand D

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

We measured 12 of 12 criteria for Zesty on 2026-09-16. We found 6 with a source and did not find 6 at the addresses we checked. That is a transparency score of 48 out of 100, band D.

Overview

0 days since the newest finding, 0 since the oldest. 12 of 12 criteria measured in the last 30 days.

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

Zesty

zesty.co · Container and cloud workload security

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

Published commitments4 of 9 found

Measured behaviour2 of 3 found

Checked 2026-09-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.

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

Where Zesty sits in Container and cloud workload security

  1. A0 0%
  2. B0 0%
  3. C1 4%
  4. D4 15%
  5. E6 23%
  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 Zesty 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 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-16.

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

Is this wrong? Send us the URL

✗

Data location stated

weight 3 of 3

No statement about data location found.

Checked 7 addresses on 2026-09-16.

Show the 7 addresses we checked
  1. https://zesty.co/security – reached, no match (HTTP 200)
  2. https://zesty.co/trust – reached, no match (HTTP 404)
  3. https://zesty.co/legal/privacy – reached, no match (HTTP 200)
  4. https://zesty.co/privacy – reached, no match (HTTP 200)
  5. https://zesty.co/privacy-policy – reached, no match (HTTP 200)
  6. https://zesty.co/compliance – reached, no match (HTTP 404)
  7. https://zesty.co/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-16.

Show the 3 addresses we checked
  1. https://status.zesty.co/ – reached, no match (HTTP 200)
  2. https://zesty.co/status – reached, no match (HTTP 404)
  3. https://zesty.co.statuspage.io/ – Could not be fetched: fetch failed.

Is this wrong? Send us the URL

✗

Public pricing

weight 2 of 3

No public pricing with figures found.

Checked 5 addresses on 2026-09-16.

Show the 5 addresses we checked
  1. https://zesty.co/pricing – reached and rendered, no match
  2. https://zesty.co/pricing/ – reached, no match (HTTP 200)
  3. https://zesty.co/plans – reached, no match (HTTP 404)
  4. https://zesty.co/en/pricing – reached, no match (HTTP 200)
  5. https://zesty.co/pricing-plans – reached, no match (HTTP 404)

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-16.

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

Is this wrong? Send us the URL

✗

security.txt (RFC 9116)

weight 1 of 3

No security.txt found.

Checked 1 address on 2026-09-16.

Show the 1 address we checked
  1. https://zesty.co/.well-known/security.txt – 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 6
✓

Data processing agreement

weight 3 of 3

Published and readable without a login.

Source: https://zesty.co/data-processing-agreement/ · checked 2026-09-16

✓

HTTPS enforced with HSTS

weight 2 of 3

HTTP redirects to HTTPS and the HSTS header is set.

  • HSTS max-age 63072000 seconds (730 days).
    Show the exact wording

    max-age=63072000; includeSubDomains; preload

    Read at https://zesty.co/
  • HSTS options includeSubDomains, preload.
    Show the 2 exact wordings

    max-age=63072000; includeSubDomains; preload

    Read at https://zesty.co/

    max-age=63072000; includeSubDomains; preload

    Read at https://zesty.co/

Source: https://zesty.co/ · checked 2026-09-16

✓

No third-party tracking before consent

weight 2 of 3

No third-party requests before any interaction.

Source: https://zesty.co/ · checked 2026-09-16

✓

Notice before subprocessors change

weight 2 of 3

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

Source: https://zesty.co/data-processing-agreement/ · checked 2026-09-16

✓

Certifications named

weight 1 of 3

SOC 2 or ISO 27001 named on a public page.

  • Named on that page SOC 2, SOC 2 Type II.
    Show the 2 exact wordings

    egulations, Zesty maintains extensive compliance standards, including Service Organization Control (SOC2) compliance, ensuring high level of data security and privacy protection.

    Read at https://zesty.co/security-overview/

    SOC2 standards and certification Zesty maintains SOC2 type 2 certification, further ensuring the Zesty’s

    Read at https://zesty.co/security-overview/

Source: https://zesty.co/security-overview/ · checked 2026-09-16

✓

Named privacy contact

weight 1 of 3

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

Source: https://zesty.co/privacy-policy/ · checked 2026-09-16

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.