Rocket.Chat

Key features

• Channel chat with desktop and mobile apps Channel-based team chat with desktop and mobile apps for distributing messaging across the whole team, positioned as a Secure CommsOS for mission-critical operations.[1][2][3]

• Self-hosted Docker to air-gapped deployment Self-hosted deployment with Docker and Docker Compose as the recommended path, plus Kubernetes with the official Helm chart, Podman, OpenShift, and dedicated air-gapped servers.[1][2]

• REST, Realtime, and Livechat APIs Documented extension points for builders: a REST API at /api/v1, a Realtime API over websockets, and a Livechat Widget API, with a downloadable OpenAPI specification for client generation.[1]

• SSO via SAML, OAuth, and LDAP Single sign-on through SAML, OAuth, and LDAP identity providers, with SAML named as the SSO standard and role-based access control for governing who can do what.[1]

• End-to-end encryption and governance End-to-end encryption with compliance-ready message governance for teams that must protect and audit message history inside their own boundary.[1][2]

• Official Slack importer for migration Official Slack workspace importer that migrates users, channels, and messages from Slack into Rocket.Chat via export file upload, URL, or server path.[1]

• Open-core TypeScript and MongoDB stack Open-core TypeScript codebase on Meteor with MongoDB as the database, so teams can read the source and run reviewed builds themselves; enterprise directories carry a separate licence.[1][2]

• Cloud path before self-hosting Managed cloud deployment alongside on-premises and air-gapped options, with a free self-managed workspace and commercial plans for trying before committing infrastructure.[1][2]

Who will love it

• Regulated and mission-critical organizations that must keep message history inside their own boundary: self-hosted and air-gapped deployment keeps chat and data on infrastructure you control.[1][2]

• Teams migrating off Slack with their history intact: the official importer moves users, channels, and messages into Rocket.Chat instead of starting over.[1][2]

• Mid-market and enterprise teams needing sovereign messaging with support: dedicated government and defense plans plus partner and sales channels back the self-managed core.[1][2]

Who should avoid it

• Teams wanting zero-operations hosted simplicity: the recommended Docker Compose path needs a Linux server, domain, firewall rules, and a reverse proxy, and updates and backups are all yours.[1][2]

• Organizations wanting every advanced control in the free tier: it is open core, so enterprise directories and premium identity modules sit behind commercial plans.[1][2][3]

• Teams with no infrastructure or integration capacity: Rocket.Chat assumes you can run MongoDB-backed services and work with APIs, which is real ongoing effort.[1][2]

Alternatives and compatibility