Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: not determined

0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.

by CAKE.com · pumble.com

Report an error on this page Is this your product? →

Link to this page

Pumble: AI-assisted analysis on whats-best.ai Pumble: AI-assisted analysis on whats-best.ai (dark)

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.

Pumble at a glance

Vendor
CAKE.com
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 16 Nov 2026
Panel verdict
The AI panel rates Pumble 2/5, the mean of 6 judges. Pumble is a cloud business messaging service from CAKE.com Inc. how scores are made
As of
Vendor pages captured 1 Oct 2026 to 16 Nov 2026; evaluated by the panel 18 Nov 2026. all sources

Pumble alternatives, European ones first →

Read this page as one judge. Each weighs the same scores by what they care about.

The panel's verdict

Pumble is a cloud business messaging service from CAKE.com Inc. of Palo Alto, California. It is strongest on messaging core, where scores cluster at 6-7: public and private channels, threads, mentions, reactions, file sharing and unlimited search over unlimited message history are documented. Integrations scores sit at 6 on a documented toolkit — a REST API with Swagger documentation, unlimited API keys, a published rate limit of 1000 requests per minute per user, incoming webhooks and an MCP server — that stops short of an app platform. Governance and discovery lands at 5-6: retention is configurable per scope on the Enterprise plan, but the documented export covers only public channel messages, with private channels and direct messages excluded. Lower still: encryption and access scores run 3-4 with no public information on encryption in transit or at rest; deployment control sits at 3; and pricing transparency runs 2-3 because Pro, Business and Enterprise carry no public figures. Sovereignty draws the widest spread, 0-2: a US contracting entity, and no public information on hosting location, a data processing agreement or subprocessors.

Report an error

Speaks for it

  • The Free tier is fully specified: free forever with unlimited users, unlimited channels and unlimited message history
  • Unlimited search over unlimited message history is stated outright by the vendor
  • Access controls are documented in detail, from Owner, Admin and Member roles to invitation-only private channels, per-channel guests and SAML2/OAuth2 single sign-on
  • The REST API comes with Swagger documentation, unlimited keys, availability on all plans and a published rate limit of 1000 requests per minute per user
  • Retention is configurable per scope and per channel on the Enterprise plan, from keeping everything to automatic permanent deletion

Report an error

Held against it

  • We found no public information on encryption of messages in transit or at rest, on key handling, or on an end-to-end mode
  • The documented export covers public channel messages and files as links, with private channels and direct messages excluded
  • Deleting a channel removes all messages and revisions within it immediately and permanently, outside retention settings
  • The captured pages give no prices or billing periods for Pro, Business and Enterprise, so an annual invoice cannot be computed
  • The contracting entity is CAKE.com Inc. in Palo Alto, California, and we found no public information on hosting location, a data processing agreement or a subprocessor list

Report an error

Best for

  • You need free-forever team chat with unlimited users, unlimited channels and searchable unlimited history for old decisions
  • You want to drive the workspace from other tools — posting messages, replies and reactions via REST API, incoming webhooks or Zapier
  • You want automatic deletion configurable separately for public channels, private channels and direct messages on the Enterprise plan
  • Your team lives in public channels and finds answers by search rather than by restructuring channels

Report an error

Avoid if

  • You need a complete exportable record of private channels and direct messages — the documented export excludes both
  • You must keep history intact through channel cleanups — deleting a channel removes all its messages and revisions immediately and permanently
  • Your procurement requires a European contracting entity or a stated hosting region — ask the vendor: the public pages we read do not show it
  • You need to budget a paid deployment without contacting sales — the captured pages offer only "See upgrades" and "Book a demo"

Report an error

The scores

Panel median The median of the judges’ scores per criterion. Each label opens its reasoning below.
Scores per criterion, in stars out of 5
Criterion Panel median
Channels, threads & search 3.5 of 5
Encryption & access control 2 of 5
Retention, discovery & co-determination 3 of 5
Deployment & data custody 1.5 of 5
Integrations & extensibility 3 of 5
European sovereignty 0.5 of 5
Pricing transparency 1.5 of 5

Channels, threads & search

Show 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.

Report an error

The Team Lead

Channels organised by topic, threads with the option to send a reply back to the channel, mentions, reactions, pins and saves, archived channels and public-to-private conversion are all documented, and search is unlimited over an unlimited message history — that part survives a busy Tuesday. What holds it back: we found no public information on search filters by channel, person or date, or on exporting a single conversation in a form a human can read. 2 3 6 1

Report an error

The Security Officer

