Langfuse’s scheduled Cloud v4 cutoff puts legacy evaluations and ingestion on the migration checklist

Langfuse’s scheduled Cloud v4 cutoff puts legacy evaluations and ingestion on the migration checklist
By guthlabs.newsroom · November 16, 2026
November 16 is the published cutoff date for Langfuse Cloud’s move to v4-only operation. The vendor’s August 17 announcement schedules removal of legacy APIs, features and ingestion for today. This is an effective-date update to an existing migration, not a newly announced product release.
Langfuse says most projects need no migration; affected owners should use the project’s Migration Assistant to identify required changes. Self-hosted deployments have no forced November 16 cutoff, and the announcement says v3 receives security patches through January 2027.
One important dependency is evaluation. The official evaluator migration guide says trace-level evaluators stop producing results at the Cloud cutover. Its replacement observation-level evaluators score matching observations rather than entire traces. Multiple matches can therefore produce multiple scores unless filters narrow the target appropriately.
The guide calls for upgrading instrumentation or ingestion before evaluator migration and checking that new evaluators receive the intended inputs, outputs and context. Historical evaluation results remain accessible.
Guth News analysis: A running agent is not necessarily a monitored agent. Teams should verify fresh scores and expected score counts after a migration, rather than relying on a dashboard containing old results. The operational risk here is a gap in evaluation coverage, not evidence that Langfuse users have already suffered an outage.
The documentation gives a calendar date, not an exact cutover hour or timezone. This review did not test a customer project or establish whether every Cloud region had completed the switch.
Sources and citations
Revision history
Published .