Business Instant Messaging
Troop Messenger
Provenance unknown Report an error0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Troop Messenger · www.troopmessenger.com
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.
Troop Messenger at a glance
- Vendor
- Troop Messenger
- Headquarters
- Not stated on the vendor’s pages as of 27 Oct 2026
- Data hosting
- Not stated on the vendor’s pages as of 27 Oct 2026
- Free plan
- Not stated on the vendor’s pages as of 27 Oct 2026
- Panel verdict
- The AI panel rates Troop Messenger 2/5, the mean of 6 judges. Troop Messenger is a self-hosted business instant messaging product. how scores are made
- As of
- Vendor pages captured 27 Oct 2026; evaluated by the panel 27 Oct 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Troop Messenger is a self-hosted business instant messaging product. Its strongest scores are encryption and access control and deployment control (7): an administrator chooses plain, Standard AES-256 or end-to-end encryption with the trade-offs stated in public, and the server installs with Docker or a Windows installer in four documented steps onto the customer's own hardware, an AWS, Azure or GCP tenancy, or a fully air-gapped network. The weakest scores are pricing transparency and sovereignty. No price appears on any captured page — buying means a tailored quote within one business day — and the vendor's own pages leave its legal entity, ownership, data residency and subprocessor exposure unknown. The sovereignty spread reflects how the judges weighed self-hosted custody: some credited running the archive on infrastructure the customer owns, while the lowest score saw only a GDPR policy page and defence customers as European signals. Messaging core and governance and discovery sit at 4: search filters are granular, but search is unavailable under Standard encryption, and we found no public information on legal hold or lawyer-usable export.
Speaks for it
- An administrator selects plain, Standard AES-256 or end-to-end encryption, with the end-to-end mode's trade-offs named in public.
- Self-hosting is a supported deployment — Docker or a Windows installer in four documented steps, on named Linux distributions, in an AWS, Azure or GCP tenancy, or fully air-gapped.
- Every action is logged, exportable and SIEM-ready via Syslog.
- Admin-enforced multi-factor authentication with five methods, idle timeout and offline validation.
- Granular search filters by contact, file, image, link, flag and read receipt.
Held against it
- The pricing route is a tailored quote within one business day — the captured pages contain no price figure.
- The vendor's legal entity, ownership, data residency and subprocessor exposure are unknown from the vendor's own captured pages.
- Conversation search and filters become unavailable once Standard encryption is switched on.
- We found no public information on export of the full archive, a migration path out, legal hold or an export format a lawyer could work from.
- The captured pages give different figures for how much is encrypted — an on-premise claim that every message, call and file is encrypted end-to-end sits beside a documented Plain mode with conversations not encrypted at rest.
Best for
- You need the messaging archive on infrastructure you own — your own data centre, an AWS, Azure or GCP tenancy, or a fully air-gapped network — with high-availability and disaster-recovery configurations.
- You are a defence or government buyer; named customers include the European Space Agency, Airbus Defence and Space and the Indian Air Force.
- You need an administrator to set the encryption mode and enforce multi-factor authentication organisation-wide.
- You need every action logged and exportable to your SIEM via Syslog.
Avoid if
- You need to compute an annual invoice from public pages — the pricing route is a tailored quote within one business day.
- Your workflows depend on conversation search — search and filters are unavailable once Standard encryption is switched on.
- You need the vendor's jurisdiction, data residency and subprocessors documented for a data-processing agreement — the captured pages leave all of these unknown.
- You need legal hold or a configurable retention policy — retention is framed as a custody statement on your own servers rather than a policy engine.
The scores
| Criterion | Panel median |
|---|---|
| Channels, threads & search | 2 of 5 |
| Encryption & access control | 3.5 of 5 |
| Retention, discovery & co-determination | 2 of 5 |
| Deployment & data custody | 3.5 of 5 |
| Integrations & extensibility | 2 of 5 |
| European sovereignty | 1 of 5 |
| Pricing transparency | 0.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 — Flat group chats with no threads; search covers recent messages only, and history is capped.
3 — Channels and direct messages with basic search, but threading is awkward or absent and file handling is a plain attachment list.
5 — Public and private channels, real threads, mentions and reactions, file sharing with previews, and full-text search across the whole 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 a documented history limit or none at all.
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
Search is the bright spot: eleven documented filters by contact, file, image, link, flag, read receipt and more is what actually finds last spring's decision. But replies encapsulate the original message rather than forming a readable thread, and we found no public information on mentions, reactions, message editing history, channel lifecycle or any documented history limit. 2 3 6 7
The Security Officer
Replies encapsulate the original message rather than forming threads, and I found no public information on mentions, reactions, pinned items, message editing history or a documented history limit. Search is genuinely filterable — by contact and by message type — which is more than basic, but the help pages state search and filters become unavailable once standard encryption is switched on, and I found no evidence the index covers years of history rather than recent traffic. 2 3 4 6
The Works Council Advocate
One-to-one and group conversations with dedicated rooms, replies that encapsulate the original message, and a search that filters by contact, file, image, link, flag and read receipt — enough to trace who said what. But replies are quotation rather than real threads, and we found no public information on mentions, reactions, message edit history, pinned items or any documented history limit. 2 3 6
The Compliance Counsel
Dedicated rooms, one-to-one and group chat, and a genuinely rich set of search filters by contact, file, image, video, link and flag are evidenced — but conversation threading amounts to replies that encapsulate the original message, and the captured pages state that search and filters are unavailable under Standard encryption, so an organisation's discovery surface depends on which encryption mode an admin chose. We found no public information on a documented history limit, message-edit history, pinned items, or exporting a conversation in a form a human can read, which is what a production request will eventually require. 2 3 4 7 8
The Platform Engineer
Group chats and dedicated rooms exist, and a reply encloses the original message rather than threading a conversation; we found no public information on mentions, reactions, or a public/private channel split. Search is the strong suit — filters by contact, file, image, link, flag and read-receipt state go well past basic. Attachment previews are documented, but we found no public information on history limits or date-filtered search, so finding a decision from eighteen months back is not something I can credit. 2 3 6 7
The Skeptic
Direct and group messaging with a reply that encapsulates the original message, and a genuinely granular set of search filters by message type, contact, flag and read-receipt. Threading beyond quoted replies is not evidenced, mentions and reactions appear nowhere in the captures, and the encryption page states that in Standard encryption the "conversation search/filter feature will not be available" — so whether search works at all depends on which encryption mode the administrator picks. I found no public information on a documented history limit or on search coverage across years of archive. 2 3 4 7
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 — Transport encryption only, undocumented; no role model beyond admin, guests indistinguishable from members.
3 — TLS and encryption at rest with vendor-held keys, basic roles, and guest access that mostly works.
5 — The above plus configurable roles per channel, SSO, guest accounts with scoped visibility, and a clear statement of what the vendor can read.
8 — Optional end-to-end encryption for direct messages or private rooms with the trade-offs named, device verification, session management an admin can revoke, 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
Three encryption modes chosen by the admin — plain TLS-only, AES-256 standard, and end-to-end with a public-private keypair — with the trade-offs named honestly: under end-to-end the web app is restricted, monitoring is off, and a lost private key means a lost account. Five MFA methods with offline validation, feature-level permissions, LDAP/Active Directory/SSO and IP-based restriction round it out; we found no public information on device verification or admin session revocation. 4 5 6 7
The Security Officer
The encryption page is unusually honest: an admin chooses plain, standard or end-to-end mode, the public-private key system is documented, and the trade-offs are named — web access restricted, no monitoring console, and a user who loses the private key loses the account. Feature-level permissions, LDAP, Active Directory and single sign-on, and five multi-factor methods with idle timeout and offline validation are all documented. What I could not find is device verification, an administrator's ability to revoke sessions, and a plain statement of what the vendor itself cannot read in cloud deployments — the no-outsider-can-reach claim is scoped to infrastructure the customer owns. 4 5 6 7
The Works Council Advocate
An administrator chooses between Plain (TLS in transit only, nothing at rest), Standard (AES-256 in transit and at rest, with search switched off — a trade-off stated plainly) and end-to-end encryption using a public-private key-pair, encryption on the sender's device, and the limits named: web access restricted, the receiver must have logged in once, and users keep their own private key or lose the account. Feature-level permissions, SSO and LDAP, and admin-enforced multi-factor authentication with five methods make this a documented mechanism with named trade-offs. We found no public information on device verification or admin-revocable sessions, and key recovery is left entirely to the user. 4 5 6 7
The Compliance Counsel
End-to-end encryption is a documented, admin-selectable mode with the trade-offs named plainly — web access restricted, monitoring unavailable, users responsible for their own private keys and locked out if they lose them — alongside role-based permissions at feature level, LDAP/Active Directory/SSO, and admin-enforced MFA with five methods and idle timeout. It sits below the top band because we found no public information on device or identity verification, on session management an administrator can revoke, and the cryptography is named (AES-256, public-private keypair) but not published for independent review. 4 5 6 7
The Platform Engineer
An admin chooses per deployment between Plain, Standard AES-256, and end-to-end encryption, and the trade-offs are named in public: end-to-end mode restricts the web client, disables the monitoring tool, and hands private keys to users who lose their account if they lose the key. Multi-factor authentication is unusually deep — five methods, admin enforcement on the app and dashboard, idle timeout, offline validation. We found no public information on device verification, identity verification, or admin-revocable sessions, and the cryptography is described only as a public-private key pair. 4 5 6
The Skeptic
The encryption documentation is unusually concrete: three administrator-selectable modes with the E2EE mode's costs stated plainly — web access restricted, TM Monitor unavailable, the receiver must have logged in once, and a lost private key means a lost account. What holds it below the top band is that the on-premise page's "every message, call and file is encrypted end-to-end" sits beside a Plain mode in which conversations are "not encrypted at rest" — the captured pages give different figures for how much is encrypted — and I found no public information on device verification or session revocation by an administrator. 4 5 6
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.
0 — No retention policy, no export beyond a manual copy, no audit log, and presence or activity analytics that cannot be disabled.
3 — Manual export of some data and a global history limit, but no per-channel retention, no audit log and no admin control over analytics.
5 — Configurable retention per channel or workspace, admin export in a documented format, an audit log of administrative actions, and status or presence that a user can control.
8 — Legal-hold and eDiscovery export including edits and deletions, retention executed per policy and evidenced, full admin audit trail, and 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 no individual-level productivity scoring anywhere in the product.
The Team Lead
The audit claim is unusually strong — every action logged, exportable, SIEM-ready via Syslog — and disappearing messages exist. Retention amounts to "you decide how long it is kept" on your own servers rather than a configurable policy, and we found no public information on legal hold, eDiscovery export, or whether read receipts and presence can be switched off for the organisation. 3 6 7
The Security Officer
The audit claim is strong — every action logged, exportable, SIEM-ready via Syslog — and self-hosted customers are told they decide how long data is kept, though that reads as infrastructure control rather than a retention feature. Beyond that I found no public information on retention configured per channel or workspace, discovery or legal-hold export in a documented format, or on whether presence and activity analytics exist and can be switched off for a works council. 6 7
The Works Council Advocate
Every action is logged and exportable, SIEM-ready via Syslog, and self-destructing messages together with the promise that you decide how long data is kept give a deletion story. But we found no public information on a configurable retention policy, a documented export format for legal discovery, or presence a user can control — and the air-gapped edition advertises lawful interception through TM-Monitor, with no public statement that monitoring can be switched off organisation-wide. 4 6 7
The Compliance Counsel
The one strong item is the audit claim — every action logged, exportable, SIEM-ready via Syslog — the kind of trail that can survive the administrator who made the change. But we found no public information on retention policy configuration per channel or workspace, legal hold, eDiscovery export including edits and deletions, or any export format a lawyer could work from; the only retention-adjacent statement is that on your own servers you decide how long data is kept, which is a custody claim rather than a policy engine. Self-destructing and disappearing messages are marketed features, and nothing documents how deletions are captured for a later production. 4 6 7
The Platform Engineer
Every action is logged, exportable, and SIEM-ready via Syslog, which is a genuinely strong administrative audit posture. Retention is framed as a consequence of running your own server — "how long it is kept" is the customer's decision — rather than a documented per-channel policy, and we found no public information on legal hold, discovery export in a lawyer-usable format, or user control over presence and activity analytics. The air-gapped edition ships a lawful-interception monitor, which is exactly the feature a works council will want switched off or contractually bounded. 6 7
The Skeptic
"Every action logged and exportable, SIEM-ready via Syslog" is a real audit trail, alongside self-destructing messages and time-scoped, leader-approved access requests. I found no public information on configurable retention, admin export of message content in a documented format, or legal hold — "you decide... how long it is kept" is a self-hosting custody statement, not a retention feature. The Troop-GRIT edition advertises "lawful interception (TM-Monitor)", which is precisely the monitoring a works council will ask to see switched off. 6 7
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 — Cloud-only, proprietary, with export limited to a partial archive.
3 — Cloud-only, but with a documented full export in an open-ish format.
5 — A private-cloud or dedicated-instance option, or a self-hosted edition that lags the cloud significantly; full export documented.
8 — A genuine self-hosted edition close to feature parity, or 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 the flagship, not a footnote: Docker or Windows installer in four steps, MySQL bundled in the container, own data centre or private cloud tenancy on AWS, Azure or GCP, and a fully air-gapped edition with a 15-day full-featured trial. We found no public information on a documented export or migration path out, and the page frames open source as handing you "the source code and the operational burden that comes with it". 6 7 2
The Security Officer
Self-hosting is real and first-class: four documented steps under Docker or the Windows installer, on Ubuntu, RHEL, CentOS or Windows Server, in your own AWS, Azure or GCP tenancy with high availability and disaster recovery, or fully air-gapped with a bundled MySQL database — and the captured pages state no vendor, cloud provider or outsider can reach the communication on infrastructure you own. What I found no public information on is the exit: no documented export of the archive with files and metadata, and the vendor positions itself against open-source platforms rather than publishing its server code. 2 6 7
The Works Council Advocate
Self-hosting is the product's identity: your own servers or an AWS, Azure or GCP tenancy, fully air-gapped operation, Docker or Windows installer with MySQL bundled, four documented steps, and the claim that no vendor or outsider can reach the communication. The server is proprietary — the vendor positions itself against open source — and we found no public information on export or a migration path in and out, which is what an exit actually needs. 6 7
The Compliance Counsel
Custody is genuinely on offer: a self-hosted server installed with Docker or a Windows installer in four documented steps, deployable into your own AWS, Azure or GCP tenancy, on MySQL 8+ you can inspect, with a fully air-gapped edition and named defence and government customers. The vendor markets the on-premise edition as an alternative to open-source platforms, and we found no public information on a documented full export including files and metadata, or on a migration path in or out — which is the other half of custody. 2 6 7
The Platform Engineer
Self-hosting here is a supported deployment, not a hobby build: Docker or Windows installers, named Linux distributions, MySQL 8+, high-availability and disaster-recovery configurations, a fully air-gapped variant with defence customers, and dedicated deployment support under a custom SLA. The vendor positions the on-premise edition against open-source platforms rather than on source availability, and we found no public information on federation or an open protocol. What holds it back is the exit: we found no public information on export of files and metadata, or on an upgrade path that says what happens to a customised install. 6 7
The Skeptic
Self-hosting is clearly the first-class deployment: Docker or a Windows installer in four documented steps, Ubuntu/RHEL/CentOS support, private-cloud tenancies on AWS, Azure or GCP with high-availability and disaster-recovery configurations, and a fully air-gapped edition aimed at defence customers. What holds it below the top band: the vendor positions explicitly against open source, licence registration is a mandatory deployment step, and I found no public information on export of the full archive or a documented migration path out. 6 7
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 — No API, no webhooks, no bots.
3 — Incoming webhooks and a handful of native integrations; no bot framework, no documented limits.
5 — Documented REST API, incoming and outgoing webhooks, slash commands, a bot account model, and SSO.
8 — A proper app framework with interactive components, event subscriptions with retries, 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
Zapier carries the weight — bidirectional, 3000+ apps claimed, 23 ready-made templates — alongside native Gmail, Zoom and Asana, back-end and realtime APIs, JavaScript SDKs and LDAP/SSO. We found no public information on a bot account model, slash commands, SCIM provisioning, documented rate limits or a sandbox, so the platform story rests on Zapier's plumbing rather than a first-party app framework. 7 8 9
The Security Officer
Zapier is available in both directions with twenty-three ready-made templates and a claimed three-thousand-plus app reach, backend and realtime APIs are documented with JavaScript SDKs for embedding messaging in your own applications, and LDAP, Active Directory and single sign-on are listed. I found no public information on native incoming or outgoing webhooks, a bot account model, slash commands, SCIM provisioning or documented rate limits, so this sits mid-scale rather than near a full app framework. 7 8 9
The Works Council Advocate
Backend and realtime APIs with JavaScript SDKs for embedding messaging, bidirectional Zapier automation with 23 ready-made templates, Gmail, Zoom and Asana, plus LDAP, Active Directory and SSO. We found no public information on webhooks, slash commands, a bot account model, rate limits or SCIM provisioning, so this sits below a documented developer platform. 7 8 9
The Compliance Counsel
Zapier is offered bidirectionally with ready-made templates and a handful of native apps such as Gmail, Zoom and Asana, and there are documented backend APIs, JavaScript chat SDKs and SSO. We found no public information on webhooks of the vendor's own, slash commands, a bot account model, SCIM provisioning, documented rate limits or a sandbox. 7 8 9
The Platform Engineer
Backend APIs for administrative tasks, users and groups, JavaScript SDKs, and a genuinely bidirectional Zapier link with ready-made templates — alongside LDAP, Active Directory and SSO — clear the documented-API bar. The chat-API offering is really an embed-our-messaging product, which is adjacent to extensibility rather than proof of it. We found no public information on a bot framework, slash commands, SCIM provisioning, documented rate limits, or an app directory whose permissions a customer could audit. 7 8 9
The Skeptic
Bidirectional Zapier with 23 ready-made templates, native Gmail, Zoom and Asana connections, LDAP/Active Directory/SSO, and documented back-end APIs for managing users and groups. The "3000+ app integrations" figure describes Zapier's catalogue rather than anything Troop Messenger maintains itself, and I found no public information on webhooks of its own, a bot framework, SCIM provisioning or documented rate limits. 7 8 9
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.
0 — Non-EU vendor and contracting entity, hosting unstated or non-EU, subprocessors unnamed.
3 — EU data residency offered for message content while metadata, search indexes or support tooling remain non-EU, or the contracting entity sits outside the EU.
5 — EU hosting as standard and an EU contracting entity, but parts of the chain — notifications, AI features, analytics — are non-EU without an explained safeguard.
8 — EU hosting on named infrastructure, EU contracting entity, full subprocessor list published, 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
A GDPR policy page and defence customers like the European Space Agency and Airbus are the only European signals in the captured pages. We found no public information on the contracting entity's jurisdiction, where the hosted archive and its metadata live, or any named subprocessor. 4 6 7
The Security Officer
The captured pages leave the contracting entity's jurisdiction, ownership, data residency and every subprocessor unstated, and I found no public information on any of them for the cloud edition. A customer can side-step the question by taking the self-hosted or air-gapped edition into their own tenancy, but that is custody, not evidence of a European chain — a German dialling code on the quote form is the only European trace I found. 6 7
The Works Council Advocate
We found no public information on the contracting entity's jurisdiction, where the cloud service hosts, or a single subprocessor — only GDPR and per-deployment privacy pages. The on-premise and air-gapped paths let the customer hold the archive inside their own infrastructure, which is the part that counts for me, but the vendor side itself is unevidenced. 6 7
The Compliance Counsel
Nothing in the captured pages establishes the vendor's legal entity or jurisdiction, its ownership, where a SaaS archive and its metadata would be hosted, or a single subprocessor — every attribute I would need for a data-processing agreement is unstated. The mitigating fact is that the product can run entirely on the customer's own infrastructure, including air-gapped, which removes the processing chain from the question, and European defence bodies appear among the named customers. 6 7
The Platform Engineer
Vendor jurisdiction, ownership, data residency and subprocessor exposure are all unevidenced, and we found no public information on certification. The one real mitigation is deployment choice: the on-premise and air-gapped editions put the archive on infrastructure the customer owns, with the vendor stating that no vendor, cloud provider or outsider can reach the communication. For the SaaS edition specifically we found no public information on where data or its metadata is processed. 6 7
The Skeptic
Legal entity, ownership, data residency and subprocessor exposure are all unknown from the vendor's own captured pages; the only European signal is a published GDPR policy page. The air-gapped, self-hosted edition can remove the question entirely for a buyer who deploys it, but for the SaaS edition nothing states where the archive or its metadata are processed. 4 6
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 per-user headline exists, but the tier where retention control, SSO or compliance export begins is unstated.
5 — Per-user prices public with billing period stated, but at least one commonly needed capability (unlimited history, SSO, eDiscovery) sits in an unpriced enterprise tier.
8 — Every tier priced publicly with per-user maths, history and storage limits, feature boundaries, 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
We found no public prices on the pages captured: the on-premise pricing page collects team size and deployment preference and promises "a tailored quote within one business day", so every tier is a sales conversation. The only visibility is a 15-day full-featured trial with no credit card required — helpful, but it is not a number a buyer can build an invoice from. 6 7
The Security Officer
We found no public prices on any page: the on-premise pricing page is a quote form promising a tailored quote within one business day, collecting team size and deployment preference. A buyer can learn the trial terms — fifteen days, full-featured, no credit card — but cannot compute any invoice from public pages, and we found no public information on where retention control, single sign-on or compliance export begin, since every tier is a conversation. 6 7
The Works Council Advocate
No public price exists anywhere captured: a 15-day full-featured trial without a credit card is published, and buying means requesting a tailored quote within one business day through a sales contact. Every purchase is a sales conversation, so a works council cannot compute an annual invoice from public pages. 2 6 7
The Compliance Counsel
We found no public prices at all: the on-premise pricing page routes every buyer to a tailored quote within one business day, so the annual invoice is a sales conversation, and we found no public information on per-user maths, storage or history limits, minimum term or VAT treatment. A 15-day full-featured trial without a credit card is reasonable evaluation access, but it does not let a buyer compute an invoice for their headcount from public pages. 2 4 6 7
The Platform Engineer
The captured pages contain no price figure at all; the pricing route is a tailored quote returned within one business day, topped by a custom SLA. The only published commercial terms are a fifteen-day full-featured trial and no credit card required. A buyer can evaluate without a conversation but cannot compute any invoice from public pages. 6 7
The Skeptic
The on-premise pricing page's offer is a "tailored quote within one business day" after submitting team size and contact details — a sales conversation with a stated turnaround, not a price. No per-user price appears anywhere in the captures, so an annual invoice is not computable from public pages; the only numbers published are the trial terms — 15 days, full-featured, no credit card required. 2 6 7
European sovereignty — proven facts
0 of 4 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 |
|---|---|---|---|
| Ownership | Not determined | — | uncited Report an error |
| Data residency | Not determined | — | uncited Report an error |
| Subprocessors | Not determined ⚠ unverified | — | uncited Report an error |
Questions about Troop Messenger
Is Troop Messenger European?
Not determined: the vendor’s pages as captured do not say where Troop Messenger is based.
Where does Troop Messenger store data?
Not stated on the vendor’s pages as of 27 Oct 2026.
Does Troop Messenger have a free plan?
Not stated on the vendor’s pages as of 27 Oct 2026.
What are the best alternatives to Troop Messenger?
As of 27 Oct 2026, the panel rates Element (3.5/5), Mattermost (3.5/5) and Stackfield (3/5) highest among the other 23 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 Element (UK / wider Europe). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: Troop Messenger alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 27 Oct 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Subprocessors. 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.
- 29 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
- 7 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
- 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
- 1 hosting 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
- 1 sovereignty dimension could not be confirmed on the vendor’s own pages and is shown as unknown. Know more? Tell us
Sources (9)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor page www.troopmessenger.com Checked 27 Oct 2026 Details →
- 2 Channels, threads & search — found from sitemap www.troopmessenger.com Checked 27 Oct 2026 Details →
- 3 Channels, threads & search — found from sitemap www.troopmessenger.com Checked 27 Oct 2026 Details →
- 4 Encryption & access control — found from sitemap www.troopmessenger.com Checked 27 Oct 2026 Details →
- 5 Encryption & access control — found from sitemap www.troopmessenger.com Checked 27 Oct 2026 Details →
- 6 Deployment & data custody — found from sitemap www.troopmessenger.com Checked 27 Oct 2026 Details →
- 7 Deployment & data custody — found from sitemap www.troopmessenger.com Checked 27 Oct 2026 Details →
- 8 Integrations & extensibility — found from sitemap www.troopmessenger.com Checked 27 Oct 2026 Details →
- 9 Integrations & extensibility — found from sitemap www.troopmessenger.com Checked 27 Oct 2026 Details →