RocketChat/Rocket.Chat

What it is

Rocket.Chat is an open-source team communications platform written in TypeScript, aimed at organizations that need to control where their messages live. It covers real-time messaging, voice calls, federation between workspaces, identity management, end-to-end encryption, and role/attribute-based access control deploy and platform overview. Extensibility comes from the Apps-Engine framework and the Marketplace, plus API access for integrations extend and integrate.

The main decision is whether you self-host the server or use a hosted option. Self-hosting is the path the project documents in most detail; desktop and mobile clients connect to a workspace rather than replacing it.

Deploy a workspace

1. Check the system requirements before choosing a method; sizing depends on your workspace and deployment target.
2. Deploy on your own servers with Docker, Podman, or Kubernetes, following the Deployment Guide. On Kubernetes, Launchpad is offered as a quick setup that manages dependencies for you Launchpad.
3. For isolated networks, follow the air-gapped deployment guide. For a hosted workspace without infrastructure management, see the cloud hosting option cloud hosting SLA.
4. Open the web app from the deployed server and create the admin account; then install the desktop client if needed. Linux users can run sudo snap install rocketchat-desktop or get it from Snapcraft desktop install; macOS and Windows builds are on the Mac App Store and Microsoft Store respectively desktop install.

Server development environments are documented separately for Linux, Windows, Mac, and Gitpod server development.

Use constraints

• Running a workspace means operating a server: deployment method, system requirements, backups, and monitoring are your responsibility when self-hosting.
• The repository states an MIT license via its README badge README; the repository metadata reports an unspecified license (NOASSERTION), so confirm the exact licensing terms before redistribution.
• Federation must be enabled explicitly, and air-gapped setups require the separate deployment path rather than a standard install.
• Desktop and mobile clients are distributed through app stores and Snapcraft; they are clients, not standalone chat services.
• Groups that need external integrations should plan for Apps-Engine development or Marketplace apps rather than assuming built-in connectors.

HotRepo's take

Rocket.Chat appeared on the TypeScript daily chart on 2026-11-12 with 54 stars gained and a best position of 16 that day; no all-language daily rank is recorded for the project. The 2015 Hacker News thread drew 155 points and 112 comments at launch, when commenters debated whether self-hosted chat apps could meet Slack-era expectations for integrations, search, uptime, and authentication, while others argued that externally hosted chat was simply not allowed in their organizations launch discussion. Ten years later, the project is still releasing (a 9.0.0 thread appeared in November 2026) and the open questions raised then—operational burden versus control—remain the practical trade-off for adopters.