Release 9.0 Native XMPP server foundationNative videoABAC-enforced workspace What's new
The Mattermost alternative

When the mission outgrows Mattermost.

Messaging, voice, video and governed AI on your networks, with native XMPP and Matrix federation, so no one is forced to switch systems.

Built forArmed forcesDefense & intelligenceDefense integrators
Runs onOn-premisesSecure cloudAir-gapped
Book a demo

See Rocket.Chat in action.

A live demo, tailored to how your teams work.

Loading the form…

Comparing quotes?

Trusted by the world's most critical organizations

US Navy eu-LISA General Dynamics Swedish Armed Forces US Army UK Home Office US Air Force Finnish Defence Forces Trafikverket Valtori Swedish National Electrical Safety Board
The platform

One platform. One security model.

Every capability runs inside your boundary, under the same policy.

Unified Communications

Messaging, voice, video and files in one workspace.

Interoperability

Native Matrix and XMPP federation, plus low-side bridges.

Governance & Control

Access, data protection and audit under one policy.

Tactical Edge

Resilient in DDIL environments, from HQ to ATAK.

Governed AI

AI on your models, scoped to each user's access.

Deploy Anywhere

On-premises, secure cloud or air-gapped.

Platform overview →
Search (⌘+K)

AI search

ResultsUPS failover test results
Searching rooms you can access where AI search is enabled
AI answer
Generated with OpenAI-compatible · your-model-in-enclave
PWR DIST A and B run active-active, with failover in under 80ms and at least 45 minutes of UPS coverage [1].
  • If both feeds drop, the system runs on UPS [2].
  • Emma is sharing last week's UPS test logs before the review [2].
  • The reviewers asked to see the UPS test logs [3].
Sources · 3 Messages
Emma Brown@emma.brownToday

Both PWR DIST A and B are in active-active mode. Failover switches in under 80ms, and backup UPS covers a minimum 45-minute window.

Emma Brown@emma.brownToday

Both feeds dropping puts us on UPS. I'll pull the logs from last week's test.

Alex Laurent@a.laurent:agency.euToday

The reviewers will want the UPS test logs as well.

Favorites
Teams
Discussions
Channels
O ops-sector-bravo
O ops-infra1
I intel-assessments
O ops-regional-coordination
F field-coordination
Direct messages
Elena Fischer1
Marco Silva3
Intelligent search
David Smith
E @elena.rossi:allied.int
intel-assessments
Alex Miller03:40 PM
Heads-up: the DoW review for Sector Bravo is tomorrow at 09:00, and power redundancy is on the agenda.
Sarah Hayes03:42 PM
Team, can someone walk me through the power redundancy config? The reviewers are flagging the failover spec.
Sarah Hayes03:43 PM
PDF
Sector-Bravo_Power_Redundancy_Spec.pdf9MB
Alex Laurent@a.laurent:agency.eu03:44 PM
Emma Brown, you own PWR DIST. Please consolidate the findings and assess the risk before the review.
Emma Brown03:46 PM
Both PWR DIST A and B are in active-active mode. Failover switches in under 80ms, and backup UPS covers a minimum 45-minute window. We're well within spec.
B0 replies
Emma Brown03:51 PM
Let's jump on a call and I'll share my screen so we can go through the document together.
Marek Nowakm.nowak@allied.int03:58 PM
That walkthrough answers our reviewers' questions too. Thanks, Emma.
@kenji.tanaka:allied.operations.gov04:02 PM
明日のレビューの前に、こちらの電源冗長化テストの結果も共有します。
Translate
Rocket.Chat AI04:02 PMOnly you can see this message
Translated from JapaneseWe'll also share our power redundancy test results before tomorrow's review.
Message #intel-assessments
←Thread
Emma Brown03:46 PM
Both PWR DIST A and B are in active-active mode. Failover switches in under 80ms, and backup UPS covers a minimum 45-minute window.
Sarah Hayes03:47 PM
What happens to the failover sequence if both feeds drop at once?
Alex Laurent03:48 PM
The reviewers will want the UPS test logs as well.
Emma Brown03:50 PM
Both feeds dropping puts us on UPS. I'll pull the logs from last week's test.
Summarize until here
Rocket.Chat AI03:59 PMOnly you can see this message
I'm summarizing this thread up to the message you selected. I'll let you know once it's ready.
Rocket.Chat AI03:59 PMOnly you can see this message
PWR DIST A and B run active-active, with failover in under 80ms and at least 45 minutes of UPS coverage. If both feeds drop, the system runs on UPS. Open item for the review: Emma to share last week's UPS test logs.
Reply in thread
You
Emma BrownLIVE
New call×
⚲
Enter username or number
Emma Brown
Call
00:00
Emma BrownCalling...
You are sharing your screen
FederateMatrixXMPPMission partnersNative Matrix and XMPP
BridgeMS TeamsLow-side platformsMS Teams and IRC
Tactical edgeTAKForward-deployed teamsInside TAK and ATAK
See it working

