Open-source WeCom alternatives

Rocket.Chat is a communications platform written in TypeScript for teams and organizations that care about data protection. It supports real-time conversations between colleagues, with partner companies, and with customers or citizens, and its topics place it in the same space as Slack, with WebRTC for calls and meetings.

The product emphasizes control over where and how it runs. Deployment options include self-hosted servers, a managed cloud and fully air-gapped environments, with a scalable architecture and performance monitoring for workspace administration. Security and sovereignty features, including identity management, are a core part of the pitch, and the platform is built to be highly customizable, so organizations can adapt it to their own workflows and integrations.

The repository's license is listed as 'Other' on GitHub, although the topics reference an MIT-licensed community core, so confirm which components fall under which terms before relying on it commercially. It suits government bodies, enterprises and regulated industries that want a Slack-style tool they can host themselves.

Mattermost is an open-core collaboration platform you host yourself, covering team chat, workflow automation, voice calls, screen sharing and AI integrations. This repository is the primary source for core development of the platform. The server is built with Go and React, ships as one Linux binary and depends on PostgreSQL. GitHub lists the license as 'Other'.

Each month, on the 16th, a newly compiled release is published under the MIT license. You can deploy Mattermost on-premises or try it in the cloud. The project highlights use cases such as DevSecOps, incident resolution and IT service desk, and it offers native clients for Android, iOS, Windows, macOS and Linux in addition to the web interface.

Installation options include Docker, Ubuntu, a tar archive, Kubernetes, Helm and an Omnibus package. Developers can build integrations through APIs, webhooks, slash commands, Apps and plugins, and the repository links product and developer documentation, security bulletins and contribution guides. It suits engineering, security and operations teams that want controlled, self-managed team messaging.

Zulip is an open-source team chat application whose defining feature is topic-based threading within channels. The idea is to blend the strengths of email and chat, so that remote and distributed teams can follow several conversations at once and catch up later without losing context. Its topics tag it as a Slack alternative.

The project is developed by a distributed community, with more than a thousand contributors and a steady flow of commits each month, and it says it has put effort into readable, tested code and extensive contributor documentation. The server is a Python web application, and there are web, desktop, built on Electron, and mobile clients, built with React Native. Zulip is used by companies and open-source projects alike, and the README says it is designed for both live and asynchronous communication.

Zulip is licensed under Apache-2.0. You can run the server on your own infrastructure, which gives full control over data, or use the hosted service operated by the project's company. It suits teams that find flat channel-based chat chaotic and want a more structured way to keep discussions organized.

Element Web is a client for Matrix, the open protocol for decentralized messaging. It is the web and desktop application formerly known as Vector and Riot, and it lets people join rooms, chat in teams and communities, and collaborate across Matrix servers rather than inside a single vendor's network.

The client is built with TypeScript on top of the Matrix JS SDK. The README defines support tiers for browsers, covering recent versions of Chrome, Firefox, Edge and Safari on desktop, best-effort handling for ESR and extended-stable releases, and community support for mobile web. For phones and tablets the maintainers recommend the native Element X apps for Android and iOS.

It is released under the AGPL-3.0 license and is typically served from your own web host or used through the hosted app from the vendor, Element. Related products such as Element Call and the Enterprise Server Suite are mentioned as part of the wider Element offering. Changes are tracked on GitHub with regular release cycles.

Openfire is a real-time collaboration server that implements XMPP, also called Jabber, which the project describes as the only widely adopted open protocol for instant messaging. It is written in Java, released under the Apache-2.0 license and maintained as an Ignite Realtime community project.

The project says Openfire is easy to set up and administer while still offering strong security and performance. Organizations use it to run their own messaging infrastructure instead of relying on a proprietary chat vendor, and because XMPP is an open standard, any compatible client can connect to it.

Support is community-based. Documentation lives on the Ignite Realtime site, discussion happens on a Discourse forum, and bugs are tracked in an issue tracker where new users are asked to post through the forum first. Nightly builds are available, translations are managed through Transifex, and the latest release listed is v5.1.2.

This repository contains the Android client app and SDK source for Wildfire IM (野火IM), an instant messaging and real-time audio and video solution maintained by Beijing Wildfire Network Technology. It is intended for secondary development or integration into existing apps. The documentation is in Chinese, and the input lists the license only as other.

Wildfire IM is described as a professional-grade solution with private deployment, a broad feature set, support for all platforms, and easy integration with third-party systems. The family of repositories includes the IM server, this Android app, and an iOS counterpart. Topics mention chat, IM, and VoIP.

An important notice in the README says that, because of anti-fraud compliance requirements, the default protocol stack in this project only connects to the official Wildfire service and cannot connect to self-deployed servers. Users must contact the vendor to obtain a temporary or unrestricted version and replace a library file. This limits its use as a fully independent open-source client.

This repository contains the source code for the Wire server, the back end of the Wire messaging platform. According to the README, it holds all the libraries and services needed to run Wire. The code is written mainly in Haskell and Rust and is licensed under AGPL-3.0, although the Wire trademark and logos are not licensed for use.

The server is split into services. Nginz is a public API reverse proxy, galley manages conversations and teams, brig handles accounts, gundeck is the push notification hub, cannon delivers WebSocket push notifications, cargohold stores assets such as images and files, proxy covers third-party API integration and spar provides single sign-on. Tools include database migration utilities and a Swagger-based backoffice interface called stern.

The project provides build scripts and Dockerfiles for some platforms, a work-in-progress demo mode that runs in memory and documentation that includes a guide for self-hosting your own Wire server. Federation is described as a long-term roadmap item. Wire itself is a commercial messaging product, and the source is published for transparency and self-hosting.

This repository contains the iOS client of Wildfire IM (野火IM), an instant messaging and real-time audio and video solution maintained by a Beijing company. It is both a working chat app and an SDK that developers can integrate into other iOS applications or customize for their own products, and its documentation is written in Chinese.

The project has three parts: a chat client library that provides the messaging capability, a UI kit library of chat interface controls that depends on it, and a demo chat app built on both. The Wildfire IM ecosystem also includes a separate IM server, Android, desktop, web and mini-program clients, an application server, robot server and push server. To run the app you configure the IM server address and the application server address in the project's configuration file.

Private deployment is a core idea, so companies host the server themselves, and the README explains how to trust self-signed certificates by adding them to the app bundle. The code is Objective-C and its licence is listed as other, so check the terms before commercial use. It suits developers building a branded, self-hosted messaging product for iOS.

Twake, published by Linagora, was an open-source digital workplace combining team chat, file storage, a shared calendar, task management, video calls and real-time document collaboration. It was designed to improve organizational productivity, with kanban boards for tasks and a drive for files. This repository is the legacy codebase and is explicitly marked deprecated.

The README states that the repository is no longer actively maintained and directs users to the newer Twake-workplace repository for current features and support. The archived instructions describe running a local instance with Docker Compose, which serves on localhost, redirects to HTTPS and uses a self-signed certificate by default unless you disable SSL certificates in the compose file. The team also offered a hosted SaaS demo, plus documentation, a community forum and Weblate-based translations.

The code is written in TypeScript and licensed under AGPL-3.0. Anyone evaluating the product today should look at the successor project rather than adopt this repository for new deployments. It remains useful mainly for existing installations and as a reference for how the platform was built.