Giscus is a comment system that stores threads in a GitHub repository's Discussions. It is free, open-source, and it does not track readers, which is why developer blogs like it. It also has one limitation that matters for a wider audience: to comment, a reader needs a GitHub account and has to authorise the app against it.
If your readers are all developers, that is fine. If they are not, the GitHub requirement quietly filters out most of the people who might otherwise join the discussion. This post is a fair look at where Giscus is strong and where an alternative like Gabden fits better.
What Giscus does well
- It is free and open-source, with no vendor pricing.
- It does not track readers or run ads.
- Your comments live in your own GitHub Discussions, which you control.
- It is light and fits neatly into static sites.
Those are real strengths, and if your audience already lives on GitHub, Giscus is a reasonable choice. The trade-offs show up when you look past that audience.
The GitHub-account wall
The core issue is participation. Every commenter must have a GitHub account and grant access to the giscus app. A casual reader on a cooking blog, a photography site, or a small-business page is not going to sign up for GitHub to leave a comment. You never see the comments they would have left, so the thread looks quiet even when readers wanted to talk.
A comment system's job is to let readers speak. Any login requirement that most of your audience does not already meet is a tax on participation.
Where Gabden differs
Gabden keeps the parts people like about Giscus, no tracking and a light footprint, and removes the account wall. Readers can comment in the way that suits them:
- Anonymously, with no account at all.
- As a guest, with just a name and email.
- Signed in with Google or GitHub for a hosted profile.
GitHub sign-in is still there for the readers who want it, but it is one option among several rather than a hard requirement. That single change usually turns a silent thread into an active one.
Privacy and speed
Gabden matches Giscus on the privacy points that matter: no tracking cookies, no fingerprinting, no cross-site tracking, and anonymous aggregate analytics only. The embed is about 10KB and loads asynchronously, so it does not slow down your pages. On both counts you are not giving anything up by moving.
Moderation and management
Giscus moderation runs through GitHub's own tools, which are built for code discussions rather than blog comments. Gabden gives you moderation modes made for this: pre-moderate everything, auto-approve, auto-approve returning verified people, or moderate only anonymous users. There is a blocked-word filter, a spam and pending queue, threaded replies, and reactions. For a growing site, that is a more direct workflow than managing comments as GitHub Discussions.
Setup and cost
Both are quick to add. Giscus configures a script tied to your repo; Gabden is one div and one script tag keyed to each page's canonical URL. Gabden is free forever up to 100,000 widget views per month per website, with a small "Powered by Gabden" mark, and Plus removes the mark for 5 dollars per month per website. Giscus has no fee at all, which is worth weighing if cost is your only constraint.
Which to choose
Choose Giscus if your readers are developers who already have GitHub accounts and you want a free, repo-backed system. Choose Gabden if you want anyone to be able to comment without a GitHub account, with moderation built for blog discussion and the same privacy posture. If you are weighing GitHub-based tools generally, the Utterances alternative post covers the same trade-off. To try Gabden, register a free site and add the widget to a post your non-developer readers actually read.
Join the discussion