Public and private channels, threads with replies that can be sent back to the channel, mentions, reactions, file sharing and unlimited search over unlimited message history are all documented, alongside guest collaborators and channel tabs. We found no public information on search filters by channel, person or date, on message edit history, or on channel rename or merge, which keeps this just under the knowledge-base level. 2 3 1

Report an error

The Works Council Advocate

Channels are public or private, with threads and reply-to-channel, mentions, emoji reactions, file sharing and "unlimited search" over unlimited message history all documented, and guests are bounded to the channel they join — a decision from eighteen months ago should still be findable. Pinned and saved items are named in the retention documentation, and archived channels appear in admin reports. We found no public information on search filters by channel, person or date, on visible message edit history, or on channel rename and merge. 1 2 3 1 3

Report an error

The Compliance Counsel

Public and private channels, threads, mentions, reactions and file sharing are all documented, with search promised for any message whenever it happened and unlimited history on the free tier. Admin reports record when channels were created, archived or made public, and the retention pages speak of message revisions and pinned or saved items, which begins to reach the archive-as-knowledge-base level. We found no public information on search filters by channel, person or date, or on renaming or merging channels without losing history. 1 2 6 1 3

Report an error

The Platform Engineer

Public and private channels, threads with replies that can be surfaced to the channel, mentions, reactions, file sharing and search over unlimited history are all documented, and guests can be added to a single channel. But deleting a channel removes its messages immediately and permanently, and I found no public information on search filters, message edit history, or channel lifecycle that preserves the archive — so this is solid daily chat, not a knowledge base you can reorganise. 1 2 3 1 6

Report an error

The Skeptic

Public and private channels, threads, mentions, reactions and file sharing are all documented, and the vendor states unlimited message history and search outright — the cap I hunt for is not in the fine print, though deleting a channel removes all its messages and revisions immediately and permanently. Guest collaborators are confined to the channels they join, and pinned or saved messages exist. Search filters by channel, person or date go unnamed, and the only export covers public-channel messages, with files as links. 2 5 6 3

Report an error

Encryption & access control

Show 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.

Report an error

The Team Lead

The access half is solid: Owner/Admin/Member roles, private channels visible only to those invited, guest collaborators confined to the channels they join, and SAML2 or OAuth2 SSO — though SSO sits on the Enterprise plan. On encryption we found no public information about transit, at rest, or any end-to-end mode, so I can only credit the room keys, not the locks. 4 3 8

Report an error

The Security Officer

Owner, admin and member roles, invitation-only private channels, guests added per channel and SAML2/OAuth2 single sign-on are documented. We found no public information on encryption in transit or at rest, end-to-end encryption, device or session management an admin can revoke, or any statement of what the vendor can and cannot decrypt — for an archive that will one day be read by someone it was not meant for, that silence decides the score. 4 8 3

Report an error

The Works Council Advocate

Access control is genuinely documented: Owner, Admin and Member roles, private channels visible only to invitees, guests confined to the channel they are added to, and single sign-on over SAML2 and OAuth2 — though single sign-on sits on the Enterprise plan and only the Workspace Owner may configure it. We found no public information on encryption in transit or at rest, on key handling, on end-to-end encryption, or on administrative revocation of devices and sessions. 4 8 3

Report an error

The Compliance Counsel

Owner, admin and member roles, private channels visible only to the invited, guests added per channel, and SSO over SAML2 and OAuth2 on the Enterprise plan are documented in real detail. We found no public information on encryption of messages in transit or at rest, on key handling, or on device or session management an admin can revoke, and those statements are what this criterion turns on. 4 8 3

Report an error

The Platform Engineer

Owner/Admin/Member roles, private channels findable only by invitees, guests confined to the channels they join, and SSO over SAML2 and OAuth2 (Enterprise plan) are all documented. I found no public information on encryption in transit or at rest, two-factor authentication, device or session revocation, or any end-to-end mode, so the access-control side is real while the crypto side is undocumented. 4 8 3

Report an error

The Skeptic

I read the captured pages for any encryption statement — in transit, at rest, end-to-end — and found none, so I score the access controls that are documented rather than an encryption level nobody stated. Owner, Admin and Member roles, invite-only private channels and guests limited to the channels they are added to are real; SAML2 and OAuth2 SSO with named identity providers is real too, but it appears only on the Enterprise plan. We found no public information on two-factor authentication, session or device revocation, or key handling. 4 8 3

Report an error

Retention, discovery & co-determination

Show 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.

Report an error

The Team Lead

