Langfuse v4: up to 165× faster · Read more
DocsLangfuse v4 is live

Langfuse v4 is live

Langfuse v4 is live on Langfuse Cloud. It makes tables, dashboards, APIs, and evaluations dramatically faster at scale. Dashboard load times for large projects improve by at least 10x.

At its core is an observations-first data model built for agentic systems. Query any LLM call, tool execution, or agent step directly, without costly joins or read-time deduplication.

New to Langfuse? There is nothing to migrate. Start with the get started guide; it already uses v4.

What’s new

Every operation is now a first-class queryable object. Find slow LLM calls, expensive models, failed tool calls, or individual agent steps directly across any number of traces.

Under the hood, Langfuse stores one immutable observations table. A trace is all rows that share a trace_id, and trace-level attributes are copied onto every row:

Observations table
Observation-level dataTrace-level data · on every row
idtypenamelatencytrace_idtrace_nameuser_idsession_id
obs-1spanhandle-chat3.1sabc123chat-requestu-42s-7
obs-2spanretrieval0.4sabc123chat-requestu-42s-7
obs-3generationllm-call2.6sabc123chat-requestu-42s-7
obs-4spanbuild-report1.2sdef789export-reportu-17s-9
obs-5generationsummarize0.9sdef789export-reportu-17s-9

Trace-level input/output is deprecated across the product. Tables, LLM-as-a-judge evaluators, and exports now read input and output from the relevant observation, usually the root span or LLM call.

Selecting one observation instead of assembling data across an entire trace is more precise and a major reason v4 loads faster.

Observations-first lets you query and evaluate the relevant sub-agent, tool call, or LLM call directly. Immutable observations also avoid repeated trace-output updates and costly read-time deduplication.

Learn more in the data model docs and the observations guide.

Timeline

Jan 2026Apr 2026Jul 2026Oct 2026Jan 2027Apr 2027
Langfuse Cloud
Self-hosted (OSS)
Legacy APIs and ingestion removed (date will follow)

On Langfuse Cloud, review your project's remaining migration actions in the app.

Cloud rollout details (until the v4 cutover)
  • Organizations created on or after April 14, 2026, 14:00 UTC run v4 by default and do not see a toggle.
  • Organizations created before that date can switch the Preview toggle (bottom-left in the UI) on and off until Langfuse Cloud becomes v4-only (date will follow).
  • Cloud projects created on or after May 20, 2026 are locked to the "enriched observations" export source; new legacy export integrations cannot be created since June 22, 2026.

Upgrade

Follow the step-by-step upgrade guide. It covers Langfuse Cloud, direct API and OpenTelemetry users, and self-hosted deployments.

Check the Versions & Compatibility matrix to see which SDK and server versions work together.

Questions

Ask rollout and migration questions in the dedicated GitHub Discussion; we use that thread for updates and answers.


Was this page helpful?

Last edited