Langfuse ยท Lesson 0001

What Langfuse is — and why “Lang” is a trap

Four popular tools start with “Lang”: LangChain, LangGraph, LangSmith, Langfuse. People assume they are versions of the same thing. They are not. Split them into two layers and the whole category becomes obvious.

Two layers, four tools

Build layer โ€” runs your app

These are frameworks. They are the code that produces the LLM calls.

Observe layer โ€” watches your app

These are platforms. They sit beside your app and record what it did.

The single sentence: Langfuse competes with LangSmith, not with LangChain/LangGraph. You can build an app with LangGraph and observe it with Langfuse โ€” they are different layers.

So what is Langfuse, concretely?

An open-source LLM engineering platform (MIT core, YC W23, ~30k GitHub stars, now owned by ClickHouse). You instrument your app; it records every LLM call, tool call and retrieval step as a trace, then gives you:

It is OpenTelemetry-native. That matters a lot for us: your Go services (via the shared core library) already emit OTel. Langfuse is simply an OTel backend — so for much of your stack, pointing the existing exporter at Langfuse is most of the integration. We go deep on the Go path in the next lesson.

The win for this lesson: you can place all four “Lang” tools into Build vs Observe, and you can state in one line why Langfuse is not a rival to LangChain. If someone says “we use LangChain, we don’t need Langfuse,” that sentence confuses the layers — you now know why.

Check yourself (cover the answers, recall first)

Quick recall

Q1. Which tool builds agents as graphs?

A1. LangGraph builds agents as graphs.

Q2. Which tool traces apps and is open source?

A2. Langfuse traces apps and is open source.

Q3. Which layer does LangSmith belong in?

A3. LangSmith belongs in the observe layer.

Answers are deliberately the same length — no formatting clues.

Primary source to read next langfuse.com/docs — start with the “Get started” tracing page. Then the “Why is Langfuse open source?” handbook chapter (it settles the license question cleanly). Skim the GitHub README for the integration list.
Stuck on anything? Ask a follow-up right here — I’m your teacher and can go deeper on any part (the license, the Go/OTel path, pricing, how it’d slot into a specific repo).
Next up when you’re ready: Lesson 0002 — the OpenTelemetry path for Go services.