Open source chat is in a healthier state in 2026 than it has ever been. The big self-hosted platforms have matured into serious Slack and WhatsApp alternatives, the React Native ecosystem has several production-grade chat codebases you can read and fork, and a newer wave of projects is wiring AI agents directly into the message stream. This roundup looks at the landscape from a React and React Native developer’s point of view: which full applications are worth studying, which libraries and engines you can actually build on, and what has quietly died since this space last got a fresh look.
A note on method: every project listed here was checked against its GitHub repository in 2026. Star counts are rounded and will drift, but maintenance status is the thing that actually matters, and that is what we verified.
Full open source chat platforms worth knowing in 2026
These are complete applications, not libraries. Even if you never deploy one, they are the best reference codebases available for how real teams structure messaging apps at scale.
| Project | What it is | Client stack | GitHub stars (approx) |
|---|---|---|---|
| Rocket.Chat | Self-hosted team chat with federation, omnichannel support, and a large plugin ecosystem | Meteor/React web, React Native mobile | 45k |
| Mattermost | Self-hosted collaboration platform popular with security-conscious engineering orgs | React web, React Native mobile | 36k |
| Signal | End-to-end encrypted personal messenger, the reference implementation for the Signal protocol | Native Android and iOS | 29k (Android repo) |
| Jitsi Meet | Video conferencing you can embed or run standalone, with a React and React Native codebase | React web, React Native mobile | 29k |
| Element | The flagship Matrix client, formerly known as Riot. The next generation Element X apps are built on the Matrix Rust SDK | React web, native mobile | 13k (web) |
Choosing between the big platforms usually comes down to two questions. If you need omnichannel features, guest access, and a marketplace of integrations, Rocket.Chat has the broadest surface area. If you want a leaner core with strong compliance tooling and a codebase that is easier to reason about, Mattermost tends to win with engineering-led teams. Element is the pick when federation matters, since Matrix lets separately hosted servers talk to each other, something neither of the other two does natively. Signal and Jitsi sit apart: one is a consumer messenger you study rather than deploy, the other a video layer you embed.
A correction worth making explicitly: older roundups, including an earlier version of this one, pointed readers at a GitHub project called Riot.js as a chat app. That was a mixup. Riot.js is an unrelated frontend UI framework. The chat client called Riot was renamed Element back in 2020 and lives under the element-hq organization on GitHub, where it remains very actively developed. Wire, another regular on these lists, still publishes its clients on GitHub under the wireapp organization, though the project is oriented around its own hosted service rather than community self-hosting.
React Native chat projects you can learn from and build on
If your goal is shipping a chat feature inside your own React Native app rather than deploying a whole platform, these are the repositories to look at first.
Rocket.Chat.ReactNative
The official Rocket.Chat mobile client is one of the largest production React Native codebases you can read end to end. It is actively maintained, written in TypeScript, and covers the hard parts most tutorials skip: offline message queues, push notification handling, end-to-end encryption UI, and deep linking. Even if you never touch Rocket.Chat itself, this repo is a masterclass.
Mattermost Mobile
The Mattermost mobile app is the other big production React Native chat client. Its second-generation architecture leans on WatermelonDB for local-first data, which makes it a useful study in keeping a chat UI responsive when the network is not cooperating.
react-native-gifted-chat
For a decade, react-native-gifted-chat (around 14k stars) was the default answer to “how do I render a chat UI in React Native”. Know its 2026 status before you adopt it: the original package is in maintenance mode and no longer receives new features. Active development, including support for streaming AI messages, continues in the maintained community fork @kesha-antonov/react-native-chat. For new projects, start with the fork. Remember also that Gifted Chat is UI only; you still need to bring your own backend, transport, and auth.
Ethora
Disclosure: Ethora is our product. Ethora is an open source chat and AI SDK built around React and React Native clients with an XMPP-based backend. It is a much smaller community than Rocket.Chat or Mattermost, so weigh that honestly, but it targets a different problem: not a standalone team chat product, but an engine for embedding chat, user management, push notifications, and AI agents into your own app, including self-hosted deployments for teams in healthcare, finance, and other regulated settings. If that embedded use case is yours, it is worth a look alongside the commercial SDKs.
Speaking of which, if you are weighing open source engines against paid options like Stream or Sendbird, we keep a separate, regularly updated comparison in our guide to the best chat SDKs for React Native. The build-vs-buy math there applies directly to everything in this section.
What changed since the last version of this list
Roundups age badly, so here is the honest churn report:
- Riot.js removed as a chat project. As covered above, it was never one. Element is the correct successor entry.
- Gifted Chat moved to maintenance mode. The community fork is now the recommended starting point.
- React Table became TanStack Table. The old react-table repository referenced in earlier versions of this post now lives on as the framework-agnostic TanStack Table, which remains excellent for admin and moderation dashboards around a chat product.
- Semantic UI is effectively dormant. The core project has not shipped a meaningful release in years. It no longer belongs on a recommended list.
- Star counts moved a lot. Numbers from 2024-era listicles undercount most of these projects by 2x to 3x. Signal’s Android repo alone sits near 29k today.
React UI libraries that pair well with a chat build
A chat product is never just the message list. You will build settings screens, admin panels, and onboarding flows, and mature component libraries save real time there.
- MUI (Material UI): still the heavyweight, with one of the largest component sets and communities in the React world. Note the repository moved from the old mui-org organization to mui.
- Ant Design: dense, data-heavy components that suit admin and moderation tooling especially well.
- React Bootstrap: the pragmatic choice when your team already knows Bootstrap conventions.
- Chakra UI: strong accessibility defaults and a pleasant developer experience for product surfaces around the chat itself.
One trend worth naming: a lot of new projects now skip packaged component libraries entirely in favor of copy-in approaches like shadcn/ui. For chat specifically, where you end up customizing message bubbles and composers heavily anyway, owning the component source is often the right call.
Deploying and securing a React chat application
The deployment basics have not changed much, but chat raises the stakes on a few of them:
- Automate your pipeline. CI for tests and builds, plus over-the-air update tooling on mobile, matters more for chat apps because messaging bugs are visible to users within minutes.
- Plan for persistent connections. WebSocket or XMPP connections change your hosting math compared to a request-response app. Load test the connection layer, not just the API.
- Encrypt in transit and be deliberate about encryption at rest. If you serve healthcare or finance customers, retention rules and audit logging are product features, not afterthoughts.
- Validate everything users send. Chat is user-generated content by definition. Sanitize rendered messages ruthlessly to shut down XSS, and rate limit at the connection level to blunt spam and abuse.
- Keep dependencies current. Chat apps carry large dependency trees across web and mobile. Automated update tooling plus a real review habit beats heroic quarterly upgrades.
Where open source chat is heading
Three shifts are shaping the next few years. First, AI agents are becoming first-class chat participants: bots that summarize threads, translate messages in place, and answer questions from a knowledge base are moving from demos into the core roadmaps of most platforms listed here. Second, self-hosting keeps gaining ground with regulated buyers, which favors projects like Rocket.Chat, Mattermost, Element, and Ethora that treat data ownership as the point rather than a limitation. Third, local-first architectures are spreading from research into practice, and the mobile clients that feel fastest are the ones that treat the network as optional.
For React and React Native developers, the practical takeaway is unchanged from a decade ago, only the options got better: read the big open codebases, build on maintained libraries, verify project health before you commit, and keep the parts of the stack you may need to customize under your own control.