Release 9.0 Native XMPP server foundationNative videoABAC-enforced workspace What's new
Interoperability

Every partner. Every system. No one forced to switch.

Native Matrix and XMPP federation, bridges to MS Teams and your mission systems in one workspace, governed by you.

Federates nativelyMatrixXMPP
Connects toMS TeamsIRCYour systems

Trusted by the world's most critical organizations

US Navy eu-LISA General Dynamics Mission Systems Swedish Armed Forces US Army UK Home Office US Air Force Finnish Defence Forces Trafikverket Valtori Swedish National Electrical Safety Board
01 · Native federation

Every ally, on their own system.

Rocket.Chat federates natively over Matrix and XMPP, server to server. Partners join your channels without moving a single user.

  • No one is forced to switchAllies, agencies and other Rocket.Chat servers join from their own systems, over Matrix or XMPP, the chat standard of Federated Mission Networking.
  • Every message keeps its real senderNo relay bot speaks for anyone, so attribution holds up in any audit.
  • One server to accreditFederation is built in. Nothing extra sits in the middle, and your access rules stay enforced on your own server.
← The architectureHow each ally connects to your serverThe product →What your users see
02 · Bridges

Bring in MS Teams partners. Keep sensitive work native.

Some partners will stay on MS Teams. A bridge keeps them in the conversation, so you get more from the MS Teams investment around you.

  • Nobody has to switchMessages flow both ways between a Rocket.Chat channel and MS Teams. The same approach reaches IRC.
  • No context switchingPeople who work in both open Rocket.Chat right inside MS Teams.
  • Sensitive work never crosses a bridgeBridges stay on the low side, for platforms you don't control. Classified and sensitive channels federate natively.
01
03 · Integrations and apps

Your systems. Your workflows. One workspace.

Connect the systems you already run, or have your developers build apps that run inside your workspace, so Rocket.Chat fits the way you work.

  • Alerts and tickets in the channelIncoming webhooks post alerts from your monitoring. Outgoing webhooks open tickets in your own systems.
  • Built around your workflowsThe REST API, SDKs and custom apps add slash commands, interactive messages and scheduled jobs, under the same permissions and audit.
  • Private or vetted, even air-gappedPrivate apps install only in your workspace and are never published. Review each Marketplace app's access before you install it. Pexip, ClamAV and more run offline.
01
Customers

Trusted to connect allies and agencies.

Classified programs, national agencies and EU institutions run their most sensitive work on Rocket.Chat.

Case study · Inside one US systems integrator · Air-gapped
Coalition exercise
40+classified programs
600+engineers
11classified sites
4,000+participants from 40+ NATO and partner nations · CCDCOE Locked Shields and Crossed Swords

Integrator figures are a case study: scale inside one US systems integrator. Several references are anonymized due to classification.

Defense industryClassified programs
US systems integrator
Rocket.Chat gives us the fine-grained access control we need, keeping teams segmented by classified program, preventing data leaks, and eliminating tool sprawl.
Infrastructure Service LeadName withheld
National agencySweden
Swedish National Electrical Safety Board
Rocket.Chat met our communication needs: secure messaging, audio and video calls, and document sharing. It checked all the security and usability boxes for us.
Jenny NilssonIT Strategist
EU institutionHosted in the EU
eu-LISA
We were looking for a platform that's easy to use, secure, and hosted in the EU. Rocket.Chat on AWS delivered exactly that, enabling us to support real-time collaboration with Member States.
Nadia RosioruInformation Technology Officer