Langfuse v3 to v4 upgrade
Planning the self-hosted Langfuse v4 upgrade: infrastructure minimums, finishing v3 background migrations, choosing the legacy or dual write mode, migrating SDKs and evaluators, backfilling history and cutting over.

Planning major self-hosted Langfuse upgrades, which change infrastructure and data models, and staying within supported SDK and security patch windows.
Planning the self-hosted Langfuse v4 upgrade: infrastructure minimums, finishing v3 background migrations, choosing the legacy or dual write mode, migrating SDKs and evaluators, backfilling history and cutting over.
Moving a Postgres-only Langfuse v2 deployment to the v3 architecture with ClickHouse, Redis and blob storage: the zero-downtime parallel approach, the version window that works, and background data migrations.

Tell us what you're working on, whether it's a deployment, an audit, a security test or a cyber range. You'll speak with an engineer who can help you scope it.