Rocket.Chat is an open-source, self-hostable team communications platform written in TypeScript that gives organisations full ownership of their messaging, voice, and federation infrastructure instead of renting it from a closed SaaS vendor.

What it is

Rocket.Chat is a communications platform for real-time and asynchronous collaboration, built in TypeScript and distributed under an open-source licence that the registry reports as NOASSERTION. It runs as a workspace that a team deploys on its own servers, in the cloud, or on an isolated network, and it combines channel messaging, voice calls, federation between separate installations, and an app platform into a single product. The web app is the primary interface, with companion desktop and mobile clients available for macOS, Windows, Linux, iOS, and Android. The repository has accumulated 46,132 stars and 13,889 forks, and it sits in the Business Software / Collaboration & Communication category with topics covering chat, collaboration, FOSS, real-time messaging, WebRTC, and Meteor.

The concrete problem it solves is data sovereignty in team communication. Organisations that cannot send internal conversations, customer exchanges, or citizen enquiries through a third-party messaging service need somewhere to put that traffic, and Rocket.Chat is the thing they put it on. It replaces hosted chat SaaS for teams whose data-protection requirements rule that route out, and it adds deployment modes those services generally do not offer, including air-gapped installations with no internet access at all. The README explicitly targets organisations with high standards of data protection, and cites Deutsche Bahn, the US Navy, and Credit Suisse as users among tens of millions of people across more than 150 countries.

Key capabilities

• Deployment by Docker, Podman, or Kubernetes, with a Launchpad option that provisions a Kubernetes workspace without managing each dependency individually.
• Air-gapped deployment mode for isolated networks, aimed at high-security and regulated environments.
• End-to-end encryption alongside identity management and role- and attribute-based access control.
• Native federation for communicating and sharing resources across separate Rocket.Chat installations.
• Voice calls and WebRTC-based real-time communication, listed among the core collaboration features.
• Apps-Engine for building custom apps, plus public apps installable from the Rocket.Chat Marketplace.
• Desktop clients distributed through the Mac App Store, Microsoft Store, and Snapcraft, where Linux users install with sudo snap install rocketchat-desktop.

Who uses it and how

• Regulated enterprises and public institutions that must keep messaging inside their own infrastructure; the README names Deutsche Bahn, the US Navy, and Credit Suisse.
• Security-sensitive teams running air-gapped workspaces on networks with no internet access, a configuration the project documents as a supported deployment path.
• Federated deployments where multiple organisations want to exchange messages and resources across independently operated servers rather than joining one shared tenant.
• Engineering and platform teams that deploy through Kubernetes and want monitoring and scaling handled as part of the cluster rather than as a separate appliance.
• Developer teams extending the product through Apps-Engine or installing prebuilt integrations from the Marketplace.

Getting started

Self-hosters deploy through Docker, Podman, or Kubernetes, following the project's deployment guide and checking the system requirements first; Launchpad is offered as a quicker Kubernetes route that avoids managing each dependency by hand. A premium, dedicated cloud hosting option with a service-level agreement exists for teams that would rather not run infrastructure themselves.

How it compares

Among the tools named in the provided facts, Slack is the closest reference point, and Rocket.Chat is positioned as the open-source, self-hostable alternative to that class of hosted messaging product. The distinction the facts support is deployment control: Rocket.Chat can run on your own servers, in the cloud, or air-gapped with no internet access, with end-to-end encryption and federation as documented features rather than add-ons. Cost model differs accordingly, since self-hosting trades subscription fees for infrastructure and operational work.

When to use it — and when not to

A self-hoster must operate the full stack: the server, its database dependency, file storage, and whatever the deployment guide's system requirements demand, plus upgrades and monitoring on an ongoing basis. Teams that want zero operational overhead, or that are happy with a hosted SaaS workspace and have no data-residency constraint, should probably not choose it. Be aware of the rough edges: the licence field reports NOASSERTION rather than a clean identifier, the repository carries 4,023 open issues, and the README excerpt provided here is largely promotional and defers most real detail to external documentation.