In 2015, four developers in Porto Alegre, Brazil, were building a customer-relationship tool and needed a live-chat widget so shoppers could talk to support. They wrote one. Then they looked at it again and realized the widget was more interesting than the software it was meant to decorate. They put a prototype on GitHub, other people started sending code, and the side project quietly ate its parent. That widget is now Rocket.Chat - an open-source communications platform running on more than 500,000 servers, used by roughly 12 million people, and installed on the networks of the US Navy and the World Bank.
The pitch is deceptively plain. Rocket.Chat does what Slack and Microsoft Teams do - channels, threads, direct messages, voice and video calls, screen sharing - but you can download the source, read every line, and run the whole thing on your own hardware. No one else holds your messages. For a birthday-reminder Slack channel, that sounds like a technicality. For a defense ministry, a hospital, or a bank, it is the entire point.
01 / WHAT IT ACTUALLY ISA chat platform you own, not one you rent
Strip away the vocabulary and Rocket.Chat is team messaging that refuses to live in someone else's cloud unless you specifically ask it to. You can deploy it on a managed cloud, on your own on-premises servers, or fully air-gapped - meaning on a network with no connection to the internet at all. The core product is free and open source. The company makes money on the enterprise edition, hosting, and support, which is the open-core model in its most literal form.
Around that core sits the rest of the toolkit. Omnichannel folds WhatsApp, Facebook Messenger, Instagram, SMS, and website livechat into a single agent inbox, so the same platform that runs internal chat can also run customer support. An Apps Engine and a marketplace of 200+ integrations let teams bolt on their own tools. And federation, built on the Matrix protocol, lets two independent Rocket.Chat servers talk to each other without agreeing on a shared vendor - email's old promise, rebuilt for chat.
02 / THE CUSTOMERSWho actually needs their own chat server
The obvious answer used to be developers and privacy-minded startups. The more interesting answer is institutions that legally cannot use a public cloud. Rocket.Chat's homepage now reads like a procurement list: the US Navy, US Army, US Air Force, the World Bank, Credit Suisse, Deutsche Bahn, Intel. It advertises US Department of Defense authorization to operate up to Impact Level 6 and support for classified networks known by their acronyms - NIPRNet, SIPRNet, JWICS.
That customer base explains a rebrand. Rocket.Chat has started describing itself as a "CommsOS" for mission-critical operations rather than simply team chat. It is a heavier phrase, but it tracks the buyers. When your users include militaries and government agencies, "we physically cannot read your messages" stops being a marketing line and becomes a requirement on a compliance checklist.
Where Rocket.Chat sits vs. the mainstream
| Capability | Rocket.Chat | Slack / Teams |
|---|---|---|
| Open source | Yes | No |
| Self-host / on-prem | Yes | No |
| Air-gapped deploy | Yes | No |
| You own the data | Yes | Vendor-held |
| Cross-server federation | Matrix | No |
Fig 1 - The trade is control for convenience. Rocket.Chat competes where data sovereignty outranks a frictionless signup.
03 / THE PROBLEMConvenience has a hidden invoice
The reason Slack and Teams won the office is that they ask nothing of you: sign up, invite the team, done. The bill comes later and quietly - your conversations, files, and history live on infrastructure you neither see nor govern, under terms you did not write. For most companies that is a fine deal. For a regulated one, it is a liability, and sometimes it is simply illegal.
Rocket.Chat's answer is to move the trust boundary. Instead of trusting a vendor's promise about your data, you trust code you can inspect and hardware you control. Being open source is not just ideology here - it is the security argument. A buyer handling sensitive traffic can have their own engineers read the source before a single message flows through it.
04 / THE EDGEWhy open source is the moat, not the giveaway
Plenty of companies open-source a product and hope for goodwill. Rocket.Chat turned the openness into distribution. More than 1,000 contributors and 30,000-plus GitHub stars mean the software is hardened, translated, and extended by people the company never hired. That community is why a small firm can credibly sell to organizations that would normally demand a much larger vendor.
Its closest rivals are the other self-hosted names - Mattermost and Element, the flagship Matrix client - rather than Slack itself. Against them, Rocket.Chat leans on breadth: omnichannel customer engagement, a large app marketplace, and a push into the highest-assurance government tiers. The bet is that owning the whole communications stack, from internal chat to customer support to cross-agency federation, beats being the best at any single slice.
Deploy anywhere - the range that wins regulated deals
Fig 2 - Most rivals stop at "on-prem." The air-gapped tier is what unlocks defense and classified work.
05 / THE BUSINESSGive away the software, sell the trust
The model is open-core. Anyone can run the free community edition forever. Revenue comes from the Enterprise plan - LDAP and Active Directory, single sign-on, multi-factor authentication, end-to-end encryption, compliance controls - plus managed hosting and support contracts aimed squarely at the regulated buyers who need them. Investors have put in about $37 million across rounds since 2019, backed by New Enterprise Associates, Valor Capital, Monashees, and Endeavor Catalyst, among others.
The team building it fits the product. Rocket.Chat is fully remote, with 150-plus employees - "Rocketeers" - across more than 30 countries, working from an employee handbook and a four-word culture code published openly on the web: Dream, Own, Trust, Share. A distributed company building the tools that let other distributed organizations talk privately has a certain internal logic to it.
06 / THE ARCFrom Porto Alegre to approved-vendor lists
- 2015A side project escapesFour developers release a chat prototype on GitHub; contributors arrive within weeks.
- 2019First institutional moneySeed funding from NEA, ONEVC, and Valor Capital; Omnichannel launches.
- 2020Series AA roughly $19M round funds the enterprise and cloud push.
- 2022Federation via MatrixIndependent servers gain the ability to message across organizations.
- 2023Series A extensionA $10M round led by Alexia Ventures brings total funding to about $37M.
- 2025The CommsOS turnRocket.Chat repositions around defense, government, and critical infrastructure.
07 / THE PLACE IN THE MARKETWinning the rooms the office can't enter
Rocket.Chat is not trying to unseat Slack in the average startup, and it probably never will. Its territory is everywhere the mainstream tools are not allowed to go: the air-gapped facility, the ministry, the ship at sea, the hospital bound by patient-data law. That is a smaller market than "every knowledge worker on earth," but it is a market that pays for the unglamorous things - compliance, sovereignty, source-code review - that never get demoed on a launch stage.
The story is really about open source growing up. A community project that began as a discarded live-chat widget now carries a security clearance, and its founders discovered that "own your data" is not a slogan but a durable line of business. The rebrand to CommsOS is just the invoice catching up to the customer list.