Mattermost
Rest of world Report an errorPanel rating · 6 judges · How to read the stars
Category median
Sovereignty: 1 of 6 dimensions proven
0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Mattermost, Inc. · mattermost.com
Compare with Slack → Compare with Element → Compare with Rocket.Chat → 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.
Mattermost at a glance
- Vendor
- Mattermost, Inc.
- 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
- Yes, per the vendor’s own page source, captured 2 Nov 2026
- Panel verdict
- The AI panel rates Mattermost 3.5/5, the mean of 6 judges. Mattermost, a self-hostable messaging platform from Mattermost of Palo Alto, earns its best marks where custody matters: deployment control scores 9-10 — three install methods, air-gapped runbooks with a bill of materials and package mirroring, full source code access and a customer-owned MySQL or PostgreSQL database. how scores are made
- As of
- Vendor pages captured 15 Sep 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
Mattermost, a self-hostable messaging platform from Mattermost of Palo Alto, earns its best marks where custody matters: deployment control scores 9-10 — three install methods, air-gapped runbooks with a bill of materials and package mirroring, full source code access and a customer-owned MySQL or PostgreSQL database. Governance and discovery spans 7-9 — retention policies, legal hold, eDiscovery automation and compliance exports to CSV, Actiance XML, Global Relay EML or Proofpoint, with edits and deletions tracked by message identifier and every query logged — the span reflecting reservations that the default retains everything, deletions included. Messaging core and encryption and access sit at 7-8: the vendor states that the database is not encrypted so search and compliance reporting keep working, and we found no public information on end-to-end encryption. Integrations scored 7. Sovereignty scores 2-3: the contracting entity is American, processing in the US is stated, transfers rest on the EU–US Data Privacy Framework and Standard Contractual Clauses, and we found no public information on EU data residency; self-hosting is the lever that puts the archive in your perimeter. Prices are sales-routed.
Speaks for it
- Deployment control scores 9-10, with three install methods for the same server, air-gapped runbooks with a bill of materials and package mirroring, full source code access and a customer-owned MySQL or PostgreSQL database.
- Compliance exports run to CSV, Actiance XML, Global Relay EML or Proofpoint, track edits and deletions by message identifier, and log every query and download in an audit history.
- Retention policies, legal hold and eDiscovery automation are named plan features, and past history can be exported from a chosen timestamp.
- The encryption trade-off is stated openly — no encryption within the database so search and compliance reporting keep working — alongside MFA, SSO and certificate-based authentication.
- Migration paths point both ways: Slack-compatible webhook formats on the way in, command-line export of past history on the way out.
Held against it
- Sovereignty scores 2-3, with an American contracting entity, stated processing in the United States, and no public information on EU data residency or subprocessor locations, though a Data Processing Addendum and Subprocessor document are listed among the legal documents.
- The vendor's documentation states the database is not encrypted so search and compliance reporting keep working, and we found no public information on an end-to-end encryption mode.
- Compliance export excludes Mattermost Playbooks and Boards content.
- Core search is documented at up to 3 million posts, with Enterprise Search recommended beyond.
- We found no public information on switching presence, read receipts or activity analytics off organisation-wide, while the documented default retains every message including edits and deletions.
Best for
- You need the message archive inside your own perimeter — self-hosting on your own MySQL or PostgreSQL database, air-gapped if required, scored 9-10 on deployment control.
- Your legal or compliance function needs a defensible record — retention policies, legal hold and eDiscovery exports in formats lawyers' discovery systems ingest, with every query and download logged.
- You work in defence, intelligence or critical infrastructure — the captured pages describe NATO & US PL3, IL4/5, IL6/7 proven deployments and FIPS-compliant, STIG-hardened container images.
Avoid if
- You need a European vendor chain — sovereignty scored 2-3, the contracting entity is Mattermost, Inc. of Palo Alto with stated processing in the United States, and we found no public information on EU data residency.
- Your works council needs presence, read receipts or activity analytics switched off organisation-wide — ask the vendor: the public pages we read do not show it
The scores
| Criterion | Panel median |
|---|---|
| Channels, threads & search | 3.5 of 5 |
| Encryption & access control | 4 of 5 |
| Retention, discovery & co-determination | 4 of 5 |
| Deployment & data custody | 4.5 of 5 |
| Integrations & extensibility | 3.5 of 5 |
| European sovereignty | 1.5 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
Channels, threaded discussions, guest accounts and file previews are all there, and the thread API plus a move-thread-to-another-channel endpoint (still marked beta) shows the archive is meant to be tidied rather than lost. Search is real but bounded — core search documented at three million posts with an enterprise search tier recommended beyond — and I found no public information on pinned or saved items or end-user search filters by channel, person and date, which keeps this just short of a working knowledge base. 2 5 6 1 2
The Security Officer
Public and private channels, threaded discussions, file sharing with previews and full searchable history across channels, threads and direct messages are documented, with a stated default that retains every message including edits and deletions. Guest accounts and shared channels with federation give cross-organisation boundaries, and a beta API moves a thread to another channel without leaving it behind. I found no public information on pinned and saved items or on end-user search filters by channel, person and date, which keeps this short of the knowledge-base grade. 2 5 10 13 1 2
The Works Council Advocate
Public and private channels, threaded discussions, file previews and full searchable history are documented, with a thread API, guest accounts and shared channels across organisations, and a stated search scale of three million posts with enterprise search beyond. We found no public information on pinned and saved items or on end-user search filters by channel, person and date, so I stop below the level where the archive works as a knowledge base. 2 5 6 13 1 2
The Compliance Counsel
Full searchable history across channels, threads and direct messages with per-channel permissions and retention is stated, and the documented search limit (core search up to 3 million posts, enterprise search beyond) tells a buyer what finding an eighteen-month-old decision actually costs. Threaded discussions, guest accounts, shared channels with federation, and moving a thread to another channel are all documented. We found no public information on pinned or saved items, which keeps this just below the working-knowledge-base level. 2 5 6 1 2
The Platform Engineer
Channels public and private, threaded discussions, previews, guest accounts, and full searchable history with all messages and files retained by default — the daily surface is documented, and edits and deletions survive into exports. The search scale limit of three million posts is stated up front, and moving a thread between channels exists but is marked beta. I found no public information on pinned or saved items or on end-user search filters by channel, person and date, so this sits a notch under the top. 2 5 9 10 13 1 2
The Skeptic
Channels, threaded discussions, file previews and "full searchable history" are documented, and by default all deployments retain all messages including edits and deletes — the cap I read for turns out to be a search cap: core search tops out at 3 million posts before Enterprise Search is recommended. Guest accounts, per-channel permissions and edit/deletion tracking in exports are listed. We found no public information on pinned or saved items, or on end-user search filtered by channel, person and date. 2 6 9 10 1 2
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
Bring-your-own-keys arrives as a documented optional add-on, session duration is configurable, and permissions run down to individual channels, with MFA, SSO and certificate-based authentication stated. The encryption documentation states plainly that the database itself is not encrypted so that search and compliance reporting of message histories can work, which is the kind of trade-off naming I want — but I found no public information on any end-to-end encryption mode, so the strongest reading stops short of that. 7 3 2
The Security Officer
Encryption in transit and at rest is stated with named mechanisms — TLS between client and server, disk-level encryption for the database and file storage, S3-managed keys on the Enterprise plan — and an optional externally managed encryption add-on brings the customer's own keys. Granular role-based and per-channel permissions, guest accounts, SSO with MFA and configurable session duration are all documented. 7 2 3 2
The Works Council Advocate
The mechanism is written down rather than asserted: TLS with named ciphers, at-rest encryption through disk, database and S3 methods, MFA with SSO and certificate login, session duration an administrator configures, and permissions set per channel. The vendor also states plainly that the database holds message text readable so that search and compliance reporting function, and bring-your-own keys appears only as an optional add-on on the top plan — honest, and exactly the point a works agreement has to weigh. 7 2 3 2
The Compliance Counsel
Encryption in transit with TLS and at rest via documented disk and database methods, MFA, SSO, certificate-based authentication, session duration configuration, guest accounts and role-based access with custom permissions are all evidenced, and bring-your-own-key encryption is offered as an optional add-on on the top plan. The deployment guide also states plainly that encryption within the database is not offered so that end-user search and compliance reporting keep working — a named trade-off rather than a hidden one. We found no public information on end-to-end encryption of message content. 7 2 3 2
The Platform Engineer
Transport and at-rest encryption are documented honestly, including the plain admission that the database itself carries no internal encryption so search and compliance reporting of message histories keep working. Bring-your-own-key encryption is an optional add-on at the top plan, with MFA, SSO, certificate authentication, session duration configuration and role-based permissions with custom definitions. We found no public information on end-to-end encryption, which caps this below first-class. 2 3 7 3 2
The Skeptic
The sentence I look for is present: "Mattermost does not offer encryption within the database," stated openly to preserve search and compliance reporting — so there is no end-to-end mode, and the vendor says so rather than hiding it. What is documented is solid: TLS with AES-256, at-rest encryption via disk or S3-managed keys, MFA, SSO, certificate-based authentication, role- and attribute-based controls, session duration configuration, and bring-your-own-keys as an optional add-on on the top plan rather than a first-class mode. 7 2 3 2
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 policies, legal hold and eDiscovery are named plan features, and compliance exports run on a daily schedule to Global Relay EML, Actiance XML or Proofpoint with edits and deletions tracked by message identifier — exports a lawyer's discovery system actually ingests, with every compliance query and download logged in an audit history. I found no public information on switching presence, read receipts or activity analytics off organisation-wide, which is exactly what a works council will ask about. 2 9 10 1
The Security Officer
Per-channel retention, legal hold and eDiscovery exports that include direct messages, files, plugin and bot posts, and edits and deletions tracked by message identifier across export batches — this is built to survive a subpoena, and every compliance query and download is logged in an audit history. The documented default retains everything, so deletion is a deliberate act by the operator. I found no public information on switching presence, read receipts or activity analytics off organisation-wide, which is the first thing a works council will raise. 2 9 10 1 3
The Works Council Advocate
Retention configurable per plan, per-channel retention, legal hold and eDiscovery exports in CSV, Actiance XML, Global Relay and Proofpoint formats that track every edit and deletion by message ID, with all queries and downloads logged in an audit history — this is a serious legal archive. My reservation as a works council: the documented default retains every message including deletions, and we found no public information on switching presence, read receipts or activity analytics off across the organisation, or on whether individual productivity scoring forms any part of the product. 2 4 9 10 1
The Compliance Counsel
This is the strongest part of the record for my purposes: by default every deployment retains all messages including edits and deletions plus all uploaded files, and the compliance export documentation shows edits and deletions carried into exports with each message trackable by its MessageId across batches, in formats lawyers already run — CSV, Actiance XML, Global Relay EML and Proofpoint. Retention policies, legal hold and eDiscovery automation are named Enterprise features, every compliance query and download is itself logged in an audit history, and past history can be exported from a chosen timestamp. Two things hold it back: Playbooks and Boards content is excluded from compliance export, and we found no public information on switching presence or read receipts off organisation-wide. 2 9 10 1
The Platform Engineer
Retention is configurable and stated as per-channel, legal hold and eDiscovery automation are listed features, and the export formats are the ones lawyers' tools ingest — CSV, Actiance XML, Global Relay EML, Proofpoint — with edits, deletions and message tracking across batches, plus audit history on every compliance query and download. Compliance queries filter by date range, user and keyword. We found no public information on switching presence, read receipts or activity analytics off organisation-wide, which is the first thing a works council will ask about, so I hold this one notch below the top band. 2 9 10 1
The Skeptic
Retention policy, legal hold and eDiscovery automation are listed plan features, the default is to retain everything including edits and deletes, and compliance export produces CSV, Actiance XML, Global Relay EML or Proofpoint output with messages tracked by ID across edits, deletions and batches — an export a lawyer can work with. Every compliance query and download is logged in an audit history. We found no public information on switching presence, read receipts or activity analytics off organisation-wide, or on individual productivity scoring. 2 9 10 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
Self-hosting is this product's centre of gravity: three documented install methods, air-gapped runbooks with registry mirroring, full source code access, your own MySQL or PostgreSQL database, and Matrix-protocol federation for cross-organisation channels. Migration paths point both ways — Slack-compatible webhooks on the way in, an export command line tool for past history on the way out — though the inbound story is thinner than the outbound one. 2 11 12 3 15
The Security Officer
Custody can be the customer's: the same server installs via Kubernetes, Linux or containers, air-gapped operation is documented down to registry mirroring and a bill of materials, full source code access is offered, and the customer stands up the database, file storage and TLS themselves. Federation through Matrix interoperability and Slack-compatible webhooks document a way in, and self-hosted deployments can export past history with a command-line tool. The documented exits remain message-centric compliance exports, which is the only thing short of a fully documented migration in both directions. 2 4 9 11 12 3 15
The Works Council Advocate
Custody is genuinely the customer's: one and the same server installs by Kubernetes, Linux or containers on your own infrastructure, air-gapped operation is documented down to a bill of materials and registry mirroring, the customer owns the MySQL or PostgreSQL database, full source code is available, and federation runs over the Matrix protocol. Migration in is documented through Slack-compatible webhooks; for migration out I see export tooling and the customer-owned database rather than a documented importable archive. 2 11 12 3 15
The Compliance Counsel
Custody genuinely can be the customer's: full source code, self-hosted subscriptions, three documented install paths that install the same server, an air-gap runbook with bill of materials and registry mirroring, FIPS-compliant STIG-hardened container images, and a backup strategy to set before the first user. The customer owns the database (MySQL or PostgreSQL) with their own internal controls, federation via the Matrix protocol is offered, and Slack-compatible webhooks plus export of past history document the way in and the way out rather than resisting either. 2 11 12 13 15
The Platform Engineer
This is the custody story I look for: the same server installed via Kubernetes, Linux or containers with the support boundaries stated plainly, an air-gapped runbook with bill of materials and registry mirroring, full source code, self-hosted subscriptions, and your own MySQL or PostgreSQL database under your internal controls. Federation runs over the Matrix protocol, and exit is a documented operation — export past history by command line, backup strategy set before users arrive — rather than a negotiation. The docs even say container-only installs are not supported for production, which is the kind of honesty that makes an operator trust the rest. 2 9 11 12 3 15
The Skeptic
Custody is the customer's on the evidence: all documented deployment methods install the same server on your Kubernetes cluster, Linux or containers, air-gapped operation has its own runbook with registry mirroring, you own the database, and full source code is offered. Federation via Matrix interoperability and Slack-compatible webhook formats give paths in and out, though a complete vendor-documented migration path in both directions is only partly evidenced. 2 11 12 13 3 15
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
A documented REST API with bearer authentication and permission checks, incoming and outgoing webhooks with Slack-compatible payloads, slash commands, an MCP server, and a plugin architecture with interactive blocks and dialogs — enough to make the chat the place work gets noticed without a partner agreement. I found no public information on documented rate limits, event-subscription retries or a sandbox, so it sits just below the full platform tier. 2 13 14 2
The Security Officer
A documented REST API with bearer authentication and per-endpoint permission checks sits alongside webhooks, slash commands, interactive dialogs and structured interactive posts with buttons and menus — a real framework rather than a webhook list. A flexible plugin platform, private integration connections and named Jira, GitHub, GitLab and ServiceNow integrations are documented. I found no public information on event subscriptions with retries, SCIM provisioning, documented rate limits or a sandbox. 6 13 14 1 2 2
The Works Council Advocate
A documented REST API with permission checks, an MCP server, webhooks with administrator-enforced channel locking, slash commands, a plugin platform, interactive blocks and dialogs, plus named integrations for Jira, GitHub, GitLab and ServiceNow. We found no public information on SCIM provisioning, documented rate limits or a sandbox environment, which keeps this below the full platform level. 13 14 1 2 3
The Compliance Counsel
A versioned REST API with bearer authentication, incoming and outgoing webhooks, slash commands, an MCP server and a flexible plugin platform are all documented, with interactive components — Mattermost Blocks and interactive dialogs — for structured interaction. Named operational integrations including Jira, GitHub, GitLab and ServiceNow and no-code Slack-compatible webhooks round this out. We found no public information on documented rate limits, SCIM provisioning, or event subscriptions with retries, which is what would distinguish a full app framework. 6 13 14 1 2
The Platform Engineer
A real plugin platform, a versioned REST API whose endpoints carry named permission requirements, Slack-compatible webhooks with admin-enforced channel locking, interactive dialogs and blocks, slash commands, MCP for the AI tooling, and Jira, GitHub, GitLab and ServiceNow maintained as integrations. Integration connections can be kept fully private, which I rate highly. We found no public information on documented rate limits, a sandbox, SCIM provisioning or an API deprecation policy, so this is a strong framework short of a full platform. 5 6 13 1 2 3
The Skeptic
A documented REST API with bearer authentication, an MCP server, incoming and outgoing webhooks with admin-enforced channel locking, slash commands, interactive Blocks and dialogs, a plugin platform and named DevSecOps integrations clear the bar comfortably. We found no public information on SCIM provisioning — Active Directory and LDAP sync is what is documented — nor on documented rate limits, a sandbox, or event subscription retries. 6 13 1 2 3 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 vendor chain is proven American on every dimension the captured pages cover — a Palo Alto contact address, stated processing in the United States, and Data Privacy Framework mechanisms as the transfer basis — and I found no public information on EU data residency, an EU contracting entity or a published subprocessor list with locations. The one thing a European buyer can lean on is that the whole product runs self-hosted inside your own perimeter on your own database, which removes the vendor from the data path without making anything about the vendor itself European. 4 11 1 4
The Security Officer
The contracting entity is American with a Palo Alto address, processing and storage in the United States and other countries, and cross-border transfers resting on the Data Privacy Framework and Standard Contractual Clauses. The one European element the captured pages support is a Data Processing Addendum and a Subprocessor document listed among the vendor's legal documents. Self-hosting and air-gapped deployment remove the vendor-hosting question entirely, but no EU data residency, EU entity or subprocessor locations appear in these captures. 4 11 12 1 4
The Works Council Advocate
The one proven European element is procedural: a Data Processing Addendum and a subprocessor document are listed among the legal documents, and GDPR appears among supported compliance programs. The contracting entity is Mattermost, Inc. of Palo Alto, the privacy policy states processing in the United States with reliance on the EU–US Data Privacy Framework, and we found no public information on where hosted message content resides — for a council that cares where the log lives, self-hosting is the only lever these pages prove. 4 11 1 4
The Compliance Counsel
The contracting entity is proven American — Mattermost, Inc. of Palo Alto — with processing in the United States and other countries and Google Analytics on its sites, so the cloud chain is not European as far as the captured pages show. What keeps this above the floor is a listed Data Processing Addendum and Subprocessor documents, explicit commitments to Standard Contractual Clauses and the EU–US Data Privacy Framework with EU rights honoured, and the fact that self-hosted or air-gapped operation puts the archive and its metadata inside the customer's own perimeter. We found no public information on EU data residency, an EU contracting entity or EU representative, or subprocessor locations. 4 1 4 15
The Platform Engineer
The vendor is a US entity in Palo Alto, transfers to the United States are stated, and the cross-border posture rests on the Data Privacy Framework with US-based dispute resolution; the captured pages list a Data Processing Addendum and a Subprocessor document, whose contents were not shown. Cloud regions run on Azure, Oracle, Google or AWS in tenancies the customer controls, and self-hosting with telemetry opt-out takes the archive off the vendor's infrastructure — but EU residency as a stated standard was not in anything I read. One European element, a published processing addendum, with the rest of the chain unstated. 4 11 1 4
The Skeptic
The contracting entity is Mattermost, Inc. of Palo Alto, information may be processed and stored in the United States, the Sites use Google Analytics, transfers rest on the Data Privacy Framework and Standard Contractual Clauses, and the optional hosted push notification service may collect usernames, full names, channel names and message preview snippets. A Data Processing Addendum and a Subprocessor document are listed among the legal documents — the one European element we could find — while data residency, subprocessor locations and the addendum's terms are not shown on the captured pages. Self-hosting lets the customer place the archive, but that is the customer's geography, not the vendor's chain. 4 11 1 4
Pricing transparency
not rated — the vendor publishes no price
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
Every paid tier — Professional, Enterprise, Enterprise Advanced — is Contact Sales, Get Pricing or Request Quote, with no public per-user figure anywhere I read; there is a free limited-use evaluation edition and genuinely useful per-tier feature lists, but no way to compute an annual invoice for a given headcount from these pages alone. 2 2 2
The Security Officer
No paid tier carries a public figure: Professional, Enterprise and Enterprise Advanced each route to contact sales, get pricing or request a quote, and the pricing FAQ lists questions about licensing, SaaS and seat overages while the captured pages show no per-user figures. A free limited-use evaluation edition and a one-hour trial environment are publicly available, which keeps this just above nothing. A buyer cannot compute an annual invoice for any headcount from these pages. 2 2 2
The Works Council Advocate
We found no public prices: Professional says Contact Sales, Enterprise says Get Pricing, Enterprise Advanced says Request Quote, and an FAQ names the questions on seat overages and SaaS without showing answers. Only a free limited-use evaluation edition is public, so an annual invoice cannot be computed for any headcount. 2 2
The Compliance Counsel
Every paid plan is a sales conversation: Professional says "Contact Sales", Enterprise says "Get Pricing", Enterprise Advanced says "Request Quote", and no per-user figure appears anywhere captured. A free limited-use evaluation edition, a one-hour trial and FAQ headings on license sales, the SaaS offering and seat overages are public, but the answers were not captured, so a buyer cannot compute an annual invoice for any headcount from public pages. 2 2
The Platform Engineer
Every paid tier routes through sales: Professional says contact sales, Enterprise says get pricing, Enterprise Advanced says request quote, and the FAQ names seat overages and licence models as questions without showing the answers. A free limited-use evaluation edition and a one-hour trial are the only things priced publicly. As a buyer I cannot compute any annual invoice for my headcount from these pages. 2 2
The Skeptic
The captured pricing pages name Professional, Enterprise and Enterprise Advanced and route all three to Contact Sales, Get Pricing and Request Quote; we found no public price for any plan. Feature boundaries per plan and a 250-user maximum on Professional are listed publicly, and a free evaluation edition and a 1-hour trial exist, but the FAQ answers on licensing, seat overages and SaaS are not shown — so an annual invoice is not computable from these pages. 2 2
European sovereignty — proven facts
1 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
unverified
Why unverified?Not confirmed on the vendor’s own pages as captured. |
— | uncited Report an error |
|---|---|---|---|
| Hosting location |
Not determined
unverified
Why unverified?Not confirmed on the vendor’s own pages as captured. |
— | uncited Report an error |
| Hosting options | Self-hostable | 1/1 pts | 11 Report an error |
| Open source | Not determined | — | uncited Report an error |
| Data processing agreement |
Not determined
unverified
Why unverified?Not confirmed on the vendor’s own pages as captured. |
— | uncited Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about Mattermost
Is Mattermost European?
No. whats-best.ai classifies Mattermost as Rest of world.
Where does Mattermost store data?
Not stated on the vendor’s pages as of 16 Nov 2026.
Does Mattermost have a free plan?
Yes. Mattermost has a free plan, per the vendor’s page captured 2 Nov 2026.
What are the best alternatives to Mattermost?
As of 19 Nov 2026, the panel rates Stackfield (3.5/5), Element (3.5/5) and Wire (Messaging) (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: Mattermost alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 15 Sep 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, Legal entity, Hosting location. Not confirmed on the vendor’s own pages as captured.
- 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.
- 17 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
- 3 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
- 3 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
- 2 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
- 2 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
- 1 legal fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 3 sovereignty dimensions could not be confirmed on the vendor’s own pages and are shown as unknown. 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 mattermost.com Checked 16 Nov 2026 +1 earlier capture: 15 Sep 2026 Details →
- 2 Pricing mattermost.com Checked 16 Nov 2026 +2 earlier captures: 2 Nov 2026, 15 Sep 2026 Details →
- 3 Security page mattermost.com Checked 16 Nov 2026 +1 earlier capture: 15 Sep 2026 Details →
- 4 Privacy policy mattermost.com Checked 16 Nov 2026 +1 earlier capture: 15 Sep 2026 Details →
- 5 Channels, threads & search — found from sitemap docs.mattermost.com Checked 16 Nov 2026 Details →
- 6 Channels, threads & search — found from sitemap docs.mattermost.com Checked 16 Nov 2026 Details →
- 7 Encryption & access control — found from sitemap docs.mattermost.com Checked 16 Nov 2026 Details →
- 8 Encryption & access control — found from sitemap docs.mattermost.com Checked 16 Nov 2026 Details →
- 9 Retention, discovery & co-determination — found from sitemap docs.mattermost.com Checked 16 Nov 2026 Details →
- 10 Retention, discovery & co-determination — found from sitemap docs.mattermost.com Checked 16 Nov 2026 Details →
- 11 Deployment & data custody — found from sitemap docs.mattermost.com Checked 16 Nov 2026 Details →
- 12 Deployment & data custody — found from sitemap docs.mattermost.com Checked 16 Nov 2026 Details →
- 13 Integrations & extensibility — found from sitemap docs.mattermost.com Checked 16 Nov 2026 Details →
- 14 Integrations & extensibility — found from sitemap docs.mattermost.com Checked 16 Nov 2026 Details →
- 15 Self-hosting / on-premises installation docs — found from the homepage mattermost.com Checked 16 Nov 2026 Details →