Our goal continues to build the best LLM engineering platform
ClickHouse has acquired Langfuse.
If you’re reading this as a Langfuse user, your first question is probably: What does this mean for me?
Our roadmap remains the same, our goal continues to build the best LLM engineering platform, and we are committed to open source and self-hosting. There are no immediate changes to how you use Langfuse and how you can reach us.
What does Change is our ability to move forward rapidly. With ClickHouse with us, we can invest more deeply in performance, reliability, and our roadmap that helps teams build and improve AI applications in production.
the one who remains the same
This is the section we also want to read first.
- Langfuse remains open source and self-hosted. There are no planned changes to licensing. As you know, we have been very much attracted to OSS over the past years.
- Langfuse Cloud continues to operate as is. Same product, same endpoint, same experience.
- The support remains the same. Same channel, same SLA for existing customers.
what would be better now
Joining Clickhouse turns years of operational learning into immediate, real customer benefits.
- The advantage of over-engineering on the toughest parts. Langfuse is a data-intensive product. Working closely with the ClickHouse engineering team helps us increase performance and reliability.
- Rapid progress on advanced enterprise-grade compliance and securityWith the help of Clickhouse’s resources.
- Learning from ClickHouse’s Customer Success and Support Playbook. It moves us years forward and allows us to spend more time on what we really care about: our users.
a quick look back
Langfuse started the same way many LLM products start: we were building the agent ourselves. And we continued to struggle with the same problems.
Building LLM apps is easy to demo and difficult to run in production. Debugging is different, quality is non-deterministic, and the iteration loop is messy. When we did Y Combinator in early 2023, we saw it every week, in our own projects and what other founders in our group were working on.
So we created a duct tape version of what we wanted: Tracing and Evaluation Primitives Easy to add, easy to self-host, and really useful to iterate on.
The first version was deliberately simple. it continued postgresBecause shipping speed matters more than theoretical scaling. This allowed us to quickly get a real product and a real community.
Then people actually started using the product more than we ever imagined.
As adoption increased, Postgres became a bottleneck for the workloads (high-throughput ingestion + fast analytical reads) required to support Langfuse. with langfuse v3We switched the core data layer clickhouse Making Langfuse scale to production workloads in both cloud and self-hosted deployments.
And if you like a deeper dive into the infrastructure, here it is.
Why join ClickHouse?
There are several ways this could have happened. We had not planned to sell the company. In fact, we had term sheets for a great Series A and we were looking forward to a few days off over Christmas after an intense year.
What changed wasn’t our strong belief in Langfuse, it was the realization of how fast we could move with Clickhouse, while staying true to what makes Langfuse work: open source, self-hosting, and a product built for real production workloads.
A shared history (before acquisition)
This dialogue did not start with any term sheet. Since Langfuse runs on ClickHouse, we naturally ended up collaborating early and often.
- We’ve always been in close contact with multiple teams at ClickHouse: sharing feedback with the database team, and using new features to make Langfuse more reliable. For example, compute-compute separation helps us reduce the risk of noisy neighbors on the Langfuse cloud.
- Langfuse Cloud is a major customer of ClickHouse Cloud.
- ClickHouse teams use Langfuse to improve their agentic applications.
- We invested heavily in ClickHouse-supported self-hosting: documentation, templates, and deployment patterns, and worked closely with ClickHouse to improve that experience.
- As a result, Langfuse introduced thousands of teams to Clickhouse when upgrading from Langfuse v2 to v3.
- We’ve put together community meetings: a Clickhouse meeting in our Berlin office, one in San Francisco, and an Openhouse talk in Amsterdam.
Langfuse runs on Clickhouse, Clickhouse uses Langfuse to customize their agentic products, we share a lot of clients and OSS deployments; Which gives Clickhouse every incentive to keep Langfuse fast, reliable, and boringly reliable at scale.
So in many ways, we acted like long-term partners. This acquisition is a way to make that partnership permanent and invest aggressively together.
Max explained at the ClickHouse Open House () in Amsterdam how we use ClickHouse to keep product performance ahead of demand.
Culture and engineering fit
The first time we met Aaron, Yuri, Alexey, Tanya, Riad, and Pete in person ended up over a long lunch in Amsterdam. It’s become clear that we share a similar perspective on building great developer tooling, how it drives everything within our companies, and how analytics is increasingly becoming fundamental to building and optimizing agentive products.
We already knew that ClickHouse has one of the best infrastructure engineering teams in the world. More importantly, engineering culture feels like an instant match:
- Open-source identity and management
- Developer-first product trend
- Performance and reliability as product features (not an afterthought)
The entire Langfuse team will join Clickhouse to continue building Langfuse. All of these aspects were important to us and we couldn’t be more excited.
What we’re focusing on next
Our North Star does not change: Help teams send useful, reliable agents by closing the loop from production data to better signals, evaluation, and product decisions.
More directly, we are investing in:
- Production Monitoring and Analysis For real agent systems (not just for offline evaluation).
- Workflow in tracing, labeling and experiments Hence the iteration loops become smaller.
- Greater performance and scale-Especially for large self-hosted and enterprise deployments.
- more polish (UI/UX, developer experience and documentation) so that the product remains simple even as the space becomes more complex.
Thank you
Langfuse exists because the community pushed it forward through GitHub issues, PR, feedback, and lots of Slack messages and spontaneous calls to dig together into a product feature.
We are grateful for the trust you have placed in us. Joining ClickHouse is our way of honoring that trust by putting more resources behind the thing we care about most: building a product you can trust.
We’re excited for what’s next!
Max, Clemens and Mark
FAQ
Is Langfuse still open source?
Yes. No changes are planned in licensing.
Can I still self-host Langfuse?
Yes. Self-hosting is a first-class path.
Has anything changed for Langfuse Cloud customers today?
No, same product, same endpoint, same contract.
Where do I go for support?
No change:
Will the Langfuse team stay on Langfuse?
Yes. The team is joining ClickHouse and will continue building Langfuse. Additionally, we also continue in Berlin and SF.
join the discussion
If you have any other questions, let’s discuss together.
If you are an enterprise customer and have additional questions, feel free to reach out
<a href