Looks really nice, thank you for open-sourcing. I keep a directory of opensource alternatives. Would you say this is a Discord or Slack alternative?

Amazing. And with SSO out of the box without weird "Oh, SSO is Enterprise only" BS.

Very cool! You should request being added to https://european-alternatives.eu/

Ah mobile app is not ready yet. I am looking for some alternative to matrix because running it with bots is a bit convoluted, i.e. you have to have limit of edits of message for model streaming or you will kill entire room. Or I never seen robots in matrix sending encrypted messages. Why bother than? Anyway if mobile will be a thing this seems like perfect thing to have for your family and friends.

I’ve known Hendrik for years, and he is one of the most talented developers I’ve ever met. I’m confident this project will become successful very quickly. Beyond the project itself, what fascinates me most is how he single-handedly developed it by leveraging agentic coding.

> It’s designed to be extremely easy to self-host on your own infrastructure.

Kudos for this. Per the docs: https://docs.chatto.run/,

> Chatto ships in a compact, self-contained binary

> it uses NATS, a compact message broker that also ships with a built-in stream persistence engine [...] NATS is just as easy to provision as Chatto, and most of our examples will show you how.

> you can also configure an external S3-compatible object storage for Chatto to store your files in, and we strongly recommend doing

> The actual calls are powered by LiveKit (Apache-2.0), which you need to deploy alongside Chatto. As with NATS, the deployment examples show the required wiring.

> ...

And kudos for backing it up with real guidance. Great project.

Would English speakers pronounce this as "Chat-to"? To a Japanese person, this clearly sounds like "Cha-tto," which simply means "chat."

> And you can just self-host it. For free, too! (A weird thing to write, but the OSS chat app space has become very weird in many ways!)

Wait, what? There are open-source chat apps that you have to pay to host yourself? How does that work? Or did I misunderstand?

This is awesome! Some feedback - I can't tell anywhere from the website if there is mobile support (which is a must-have if I want to consider moving my company or friends over to this)

What's the rationale for the dual licensing? It looks like the Go backend is AGPL but the TypeScript frontend is Apache 2.0.

Why not keep it all AGPL?