# Rocket.Chat FAQ

> Rocket.Chat is the secure, interoperable-by-design collaboration platform for defense, government and critical infrastructure. Organizations work with every agency, ally and partner, across borders and classification levels, on infrastructure they control.

Source: https://www.rocket.chat/faqs · Last reviewed: 2026-10-16

## Platform

### What is Rocket.Chat?

Rocket.Chat is a secure, interoperable-by-design collaboration platform for defense, government and critical infrastructure. It brings messaging, voice, video, screen sharing, files, apps and governed AI into one workspace that runs on infrastructure you control: on-premises, in a secure cloud or air-gapped. Native Matrix and XMPP federation lets you work with every agency, ally and partner across borders and classification levels, without forcing anyone to switch systems.

Learn more: [Platform overview](https://www.rocket.chat/platform)

### Who uses Rocket.Chat?

Rocket.Chat is used by armed forces, intelligence agencies, federal system integrators, government agencies, EU institutions, first responders and critical infrastructure operators. Customers include the U.S. Navy, eu-LISA, NATO CCDCOE and the Government of British Columbia. More than 12 million people in over 150 countries use Rocket.Chat.

Learn more: [Customers](https://www.rocket.chat/customers)

### What does "interoperable by design" mean for Rocket.Chat?

Interoperable by design means Rocket.Chat is built to connect your organization with partners on their own systems, instead of making everyone join one vendor's cloud. Rocket.Chat federates natively over Matrix and XMPP, connects to MS Teams users through a low-side bridge, and brings mission systems such as ATAK into channels. Each organization keeps its own server, its own data and its own rules.

Learn more: [Interoperability](https://www.rocket.chat/platform/interoperability)

### What can teams do in Rocket.Chat?

In Rocket.Chat, teams message, call, meet on native video, share screens and files, and work in channels, threads and discussions, all in one workspace. On top of that they get governed AI for summaries, translation and search, federation with partner systems, and Apps Engine for building custom apps, workflows and integrations. Everything runs under one set of access controls and one audit trail.

Learn more: [Unified Communications](https://www.rocket.chat/platform/unified-communications)

### Is Rocket.Chat open source?

Yes. Rocket.Chat's core is open source under the MIT license, and its code is public on GitHub with more than 46,000 stars and 1,500+ contributors. Your security team can audit the code your organization runs. Enterprise plans add the governance, compliance, scale and support that regulated organizations need in production.

Learn more: [About Rocket.Chat](https://www.rocket.chat/company/about-us)

### Does Rocket.Chat have desktop and mobile apps?

Yes. Rocket.Chat has apps for Windows, macOS, Linux, iOS and Android, plus a web client, so people reach the same workspace on every screen. Mobile apps encrypt messages and files stored on the device, support biometric or PIN app lock, and let administrators control what push notifications reveal.

Learn more: [Mobile & desktop apps](https://www.rocket.chat/download-apps)

## Governed AI

### What is Governed AI in Rocket.Chat?

Governed AI is a core part of the Rocket.Chat platform, not an add-on. It works inside the conversations your teams already have, on your own models and infrastructure, under the same access rules as your people: every answer is scoped to what each person may see, and nothing leaves your environment. It summarizes and translates conversations, answers from your organization's knowledge, and runs AI agents that act with human approval.

Learn more: [Governed AI](https://www.rocket.chat/platform/governed-ai)

### Can Rocket.Chat AI run on our own models, even air-gapped?

Yes. Rocket.Chat governed AI runs on the model you choose, through any OpenAI-compatible endpoint you host, so it works on-premises, in a secure cloud or fully air-gapped. Public AI services are never in the path, which lets accreditors approve AI on the same terms as the rest of the platform.

Learn more: [Governed AI](https://www.rocket.chat/platform/governed-ai)

### How does Rocket.Chat stop AI from showing people data they shouldn't see?

Rocket.Chat AI acts with each person's own access. Summaries, search results and answers draw only on the channels, messages and knowledge sources that person is allowed to see, so two people asking the same question can get different, correctly scoped answers. Every AI action is logged in the same audit trail as the rest of the platform.

Learn more: [Governed AI](https://www.rocket.chat/platform/governed-ai)

### Can AI agents take actions in Rocket.Chat?

Yes. Your developers build AI agents with the Rocket.Chat Agent Kit or connect them through Rocket.Chat's native MCP server. Agents act on request or run on a schedule, such as drafting a morning situation report, and they propose actions for a person to approve before anything is posted or changed. Humans stay in command, and every run is audited.

Learn more: [Governed AI](https://www.rocket.chat/platform/governed-ai)

### Does Rocket.Chat send our data to public AI services?

No. Rocket.Chat governed AI keeps prompts, conversations and answers inside your perimeter, on the model and infrastructure you run. No data goes to a public AI provider unless you choose to connect one.

Learn more: [Governed AI](https://www.rocket.chat/platform/governed-ai)

### Can Rocket.Chat translate messages from partners?

Yes. Rocket.Chat governed AI translates conversations, so messages from a federated partner can arrive already translated into each reader's language. Coalition and cross-border teams keep working in their own languages, on your own model.

Learn more: [Governed AI](https://www.rocket.chat/platform/governed-ai)

## Interoperability

### Does Rocket.Chat support Matrix federation?

Yes. Rocket.Chat has built-in Matrix federation, so your workspace talks server to server with Matrix-based systems, including Element, without running a separate homeserver. Partners stay on their own platform, and your access rules are enforced on your own server.

Learn more: [Interoperability](https://www.rocket.chat/platform/interoperability)

### Does Rocket.Chat support XMPP?

Yes. Since version 8.7, Rocket.Chat federates natively over XMPP, the protocol behind many defense and coalition chat systems. Allies on XMPP join shared channels from their own servers, with every message tied to its real, verified sender.

Learn more: [Interoperability](https://www.rocket.chat/platform/interoperability)

### Can Rocket.Chat users talk with people on MS Teams?

Yes. Rocket.Chat connects to MS Teams through a low-side bridge, so contractors, suppliers and partners on MS Teams stay in the loop without moving. Your sensitive and classified work stays on Rocket.Chat, while bridged conversations carry the context partners need.

Learn more: [Interoperability](https://www.rocket.chat/platform/interoperability)

### How does Rocket.Chat connect different agencies and allies?

With Rocket.Chat, each agency or ally runs its own server and federates with the others, so no one gives up control of its data or infrastructure. Shared channels connect the teams that need to work together, each side applies its own access rules, and every message carries its real sender. Nothing sits in the middle, and there is no extra server to accredit.

Learn more: [Interoperability](https://www.rocket.chat/platform/interoperability)

### What integrations and APIs does Rocket.Chat offer?

Rocket.Chat connects to the systems you already run through REST and real-time APIs, incoming and outgoing webhooks, SDKs and Marketplace apps. Apps Engine lets your developers build custom apps, workflows and integrations, including private apps that run only in your workspace. Common connections include identity providers, Jira, GitHub, GitLab, ticketing, case management and GIS tools.

Learn more: [Interoperability](https://www.rocket.chat/platform/interoperability)

### Does Rocket.Chat work with ATAK?

Yes. Rocket.Chat brings ATAK into the same channels as headquarters, so patrol reports and position updates from the field land where planners and commanders already work. Messages flow both ways, under the same permissions, audit trail and boundary as everything else in Rocket.Chat.

Learn more: [Deploy Anywhere](https://www.rocket.chat/platform/deploy-anywhere)

### Does Rocket.Chat work with Pexip for video meetings?

Yes. Rocket.Chat integrates with Pexip, so secure video meetings start from any channel. Persistent chat and the call record stay in the channel or discussion where the meeting started, which helps organizations that must keep those records. Rocket.Chat also includes native video.

Learn more: [Rocket.Chat and Pexip](https://www.rocket.chat/pexip)

## Deployment

### Where can Rocket.Chat be deployed?

Rocket.Chat runs on-premises, in a secure cloud or fully air-gapped, from headquarters to the tactical edge. Every option runs the full platform under the same controls, so you can mix environments with one security review. Rocket.Chat is also available on AWS, including AWS GovCloud (US).

Learn more: [Deploy Anywhere](https://www.rocket.chat/platform/deploy-anywhere)

### Can Rocket.Chat run in a fully air-gapped network?

Yes. Rocket.Chat runs fully offline with no external dependencies once deployed, including messaging, calls, file storage, apps and governed AI on your own model. At one U.S. federal agency alone, more than 4,000 people use Rocket.Chat on an air-gapped platform at Impact Level 6.

Learn more: [Deploy Anywhere](https://www.rocket.chat/platform/deploy-anywhere)

### Does Rocket.Chat work at the tactical edge on poor links?

Yes. Rocket.Chat is built for disconnected, intermittent and limited links, from fiber to SATCOM to HF radio. When the link drops, messages queue on the device and sync as soon as it returns, so field teams and headquarters stay in the same conversation.

Learn more: [Deploy Anywhere](https://www.rocket.chat/platform/deploy-anywhere)

### Can we run Rocket.Chat on AWS, including GovCloud?

Yes. Rocket.Chat runs in your own AWS account, in commercial Regions, AWS GovCloud (US) or air-gapped AWS environments, and you can buy it through AWS Marketplace. Your data stays in your account and your chosen Region.

Learn more: [Rocket.Chat on AWS](https://www.rocket.chat/aws)

### How does Rocket.Chat scale and stay available?

Rocket.Chat scales from a single server to multiple instances behind a load balancer, and to microservices on Kubernetes for very large deployments. High availability and database failover keep it running when a node fails, and Out-of-Band Failover keeps command communicating if the primary network is compromised.

Learn more: [Deploy Anywhere](https://www.rocket.chat/platform/deploy-anywhere)

### Can Rocket.Chat be our out-of-band communication channel?

Yes. Many organizations run Rocket.Chat as an out-of-band channel that stays up when primary systems are down or compromised, for example during a cyberattack. Because it runs on infrastructure you control, incident teams can coordinate without relying on the systems under attack.

Learn more: [Out-of-band Communication](https://www.rocket.chat/use-case/out-of-band-communication)

### How is Rocket.Chat installed, and what does it need?

Rocket.Chat installs with Docker, Kubernetes or Launchpad, or from AWS and DigitalOcean. A small workspace runs on a modest server, while large deployments use multiple instances or microservices sized with our team. Production deployments for regulated organizations are planned with our engineers or a certified partner.

Learn more: [Install & update](https://www.rocket.chat/install)

## Security & compliance

### How does Rocket.Chat keep our data sovereign?

With Rocket.Chat, you decide where every message, file and AI answer is stored, because the platform runs on infrastructure you control. Rocket.Chat as a vendor has no access to your deployment, and federation lets you work with partners without copying your data into anyone else's cloud.

Learn more: [Sovereign Collaboration](https://www.rocket.chat/use-case/sovereign-collaboration)

### Can all our data stay in one country, or inside the EU?

Yes. Rocket.Chat can run entirely in the country, region or data center you choose, including fully inside the EU, so it meets national data residency and localization rules. eu-LISA, the EU agency for large-scale IT systems, runs Rocket.Chat for more than 1,200 users across EU Member States alone, hosted in the EU.

Learn more: [Sovereign Collaboration](https://www.rocket.chat/use-case/sovereign-collaboration)

### Is Rocket.Chat GDPR compliant?

Yes. Rocket.Chat supports GDPR compliance with a Data Processing Agreement that includes the EU Standard Contractual Clauses and documented technical and organizational measures. Self-hosting in the EU gives you full control over personal data, retention and deletion. Rocket.Chat is ISO/IEC 27001 certified.

Learn more: [Trust Center](https://trust.rocket.chat/)

### Which security certifications does Rocket.Chat hold?

Rocket.Chat holds SOC 2 Type II and ISO/IEC 27001 certifications, and it runs at up to Impact Level 6 (IL6) for U.S. defense. It conforms to WCAG 2.1 Level AA for accessibility. Reports and security documentation are available in the Rocket.Chat Trust Center.

Learn more: [Trust Center](https://trust.rocket.chat/)

### Does Rocket.Chat offer end-to-end and post-quantum encryption?

Yes. Rocket.Chat offers end-to-end encryption for direct messages and private channels, with keys held on members' devices, and post-quantum encryption to protect against harvest-now, decrypt-later attacks. Data is also encrypted in transit and on mobile devices at rest.

Learn more: [Governance & Control](https://www.rocket.chat/platform/governance-control)

### Can Rocket.Chat run on classified networks?

Yes. Rocket.Chat runs on classified networks, including U.S. NIPRNet, SIPRNet and JWICS, and in air-gapped environments for allied defense and intelligence. Inside one U.S. systems integrator alone, more than 40 classified programs run on Rocket.Chat, each kept apart from the others.

Learn more: [Defense & Intelligence](https://www.rocket.chat/industry/defense-and-intelligence)

### How does Rocket.Chat control who sees what?

Rocket.Chat combines role-based access control with attribute-based access control (ABAC), so membership follows each person's clearance, nationality or program. ABAC re-checks access on a schedule and removes people whose attributes change, classification banners mark every channel, and deactivating an account ends sessions immediately. Rocket.Chat works with your own attributes or with Virtru.

Learn more: [Governance & Control](https://www.rocket.chat/platform/governance-control)

### Does Rocket.Chat have audit logs and data loss prevention?

Yes. Rocket.Chat keeps audit logs of messages, administrator actions and security settings, including edited and deleted messages, and exports them for investigations. Data loss prevention catches sensitive data such as personnel IDs before it spreads, retention policies prune content on your schedule, and uploads are scanned for malware.

Learn more: [Governance & Control](https://www.rocket.chat/platform/governance-control)

### Which sign-in methods does Rocket.Chat support?

Rocket.Chat supports LDAP and Active Directory, SAML 2.0, OAuth and OpenID Connect single sign-on, multi-factor authentication including phishing-resistant options, and certificate-based sign-in. It syncs users and groups from your directory, so access is granted and removed in one place.

Learn more: [Governance & Control](https://www.rocket.chat/platform/governance-control)

### Is Rocket.Chat FedRAMP authorized, and does it align with NIST?

Rocket.Chat is usually self-hosted inside your own authorization boundary, so it is assessed as part of your system's ATO rather than as a FedRAMP cloud service. It aligns with NIST SP 800-53, NIST SP 800-171 and Zero Trust guidance, and it runs at up to IL6 for U.S. defense. For the current status of any hosted offering, ask our government team.

Learn more: [Talk to sales](https://www.rocket.chat/sales-contact)

## Who it's for

### Is Rocket.Chat built for defense and intelligence?

Yes. Rocket.Chat is built for armed forces and intelligence agencies that work across classification levels and with allies. It runs air-gapped and at the tactical edge, federates natively with coalition systems over Matrix and XMPP, and enforces access by clearance and program. Customers include the U.S. Navy and NATO CCDCOE, which runs Locked Shields on Rocket.Chat.

Learn more: [Defense & Intelligence](https://www.rocket.chat/industry/defense-and-intelligence)

### Can government agencies and EU institutions use Rocket.Chat?

Yes. National ministries, EU institutions, regional and city governments use Rocket.Chat to keep official communication under their own control. eu-LISA connects teams across EU Member States, and the Government of British Columbia runs it on its own private cloud.

Learn more: [Public Sector](https://www.rocket.chat/industry/public-sector)

### Does Rocket.Chat support emergency management and first responders?

Yes. Rocket.Chat connects emergency managers, first responders and partner agencies in one place during an incident, even when primary networks fail. Message auditing supports after-action reviews and reimbursement claims. Bridge 4 Public Safety connects more than 400 agencies on one Rocket.Chat-based app alone.

Learn more: [Emergency Preparedness](https://www.rocket.chat/use-case/emergency-preparedness)

### Is Rocket.Chat used in critical infrastructure?

Yes. Utilities, energy, transport and other critical infrastructure operators use Rocket.Chat for daily operations and as an out-of-band channel during incidents. Contractors, regulators and emergency services join from their own systems, and every message stays on infrastructure the operator controls.

Learn more: [Critical Infrastructure](https://www.rocket.chat/industry/critical-infrastructure)

### How do federal system integrators use Rocket.Chat?

Federal system integrators run Rocket.Chat inside their programs to keep each program's people and data apart on one platform, often air-gapped. Inside one U.S. systems integrator alone, more than 40 classified programs run on Rocket.Chat.

Learn more: [Federal System Integrators](https://www.rocket.chat/industry/federal-system-integrators)

### Is Rocket.Chat a secure alternative to WhatsApp or Signal for official work?

Yes. Rocket.Chat gives official teams the ease of a consumer messenger with what consumer apps can't offer: your own infrastructure, records you can audit and retain, access tied to your directory, and federation with partner organizations. Consumer apps are built for private use and keep official records outside your control.

Learn more: [Sovereign Collaboration](https://www.rocket.chat/use-case/sovereign-collaboration)

## Comparisons

### How does Rocket.Chat compare with Mattermost?

Rocket.Chat and Mattermost are both open-source, self-hosted collaboration platforms used in defense, and both are mature choices. Rocket.Chat stands out where you must work with partners on other systems: it federates natively over Matrix and XMPP and bridges to MS Teams on the low side. It also offers governed AI on your own models, ABAC with clearance-based access, and native video.

Learn more: [Interoperability](https://www.rocket.chat/platform/interoperability)

### How does Rocket.Chat compare with Element and other Matrix apps?

Element is a strong Matrix-native messenger with end-to-end encryption, used by several European governments. Rocket.Chat federates natively with Matrix, so your teams can work with Element users directly, and it also federates over XMPP and bridges to MS Teams. It adds governed AI, ABAC, audit and DLP, Apps Engine for custom apps and workflows, and tactical edge support in one platform.

Learn more: [Interoperability](https://www.rocket.chat/platform/interoperability)

### How does Rocket.Chat compare with Wire?

Wire is built around end-to-end encryption on every conversation by default, which suits teams whose first priority is private messaging and calls. Rocket.Chat is a broader collaboration platform: end-to-end and post-quantum encryption where you need it, plus native Matrix and XMPP federation, governed AI, audit and DLP, and deployment from headquarters to the tactical edge.

Learn more: [Platform overview](https://www.rocket.chat/platform)

### How does Rocket.Chat compare with MS Teams?

MS Teams runs in Microsoft's cloud as part of Microsoft 365. Rocket.Chat runs on infrastructure you control, including air-gapped and classified networks, and needs no Microsoft 365 license. The two can coexist: Rocket.Chat's low-side bridge keeps MS Teams users in the loop while sensitive work stays on Rocket.Chat.

Learn more: [Interoperability](https://www.rocket.chat/platform/interoperability)

### How does Rocket.Chat compare with Slack?

Slack is a cloud service, including GovSlack for U.S. government. Rocket.Chat gives you a similar channel-based workspace that you deploy on-premises, in a secure cloud or air-gapped, with native federation to Matrix and XMPP partners and governed AI on your own models. You can import Slack workspaces into Rocket.Chat.

Learn more: [Platform overview](https://www.rocket.chat/platform)

### Is Rocket.Chat an alternative to Skype for Business Server?

Yes. Rocket.Chat is a modernization path and an alternative for organizations on Skype for Business Server, which reached end of support on 14 October 2025. It covers chat, presence, persistent chat, voice and meetings on your own servers, adds governed AI, and keeps MS Teams contacts reachable through a low-side bridge.

Learn more: [Skype for Business Server alternative](https://www.rocket.chat/skype-for-business-alternative)

## Plans & getting started

### What plans does Rocket.Chat offer, and how much does it cost?

Rocket.Chat offers three enterprise plans, Commercial, Government and Defense, priced to your deployment, users and compliance needs. Every new deployment starts on Starter, free for up to 50 users. Past 50 users, you upgrade to a paid plan or downgrade to Community Edition. Voice calls, native video meetings and mission critical support are available as add-ons.

Learn more: [Plans](https://www.rocket.chat/plans)

### What is the difference between Community Edition and the paid plans?

Community Edition is Rocket.Chat's free, open-source edition for hobby projects and communities, not for regulated or business-critical operations. The paid plans add what production needs: unlimited users, single sign-on, advanced governance and Zero Trust access controls, DLP, federation, high availability, governed AI and enterprise-grade support.

Learn more: [Get started](https://www.rocket.chat/get-started)

### How do we evaluate and buy Rocket.Chat?

Start by talking to our team: we map your environments, partners and compliance needs, then run a pilot on your own infrastructure or a guided evaluation hosted by us. Rocket.Chat can be bought directly, through certified partners, through AWS Marketplace, and through U.S. government contract vehicles.

Learn more: [Talk to sales](https://www.rocket.chat/sales-contact)

### Can we migrate to Rocket.Chat from Slack or MS Teams?

Yes. Rocket.Chat imports users, channels, messages and files from Slack exports. Moving from MS Teams is usually phased: teams start on Rocket.Chat while the low-side bridge keeps them connected with colleagues still on MS Teams, so nobody loses contact during the move.

Learn more: [Interoperability](https://www.rocket.chat/platform/interoperability)

### What support does Rocket.Chat provide?

Rocket.Chat enterprise plans include enterprise-grade support, with mission critical support available as an add-on for round-the-clock coverage and priority response. Professional services help with architecture, integrations, hardening and accreditation, directly or through certified partners.

Learn more: [Plans](https://www.rocket.chat/plans)

### Will we be locked in to Rocket.Chat?

No. Rocket.Chat is open source under the MIT license, runs on infrastructure you own, and uses open protocols such as Matrix and XMPP. Your data stays in your environment and can be exported in standard formats, so you keep control of your communications whatever you decide later.

Learn more: [About Rocket.Chat](https://www.rocket.chat/company/about-us)
