---
title: "Langfuse Launch Week #1"
date: 2024/04/19
description: "Unveiling Langfuse 2.0 in a week of releases"
tag: launchweek
ogImage: /images/blog/launch-week-1/langfuse-launch-week.png
author: Clemens
---

  ![Langfuse](/images/blog/launch-week-1/langfuse-launch-week.png)

## Joins us for Launch Week #1

We’re excited to announce Langfuse's first launch week. We're kicking it off on Monday April 22nd and will release a major upgrade to the Langfuse platform every day until Friday.

- ⭐️ [Star us](https://github.com/langfuse/langfuse/) on GitHub & see _all_ of our releases!
- [Twitter](https://x.com/langfuse) will be our main channel for all of Launch Week #1
- Join our [first town hall](#townhall) on Wednesday

## Launches

### Day 0: OpenAI JS SDK Integration

```ts /import { observeOpenAI } from "langfuse"/ /observeOpenAI/
import OpenAI from "openai";
import { observeOpenAI } from "langfuse";

// wrap the OpenAI SDK
const openai = observeOpenAI(new OpenAI());

// use the OpenAI SDK as you normally would
const res = await openai.chat.completions.create({
  messages: [{ role: "system", content: "Tell me a story." }],
});
```

We [launched](/changelog/2024-04-21-openai-integration-JS-SDK) a new wrapper for the OpenAI JS SDK. This integration, designed to enable easier monitoring of OpenAI API usage, features seamless observability with enhancements like automatic tracking of prompts, completions, and API errors, as well as insights into model usage and costs. After a soft launch that gathered user feedback for improvements, the integration is now fully available, complete with comprehensive [documentation](/integrations/model-providers/openai-js) and an example notebook.

### Day 1: PostHog Integration

We teamed up with [PostHog](https://posthog.com) (OSS product analytics) to integrate LLM-related product metrics into your existing PostHog dashboards. This integration is [now available](/changelog/2024-04-22-posthog-integration) in public beta on Langfuse cloud. You can configure it within your Langfuse project settings. When activated, Langfuse sends metrics related to traces, generations, and scores to PostHog. You can then build custom dashboards to visualize the data or use the _LLM Analytics_ dashboard template to get started quickly. See [docs](/integrations/analytics/posthog) for more information.

### Day 2: LLM Playground

We're excited to introduce the [**LLM Playground**](/docs/playground) to Langfuse. By making prompt engineering possible directly in Langfuse, we take another step in our mission to build a feature-complete AI engineering platform that helps you along the full live cycle of your LLM application. With the LLM playground, you can now test and iterate your prompts directly in Langfuse. Either start from scratch or jump into the playground from an existing prompt in your project. See the [docs](/docs/playground) for more details and let us know what you think in the [GitHub discussion](https://github.com/orgs/langfuse/discussions/1170).

### Day 3: Decorator-based integration for Python

We're happy to share that the Decorator-based integration for Python now supports all Langfuse features and is the recommended way to use Langfuse in Python. The decorator makes integrating with Langfuse so much easier. Head over to the [Python Decorator docs](/docs/sdk/python/decorators) to learn more. All inputs, outputs, timings are captured automatically, and it works with all other [Langfuse integrations](/integrations) (LangChain, LlamaIndex, OpenAI SDK, ...). To celebrate this milestone, we wrote a [blog post](/blog/2024-04-python-decorator) on the technical details and created the example notebook shown in the video as it demonstrates what's really cool about the decorator. Thanks again to [@lshalon](https://github.com/lshalon) and [@AshisGhosh](https://github.com/AshisGhosh) for your contributions to this!

### Day 4: Datasets v2

We're thrilled to release Datasets v2, featuring significant enhancements to the dataset experience in Langfuse. Improvements include a new editor powered by Codemirror, metadata support on all objects, tables that render inputs/outputs side-by-side, the ability to link dataset runs to traces, and the option to create dataset items directly from traces. We've also extended the public API with new endpoints for programmatic management of datasets. Check out the [changelog](/changelog/2024-04-25-datasets-v2) which summarizes all the new features and improvements.

### Day 5: Model-based Evaluations

On the final day of Launch Week 1, we're happy to release the biggest change to Langfuse yet: Model-based evaluations run right in Langfuse. So far, it was easy to measure LLM cost and latency in Langfuse. Quality is based on [scores](/docs/scores) which can be user feedback, manual labeling results, or be ingested by evaluation pipelines that you built yourself using the Langfuse SDKs/API. Model-based Evaluations in Langfuse make it way easier to continuously evaluate your application on the dimensions you care about. These can be: hallucinations, toxicity, relevance, correctness, conciseness, and so much more. We provide you with some battle-tested templates to get you started, but you can also write your own templates to cover any niche use case that might be exclusive to your application. Check out the [changelog](/changelog/2024-04-26-model-based-evaluation) or watch the video to learn more about all the details.

## Launch Week Events

### Wednesday: First virtual town hall [#townhall]

You're invited to our first virtual town hall. We (Max, Marc and Clemens) will be demoing new features in Langfuse, answering questions and talking about where we're taking the project. We're looking forward to hanging out!

- When: Wednesday, April 24th, noon PT, 9pm CET
- [Recording on YouTube](https://www.youtube.com/watch?v=WGERHcRnBYQ)

### Friday: Langfuse 2.0 on Product Hunt

We will end the week with the launch of **Langfuse 2.0** on Product Hunt on Friday, April 26th. After our initial launch last year – which led to a [Golden Kitty Award](https://www.producthunt.com/golden-kitty-awards/hall-of-fame?year=2023#ai-infra) – we are very excited to be back on Product Hunt.

[Launch post](https://www.producthunt.com/posts/langfuse-2-0) (_Spoiler: Langfuse became the #1 product of the day 🥇_)

<!-- agent-instructions -->

---

## Agent Instructions

This page is part of the [Langfuse](https://langfuse.com) documentation, published as plain Markdown for AI agents. Every page is available as Markdown by appending `.md` to its URL, or by sending an `Accept: text/markdown` header. This page: `https://langfuse.com/blog/launch-week-1.md`.

### Querying these docs

If the answer is not on this page, query the documentation instead of guessing:

- **Semantic search** across all Langfuse docs, returning an answer with the relevant pages and excerpts. Ask a specific, self-contained question:

  ```bash
  curl -sG "https://langfuse.com/api/search-docs" --data-urlencode "query=How do I trace a LangGraph agent?"
  ```

- **Index of every page**: <https://langfuse.com/llms.txt>, with per-section indexes [llms-docs.txt](https://langfuse.com/llms-docs.txt), [llms-integrations.txt](https://langfuse.com/llms-integrations.txt), and [llms-self-hosting.txt](https://langfuse.com/llms-self-hosting.txt).

### Before writing Langfuse code

- **Install the [Langfuse Agent Skill](https://langfuse.com/docs/api-and-data-platform/features/agent-skill).** It encodes Langfuse's own best practices for instrumentation, prompt management, and evaluation, and materially improves results.
- **Read [What does a good trace look like?](https://langfuse.com/docs/observability/best-practices.md)** before instrumenting an application.
- **Verify endpoints, parameters, and response fields** against the [API reference](https://api.reference.langfuse.com) instead of inferring them from code examples.
- **Use the [Langfuse CLI](https://langfuse.com/docs/api-and-data-platform/features/cli)** (`npx langfuse-cli api <resource> <action>`) to read or write traces, prompts, datasets, and scores from the terminal.

Found an error in these docs? Please open an issue at <https://github.com/langfuse/langfuse-docs/issues>.