Retention is the strong part: separate settings for public channels, private channels and DMs, per-channel message history, message-versus-file distinction, and edits and deletions tracked unless configured otherwise — all restricted to the Workspace Owner on Enterprise, with deletion permanent and run once a day. Discovery wobbles because the owner export covers only public channel messages and files as links while private channels and DMs are excluded, and we found no public information on legal hold or a full admin audit trail beyond channel-lifecycle reports. 6 5 3

Report an error

The Security Officer

Retention is genuinely granular — per-channel message retention, workspace-level file retention, opt-in, daily permanent deletion with pinned messages included — but it is restricted to the Enterprise plan and the Workspace Owner, and the admin export covers public channels only, excluding the direct messages and private channels a discovery request would need. Channel lifecycle reports are the only administrative activity record shown; we found no public information on legal hold, eDiscovery export, a full audit trail, or organisation-wide switches for presence and read receipts. Members can set their own retention for private channels and direct messages if the owner allows it, which a works council would note. 5 6 3

Report an error

The Works Council Advocate

Retention here deletes rather than hides: the default keeps everything, and the Workspace Owner on the Enterprise plan can set automatic, permanent deletion separately for public channels, private channels, direct messages and per individual channel — with an option to keep messages without tracking edits or deletions, and an opt-in letting members set retention for their own private conversations, both of which I welcome. The export, however, reaches only public channel messages, public files as links and users, leaving private channels and direct messages out. We found no public information on an audit log of administrative actions, legal hold, eDiscovery, or an organisation-wide switch for presence, read receipts and analytics. 5 6 3

Report an error

The Compliance Counsel

Retention is real machinery: configurable per scope, editable per channel, with options to keep everything, keep messages without tracking edits or deletions, or delete after a set period — though it sits on the Enterprise plan, deletions run once a day, and the pages state deletion is permanent. The export a lawyer would work from falls short: the workspace-owner export carries public channel messages with files exported as links, and the page states that private channels and direct messages aren't included, while deleting a channel removes all messages and revisions immediately and permanently. We found no public information on legal hold, eDiscovery export, or an admin audit trail beyond reports on channel lifecycle events. 5 6 3

Report an error

The Platform Engineer

Retention is genuinely configurable — per public channel, private channel and direct message, opt-in for the Workspace Owner on the Enterprise plan, executed once a day and permanent — with a default of keep-everything. The export is the weak point: Owner-only, public channel messages, files as links and the user list, with private channels and direct messages explicitly excluded, and the closest thing to an audit trail is a channel activity report; I found no public information on legal hold or a discovery export a lawyer could use. 6 5 3

Report an error

The Skeptic

Retention is genuinely configurable — per workspace, per channel, and separately for public channels, private channels and direct messages — with deletion documented as permanent, executed once a day, and sparing not even pinned messages; but the feature exists only on the Enterprise plan, and members can be allowed to set their own retention for private channels and direct messages. Export runs on all plans yet excludes private channels and direct messages outright, with files delivered as links. We found no public information on an audit log of administrative actions, legal hold, or organisation-wide switches for presence and read receipts. 5 6 3

Report an error

Deployment & data custody

Show 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.

Report an error

The Team Lead

This is a cloud service, and the documented exit is a Workspace Owner export of public channel messages, files as links and users, with private channels and direct messages excluded from it. We found no public information on self-hosting, a choice of hosting region, or a dedicated or private-cloud instance. 5

Report an error

The Security Officer

This is a cloud service with clients on six platforms, and the exit path is a Workspace Owner export of public channel messages, file links and users; private channels and direct messages are excluded from it. We found no public information on self-hosting, an open-source core, a choice of hosting region, a dedicated instance or a private-cloud option, so custody of the archive stays with the vendor. 5 1

Report an error

The Works Council Advocate

This is a cloud service in which the Workspace Owner on any plan can export public channel messages, public channel files as links and users. Private channels and direct messages are excluded from that export, and we found no public information on self-hosting, open source, a choice of hosting region, dedicated instances or federation. 5

Report an error

The Compliance Counsel

This is a cloud service whose documented exit is a workspace-owner export of users and public channel messages, with files exported as links rather than as files. We found no public information on self-hosting, a private cloud or dedicated instance, a choice of hosting region, or an export that includes private channels, direct messages and the files themselves. 5

Report an error

The Platform Engineer

Everything documented points to a hosted service run by CAKE.com Inc.: client apps for six platforms, an API at the vendor's host, and an Owner export of public channel messages with files as links. I found no public information on a self-hosted edition, an open-source core, federation, a private-cloud option or a hosting-region choice, so custody stays with the vendor and the documented exit is not a complete archive. 5 1 8

Report an error

The Skeptic

