SaaS Ranking
Menu

Domino

domino.ai · MLOps and model serving · checked 2026-09-03

Not enough data: 8 of 12 criteria measured, so no transparency score

We measured 8 of 12 criteria for Domino on 2026-09-03. We found 4 with a source and did not find 4 at the addresses we checked; 4 we could not measure at all. Below our threshold there is no score and no rank, and that is a statement about our measurement.

Overview

Transparency labelsaas-ranking.com

Domino

domino.ai · MLOps and model serving

  1. A
  2. B
  3. C
  4. D
  5. E
  6. F
Not enough data8 of 12 measured, no score

Published commitments3 of 5 found, 4 not measured

Measured behaviour1 of 3 found

Checked 2026-09-03. 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. We could measure 8 of 12 criteria, which is below our threshold, so there is no rank. That is a statement about our measurement, not about Domino.

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

Gaps, heaviest first

✗

Status page with history

weight 2 of 3

No public status page found.

Checked 3 addresses on 2026-09-03.

Show the 3 addresses we checked
  1. https://status.domino.ai/ – The name "status.domino.ai" could not be resolved.
  2. https://domino.ai/status – reached, no match (HTTP 200)
  3. https://domino.ai.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-03.

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

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

Show the 1 address we checked
  1. https://domino.ai/ – third-party requests before any interaction: alb.reddit.com, cdn-app.pathfactory.com, consent.cookiebot.com, consentcdn.cookiebot.com, plausible.io, scripts.clarity.ms, u.clarity.ms, www.clarity.ms, www.googletagmanager.com, www.redditstatic.com

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

Show the 1 address we checked
  1. https://domino.ai/.well-known/security.txt – reached, no match (HTTP 200)

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

Data location stated

weight 3 of 3

The hosting location is stated on a public page.

Source: https://domino.ai/legal/privacy-policy · checked 2026-09-03

✓

HTTPS enforced with HSTS

weight 2 of 3

HTTP redirects to HTTPS and the HSTS header is set.

Source: https://domino.ai/ · checked 2026-09-03

✓

Certifications named

weight 1 of 3

SOC 2 or ISO 27001 named on a public page.

Source: https://domino.ai/security · checked 2026-09-03

✓

Named privacy contact

weight 1 of 3

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

Source: https://domino.ai/legal/privacy-policy · checked 2026-09-03

Not measured by us 4
–

Data processing agreement

weight 3 of 3

Not measured. The vendor’s robots.txt excludes us from at least one of these addresses, so this was not measured.

Show the 8 addresses we checked
  1. https://domino.ai/legal/dpa – excluded by robots.txt
  2. https://domino.ai/dpa – reached, no match (HTTP 200)
  3. https://domino.ai/legal/data-processing-agreement – excluded by robots.txt
  4. https://domino.ai/data-processing-agreement – reached, no match (HTTP 200)
  5. https://domino.ai/legal/data-processing-addendum – excluded by robots.txt
  6. https://domino.ai/legal/gdpr – excluded by robots.txt
  7. https://domino.ai/trust/dpa – reached, no match (HTTP 200)
  8. https://domino.ai/privacy/dpa – reached, no match (HTTP 200)

Is this wrong? Send us the URL

–

Subprocessor list

weight 3 of 3

Not measured. The vendor’s robots.txt excludes us from at least one of these addresses, so this was not measured.

Show the 7 addresses we checked
  1. https://domino.ai/legal/subprocessors – excluded by robots.txt
  2. https://domino.ai/subprocessors – reached, no match (HTTP 200)
  3. https://domino.ai/sub-processors – reached, no match (HTTP 200)
  4. https://domino.ai/legal/sub-processors – excluded by robots.txt
  5. https://domino.ai/trust/subprocessors – reached, no match (HTTP 200)
  6. https://domino.ai/privacy/subprocessors – reached, no match (HTTP 200)
  7. https://domino.ai/legal/subprocessor-list – excluded by robots.txt

Is this wrong? Send us the URL

–

Notice before subprocessors change

weight 2 of 3

Not measured. The vendor’s robots.txt excludes us from at least one of these addresses, so this was not measured.

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

Is this wrong? Send us the URL

–

Uptime SLA with a figure

weight 1 of 3

Not measured. The vendor’s robots.txt excludes us from at least one of these addresses, so this was not measured.

Show the 6 addresses we checked
  1. https://domino.ai/legal/sla – excluded by robots.txt
  2. https://domino.ai/sla – reached, no match (HTTP 200)
  3. https://domino.ai/legal/service-level-agreement – excluded by robots.txt
  4. https://domino.ai/trust/sla – reached, no match (HTTP 200)
  5. https://domino.ai/uptime – reached, no match (HTTP 200)
  6. https://domino.ai/legal/uptime-sla – excluded by robots.txt

Is this wrong? Send us the URL

History

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

Compare