SaaS Ranking
Menu

Metaplane

metaplane.dev · Data catalogs and governance · checked 2026-09-04

48/100DBand D

Rank 3 of 16 in Data catalogs and governance, where the median is 15.

We measured 12 of 12 criteria for Metaplane on 2026-09-04. 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

Transparency labelsaas-ranking.com

Metaplane

metaplane.dev · Data catalogs and governance

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

Published commitments5 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 Metaplane 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

No data processing agreement found.

Checked 8 addresses on 2026-09-04.

Show the 8 addresses we checked
  1. https://metaplane.dev/legal/dpa – reached, no match (HTTP 404)
  2. https://metaplane.dev/dpa – reached, no match (HTTP 404)
  3. https://metaplane.dev/legal/data-processing-agreement – reached, no match (HTTP 404)
  4. https://metaplane.dev/data-processing-agreement – reached, no match (HTTP 404)
  5. https://metaplane.dev/legal/data-processing-addendum – reached, no match (HTTP 404)
  6. https://metaplane.dev/legal/gdpr – reached, no match (HTTP 404)
  7. https://metaplane.dev/trust/dpa – reached, no match (HTTP 404)
  8. https://metaplane.dev/privacy/dpa – 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.metaplane.dev/security · checked 2026-09-04

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

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

Show the 1 address we checked
  1. https://metaplane.dev/ – third-party requests before any interaction: ajax.googleapis.com, analytics.ahrefs.com, analytics.quantif.ai, api.hubapi.com, app.clearbit.com, cdn.jsdelivr.net, cdn.prod.website-files.com, cdnjs.cloudflare.com, d3e54v103j8qbb.cloudfront.net, fonts.googleapis.com, fonts.gstatic.com, hubspotonwebflow.com, imgix.datadoghq.com, js.hs-analytics.net, js.hs-banner.com, js.hs-scripts.com, js.hsadspixel.net, js.hsforms.net, metaplane-dev.s3.amazonaws.com, mtp-code.netlify.app, tag.clearbitscripts.com, track.hubspot.com, transcend-cdn.com, unpkg.com, web-a.quantif.ai, widget.intercom.io, www.google.com, www.googletagmanager.com, x.clearbitjs.com

Is this wrong? Send us the URL

✗

Notice before subprocessors change

weight 2 of 3

No commitment to give notice before subprocessors change found.

Checked 8 addresses on 2026-09-04.

Show the 8 addresses we checked
  1. https://metaplane.dev/legal/subprocessors – reached, no match (HTTP 200)
  2. https://metaplane.dev/subprocessors – reached, no match (HTTP 404)
  3. https://metaplane.dev/sub-processors – reached, no match (HTTP 404)
  4. https://metaplane.dev/legal/dpa – reached, no match (HTTP 404)
  5. https://metaplane.dev/dpa – reached, no match (HTTP 404)
  6. https://metaplane.dev/legal/data-processing-agreement – reached, no match (HTTP 404)
  7. https://metaplane.dev/trust/subprocessors – reached, no match (HTTP 404)
  8. https://metaplane.dev/legal/sub-processors – 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-04.

Show the 6 addresses we checked
  1. https://metaplane.dev/legal/sla – reached, no match (HTTP 404)
  2. https://metaplane.dev/sla – reached, no match (HTTP 404)
  3. https://metaplane.dev/legal/service-level-agreement – reached, no match (HTTP 404)
  4. https://metaplane.dev/trust/sla – reached, no match (HTTP 404)
  5. https://metaplane.dev/uptime – reached, no match (HTTP 404)
  6. https://metaplane.dev/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-04.

Show the 1 address we checked
  1. https://metaplane.dev/.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
✓

Subprocessor list

weight 3 of 3

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

Source: https://www.metaplane.dev/legal/subprocessors · checked 2026-09-04

✓

Status page with history

weight 2 of 3

A public status page with incident history.

Source: https://status.metaplane.dev/ · checked 2026-09-04

✓

Public pricing

weight 2 of 3

Actual numbers on a public page.

Source: https://www.metaplane.dev/pricing · checked 2026-09-04

✓

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://metaplane.dev/

Source: https://metaplane.dev/ · checked 2026-09-04

✓

Certifications named

weight 1 of 3

SOC 2 or ISO 27001 named on a public page.

  • Named on that page HIPAA, ISO/IEC 27001, SOC 2.
    Show the 3 exact wordings

    Compliant with SOC 2, GDPR, and HIPAA Metaplane is designed to store no sensitive customer information and as little sensitive data about

    Read at https://www.metaplane.dev/security

    and we only work with cloud providers whose datacenters are SOC 2 and ISO 27001 certified.

    Read at https://www.metaplane.dev/security

    Compliant with SOC 2, GDPR, and HIPAA Metaplane is designed to store no sensitive customer information and as little sen

    Read at https://www.metaplane.dev/security

Source: https://www.metaplane.dev/security · checked 2026-09-04

✓

Named privacy contact

weight 1 of 3

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

Source: https://www.metaplane.dev/legal/privacy · checked 2026-09-04

History

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

Compare