Rocket.Chat
Rest of world Report an errorPanel rating · 6 judges · How to read the stars
Category median
Sovereignty: 3 of 6 dimensions proven
0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Rocket.Chat Technologies Corp. · www.rocket.chat
Compare with Mattermost → Report an error on this page Is this your product? →
Link to this page
Add ?theme=dark to the image address for dark backgrounds.
The badge shows the category and the month of the latest evaluation, and EU-Made where
that is the product’s provenance. It never shows a score.
Rocket.Chat at a glance
- Vendor
- Rocket.Chat Technologies Corp.
- Headquarters
- Not stated on the vendor’s pages as of 16 Nov 2026
- Data hosting
- Not stated on the vendor’s pages as of 16 Nov 2026
- Free plan
- Not stated on the vendor’s pages as of 16 Nov 2026
- Panel verdict
- The AI panel rates Rocket.Chat 3/5, the mean of 6 judges. Rocket.Chat is a business instant messaging platform that scores highest on deployment control, at 9, and encryption and access, at 8 to 9, and lowest on sovereignty, 2 to 4, and pricing transparency, 1 to 2. how scores are made
- As of
- Vendor pages captured 31 Aug 2026 to 16 Nov 2026; evaluated by the panel 18 Nov 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Rocket.Chat is a business instant messaging platform that scores highest on deployment control, at 9, and encryption and access, at 8 to 9, and lowest on sovereignty, 2 to 4, and pricing transparency, 1 to 2. Custody is the strength judges name most: self-hosting on Docker Compose, Podman or Kubernetes, an MIT-licensed core with premium components licensed, a documented air-gapped path, native Matrix and XMPP federation, and a free Starter workspace on customer infrastructure up to 50 users. The weak scores share two causes: no public per-user price for the Commercial, Government or Defense tiers, only a "Get pricing" contact, and pages that never state where the vendor's managed cloud stores data by default while the contracting entity sits in Wilmington, Delaware. The sovereignty spread from 2 to 4 reflects how much weight each judge gave the selectable EU-hosted sovereign cloud and self-hosting against that unstated default. Elsewhere, messaging core, governance and discovery, and integrations cluster at 6 to 7, with no public information on legal hold, eDiscovery export, or SCIM provisioning.
Speaks for it
- Deployment control scores sit at 9, on self-managed deployment via Docker Compose, Podman or Kubernetes with a documented air-gapped path.
- End-to-end encryption for private and direct conversations is documented to named algorithms and can be forced on every new private room from version 8.8.0.
- A free Starter workspace runs on customer infrastructure for up to 50 users, limited to one workspace per organization.
- Retention is documented at global and per-room levels with a warning shown to users wherever a policy applies.
- Native Matrix and XMPP federation plus vendor-documented migration services give a path in and out.
Held against it
- No per-user price is public for the Commercial, Government or Defense tiers, which route through a "Get pricing" contact.
- Sovereignty scores sit at 2 to 4, with the contracting entity in Wilmington, Delaware and no stated default data location for the vendor's managed cloud.
- We found no public information on legal hold or an eDiscovery export covering edits and deletions.
- Encrypted messages do not appear in search, federated rooms are exempt, and encrypted content cannot be audited or monitored.
- Air-gapped deployment requires a paid plan, and self-hosted services report usage data to the vendor by default.
Best for
- You need your workspace and its archive inside your own perimeter, self-managed on Docker Compose, Podman or Kubernetes.
- You need end-to-end encryption for private and direct conversations that the server can make mandatory for every private room from version 8.8.0.
- You want to pilot on a free Starter workspace of up to 50 users on your own hardware, limited to one workspace per organization.
- You need granular retention with a visible warning to users in affected rooms, ready for review with a works council.
Avoid if
- You need to compute an annual invoice from public pages before engaging sales.
- Your procurement requires an EU-based contracting entity — the captured terms place it in Wilmington, Delaware.
- You plan to build on Marketplace apps, which the vendor or an app vendor may remove at any time.
- You expect the free tier to cover the whole product — premium components sit behind a licence and air-gapped deployment requires a paid plan.
The scores
| Criterion | Panel median |
|---|---|
| Channels, threads & search | 3.5 of 5 |
| Encryption & access control | 4 of 5 |
| Retention, discovery & co-determination | 3 of 5 |
| Deployment & data custody | 4.5 of 5 |
| Integrations & extensibility | 3.5 of 5 |
| European sovereignty | 2 of 5 |
| Pricing transparency | 1 of 5 |
Channels, threads & search
Show reasoningHide reasoning
How this is scored
The daily surface: channel model, threading, mentions, files, and whether search can find a decision made eighteen months ago.
0 — Not a team chat: no persistent channels or group conversations, only notifications or one-off messages.
3 — Group chats or channels and direct messages, file sharing, and search over messages.
5 — Public and private channels, threaded replies, mentions and reactions, file sharing with previews, and search across message history.
8 — Cross-organisation or guest channels with clear boundaries, message editing history, pinned and saved items, search with filters by channel, person and date, and unlimited history or a documented history limit per plan.
10 — The archive is a working knowledge base: search that ranks well across years, threads that stay readable, channel lifecycle management (archive, rename, merge) without losing history, and export of a conversation in a form a human can read.
The Team Lead
Public, private and password-protected channels with real threading — following and unread filters, search inside the threads panel, permalinks that jump straight to a reply — and messages are never deleted by default, which is exactly the archive behaviour I want. Archiving leaves the channel findable by admins, and message search and export is claimed. I found no public information on search filters by person or date, on message edit history, or on the export format a human would actually read. 4 5 2 8
The Security Officer
Public and private invitation-only channels, threads on by default with follow notifications, per-thread search and expand-and-collapse, reactions, and channel archiving that admins can still find in the directory are all documented, and messages are never deleted by default, so history is effectively unlimited. Search across messages and threads with jump-to-message behaviour is described, though we found no public information on message editing history, saved items, or search filters by channel, person and date. 4 5 2 8
The Works Council Advocate
Public and private channels with invitation control, threads that follow, filter and search themselves, message search with jump-to-message, archived channels that admins can still find through the directory, and a default where messages are never deleted — the record stays whole unless an administrator prunes it. Guest users exist as a type and Matrix and XMPP federation give cross-organisation rooms. We found no public information on search filters by channel, person and date, on message edit history, or on saved items, which holds this below the top band. 4 5 8 3 1
The Compliance Counsel
Public, private, password-protected and invitation-only channels, threads on by default with follow and unread filters, search inside threads, and a stated default under which messages are never deleted give the workspace a durable, searchable record. Channels can be archived and remain findable to administrators through the directory, and pinned items are carried through retention exclusions; we found no public information on message editing history or search filters by channel, person and date, and the documented message search and export names no export format. 4 5 8 2
The Platform Engineer
Channels come in public, private, password-protected, encrypted, broadcast and read-only flavours with per-channel settings, threads are enabled by default with follow/unfollow, panel filters and search inside threads, and history is unlimited by default because messages are never deleted unless a policy says so. Search is documented as covering public channels and threads, though encrypted rooms are excluded from results, and we found no public information on message edit history or on filtering search by person and date. 4 5 2 7
The Skeptic
Public and private channels, threads enabled by default with their own search and follow behaviour, reactions, pinned messages and an auto-created general channel are all documented, and archived channels remain findable by administrators through the Directory. The stated default is that messages are never deleted, so the history cap I go looking for appears instead as a documented default of permanent retention. We found no public information on message edit history, search filters by channel, person or date, or merging channels without losing history. 4 5 2 8
Encryption & access control
Show reasoningHide reasoning
How this is scored
What is encrypted and against whom, plus who can reach which room. Judged on documented mechanism, since "encrypted" in this category usually means the vendor holds the keys.
0 — The vendor states that messages are transmitted or stored unencrypted.
3 — Encryption in transit stated, with admin and member roles.
5 — Encryption in transit and at rest stated, admin roles and private channels, guest accounts limited to the channels they are invited to, and SSO or two-factor authentication.
8 — Optional end-to-end encryption for direct messages or private rooms with the trade-offs named, or customer-managed encryption keys; device or session management an admin can revoke, granular permissions per channel, and documented key handling.
10 — End-to-end encryption as a first-class mode — documented or open cryptography, cross-device key management that ordinary users survive, identity verification, and the vendor stating plainly what it cannot decrypt.
The Team Lead
End-to-end encryption for private and direct conversations with the cryptography documented down to named algorithms and key derivation, a mnemonic recovery phrase instead of raw key exports, forced encryption for private rooms from version 8.8, and mobile push carrying only the encrypted payload. The trade-offs are stated plainly: encrypted rooms do not appear in search, federated rooms are exempt, bots may be locked out, and losing all keys loses the conversation. I found no public information on identity verification between users or a plain statement of what the vendor itself cannot decrypt. 6 7 7 2
The Security Officer
End-to-end encryption is documented to a specification — AES-GCM 256-bit keys, a mnemonic recovery phrase that re-derives the master key, room key reset restricted to owners and administrators, encrypted push payloads decrypted only on the device, and a server-side setting from version 8.8.0 that forces encryption on every private room and rejects unencrypted creation attempts — with MFA, custom password policies and granular role-based access alongside. The trade-offs are named honestly, including that federated rooms are exempt, encrypted messages do not appear in search, and encrypted content cannot be audited or monitored. I hold it below the top level because we found no public information on device or identity verification, no administrator revocation of sessions, and no plain statement of what the vendor itself cannot decrypt. 6 7 7 9 2
The Works Council Advocate
End-to-end encryption for private and direct conversations is documented down to the algorithms, keys sit encrypted on the server and are re-derived from a user's recovery phrase, and from version 8.8 private rooms can be forced encrypted with the server rejecting unencrypted creation even through the API. The vendor states plainly that encrypted content cannot be audited or monitored, and names the trade-offs honestly: no search results, no bots, no federation. We found no public information on identity verification or end-to-end encryption for public rooms, so it stops short of the top level despite solid role-based access control, SSO, LDAP and MFA. 6 7 7 2 9
The Compliance Counsel
End-to-end encryption for private and direct conversations is documented down to key derivation, algorithms, server-side storage of the encrypted private key, mnemonic recovery, and forced encryption of every newly created private room from version 8.8.0, with the trade-offs stated plainly — encrypted content cannot be audited or monitored, and encrypted messages do not appear in search. Public and federated rooms are stated as not covered, and we found no public information on identity verification between users or administrator revocation of device sessions. 6 7 7 2
The Platform Engineer
End-to-end encryption for private and direct conversations is documented down to the algorithms — AES-GCM 256, RSA-OAEP 2048, PBKDF2 at 100,000 iterations — with keys recovered via a mnemonic phrase, push payloads decrypted on the device, and private-room encryption enforceable server-side since release 8.8.0. The trade-offs are named plainly: encrypted content cannot be audited, encrypted messages do not appear in search, federated rooms are exempt, and losing all session keys makes a conversation permanently inaccessible. Granular role-based access control, SSO, LDAP, SAML and MFA round out the access side. 6 7 9 2 7
The Skeptic
End-to-end encryption for private rooms and direct messages is specified down to named algorithms and key storage, and can be made mandatory for every private room from version 8.8.0 with the server rejecting unencrypted creation, including via the API. The trade-offs I go looking for are written out plainly: encrypted messages do not appear in search results, encrypted content cannot be audited or monitored, federated rooms are exempt, and losing all session keys makes a conversation permanently inaccessible. Granular roles, invite-only private channels, SSO via LDAP, SAML 2.0 and Active Directory, and MFA are all evidenced; we found no public information on identity verification for keys or admin-revocable device and session management. 6 7 7 2 9
Retention, discovery & co-determination
Show reasoningHide reasoning
How this is scored
The archive as a legal object: retention policies, export for discovery, audit, and the monitoring features a works council will ask to have switched off under BetrVG §87(1) no. 6.
0 — A messenger with no organisation-level administration: each user controls their own history, and the organisation has no central export or retention.
3 — Admin export of workspace data or a history setting, with users controlling their own status.
5 — Configurable retention for messages and files, admin export of workspace data in a documented format, and an audit log or activity log of administrative actions.
8 — Per-channel retention executed per policy, legal-hold and eDiscovery export including edits and deletions, a full admin audit trail, and presence, read receipts or activity analytics switchable off organisation-wide.
10 — Built to pass a works agreement and a subpoena on the same day: granular retention with documented deletion, discovery export a lawyer can use, complete audit, and individual productivity scoring stated as not part of the product.
The Team Lead
Retention is genuinely granular — global and per-room policies with exclusions for pinned messages, threads and discussions, files-only mode, admin-only permissions by default, and deletion mechanics documented down to the thirty-day trash window before permanent removal. Tamper-evident audit logs including across federated partners, plus a user-visible warning whenever a pruning policy is active, which a works council will actually appreciate. I found no public information on legal hold, on discovery export covering edits and deletions, or on switching read receipts and presence off organisation-wide. 8 8 2 1
The Security Officer
Retention is unusually well documented: global and per-room policies with exclusions for pinned messages, threads and discussions, configurable pruning frequency via cron, a thirty-day trash collection before permanent removal, files that cannot be restored, admin-only permissions by default, and a user-visible warning whenever a policy applies — co-determination done properly. Tamper-evident audit logs, including across federated partners, and message search and export are listed. We found no public information on legal hold, an eDiscovery export covering edits and deletions, or organisation-wide switch-off of presence and read receipts. 8 1 2 8 8
The Works Council Advocate
Retention here is deletion rather than hiding: global and per-room policies prune messages and files, deleted messages spend thirty days in a trash collection before a TTL index removes them permanently, and deleted files cannot be restored by the vendor at all; users are warned inside the room when a policy applies, which is transparency I can take into a works agreement. Tamper-evident audit logs, audit across federated partners, and message search and export are documented. We found no public information on legal hold or eDiscovery export including edits and deletions, on switching read receipts, presence or activity analytics off organisation-wide, or on any statement about individual productivity scoring — and omnichannel messages sit outside the retention policy with separate controls. 8 8 8 2 1 9
The Compliance Counsel
Retention is administered like a legal object: global and per-room policies split across channels, private groups and direct messages, exclusions for pinned messages, threads and discussions, policy permissions restricted to administrators by default, and a visible warning to users where pruning is active — alongside tamper-evident audit logs that extend across federated partners. We found no public information on legal hold or eDiscovery export; the trash collection preserves deleted messages for thirty days before permanent removal, uploaded files are not kept at all, and the documented export names no format a lawyer could work from. 8 8 1 2
The Platform Engineer
Retention is documented at global and per-room levels with exclusions for pinned messages, threads and discussions, files-only mode, cron control over pruning, a 30-day trash collection before permanent removal, admin-only permissions by default and a user-visible warning in affected rooms. Tamper-evident audit logs are claimed including across federated partners, and message search and export appear among the compliance features, but we found no public information on legal hold or eDiscovery export, or on switching read receipts or activity analytics off organisation-wide. 3 1 2 8
The Skeptic
Retention runs at global and per-room level with exclusions for pinned messages, threads and discussions, deletion frequency configurable down to a cron expression, manual pruning with date and user filters, a 30-day trash copy for deleted messages, and a warning shown to users when a policy applies — unusually honest toward the monitored. Tamper-evident audit logs including federated partners, and message search and export, are documented. We found no public information on legal hold, eDiscovery export covering edits and deletions, or an organisation-wide switch for read receipts, presence or activity analytics. 8 8 8 2 1
Deployment & data custody
Show reasoningHide reasoning
How this is scored
Whether the customer can hold their own archive: self-hosting, private cloud, open source, federation, and what an exit actually looks like.
0 — The terms state that the customer's messages cannot be exported or are not returned when the account ends.
3 — Cloud service with an admin export of messages and files.
5 — Cloud service with a documented full export of messages, files and channel structure, or a choice of hosting region, a dedicated instance or a private-cloud option.
8 — A self-hosted edition close to feature parity, or an open-source core with a documented upgrade path, plus complete export including files and metadata.
10 — Custody is the customer's: open-source or source-available server, self-hosting supported as a first-class deployment, open protocol or federation, and a migration path in and out that the vendor documents rather than resists.
The Team Lead
Three deployment models with self-managed as a first-class citizen: Docker, Podman and Kubernetes, a free Starter workspace of up to fifty users on your own hardware, and a documented air-gapped path. The core is MIT-licensed with code on GitHub, a premium license grants full codebase access and audit rights, Matrix and XMPP federation are native, and migration services move workspaces in and out. The catch is that premium features sit behind a license and air-gapped requires a paid plan, so the free self-hosted build is not the whole product. 10 11 1 14
The Security Officer
Custody can genuinely be the customer's: three deployment models, self-management with Docker Compose, Podman or Kubernetes, an air-gapped guide that even documents building a fully free version from the public repository, native Matrix and XMPP federation, migration and workspace-merge services, and terms stating the customer keeps ownership of their data — with a premium license granting access to the full codebase and code audits. I take a point off because the free build ships without premium components, and we found no public information on a documented complete export format including files and metadata. 3 10 11 1 14 2
The Works Council Advocate
Custody can be entirely the customer's: a self-managed deployment on Docker Compose, Podman or Kubernetes with a free Starter workspace up to 50 users, a documented air-gapped path including a FOSS build route from GitHub, an MIT-licensed core, native Matrix and XMPP federation, and both migration services and a documented upgrade path without data loss. Two things belong in the agreement before signing: premium components sit behind a licence and air-gapped deployment is paid-only, and self-hosted workspaces report usage data to the vendor by default unless a written agreement provides otherwise. 10 11 3 1 14 2
The Compliance Counsel
Custody can genuinely sit with the customer: self-hosting on Docker Compose, Podman or Kubernetes with detailed air-gapped deployment guides, an MIT-licensed core on GitHub, native Matrix and XMPP federation, and vendor-provided migration services; a free Starter workspace runs on customer infrastructure up to fifty users. The stated codebase includes commercial components and air-gapped deployment requires a paid plan, and self-hosted services report usage data to the vendor by default with a manual option only under written agreement — qualifications I would put before the works council, not obstacles to custody. 10 11 14 3 1
The Platform Engineer
Self-managed is a first-class deployment: Docker Compose, Podman or Kubernetes with a free Starter up to 50 users, a step-by-step air-gapped guide covering image transfer and private registries, and six months of support per release. The core is MIT-licensed on GitHub with premium components behind a licence, and federation is native — the platform is both a Matrix homeserver and an XMPP server with no bridge to deploy. Migration and workspace-merge services plus a documented Starter-to-paid path without data loss give the exit story I want, tempered by the licensed premium tier. 3 10 11 1 14 2
The Skeptic
Three deployment models are documented — vendor cloud, self-managed on Docker Compose, Podman or Kubernetes with a free Starter up to 50 users, and air-gapped including a build-it-yourself path from GitHub — plus native Matrix and XMPP federation and vendor-documented migration services for moving or merging workspaces. A premium licence grants access to the full codebase with code-audit rights, while the MIT licence covers only the original repositories, so part of the server sits behind a licence. We found no public information on a documented full export of messages together with files and metadata from the cloud offering. 10 11 3 1 14
Integrations & extensibility
Show reasoningHide reasoning
How this is scored
Bots, webhooks, app framework, identity — whether the chat becomes the place work is noticed, and whether that is buildable without a partner agreement.
0 — A closed messenger: no integrations, webhooks, bots or API.
3 — Incoming webhooks or a handful of named integrations.
5 — An app directory or a list of native integrations with common tools, a documented API, incoming webhooks and bots or slash commands.
8 — A proper app framework with interactive components, event subscriptions with retries, SSO and SCIM provisioning, documented rate limits and a sandbox.
10 — A platform: versioned API with a deprecation policy, an app directory or plugin system with permissions a customer can audit, and integrations the vendor maintains rather than lists.
The Team Lead
Two-way webhooks with custom JavaScript in an isolated virtual machine, configurable retries with selectable delay algorithms, event triggers from message sent to room archived, a Marketplace for apps, REST APIs and SDKs, and directory sync over AD, LDAP, SAML and OAuth — this is buildable without a partner agreement. I found no public information on SCIM provisioning, documented rate limits, or a developer sandbox, so it stops short of a full app-framework story. 12 12 1 13
The Security Officer
The integration engine is serious: incoming and outgoing webhooks, custom JavaScript running in an isolated virtual machine, configurable retries with selectable delay algorithms, event triggers from message sent to room archived, a CSRF-verification token option, an app Marketplace, documented REST APIs and SDKs, and identity integration covering SSO, LDAP, SAML 2.0 and Active Directory. We found no public information on SCIM provisioning, documented rate limits, or interactive UI components, which keeps it below a full platform level. 12 13 1 2 12
The Works Council Advocate
Incoming and outgoing webhooks with custom JavaScript in an isolated runtime, configurable retries with three delay algorithms, seven event triggers, wildcard channel scoping and a programmatic Integration API, alongside a marketplace offering apps on licence, one-time paid or subscription terms and a long named list from GitLab and GitHub to Microsoft Teams, Prometheus and Grafana. Directory and identity integration covers AD, LDAP, OAuth and SAML. We found no public information on SCIM provisioning, documented rate limits, a developer sandbox, or interactive app components. 12 12 13 2 14
The Compliance Counsel
Incoming and outgoing webhooks with isolated V8 scripting, configurable retries and named delay algorithms, a rich set of event triggers, an app marketplace with licence, one-time and subscription models, a long list of predefined integrations, identity synchronisation over AD, LDAP, OAuth and SAML, and native federation make this a buildable platform. We found no public information on SCIM provisioning, documented rate limits, a developer sandbox, or a versioned API with a deprecation policy. 12 12 13 1 2
The Platform Engineer
Incoming and outgoing webhooks with JavaScript in an isolated V8 sandbox, configurable retries with selectable delay algorithms, event triggers from message sent to room archived, roughly eighteen named integration guides, a marketplace for plugins with custom app development, REST APIs and SDKs, plus SSO, LDAP, SAML and AD syncing. We found no public information on SCIM provisioning or documented API rate limits, and the marketplace terms let the vendor or an app vendor remove an app at any time, which is the kind of dependency I want in writing before building on it. 12 13 1 12
The Skeptic
Incoming and outgoing webhooks are documented in unusual depth — ES2015 scripts in an isolated V8 sandbox, configurable retry counts and delay algorithms, event triggers from message sent to user created — alongside a marketplace for pre-built and custom apps, a long list of named integration guides, REST APIs and SDKs, and SSO via LDAP, SAML 2.0, OAuth and Active Directory with attribute-based access control. We found no public information on SCIM provisioning, documented rate limits, a developer sandbox or an API deprecation policy. 12 13 1 2
European sovereignty
panel opinion
Show reasoningHide reasoning
How this is scored
Where the archive and its metadata live, who the contracting entity is, which subprocessors touch it. Independently sourced by the sovereignty pipeline; scored here as this buyer weighs it. Dimensions the evidence does not establish are unknown, not non-EU.
0 — Proven non-EU on every dimension the evidence covers: non-EU vendor and contracting entity and non-EU hosting, with no EU option stated.
3 — One European element proven — EU data residency for message content, an EU contracting entity or EU representative, or a published DPA — with the rest of the chain unstated.
5 — EU hosting stated as standard or selectable and an EU contracting entity or EU representative, with a DPA offered; the subprocessor chain (notifications, AI features, analytics) is unstated or partly non-EU.
8 — EU hosting on named infrastructure covering content and metadata, EU contracting entity, subprocessor list published with locations, any non-EU processing named with its legal basis.
10 — Sovereign end to end and evidenced: vendor, entity, hosting and every subprocessor European, certification published, and a self-hosted option that removes the question.
The Team Lead
The contracting entity is a Delaware corporation, and the captured pages never say where the managed cloud stores data by default, so most of the chain is unstated. What is proven: an EU-hosted sovereign cloud as a deployment option, GDPR-ready claims with full EU data handling on the government plans, a DPA available on request, and self-hosting that takes the question off the table entirely. The subprocessor document names each entity's purpose, but these pages give no locations for them. 3 1 2 10
The Security Officer
EU hosting is offered as a selectable deployment — an EU-hosted sovereign cloud, with GDPR readiness and full EU data handling claimed — and a Data Processing Addendum is available on request, but the contracting entity is a corporation in Wilmington, Delaware, and the subprocessor document gives each entity's purpose without locations. The captured pages never state where the vendor's own managed cloud stores data by default. Self-hosting or an air-gapped deployment can remove the question entirely, which I weigh in the product's favour. 1 3 9 1 2
The Works Council Advocate
The contracting entity is proven to be Rocket.Chat Technologies Corp of Wilmington, Delaware, and we found no public information on where the vendor's own managed cloud stores data by default; the subprocessor document publishes each entity's purpose, but the pages we read give no locations. European elements exist as choices rather than as a default: an EU-hosted sovereign cloud deployment, a data processing agreement on request for GDPR customers, and self-hosting that removes the question entirely. 3 13 1 9 10
The Compliance Counsel
The captured terms place the contracting entity in Wilmington, Delaware, and we found no public information on an EU representative or on where the managed cloud stores data by default; an EU-hosted sovereign cloud is offered as a selectable deployment, a GDPR data processing addendum is available on request, and a subprocessor document names each entity's purpose but no locations. Self-hosting and air-gapped deployment put the archive inside the customer's own perimeter, which is the strongest sovereignty answer on these pages. 3 13 1 9 10
The Platform Engineer
The contracting entity is a US Delaware corporation, and an EU-hosted sovereign cloud is offered as a deployment choice alongside on-premises and air-gapped, with the captured pages not stating where the managed cloud keeps data by default. A data processing addendum is available on request, and a subprocessors document names each entity's purpose without locations, so the chain is only partly visible. For my money the self-managed and air-gapped options are what actually settle the custody question. 3 9 10 13 1 2
The Skeptic
The contracting entity is proven to be Rocket.Chat Technologies Corp. of Wilmington, Delaware, and we found no public information on where the vendor's own managed cloud stores data — an EU-hosted sovereign cloud appears only as one of several deployment choices in homepage marketing. A GDPR data processing addendum is offered on request and a subprocessor document names each entity's purpose. Beyond that, the self-managed and air-gapped deployments are the only route on these pages that settles where the archive lives. 13 1 3 9 10
Pricing transparency
Show reasoningHide reasoning
How this is scored
Whether a buyer can compute the annual invoice for their headcount — including the retention, compliance and guest features they actually need — from public pages alone.
0 — No public prices at all; every tier is a sales conversation.
3 — A public "from" price or one priced tier per user.
5 — Per-user prices public for the main tiers with the billing period stated and the main features per tier listed.
8 — Every tier priced publicly with per-user maths, history and storage limits, feature boundaries (retention, SSO, eDiscovery), minimum term and VAT treatment stated; self-hosted licensing priced too where offered.
10 — Complete price computability: annual invoice derivable for a given headcount and deployment choice, including guest users, storage and any per-instance licence.
The Team Lead
No per-user price is published for any commercial tier — the pricing page offers a 'Get pricing' contact — so an annual invoice cannot be computed from public pages. What is public: a free self-managed Starter workspace up to fifty users, a cloud entry point via the Cloud Portal, twelve-month auto-renewing terms with thirty-day notice, fees stated exclusive of taxes, and WhatsApp template messages charged separately on Facebook/WhatsApp pricing in USD on top of the licence. The free tier is real, but everything a paying buyer needs is a sales conversation. 2 2 10 3
The Security Officer
No public prices are published; the pricing pages show only a 'Get pricing' contact for the commercial, government and defence plans, and we found no public information on guest-user figures beyond a terms note that pricing and functionality may vary by end-user type. The only public figures are the free entry points — a cloud workspace via the Cloud Portal and a self-managed Starter workspace capped at fifty users and one workspace per organisation — while the contract terms state fees are exclusive of taxes, on a twelve-month auto-renewing term with thirty days' cancellation notice, and non-refundable. 2 3 10 2
The Works Council Advocate
No paid tier carries a public per-user price — commercial pricing runs through a 'Get pricing' contact — so no buyer can compute an annual invoice from public pages; only the free Starter workspace up to 50 users and the plan structure of Commercial, Government and Defense are public. The published terms do fix the conditions around the invisible numbers: fees exclude taxes, twelve-month terms renew automatically unless notice is given at least thirty days prior, sums paid are non-refundable, guest users may price differently, and WhatsApp template messages are charged separately at Facebook/WhatsApp pricing in USD. Air-gapped deployment requires a paid plan. 2 2 10 3 13
The Compliance Counsel
The pricing pages publish no figures for paid plans — commercial, government and defense tiers are reached through a Get pricing contact — so an annual invoice cannot be computed for any headcount from public pages. A free Starter workspace is public with a fifty-user limit on customer infrastructure, and the terms state twelve-month auto-renewal with thirty days' notice, fees exclusive of taxes, and non-refundable sums; we found no public per-user price for any paid tier. 2 2 10 3
The Platform Engineer
No per-user prices are public — commercial plans sit behind a "Get pricing" contact — so an annual invoice is not computable from public pages; the public entry point is a free self-managed Starter workspace limited to 50 users and one workspace per organisation. The terms do state that fees are exclusive of taxes, the initial term runs twelve months with automatic renewal and thirty days' notice, and WhatsApp template messages are billed separately on Facebook's pricing. A buyer can price the free tier and nothing above it. 2 3 10 2
The Skeptic
Every paid segment — Commercial, Government, Defense — routes through a 'Get pricing' contact with no published per-user price, so no annual invoice can be computed for any headcount. What is public is the free Starter at up to 50 self-managed users limited to one workspace per organisation, plus the contract economics: a twelve-month auto-renewing term with 30-day notice, fees exclusive of taxes and non-refundable, pricing that varies between Users and Guest users, and WhatsApp template messages billed per Facebook/WhatsApp USD pricing outside the licence. The per-user multiplier behind all of it is the sentence we did not find. 2 2 10 3 13
European sovereignty — proven facts
3 of 6 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity | Not determined | — | uncited Report an error |
|---|---|---|---|
| Hosting location |
Not determined
unverified
Why unverified?EU hosting is stated only as one deployment choice alongside self-hosted and air-gapped in homepage marketing copy, and the pages never say where Rocket.Chat's own managed cloud stores data by default. |
— | uncited Report an error |
| Hosting options |
Self-hostable
unverified
Why unverified?Air-gapped deployment requires a paid plan and premium features sit behind a license, but a free self-managed Starter workspace still runs on customer infrastructure. |
1/1 pts | 10 Report an error |
| Open source |
Open source (permissive)
unverified
Why unverified?S4 states the codebase 'includes both open-source and commercial components', so the premium parts of the product are not covered by the MIT License. |
1/1 pts | 3 Report an error |
| Data processing agreement |
On request
unverified
Why unverified?The same paragraph also directs customers to the Privacy Center to access 'the latest privacy agreement templates', and the docs navigation lists a 'Data Processing Agreement (GDPR)' article, so the DPA may also be retrievable online. |
0/1 pts | 3 Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about Rocket.Chat
Is Rocket.Chat European?
No. whats-best.ai classifies Rocket.Chat as Rest of world.
Where does Rocket.Chat store data?
Not stated on the vendor’s pages as of 16 Nov 2026.
Does Rocket.Chat have a free plan?
Not stated on the vendor’s pages as of 16 Nov 2026.
What are the best alternatives to Rocket.Chat?
As of 19 Nov 2026, the panel rates Stackfield (3.5/5), Mattermost (3.5/5) and Element (3.5/5) highest among the other 27 Business Instant Messaging products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is Stackfield (EU-Made, Germany). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: Rocket.Chat alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 31 Aug 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Data processing agreement. The same paragraph also directs customers to the Privacy Center to access 'the latest privacy agreement templates', and the docs navigation lists a 'Data Processing Agreement (GDPR)' article, so the DPA may also be retrievable online.
- Weak sourcing — Open source. S4 states the codebase 'includes both open-source and commercial components', so the premium parts of the product are not covered by the MIT License.
- Weak sourcing — Hosting location. EU hosting is stated only as one deployment choice alongside self-hosted and air-gapped in homepage marketing copy, and the pages never say where Rocket.Chat's own managed cloud stores data by default.
- Weak sourcing — Hosting options. Air-gapped deployment requires a paid plan and premium features sit behind a license, but a free self-managed Starter workspace still runs on customer infrastructure.
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
What we left out
A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.
- 138 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 33 compliance facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 26 integrations facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 19 pricing facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 9 support facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 8 data facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 6 hosting facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 2 legal facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- The pricing here was last read more than 30 days ago. Vendors change prices without notice; the capture date is shown with every figure. Know more? Tell us
Sources (15)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage www.rocket.chat Checked 16 Nov 2026 +2 earlier captures: 9 Nov 2026, 5 Oct 2026 Details →
- 2 Pricing www.rocket.chat Checked 16 Nov 2026 +4 earlier captures: 9 Nov 2026, 5 Oct 2026, 11 Sep 2026, 31 Aug 2026 Details →
- 3 Terms of service docs.rocket.chat Checked 16 Nov 2026 Details →
- 4 Channels, threads & search — found from sitemap docs.rocket.chat Checked 16 Nov 2026 Details →
- 5 Channels, threads & search — found from sitemap docs.rocket.chat Checked 16 Nov 2026 Details →
- 6 Encryption & access control — found from sitemap docs.rocket.chat Checked 16 Nov 2026 Details →
- 7 Encryption & access control — found from sitemap docs.rocket.chat Checked 16 Nov 2026 +1 earlier capture: 2 Nov 2026 Details →
- 8 Retention, discovery & co-determination — found from sitemap docs.rocket.chat Checked 16 Nov 2026 +2 earlier captures: 2 Nov 2026, 5 Oct 2026 Details →
- 9 Retention, discovery & co-determination — found from sitemap docs.rocket.chat Checked 16 Nov 2026 Details →
- 10 Deployment & data custody — found from sitemap docs.rocket.chat Checked 16 Nov 2026 Details →
- 11 Deployment & data custody — found from sitemap docs.rocket.chat Checked 16 Nov 2026 Details →
- 12 Integrations & extensibility — found from sitemap docs.rocket.chat Checked 16 Nov 2026 +1 earlier capture: 26 Oct 2026 Details →
- 13 Integrations & extensibility — found from sitemap docs.rocket.chat Checked 16 Nov 2026 Details →
- 14 Self-hosting / on-premises installation docs — found from the homepage www.rocket.chat Checked 16 Nov 2026 +1 earlier capture: 9 Nov 2026 Details →
- 15 Code repository (open-source licence) — found from the homepage github.com Checked 16 Nov 2026 +3 earlier captures: 9 Nov 2026, 2 Nov 2026, 1 Nov 2026 Details →