This is a cloud service whose documented exit is a Workspace Owner export of public-channel messages, files as links, and users — the level where the customer gets an export but not custody. Private channels and direct messages stay behind when you leave, and we found no public information on self-hosting, a private-cloud or dedicated-instance option, hosting-region choice, open source or federation. 5 1

Report an error

Integrations & extensibility

Show 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.

Report an error

The Team Lead

The API is genuinely documented — Swagger docs, unlimited API keys, a stated rate limit of 1000 requests per minute per user — and incoming webhooks come with payloads, rich text, error codes and their own rate limit, plus an MCP server and named integrations like Google Drive and Gmail. But everything flows inward: we found no public information on outgoing event subscriptions, a bot or app framework with interactive components, or SCIM provisioning. 8 7 7 3

Report an error

The Security Officer

A documented API with Swagger documentation, unlimited keys, a published rate limit of up to 1000 requests per minute per user and actions from posting to channel creation, thorough incoming webhooks with rich text, error codes and their own rate limit, an MCP server and a list of named integrations make this a real toolkit available on all plans. We found no public information on event subscriptions with retries, an interactive app framework, SCIM provisioning or a sandbox, so it stops short of a platform. 2 8 7 3

Report an error

The Works Council Advocate

There is a documented API available on all plans, with Swagger documentation, a published rate limit of 1000 requests per minute per user, unlimited keys and an Addon Bot, plus incoming webhooks with rich text, documented error codes and their own rate limit. Named integrations include Gmail, Google Drive, Calendly, RSS, GitLab via webhooks and Zoom via Zapier, alongside an MCP server and single sign-on. We found no public information on an app framework with interactive components, event subscriptions, SCIM provisioning or a sandbox. 2 4 7 8 7 3

Report an error

The Compliance Counsel

There is a documented REST API with Swagger documentation, a published rate limit of 1000 requests per minute per user, role-based keys in unlimited number, plus rich incoming webhooks with error tables, an MCP server, native integrations with Gmail, Google Drive, Calendly and RSS, and Zapier for the rest. We found no public information on an app framework with interactive components, event subscriptions with retries, SCIM provisioning or a sandbox, so this is a solid documented API rather than a platform. 7 8 7 3

Report an error

The Platform Engineer

There is a real documented API — Swagger docs, unlimited API keys per user, a stated rate limit of 1000 requests per minute, an Addon Bot and an MCP server — plus incoming webhooks with rich text, published error codes and their own one-second rate limit. The named integrations are modest (Gmail, Google Drive, RSS, Calendly, GitLab via webhooks, Zapier), and I found no public information on an app framework with permissions, event subscriptions with retries, or SCIM provisioning. 8 7 7 3 2

Report an error

The Skeptic

There is a documented REST API with Swagger documentation, unlimited keys, a published rate limit of 1000 requests per minute per user and availability on all plans — once the API addon is installed — beside incoming webhooks with rich text and a full error table, an MCP server, and named integrations such as Gmail, Google Drive, Calendly, RSS and GitLab. It stops short of a platform: we found no public information on event subscriptions with retries, SCIM provisioning, a sandbox or interactive components, and SSO sits on the Enterprise plan. 2 8 7 3

Report an error

European sovereignty panel opinion

Show 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.

Report an error

The Team Lead

The only proven facts point west: the vendor and contracting entity is CAKE.com Inc. at a Palo Alto, California address, and no EU option is stated on any captured page. Beyond that we found no public information on hosting location, an EU representative or DPA, or the subprocessor chain — so nothing European is evidenced anywhere I looked. 1 3 8

Report an error

The Security Officer

The contracting and copyright entity is CAKE.com Inc. at a Palo Alto, California address, which makes the head of the chain proven US. We found no public information on hosting location, an EU contracting entity or representative, a data processing agreement or any subprocessor, so no European element is established anywhere in the documented chain. 8 3 1

Report an error

The Works Council Advocate

The captured pages show a US vendor — CAKE.com Inc. at an address in Palo Alto, California — and no European element appears anywhere on the pages we read. We found no public information on where the archive and its metadata are hosted, on an EU contracting entity or representative, on a data processing agreement, or on any subprocessor list. 8 3 1

Report an error

The Compliance Counsel

The contracting entity is CAKE.com Inc. at a Palo Alto, California address, so the party a European customer would sign with is proven non-EU. We found no public information on hosting location or a European hosting option, a DPA, or any subprocessor list, so where the archive and its metadata actually sit is unknown from these pages. 8 3 1

Report an error

The Platform Engineer

