SaaS Ranking
Menu

Garden

garden.io · Developer collaboration and CI · checked 2026-09-04

9/100FBand F

Rank 28 of 30 in Developer collaboration and CI, where the median is 24.

We measured 12 of 12 criteria for Garden on 2026-09-04. We found 1 with a source and did not find 11 at the addresses we checked. That is a transparency score of 9 out of 100, band F.

Overview

Transparency labelsaas-ranking.com

Garden

garden.io · Developer collaboration and CI

  1. A
  2. B
  3. C
  4. D
  5. E
  6. F
F 9of 100 Rank 28 of 30

Published commitments0 of 9 found

Measured behaviour1 of 3 found

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

We do not issue badges: a badge is the first step towards a paid placement, and there is none here. The SVG is a document with the date in it, for your own files.

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 Garden 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

✗

Data processing agreement

weight 3 of 3

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

Seen at https://docs.garden.io/ · checked 2026-09-04

Show the 8 addresses we checked
  1. https://garden.io/legal/dpa – found, but behind a sign-in
  2. https://garden.io/dpa – found, but behind a sign-in
  3. https://garden.io/legal/data-processing-agreement – found, but behind a sign-in
  4. https://garden.io/data-processing-agreement – found, but behind a sign-in
  5. https://garden.io/legal/data-processing-addendum – found, but behind a sign-in
  6. https://garden.io/legal/gdpr – found, but behind a sign-in
  7. https://garden.io/trust/dpa – found, but behind a sign-in
  8. https://garden.io/privacy/dpa – found, but behind a sign-in

Is this wrong? Send us the URL

✗

Subprocessor list

weight 3 of 3

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

Seen at https://docs.garden.io/ · checked 2026-09-04

Show the 7 addresses we checked
  1. https://garden.io/legal/subprocessors – found, but behind a sign-in
  2. https://garden.io/subprocessors – found, but behind a sign-in
  3. https://garden.io/sub-processors – found, but behind a sign-in
  4. https://garden.io/legal/sub-processors – found, but behind a sign-in
  5. https://garden.io/trust/subprocessors – found, but behind a sign-in
  6. https://garden.io/privacy/subprocessors – found, but behind a sign-in
  7. https://garden.io/legal/subprocessor-list – found, but behind a sign-in

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://docs.garden.io/ · checked 2026-09-04

Show the 7 addresses we checked
  1. https://garden.io/security – found, but behind a sign-in
  2. https://garden.io/trust – found, but behind a sign-in
  3. https://garden.io/legal/privacy – found, but behind a sign-in
  4. https://garden.io/privacy – found, but behind a sign-in
  5. https://garden.io/privacy-policy – found, but behind a sign-in
  6. https://garden.io/compliance – found, but behind a sign-in
  7. https://garden.io/legal/privacy-policy – found, but behind a sign-in

Is this wrong? Send us the URL

✗

Status page with history

weight 2 of 3

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

Seen at https://docs.garden.io/ · checked 2026-09-04

Show the 3 addresses we checked
  1. https://status.garden.io/ – The name "status.garden.io" could not be resolved.
  2. https://garden.io/status – found, but behind a sign-in
  3. https://garden.io.statuspage.io/ – Could not be fetched: fetch failed.

Is this wrong? Send us the URL

✗

Public pricing

weight 2 of 3

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

Seen at https://docs.garden.io/ · checked 2026-09-04

Show the 5 addresses we checked
  1. https://garden.io/pricing – found, but behind a sign-in
  2. https://garden.io/pricing/ – found, but behind a sign-in
  3. https://garden.io/plans – found, but behind a sign-in
  4. https://garden.io/en/pricing – found, but behind a sign-in
  5. https://garden.io/pricing-plans – found, but behind a sign-in

Is this wrong? Send us the URL

✗

No third-party tracking before consent

weight 2 of 3

No consent-free first load found.

  • Third-party hosts we saw on the first load 1 gitbook.com.
    Show the exact wording

    app.gitbook.com, static-2v.gitbook.com

    Read at https://garden.io/

Checked 1 address on 2026-09-04.

Show the 1 address we checked
  1. https://garden.io/ – third-party requests before any interaction: app.gitbook.com, static-2v.gitbook.com

Is this wrong? Send us the URL

✗

Notice before subprocessors change

weight 2 of 3

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

Seen at https://docs.garden.io/ · checked 2026-09-04

Show the 8 addresses we checked
  1. https://garden.io/legal/subprocessors – found, but behind a sign-in
  2. https://garden.io/subprocessors – found, but behind a sign-in
  3. https://garden.io/sub-processors – found, but behind a sign-in
  4. https://garden.io/legal/dpa – found, but behind a sign-in
  5. https://garden.io/dpa – found, but behind a sign-in
  6. https://garden.io/legal/data-processing-agreement – found, but behind a sign-in
  7. https://garden.io/trust/subprocessors – found, but behind a sign-in
  8. https://garden.io/legal/sub-processors – found, but behind a sign-in

Is this wrong? Send us the URL

✗

Certifications named

weight 1 of 3

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

Seen at https://docs.garden.io/ · checked 2026-09-04

Show the 6 addresses we checked
  1. https://garden.io/security – found, but behind a sign-in
  2. https://garden.io/trust – found, but behind a sign-in
  3. https://garden.io/trust-center – found, but behind a sign-in
  4. https://garden.io/compliance – found, but behind a sign-in
  5. https://garden.io/legal/security – found, but behind a sign-in
  6. https://trust.garden.io/ – The name "trust.garden.io" could not be resolved.

Is this wrong? Send us the URL

✗

Uptime SLA with a figure

weight 1 of 3

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

Seen at https://docs.garden.io/ · checked 2026-09-04

Show the 6 addresses we checked
  1. https://garden.io/legal/sla – found, but behind a sign-in
  2. https://garden.io/sla – found, but behind a sign-in
  3. https://garden.io/legal/service-level-agreement – found, but behind a sign-in
  4. https://garden.io/trust/sla – found, but behind a sign-in
  5. https://garden.io/uptime – found, but behind a sign-in
  6. https://garden.io/legal/uptime-sla – found, but behind a sign-in

Is this wrong? Send us the URL

✗

security.txt (RFC 9116)

weight 1 of 3

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

Seen at https://docs.garden.io/ · checked 2026-09-04

Show the 1 address we checked
  1. https://garden.io/.well-known/security.txt – found, but behind a sign-in

Is this wrong? Send us the URL

✗

Named privacy contact

weight 1 of 3

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

Seen at https://docs.garden.io/ · checked 2026-09-04

Show the 7 addresses we checked
  1. https://garden.io/legal/privacy – found, but behind a sign-in
  2. https://garden.io/privacy – found, but behind a sign-in
  3. https://garden.io/privacy-policy – found, but behind a sign-in
  4. https://garden.io/legal/privacy-policy – found, but behind a sign-in
  5. https://garden.io/legal/privacy-notice – found, but behind a sign-in
  6. https://garden.io/trust/privacy – found, but behind a sign-in
  7. https://garden.io/datenschutz – found, but behind a sign-in

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 1
✓

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://garden.io/

Source: https://garden.io/ · checked 2026-09-04

History

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

Compare