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 — Cusdis 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.

## Cusdis (cusdis)
- URL: https://cusdis.com
- Category: Realtime, comments & collab
- Cost: mixed — Self-host free under GPLv3. Hosted free tier: 1 site, 100 approved comments/mo, 10 quick approves/mo. Cloud Pro $12 per year for unlimited sites, comments and quick approvals
- What it is: Roughly 5 KB embeddable comment widget positioned as a privacy-friendly Disqus alternative. Readers comment without signing in and it sets no cookies whatsoever. Submissions land in a moderation queue you approve by email or from the dashboard. Self-hostable via Docker or a one-click Railway deploy; current version is 1.4.0.
- Why builders pick it: The cheapest real comment system that works for a non-technical audience — $12 a year hosted, or free on a box you already run. No login wall means casual readers actually leave comments instead of bouncing.
- Trap: Development is slow and the maintainer has publicly offered to sell the project, so treat it as low-activity software you may end up maintaining. No-login commenting plus a thin anti-spam story means you personally moderate every single thread.
- Wiring: Self-host with Docker or Railway, or paste the widget script from cusdis.com
- Full dossier: /api/public/tools/cusdis

## 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=cusdis,giscus,partykit