# Push live updates to browsers and devices

> Push live updates to browsers and devices: 1 companies fully do it, 3 with a limit, 4 carry the tag. Every listing in Event delivery & webhooks with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/webhooks.realtime-fanout/
- Markdown: https://www.anchorterminal.com/niches/webhooks.realtime-fanout/index.md (~1,000 tokens)
- Slim: https://www.anchorterminal.com/niches/webhooks.realtime-fanout/index.min.md (~230 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/webhooks.realtime-fanout/index.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-15

One company's docs show a full fit.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 1 | 3 | 4 | 18 | 8 |

## What counts as done

A message published once reaches every subscribed client, a client that reconnects can recover missed messages from history, and presence or unsubscribe events reach the backend.

How agents ask for it: show live updates in the app; push this to every connected client; build a chat backend; notify the device when a message arrives

## Does the job

The docs show it meets the test above, and nothing we read says otherwise.

- **Centrifugo (Centrifugal Labs LTD)**: One publish via the server API reaches every subscriber; with history enabled per namespace, clients recover missed messages by offset and epoch; proxy events reach the backend, and the unsubscribe gap (#1147) is closed. acc-19 to acc-21 run it in production.

## Does the job, with a limit

It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.

- **Ably (Ably Realtime Ltd)**: Publish once reaches every subscriber in order, and outbound webhooks carry presence events to a backend, but resume covers only 2 minutes unless persistence is enabled by channel rule, and acc-40 reports connections failing on Vercel.
- **PubNub (PubNub Inc.)**: One publish reaches every subscriber, clients resume from their last timetoken via Message Persistence, and presence events forward to webhooks; but persistence is off on new keysets, and the server never deduplicates, so a retried publish duplicates.
- **Pusher Channels (MessageBird UK Limited)**: One publish reaches every subscriber and presence webhooks reach the backend, signed with HMAC over the body; but there is no message history, so a reconnecting client cannot recover missed messages, and publish has no idempotency key.

- not this job: 402cron (Georgi Kalchev (operator, a named person; no company named)): No channels or subscribers.
- not this job: Amazon EventBridge (Amazon Web Services, Inc.): No client subscriptions or channel history.
- not this job: Convoy (Frain Technologies Inc.): No client subscriptions or channel history.
- not this job: Hook0 (FGRibreau SARL): No client subscriptions or history.
- not this job: Hookdeck (Hookdeck Technologies Inc.): No client subscriptions or channel history.
- not this job: Svix (Svix Inc.): No client subscriptions or channel history.
- not this job: Upstash QStash (Upstash, Inc.): No client subscriptions or history.
- not this job: Webhook Relay (AppScension Ltd): No client subscriptions or channel history.

## What stops agents finishing

- history off by default or held for minutes only
- connection fails on serverless hosting
- no idempotency key, so a retried publish duplicates

## Around it

Before: webhooks.receive-reliably. 

## Where this comes from

Weight 18 of 100 in Event delivery & webhooks: 8 of 40 accounts (Centrifugo 5, PubNub 1, Pusher 1, Ably 1); none is an agent using the channel itself

As data: https://www.anchorterminal.com/api/v1/use-cases/webhooks.realtime-fanout.json, or the MCP tool get_use_case with id webhooks.realtime-fanout. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
