SaaS Ranking
Menu

Langfuse

langfuse.com · LLM tooling and evaluation · checked 2026-09-04

74/100BBand B

Rank 1 of 28 in LLM tooling and evaluation, where the median is 19.5.

We measured 12 of 12 criteria for Langfuse on 2026-09-04. We found 8 with a source and did not find 4 at the addresses we checked. That is a transparency score of 74 out of 100, band B.

Overview

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 28

Published commitments7 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 Langfuse 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

✗

Status page with history

weight 2 of 3

No public status page found.

Checked 3 addresses on 2026-09-04.

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

✗

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://langfuse.com/ – third-party requests before any interaction: analytics.ahrefs.com, cdn-cookieyes.com, js-eu1.hs-scripts.com, log.cookieyes.com, www.googletagmanager.com

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://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

✗

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://langfuse.com/.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 8
✓

Data processing agreement

weight 3 of 3

Published and readable without a login.

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

✓

Subprocessor 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-09-04

✓

Data location stated

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

✓

Public pricing

weight 2 of 3

Actual numbers on a public page.

Source: https://langfuse.com/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 63072000 seconds (730 days).
    Show the exact wording

    max-age=63072000

    Read at https://langfuse.com/

Source: https://langfuse.com/ · checked 2026-09-04

✓

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-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 Type II.
    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-09-04

✓

Named privacy contact

weight 1 of 3

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

Source: https://langfuse.com/privacy · checked 2026-09-04

History

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

Compare