{
  "data": null,
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/niches/webhooks.realtime-fanout/",
    "json": "https://www.anchorterminal.com/niches/webhooks.realtime-fanout/index.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/niches/webhooks.realtime-fanout/index.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/niches/webhooks.realtime-fanout/index.min.md"
  },
  "markdown": "One company's docs show a full fit.\n\n| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |\n| --- | --- | --- | --- | --- |\n| 1 | 3 | 4 | 18 | 8 |\n\n## What counts as done\n\nA 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.\n\nHow 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\n\n## Does the job\n\nThe docs show it meets the test above, and nothing we read says otherwise.\n\n- **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.\n\n## Does the job, with a limit\n\nIt 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.\n\n- **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.\n- **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.\n- **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.\n\n- not this job: 402cron (Georgi Kalchev (operator, a named person; no company named)): No channels or subscribers.\n- not this job: Amazon EventBridge (Amazon Web Services, Inc.): No client subscriptions or channel history.\n- not this job: Convoy (Frain Technologies Inc.): No client subscriptions or channel history.\n- not this job: Hook0 (FGRibreau SARL): No client subscriptions or history.\n- not this job: Hookdeck (Hookdeck Technologies Inc.): No client subscriptions or channel history.\n- not this job: Svix (Svix Inc.): No client subscriptions or channel history.\n- not this job: Upstash QStash (Upstash, Inc.): No client subscriptions or history.\n- not this job: Webhook Relay (AppScension Ltd): No client subscriptions or channel history.\n\n## What stops agents finishing\n\n- history off by default or held for minutes only\n- connection fails on serverless hosting\n- no idempotency key, so a retried publish duplicates\n\n## Around it\n\nBefore: webhooks.receive-reliably. \n\n## Where this comes from\n\nWeight 18 of 100 in Event delivery \u0026 webhooks: 8 of 40 accounts (Centrifugo 5, PubNub 1, Pusher 1, Ably 1); none is an agent using the channel itself\n\nAs 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.\n",
  "meta": {
    "attribution": "Anchor Terminal (https://www.anchorterminal.com)",
    "attributionRequired": true,
    "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)",
    "docs": "https://www.anchorterminal.com/docs/",
    "generatedAt": "2026-11-16",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "0.8",
    "openapi": "https://www.anchorterminal.com/openapi.json",
    "preview": false,
    "run": "2026-10-01",
    "runLabel": "October 2026 research run",
    "terms": "https://www.anchorterminal.com/terms/#data"
  },
  "page": {
    "breadcrumbs": [
      {
        "name": "Home",
        "url": "https://www.anchorterminal.com/"
      },
      {
        "name": "For agents",
        "url": "https://www.anchorterminal.com/agents/"
      },
      {
        "name": "Niches",
        "url": "https://www.anchorterminal.com/niches/"
      },
      {
        "name": "Push live updates to browsers and devices",
        "url": ""
      }
    ],
    "description": "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 \u0026 webhooks with the reason and a source.",
    "facts": null,
    "h1": "Push live updates to browsers and devices",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/niches/webhooks.realtime-fanout/",
    "published": "",
    "section": "agents",
    "title": "Push live updates to browsers and devices | Anchor Terminal",
    "toc": null,
    "updated": "2026-11-15",
    "url": "https://www.anchorterminal.com/niches/webhooks.realtime-fanout/"
  },
  "tokens": {
    "markdown": 1000,
    "slim": 230
  },
  "version": 1
}
