tylerhannan

Check the comments below or the OP. I think Ryadh does a great job of explaining the “why”

Why is that?

From the post

“ LibreChat remains 100% open-source under its existing MIT license Community-first development continues with the same transparency and openness Expanded roadmap to bring an even more enterprise-ready analytics experience. This proven playbook is the same one that we applied when joining forces with PeerDB to provide our ClickPipes CDC capabilities, and HyperDX, which became the UX of our observability product, ClickStack.”

Also, I work at ClickHouse, my email is super easy to figure out. Would love to alleviate concerns where I can.

We aren't a charity.

But, we are also a database provider.

Ryadh mentions some examples below where we have joined forces, incorporated code into ClickHouse Cloud (our commercial offering), and OSS has grown.

Time will tell (I can't predict future)...but I'm excited about the future of OSS LibreChat.

(disclaimer: I work at ClickHouse)

Nothing worse than having to update my IRC clients again ;)

(disclaimer: I work at ClickHouse)

At its simplest the team who was building that rad thing called LibreChat, now works at ClickHouse and build that rad thing called LibreChat.

Even simpler, the LibreChat team works at ClickHouse and are now my colleagues.

More complex, acquisitions can take a variety of "forms"...most importantly in these scenarios (and now I speak without knowledge of the deal structure) is making sure the team is paid, that copyright/trademark stuff is worked out, that OSS plans are discussed, and that everyone is excited to work together.

A database in isolation is meaningless.

Rather, people have to ask questions of it, and interact with the data. Increasingly, that is via AI tooling.

We've had a long-standing demo at llm.clickhouse.com (librechat, bedrock, anthropic).

(disclaimer: work at ClickHouse)

I actually took that picture a few years ago.

It's a fun story.

Our first swag shipment with the new colours had just arrived, the founders were in one place together for one of the first times, the weather wasn't terrible in Amsterdam for one day.

Not a pringles can. Rather they were stuffed in a shipping box that came from a warehouse, manhandled by customs, and thrown onto them for the purpose of taking the photo.

#startuplife eh?

Heya, I'm Tyler. I work at ClickHouse, looking after Devrel (and, of course, don't speak on behalf of the whole company).

ClickHouse is, indeed, the best database to build observability tooling on. And, for those of our users who want observability "out of the box," HyperDX is the best solution.

As part of this, we are increasing our investment in observability across the board. For instance, we plan to continue building/improving ClickHouse core capabilities to support the observability use case (eg. inverted indexes, semi-structured data support, time-series table engine and more).

I look forward to seeing how other observability companies innovate atop ClickHouse. There is room for all of us to succeed.

Re. licensing. I can tell you that we are planning no changes at the moment. At one point we may align licensing on the HyperDX and ClickHouse open-source projects (Apache 2)...but that is TBD.

Do let us know if you have any questions...happy to answer.

(disclaimer: I work at ClickHouse and am super excited the PeerDB team is joining us)

There is something about this that makes me so very happy.