Every ally. One workspace.

Your workspace federates with allies over XMPP, agencies over Matrix and forward teams on ATAK. Each joins the channels you share with them, as themselves.

01
Native where Mattermost bridges

Zero trust. Or implied trust.

Mattermost bridges XMPP and Matrix through plugins: a component in the middle both sides have to trust. Rocket.Chat is native on both, so nothing sits in between.

Native federation on both protocols
Allied nationon XMPP
Rocket.Chat
XMPP federation
Matrix federation
Partner agencyon Matrix
real identities · attribution intact · one accreditation scope
Bridge · low side only
MS Teamsplatforms you don't control

01

Native on both protocols

XMPP and Matrix are built into Rocket.Chat and upgrade with it. Nothing extra to run, patch or accredit for either.

02

Proof of who said what

Each sender is verified by their own server, so your access rules and audit trail rely on the real person.

03

MS Teams on the low side

A low-side bridge keeps MS Teams users in the conversation, while classified channels stay native.

Where we differ

Same foundations. Different reach.

Both run self-hosted and air-gapped, with attribute-based access control, at DoW IL2 to IL6. The difference shows the moment you work beyond your own walls.

Rocket.ChatInteroperable by design. Governed by you.
Mattermost
FederationNative XMPP and Matrix.Allies connect server to server, with nothing in between.
FederationA bridge plugin for each.Every message passes through a component both sides must trust.
IdentityEvery sender verified by their own server.You always know who said what.
IdentityAn account the plugin controls.Who said what can't be proven.
EncryptionZero-knowledge end-to-end encryption.Keys stay with the intended recipients.
EncryptionNot native.Messages are readable on the server.
IntegrationsCustom apps and workflows that survive upgrades.Built on Apps Engine, separate from the core.
IntegrationsPlugins may need rebuilding after major upgrades.An upgrade can break what the mission relies on.
VideoNative video from any channel.Teams see each other, on your own servers.
Video1:1 calls only, experimental.Teams can't see each other in a group call.
Guest meetingsPexip meeting chat saved, searchable and auditable.The full record stays in the channel, ready for audit and compliance.
Guest meetingsStart and end notices only.What was said isn't kept, leaving a gap in your audit record.

Source: Mattermost documentation and GitHub, and Pexip documentation, November 2026.

In production

Trusted across U.S. defense.

40+classified programs inside one U.S. systems integrator alone
7active programs inside the U.S. Navy alone
4,000+air-gapped IL6 users at one federal agency alone
Defense industryMulti-Level Security
"What drove us to partner with Rocket.Chat was the opportunity to bring commercial chat functionality into our Multi-Level Security environment."
Stephanie MeckelMLS Solutions Business Area Lead, General Dynamics Mission Systems
Classified engineeringOn-premises
"We needed our engineers to be able to work across multiple programs simultaneously, with absolute confidence that there was zero data leakage between them."
Program ManagerU.S. federal systems integrator
U.S. systems integratorAir-gapped
"With over 40 active programs, we needed a stable, secure way to keep our teams connected."
Infrastructure Services LeadU.S. federal systems integrator
Questions

What teams ask before a demo.

Book a demo ↑
How does a move from Mattermost work?

Our professional services team moves everything with proven migration tools: conversations, files, users and configurations. We run the whole process to keep disruption low, and you can pilot on your own infrastructure before anyone switches.

Will we lose conversation history?

No. Conversation history, files and configurations all come across, with data integrity and the full audit trail preserved.

Mattermost has access control too. What's different?

Both enforce rules inside the workspace. The difference is at its edge: with native XMPP and Matrix federation, partners arrive as real, verified people, so your rules and audit trail rely on who they are, not on an account a bridge plugin controls.

How do we work with allies and agencies on other systems?

Through native federation. Allies on XMPP and agencies on Matrix connect server to server and join the channels you share with them, as themselves, under your rules and audit trail. Allies on Rocket.Chat connect directly, and MS Teams users join through a low-side bridge.

Which networks and accreditations does it run on?

Rocket.Chat runs on NIPR, SIPR and JWICS, at DoW IL2 to IL6. It's hardened on Iron Bank, Platform One Awardable, and available through the AWS Marketplace for the U.S. Intelligence Community (ICMP), where deployments are always air-gapped.

How does pricing work?

Every quote is built around your deployment: your networks, your users and the support you need. Book a demo, or tell us you're comparing quotes, and a specialist will talk you through pricing.