Stop guessing which one. Put them side by side.

The grid says what these tools are. This says what builders did about it — one decision per person, changeable whenever you change your mind.

# Tool comparison — Pusher Channels vs Giscus vs PartyKit

Source: Kbaise, a directory of tools that work with Lovable projects.
Pick one and tell me why before writing any integration code.

## Pusher Channels (pusher-channels)
- URL: https://pusher.com/channels
- Category: Realtime, comments & collab
- Cost: mixed — Sandbox free: 200,000 messages/day, 100 concurrent connections. Startup $49/mo (1M msgs/day, 500 connections); Pro $99/mo (4M, 2,000); Business $299/mo (10M, 5,000); Premium $499/mo (20M, 10,000); Growth $699/mo (40M, 15,000)
- What it is: The classic hosted pub/sub WebSocket service: your backend triggers events on named channels and browser clients subscribe. Supports private and presence channels with server-side auth endpoints, official SDKs for every major platform, and webhooks for connection and channel events. No infrastructure to run.
- Why builders pick it: Notification badges, live comment counts and 'N people reading this' banners in an afternoon. The API surface is small enough to learn in one sitting, and 200,000 free messages a day covers a lot of ordinary ordinary traffic.
- Trap: Billing keys on concurrent connections and messages per day, both of which spike exactly when an article goes viral. Exhausting the daily message cap on the free plan stops delivery entirely until the counter resets at midnight UTC.
- Wiring: npm i pusher pusher-js
- Full dossier: /api/public/tools/pusher-channels

## Giscus (giscus)
- URL: https://giscus.app
- Category: Realtime, comments & collab
- Cost: free — Free forever and open source. No hosting cost, no database, no accounts to administer — every thread is stored as a GitHub Discussion in a repository you already own
- What it is: Comment widget that stores each thread as a GitHub Discussion. You install the giscus app, enable Discussions on a public repo, and a script tag maps each page to a discussion by pathname, URL or og:title. Supports threaded replies, reactions, themes and lazy loading, with no database of your own.
- Why builders pick it: Zero infrastructure, zero cost, zero moderation queue — GitHub handles authentication, spam and abuse reporting for you. For a developer-audience project or a docs site it is the default answer and takes about ten minutes.
- Trap: Commenters need a GitHub account and must authorise the app, which excludes almost all non-technical readers — usually disqualifying for a general-audience project. The repository must be public, so every comment is public too.
- Wiring: Paste the generated script tag from giscus.app/#configuration
- Full dossier: /api/public/tools/giscus

## PartyKit (partykit)
- URL: https://www.partykit.io
- Category: Realtime, comments & collab
- Cost: free — Individual free: deploy to PartyKit cloud, up to 10 live projects, room storage cleared every 24 hours. Commercial free: deploy to your own Cloudflare account with unlimited projects and custom domains, paying only Cloudflare Workers and Durable Objects usage
- What it is: Open-source framework for stateful realtime servers built on Cloudflare Durable Objects. Each 'party' is a server-side class owning a room of WebSocket clients, so presence, chat, cursors and Yjs sync take a few dozen lines. PartyKit announced it was joining Cloudflare in April 2024.
- Why builders pick it: You want a multiplayer backend without operating one. npx partykit dev gives a local room server in seconds, and deploying to your own Cloudflare account keeps the bill at raw Workers prices instead of a per-message meter.
- Trap: Since the Cloudflare acquisition, momentum has shifted toward Cloudflare's own Durable Objects and Agents SDK — treat PartyKit as a convenience layer that may fold into the platform. Free-tier room storage is wiped every 24 hours, so it is not durable.
- Wiring: npm create partykit@latest
- Full dossier: /api/public/tools/partykit

## Quick read

- Free with no card: Giscus, PartyKit.

## Rules
1. Prefer the free tier when no budget was stated, and say what the ceiling is.
2. Read the full dossier before integrating.
3. Fetch /api/public/models before writing any AI model ID.

Agents can fetch the same thing: GET /api/public/compare?slugs=pusher-channels,giscus,partykit