Chatto is now open source, with creator Hendrik Mans announcing the public release on July 8, 2026 and shipping a self-hostable build at version 0.4. The release turned a previously closed repository into a public codebase under AGPL-3.0, alongside the product pitch that has defined it from the start: a privacy-first team chat app you can run yourself as a single roughly 50 MB binary.
Chatto is a team chat app from Hendrik Mans, an independent developer who positioned it from the start as a simpler, self-hosted alternative to Slack and Discord. Its main design bet is operational plainness: one binary, one server, built-in chat plus audio and video calls, instead of the more sprawling setup common in older self-hosted stacks.
Chatto’s July 8 open-source release
The July 8 release shipped three concrete changes at once. The source code is now public, self-hosting is officially available, and the project has reached version 0.4, which Mans describes as usable but still pre-1.0.
That matters because as late as March 2026, the Chatto FAQ said the repository was not yet public. The shift is exactly the kind of move that lets outsiders inspect real architecture instead of marketing claims, the same basic dynamic behind broader debates over open models versus closed incumbents and, in a different market, open-source AI strategy.
Mans said the release is open source under AGPL-3.0, not the earlier Apache-2.0 plan he mentioned in December 2025. That is a real tradeoff, not a footnote: AGPL is designed to keep networked derivatives open too, which is friendlier to community availability than to vendors hoping to wrap the code into a mostly closed hosted product.
“Chatto is now Open Source,” Mans wrote in the July 8 announcement, where he also said the project is available for self-hosting and remains on the road to 1.0.
One limitation is immediate and explicit: Mans says Chatto is not accepting outside contributions right now. The code is public, but governance is still effectively single-author at this stage.
Chatto’s deployment and product architecture
Chatto’s clearest differentiator is single-binary deployment. The official site says you can run it as one 50 MB binary, which is unusually compact for a modern team chat system that also includes built-in audio and video calls.
That makes Chatto a different kind of self-hosted option from tools that ask administrators to assemble more moving parts. Its pitch is less “infinite enterprise configurability” and more “get a private chat server running without spending your weekend in Docker Compose.”
The architecture choice comes with a boundary. Chatto is built around one server powering one community, and it does not federate between servers. If Slack is a hosted office tower and Discord is a giant rented arena, Chatto is closer to a well-equipped private clubhouse: simpler to control, but not designed to join a larger network of peer servers the way Matrix-style systems are.
Recent release notes also show the app maturing in practical ways before the public open-source debut. The v0.1.0-rc.0 release included external login providers, Prometheus metrics, and self-hosting changes, while v0.2.0 reflected further self-hosting improvements in June 2026. Those are not glamorous features, but they are the plumbing that decides whether a self-hosted tool feels toy-like or livable.
| Product | Core deployment shape |
|---|---|
| Chatto | Single self-hosted binary with built-in calls |
| Slack | Hosted SaaS product |
| Discord | Hosted SaaS product centered on communities |
| Mattermost and similar self-hosted tools | Typically more conventional multi-component server deployment |
The source became public only this week, so independent long-term production reports are still limited.
Chatto’s clearest differentiator is single-binary deployment.
What Chatto still lacks before 1.0
The biggest caveat is versioning. Chatto is still only at version 0.4, and Mans says breaking changes are still possible before 1.0. Anyone deploying it now is signing up for a moving target.
That does not mean the feature set is empty. The official site already advertises chat, privacy-first self-hosting, and built-in audio and video calls, and the release history shows attention to authentication and observability. But the roadmap is still the roadmap: the January 2026 timeline post framed open-sourcing as one step on the way to a fuller 1.0 release later in 2026.
For teams comparing it with Slack or Discord, the answer is simple. Chatto is now a real open-source, self-hostable alternative, but it is not yet a finished one. For teams comparing it with older self-hosted chat platforms, the more interesting question is whether its stripped-down architecture turns out to be enough, enough features, enough reliability, enough admin surface, without growing into the same kind of complexity it is trying to dodge.
The next milestone is still version 1.0, which Mans says will follow after the current pre-release phase.
Key Takeaways
- Chatto became open source on July 8, 2026, with a public self-hostable release at version 0.4.
- The project is licensed under AGPL-3.0, replacing an earlier Apache-2.0 plan mentioned in 2025.
- Chatto’s main product distinction is a single roughly 50 MB binary that includes built-in audio and video calls.
- Chatto does not federate; it is designed around one server for one community.
- Breaking changes are still possible before 1.0, and outside contributions are not being accepted right now.
Further Reading
- Chatto is now Open Source!, Hendrik Mans’s July 8 announcement of the open-source release and self-hosting availability.
- Chatto official site, Product overview covering deployment, calls, and privacy-first positioning.
- The Chatto FAQ, Earlier FAQ on repository status and the non-federated design.
- Introducing Chatto, The original December 2025 introduction and early product intent.
- The Chatto Timeline, January 2026 roadmap post for the path toward open source and 1.0.