A really good chat application that you can self-host.
1.2k
Stars
45
Forks
156
Open issues
2
Contributors
AI Analysis
Chatto is a self-hosted chat application written in Go that emphasizes privacy, GDPR compliance, and communication features including video calls, voice calls, and screen sharing. It is purpose-built for teams and communities seeking on-premises messaging infrastructure rather than a general-purpose SaaS platform. The project serves organizations prioritizing data sovereignty and privacy over managed cloud services.
Inferred from signals mentioned in the README (tests, CI, type safety) — not a review of the actual code.
AI's overall editorial judgment — not an average of the bars above, can weigh other factors too.
Self-hosted team chat built in Go, three months old with accelerating early adoption
Chatto is a self-hosted team messaging application written in Go, positioned as an alternative to SaaS platforms like Slack. Created in April 2026, it targets organizations seeking deployment control and data sovereignty. Early signals show rapid GitHub interest (1,245 stars in ~3 months, 93 gained in last week), active maintenance, and planned commercial hosting. Real-world production adoption remains unverified; project remains pre-1.0 and explicitly closed to external contributions.
Launched April 2026 by chattocorp. Project is extremely young—roughly 3 months old as of July 2026. Exists within a contested category of self-hosted chat alternatives (Mattermost, Rocket.Chat, Zulip) but positions itself with emphasis on ease of self-hosting and commercial hosting optionality. No prior versions or evolution history available.
Strong early velocity: 1,245 stars accumulated in ~90 days suggests discovery momentum, possibly driven by privacy-conscious or self-hosting-focused communities. Recent 7-day gain of 93 stars indicates sustained interest, not one-time spike. Growth pattern consistent with a new project gaining visibility in its niche rather than mainstream breakout. Accelerating weekly gains suggest word-of-mouth traction among early adopters.
Adoption not verified. No deployment counts, user testimonials, case studies, or references to production instances in README. Official community server exists (chat.chatto.run) but this may be demo/reference only. Cloud hosting described as 'available soon' suggests commercial model still forming. Cannot confirm enterprise or significant community deployments.
Likely built as monolithic Go backend with standalone frontend (README notes Apache-2.0 exceptions for frontend). Appears structured around modular integration surfaces. Build signals (CI/CD workflows present) suggest disciplined release process. Based on README only; actual architectural complexity not verifiable without source inspection.
Not documented in README. CI workflow badge present but coverage metrics not exposed.
Highly active: last push 2026-07-09, one day before analysis date. Release workflow operational. Project maintains security policy and contributing guidelines. However, explicitly not accepting external contributions, suggesting focused, closed development model. This is a deliberate choice, not a sign of abandonment. Three months of consistent maintenance with zero gap since creation indicates stable stewardship.
ADOPT IF: you need a minimal self-hosted team chat, prioritize simplicity over feature breadth, are comfortable with young software (pre-1.0), and have capacity to follow a closed-contribution project's releases. AVOID IF: you require production stability guarantees, need extensive third-party integrations, depend on community-driven development, or plan to fork and customize (project explicitly discourages this). MONITOR IF: you are evaluating self-hosted chat alternatives and want to track whether Chatto's early velocity translates to real deployments and ecosystem maturity over the next 12–18 months.
Independent dimensions
Mainstream potential
3/10
Technical importance
6/10
Adoption evidence
2/10
- Pre-release status and closed-contribution model limit ecosystem resilience. If core maintainers deprioritize, project has no fallback community velocity.
- No verified production adoption. Adoption claims cannot be validated; GitHub stars may reflect curiosity rather than deployment intent.
- Immaturity risk: Go-based chat systems have complex operational requirements (databases, clustering, file storage). Unclear how battle-tested Chatto's operational story is for medium-scale teams.
- Commercial cloud hosting 'coming soon' introduces business risk: if cloud offering underperforms, company may shift focus or deprioritize open-source.
- License (AGPL-3.0-or-later with Apache-2.0 exceptions) may deter some enterprises; more restrictive than Mattermost or Rocket.Chat's dual-license models.
Likely to gain more traction among self-hosting enthusiasts over next 6 months. Will either consolidate into stable niche (similar to Zulip's trajectory) or lose momentum if commercial cloud launch disappoints or founder attention shifts. Probability of becoming broader alternative to Mattermost appears low given maturity gap and closed-contribution stance, but niche leadership in 'simplest self-hosted chat' is plausible.
Explore similar
Newsletter
Get analyses like this every Monday
Free weekly digest of the most interesting open-source discoveries.
Languages
Information
- Website
- https://chatto.run
- Language
- Go
- License
- AGPL-3.0
- Last updated
- 23h ago
- Created
- 3mo ago
- Analyzed with
- anthropic/claude-haiku-4-5
Stars over time
Contributors over time
Top 100 contributors only — repos with more will plateau at 100.
Open issues
[Bug]: Broken link in docker compose page
Question: diagrams in the docs
PWA should use server icon if one has been uploaded
[Bug]: You cannot escape the notification screen on an un-logged in server
Prevent reaction abuse
Top contributors
Recent releases
Similar repos
| Repository | Stars | Week Δ | Language | Score | Updated |
|---|---|---|---|---|---|
|
chattocorp/chatto
this
|
1.2k | +93 | Go | 7/10 | 23h ago |
 badoo/Chatto
|
4.5k | — | Swift | 7/10 | 3mo ago |
 okisdev/ChatChat
|
1.3k | — | TypeScript | 7/10 | 15h ago |
 tinode/chat
|
13.4k | — | Go | 7/10 | 5d ago |
 RocketChat/Rocket.Chat
|
45.8k | — | TypeScript | 8/10 | 7h ago |
Mature (10+ years), much larger community, established self-hosting ecosystem. Chatto trades years of polish for simpler onboarding claim. Mattermost has extensive third-party plugins; Chatto emphasizes core experience. Market segment overlaps but Mattermost's installed base gives it substantial advantage.
Longer history, broader feature set. Rocket.Chat serves both enterprise and self-hosted markets. Chatto targets simpler deployment; unclear if this translates to adoption advantage or niche positioning.
Focused on threaded conversations; philosophically distinct approach to chat UX. Smaller but loyal user base. Chatto's positioning relative to Zulip not clear from README; both target self-hosters but solve different conversation models.
Dominant, not self-hosted. Chatto explicitly serves those rejecting SaaS model. Not a direct replacement but positions against Slack's control and costs.
Decentralized federation model; Chatto appears to target single-instance self-hosting. Different architectural philosophy. Element has larger adoption; Chatto trades federation for simplicity claim.