The contracting and copyright entity is CAKE.com Inc. of Palo Alto, California, so the one proven element of the chain is non-EU, and no EU option is stated anywhere I read. I found no public information on hosting location, an EU representative, a published data-processing agreement, or any subprocessor list. 1 8 3

Report an error

The Skeptic

The proven chain starts and ends in California: CAKE.com Inc. at 2100 Geng Rd, Palo Alto is the vendor and copyright entity on the captured pages, and no EU hosting, EU contracting entity, EU representative or published DPA appears anywhere I read. Where messages and their metadata are hosted, and which subprocessors touch them, are unknown from this evidence. On every dimension the pages do establish, the answer is American, with no EU option stated. 8 3 1

Report an error

Pricing transparency

Show 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.

Report an error

The Team Lead

Four tiers are named — Free, Pro, Business, Enterprise — and the free one is fully specified with unlimited users, unlimited channels and unlimited message history, free forever. We found no public prices for the paid tiers, so a buyer cannot compute an annual invoice for a paying headcount, including the Enterprise-level retention and SSO features, from these pages alone. 2 1 1

Report an error

The Security Officer

The four plan names and a detailed free tier — unlimited users, unlimited channels, unlimited message history, free forever — are public, and some feature boundaries are stated, such as retention and single sign-on being Enterprise-only. We found no public information on prices, billing periods or per-user maths for Pro, Business and Enterprise, so an annual invoice for a given headcount cannot be worked out from the captured pages. 1 2 1

Report an error

The Works Council Advocate

The four plan names are public and the free tier is fully specified — free forever, unlimited users, unlimited channels, unlimited message history — but we found no public prices for the Pro, Business and Enterprise plans. Retention and single sign-on both sit on the Enterprise plan, so the compliance features a works agreement will turn on cannot be costed from public pages, and the annual invoice for a given headcount cannot be computed. 1 2 4 6 1

Report an error

The Compliance Counsel

The Free tier is fully specified — free forever with unlimited users, channels and message history — and four plan names are public. The captured pages give no price for Pro, Business or Enterprise and no billing period, so the annual invoice for a given headcount cannot be computed; the compliance-relevant features, retention and SSO, are documented as Enterprise-only, in the tier these pages do not price. 1 2 4 6 1

Report an error

The Platform Engineer

Four tiers are named — Free, Pro, Business, Enterprise — and the free tier is fully specified as unlimited users, unlimited channels, unlimited message history, free forever. I found no public per-user prices for the paid tiers on the pages I read, so an annual invoice for a given headcount is not computable; the one useful boundary that is stated is that retention and SSO sit on the Enterprise plan. 1 2 1

Report an error

The Skeptic

The Free tier is priced publicly and unusually clearly — free forever, unlimited users, unlimited channels, unlimited message history — but Pro, Business and Enterprise carry no figures on the captured pages, only "See upgrades" and "Book a demo". The features that force the paid decision, retention and SSO, are both documented as Enterprise-only, so the annual invoice a compliance-minded buyer actually needs is the one thing no page prices. Billing period, VAT treatment and minimum term are unstated. 2 4 6 1 1

Report an error

Questions about Pumble

Is Pumble European?

Not determined: the vendor’s pages as captured do not say where Pumble is based.

Where does Pumble store data?

Not stated on the vendor’s pages as of 16 Nov 2026.

Does Pumble have a free plan?

Yes. Pumble has a free plan, per the vendor’s page captured 16 Nov 2026.

What are the best alternatives to Pumble?

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: Pumble alternatives.

Where this could be wrong

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.

Sources (8)

The pages every claim on this page was read from — each one checked, dated, and kept verifiable.

  1. 1 Vendor page pumble.com Checked 16 Nov 2026 +2 earlier captures: 9 Nov 2026, 2 Nov 2026 Details →
  2. 2 Channels, threads & search — found from sitemap pumble.com Checked 16 Nov 2026 Details →
  3. 3 Channels, threads & search — found from sitemap pumble.com Checked 16 Nov 2026 +1 earlier capture: 2 Nov 2026 Details →
  4. 4 Encryption & access control — found from sitemap pumble.com Checked 16 Nov 2026 Details →
  5. 5 Retention, discovery & co-determination — found from sitemap pumble.com Checked 16 Nov 2026 Details →
  6. 6 Retention, discovery & co-determination — found from sitemap pumble.com Checked 16 Nov 2026 Details →
  7. 7 Integrations & extensibility — found from sitemap pumble.com Checked 16 Nov 2026 +1 earlier capture: 1 Oct 2026 Details →
  8. 8 Integrations & extensibility — found from sitemap pumble.com Checked 16 Nov 2026 Details →