Chatto is a newly open-sourced chat platform aimed at the space between Slack, Discord, Teams, and self-hosted tools like Mattermost. The pitch is straightforward: a fast chat app you can run yourself without the usual open-core traps, with voice and video support, SSO, a compact deployment model, and a web app that feels more polished than most open-source messaging software. Under the hood it ships as a single binary, uses NATS and JetStream for messaging and persistence, relies on LiveKit for calls, and leans hard into a strong PWA instead of native apps for now. The author was explicit about a few boundaries. Chatto is not end-to-end encrypted for chat, federation is intentionally avoided, and each server is isolated by design, though lightweight cross-server identity is being explored.
The strongest reaction was relief that someone is trying to build a self-hostable chat tool that does not feel clunky. A lot of the praise centered less on raw feature count and more on the familiar pain points of existing options. Slack is seen as slow and increasingly unpleasant. Mattermost is capable but often bloated, confusingly licensed, or missing features in the open version.
Matrix gets credit for openness, but many people called its UX, key management, and operational complexity a tax they do not want to keep paying. Chatto landed because it seems to optimize for the opposite set of tradeoffs: speed, simple deployment, and a product feel that does not scream “enterprise software afterthought.” Several comments from people who installed it said setup was smooth and the UI felt genuinely snappy.
The practical caveats came through clearly. Mobile is PWA-first today, not native. That works better than some expected, including iOS push in at least some setups, but it does not erase the ugly reality of Apple and Google push infrastructure for full mobile clients. Onboarding is still rough in places, especially for first server setup and account creation. The product also has a strategic hole that every chat upstart has to stare at: network effects. Chatto is much easier to justify for private groups, homelabs, internal company chat, and communities that want control over their own server. It is much harder to justify when your customers, vendors, or partner communities already live in Slack or Discord and expect interoperability. The author acknowledged this by positioning Chatto more as isolated community and business infrastructure than as a federated network.
Comments also surfaced two business-relevant details that matter more than the homepage copy suggests. First, SSO is available without the usual enterprise paywall, which resonated with people burned by open-core chat products. Second, the data model is deliberately configurable around deletion and retention, which matters if you want privacy-friendly defaults for community servers but still need softer deletion and legal-hold style behavior in workplace deployments. The overall read is that Chatto is interesting because it picked a coherent product stance instead of trying to be everything. It is betting that a lot of people want “fast, self-hosted, good enough, pleasant to use” more than they want federation, universal compatibility, or maximal cryptographic purity.
hmans.dev