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

## Crisp (crisp)
- URL: https://crisp.chat
- Category: Realtime, comments & collab
- Cost: mixed — Free: 2 seats, 100 customer profiles, no AI credits. Mini $45/mo per workspace (4 seats, 5,000 profiles, $5 AI credits); Essentials $95/mo (10 seats, 50,000 profiles, $25 credits); Plus $295/mo (20+ seats, 200,000 profiles). Extra seats $10/mo
- What it is: Live chat widget plus a shared team inbox covering email, chat, WhatsApp and social channels, with a knowledge base, chatbot builder, co-browsing and campaign messaging. Priced per workspace with seats bundled in rather than strictly per agent, which is unusual in this category and much cheaper for small teams.
- Why builders pick it: The cheapest way to put a real support widget and shared inbox on a site — $45/mo covers four people where Intercom bills each of them separately. The free tier is enough for a two-person project to answer reader mail.
- Trap: The free plan caps you at 100 customer profiles, which a public site burns through in days. AI and chatbot features are metered as credits on top of the plan price, so the sticker price is not the whole bill.
- Wiring: npm i crisp-sdk-web, or paste the Crisp website script tag
- Full dossier: /api/public/tools/crisp

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