Lightweight page comments
Bootstrapware Comments vs Giscus, Cusdis, Hyvor Talk, and Commento
Those tools put a comment box on a page. layout="section" is that shape inside a record your server already authorized. The actor is the host session, not a separate commenter account.
Last reviewed November 2026. Vendor packaging changes; verify their site before you buy.
See Comments on a host-owned record and Comments pricing. Local and test are free. BYO is $9.99. Hosted is $19.99. No price below is a competitor's.
Fit
| Tool | What it is | Who comments |
|---|---|---|
| Giscus | Comments backed by GitHub Discussions. | A GitHub account. No GitHub user, no comment. |
| Cusdis | A small open-source comment box, aimed at sites you host. | A Cusdis commenter, not the session your app already has. |
| Hyvor Talk | A hosted comment product for websites. | Hyvor Talk's commenter identity, unless you integrate past it. |
| Commento | A self-hosted comment engine for sites. | A Commento login, not your host session. |
| Bootstrapware Comments | layout="section" is one stream on a host-owned record. Nested replies stop at depth 5. There is no thread list in that layout. | The host session. Your server mints the author token. Mentioning someone does not grant access. |
What we do not claim
This page does not say those tools lack moderation, spam controls, or a self-host option. Giscus, Cusdis, and Commento are commonly self-hosted or backed by a repo you control. Hyvor Talk is a hosted service. The split that matters here is authorization: a page widget with its own commenter, versus a section whose actor is the user your app already signed in.
Stored comment text stays plain. The widget renders a small inline subset: bold, italic, inline code, and http(s) links. Raw HTML stays text. Chat is person-to-person messaging. Feedback is requests and votes.
FAQ
Is layout=section a page comment box?
Yes. layout=section is one comment stream under a host-owned record, with nested replies and no thread list. The host session is the actor. Your server mints the author token. Readers do not create a Bootstrapware account.
Why mention Giscus separately?
Giscus stores comments as GitHub Discussions. Commenting needs a GitHub account. Bootstrapware does not. The actor is the user your app already signed in.
Do Cusdis, Hyvor Talk, or Commento use the host session?
Not as the product. They are website comment tools with their own commenter identity (or GitHub, in Giscus's case). Wiring them to your session is integration work. Comments starts from that session.
What does Bootstrapware charge?
Local and test are free. BYO is $9.99 per workspace per month. Hosted is $19.99. This page does not copy a Giscus, Cusdis, Hyvor Talk, or Commento price.
Related: Comments on a host-owned record · Comments pricing · FastComments · React component · All comparisons
Who should pick a lightweight widget or Bootstrapware Comments
Pick giscus when the page is a public docs site and GitHub Discussions is an acceptable store. giscus.app says it is always free, with no database of its own. For a lightweight comment widget, treat that as the starting constraint rather than a footnote. The work belongs in the product the customer is already signed into. Bootstrapware publishes configuration and, only on a Hosted plan you choose, the records that plan names. It does not become a second system of record by accident.
Pick Hyvor Talk when you want a hosted comment SaaS. Checked 2026-11-16: Personal is €5 per month billed annually at €50, Premium is €12 per month, and Business is €40 per month. The spreadsheet, message, post, checklist, thread, quote file, or visitor question stays on the path you picked. When the product is Importer, the spreadsheet never leaves the browser: parsing, mapping, validation, and in-file duplicate checks run in the tab. File bytes, parsed rows, and the filename are not posted to Bootstrapware. onComplete is what GitHub Discussions, a hosted comment SaaS, or your own record is allowed to see.
driver.js is not a comment system. For product tours, driverjs.com says the library is free for everyone under the MIT license. Write the server handler so a failed row is reported back instead of half-inserted. Preview errors stay inline. A customer can fix the cell, exclude the row, or download the error file and try again. Do not log payloads you would not want in an application log. Do not send those payloads to MCP or to a webhook.
Pick Bootstrapware Comments when the thread belongs on a private record your server already authorizes. Cusdis and Commento prices are omitted because their public pricing pages were not readable on 2026-11-16. Install the package, render it in a client boundary, and point the callback at your server. Publishable keys identify the workspace. Secret keys stay on the server. Local mode and test keys are free. Live config and live Hosted writes follow the price already printed on this product's pricing page. Re-read that page before you quote a number in your own UI. Link the landing page and the pricing page from the install notes so the next reader can see the boundary and the plan without searching.
Ship a thin vertical slice first: one required field, one successful completion, and one deliberate failure. Then add the real schema. If an agent writes the integration, hand it the product AGENTS.md and reject a diff that uploads content Bootstrapware is not supposed to store. The component is typed. The adapter is yours on BYO. Hosted is the plan where Bootstrapware stores that product's customer content, with the cancel rule already stated on the pricing page: writes freeze, export stays for 30 days, then Hosted data is deleted. Switching Hosted to BYO keeps the rows.
| If you need | Pick |
|---|---|
| Public docs comments stored in GitHub Discussions | giscus |
| A hosted comment SaaS billed in euros | Hyvor Talk |
| Threads on a host-owned record behind your auth | Bootstrapware Comments |
React comments component · React comments pricing · Bootstrapware Comments vs FastComments · Bootstrapware Comments vs Talkyard