SaaS Ranking
Menu

Langfuse: what they publish

langfuse.com · LLM tooling and evaluation · checked 2026-10-16

74/100BBand B

Rank 1 of 49 in LLM tooling and evaluation, where the median is 17.

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

Langfuse

langfuse.com · LLM tooling and evaluation

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

Published commitments7 of 9 found

Measured behaviour1 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 Langfuse has no such document.

Where Langfuse sits in LLM tooling and evaluation

  1. A0 0%
  2. B1 2%
  3. C0 0%
  4. D6 12%
  5. E11 22%
  6. F31 63%
49 vendors with a score; 1 more without a score because we could measure too little. Bands have fixed thresholds, see how the score works.

The band of Langfuse 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 Langfuse 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

✗

Status page with incident history

weight 2 of 3

No public status page found.

Checked 3 addresses on 2026-10-16.

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

Is this wrong? Send us the URL

Across the market: Status page with history in LLM tooling and evaluation: 5 of 49 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://langfuse.com/ – third-party requests before any interaction: analytics.ahrefs.com, api.cr-relay.com, cdn-cookieyes.com, cdn.cr-relay.com, fonts.googleapis.com, github-production-user-asset-6210df.s3.amazonaws.com, github.com, js-eu1.hs-analytics.net, js-eu1.hs-banner.com, js-eu1.hs-scripts.com, log.cookieyes.com, pagead2.googlesyndication.com, region1.google-analytics.com, static.hex.site, track-eu1.hubspot.com, unpkg.com, www.googletagmanager.com

Is this wrong? Send us the URL

Across the market: No third-party tracking before consent in LLM tooling and evaluation: 4 of 50 companies

✗

Uptime SLA with a figure

weight 1 of 3

No uptime figure found.

Checked 6 addresses on 2026-10-16.

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

Is this wrong? Send us the URL

Across the market: Uptime SLA with a figure in LLM tooling and evaluation: 0 of 49 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://langfuse.com/.well-known/security.txt – reached, no match (HTTP 404)

Is this wrong? Send us the URL

Across the market: security.txt (RFC 9116) in LLM tooling and evaluation: 1 of 49 companies

Evidence

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

Published, with a source 8
✓

Data processing agreement (DPA)

weight 3 of 3

Published and readable without a login.

Source: https://clickhouse.com/legal/agreements/data-processing-addendum · checked 2026-10-16

Across the market: Data processing agreement in LLM tooling and evaluation: 7 of 49 companies

✓

Subprocessors: the published list

weight 3 of 3

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

Source: https://clickhouse.com/legal/agreements/langfuse-subprocessors · checked 2026-10-16

Across the market: Subprocessor list in LLM tooling and evaluation: 3 of 49 companies

✓

Data location: where they say data is hosted

weight 3 of 3

The hosting location is stated on a public page.

  • Locations named next to the hosting wording Ireland, Japan, Oregon, us-west. This does not establish the company’s headquarters.
    Show the 4 exact wordings

    ly runs on AWS and ClickHouse Cloud : US & HIPAA region : us-west-2 (Oregon) EU region : eu-west-1 (Ireland) JP region : ap-northeast-1 (Japan) Self‑hosted customers can choose any region / provider.

    Read at https://langfuse.com/security

    Langfuse Cloud – fully‑managed SaaS (multi‑tenant) with US, EU, Japan, and HIPAA data regions Self‑hosted OSS – MIT‑licensed software that you can deploy on your own infrastructure Self‑hosted Enterpr...

    Read at https://langfuse.com/security

    Langfuse Cloud mainly runs on AWS and ClickHouse Cloud : US & HIPAA region : us-west-2 (Oregon) EU region : eu-west-1 (Ireland) JP region : ap-northeast-1 (Japan) Self‑hosted customers can choose any....

    Read at https://langfuse.com/security

    Langfuse Cloud mainly runs on AWS and ClickHouse Cloud : US & HIPAA region : us-west-2 (Oregon) EU region : eu-west-1 (Ireland) JP region : ap-northeast-1 (Japan) Self‑hosted customers can choose any....

    Read at https://langfuse.com/security

Source: https://langfuse.com/security · checked 2026-10-16

Across the market: Data location stated in LLM tooling and evaluation: 10 of 49 companies

✓

Public pricing with figures

weight 2 of 3

Actual numbers on a public page.

Source: https://langfuse.com/pricing · checked 2026-10-16

Across the market: Public pricing in LLM tooling and evaluation: 28 of 49 companies

✓

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

    Read at https://langfuse.com/

Source: https://langfuse.com/ · checked 2026-10-16

Across the market: HTTPS enforced with HSTS in LLM tooling and evaluation: 38 of 50 companies

✓

Notice before subprocessors change

weight 2 of 3

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

Source: https://clickhouse.com/legal/agreements/langfuse-subprocessors · checked 2026-10-16

Across the market: Notice before subprocessors change in LLM tooling and evaluation: 7 of 49 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 HIPAA (not counted: the sentence does not carry it), ISO/IEC 27001 (not counted: the sentence does not carry it), SOC 2 Type II (unclear from the sentence). 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

    sure Security FAQ Vulnerability Management Whistleblowing TOMs ↗ Compliance SOC 2 Type II ISO 27001 HIPAA Compliance FAQ Privacy DPA ↗ Subprocessors ↗ GDPR Managing Personal Data Privacy FAQ Legal Ter...

    Read at https://langfuse.com/security

    ble Disclosure Security FAQ Vulnerability Management Whistleblowing TOMs ↗ Compliance SOC 2 Type II ISO 27001 HIPAA Compliance FAQ Privacy DPA ↗ Subprocessors ↗ GDPR Managing Personal Data Privacy FAQ...

    Read at https://langfuse.com/security

    sting Responsible Disclosure Security FAQ Vulnerability Management Whistleblowing TOMs ↗ Compliance SOC 2 Type II ISO 27001 HIPAA Compliance FAQ Privacy DPA ↗ Subprocessors ↗ GDPR Managing Personal Da...

    Read at https://langfuse.com/security

Source: https://langfuse.com/security · checked 2026-10-16

Across the market: Certifications named in LLM tooling and evaluation: 12 of 49 companies

✓

Named privacy contact (DPO or privacy address)

weight 1 of 3

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

Source: https://langfuse.com/privacy · checked 2026-10-16

Across the market: Named privacy contact in LLM tooling and evaluation: 17 of 49 companies

History

100 0 2026-10-09: 74 of 1002026-10-16: 74 of 100 2026-10-09 2026-10-16
Score over the last 2 runs we measured Langfuse in: 74 (2026-10-09), 74 (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.

Langfuse

8 found · 4 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 4 open evidence questions
  1. Status page with history

    Where can we review incident history for the service we will use, and how do we subscribe to incident updates?

    Inspect this check
  2. Uptime SLA with a figure

    Which availability commitment applies to our plan? Please include the measurement window, exclusions and credit claim process.

    Inspect this check
  3. 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
  4. security.txt (RFC 9116)

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

    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.