langfuse VS openlit

Langfuse is an open-source LLM engineering platform that helps teams collaboratively debug, analyze, and iterate on their LLM applications.

Congrats on the Show! How’s this different from https://github.com/langfuse/langfuse? The exports seems really interesting

Thus, we started working on Langfuse.com (GitHub) to establish an open source LLM engineering platform with tightly integrated features for tracing, prompt management, and evaluation. In the beginning we just solved our own and our friends’ problems. Today we are at over 1000 projects which rely on Langfuse, and 2.3k stars on GitHub. You can either self-host Langfuse or use the cloud instance maintained by us.

- We want to build a tool that is recommended here on HN: you can build a tool you would want to use yourself.

Please see more details here: https://langfuse.com/careers or reach out directly to me: [email protected]

[1] https://github.com/langfuse/langfuse

[2] https://create.t3.gg/

We struggled with this ourselves while building LLM-based products and then open-sourced our observability/monitoring tool [1]. Many use it to track RAG and agents in production, run custom evals on the production traces (focused on hallucination), and track how metrics are different across releases or customers. Feel free to dm if there is something specific you are looking to solve, happy to help.

[1] https://github.com/langfuse/langfuse

Visit us on Discord and Github to engage with our project.

Maybe try https://github.com/langfuse/langfuse

It was recently shared on HN

Last week we showcased our open-source project, OpenLIT (https://github.com/openlit/openlit), here, and thanks to this incredible community, we hit 300 stars in just a couple of days!

One of my mentors, a core lead on OpenTelemetry, suggested we consider adding a Contributor License Agreement (CLA) to our project, similar to what has been done with OpenTelemetry.

I understand the potential legal benefits a CLA offers, such as ensuring contributions can be freely used and distributed, which could be crucial for the project's long-term viability and to avoid legal complications.

However, I’m equally concerned about the potential downsides, especially regarding community contributions. I worry that a CLA might stop new contributors who prefer to avoid legal hurdles or are reluctant to sign documents. Since OpenLIT aims to be truly open-source and community-driven, keeping the contribution process as straightforward as possible is essential to me.

So, I’m turning to you, HN community, for guidance:

- Have you implemented a CLA for your project? What impact did it have on contributions?