Two ways to run comments
When you decide to add comments, you pick between running the software yourself (self-hosted) or letting a service run it for you (hosted). Both can be privacy-respecting, and both can end badly if you choose the wrong one for your situation. The right answer depends less on the feature lists and more on how much operational work you actually want to own.
What self-hosting gives you
Self-hosted comment software, the open-source kind you install on a server you control, has real appeal. The data sits in your database. You can read the code, patch it, and change how it behaves. There is no per-site subscription. For a team that already runs servers and wants full control, this is a reasonable default.
The catch is that "free software" is not the same as "free to run." You are now responsible for the parts a host would otherwise handle:
- A server, a database, and the bill for both, sized for your traffic spikes.
- Security updates, applied promptly, because a comment box is a public write endpoint and an attractive target.
- Spam defense, which you tune and maintain yourself.
- Backups you actually test, and a plan for restoring them.
- Uptime, so a comment outage does not take the reader's trust with it.
None of this is exotic, but it is ongoing. The cost is your time, and time has a way of not showing up on the invoice. There is a fuller accounting in the real cost of a self-hosted comment system.
What hosting gives you
A hosted comment service runs the servers, the database, the spam filtering, and the updates. You paste an embed and move on. The classic worry with hosted tools is privacy: some of the biggest ones pay for themselves by loading ads and tracking readers across sites. That is a real objection, but it is a property of specific products, not of hosting itself. A hosted service can be built to not track anyone.
Gabden is a hosted service that keeps the privacy posture people usually associate with self-hosting. No tracking cookies, no fingerprinting, no cross-site tracking. Analytics are anonymous and aggregate. You still own your data and can export all of it as JSON or CSV, so choosing hosted does not mean giving up portability.
Comparing the tradeoffs
Maintenance
Self-hosted: yours, forever. Hosted: theirs. If nobody on your team wants to be paged when the comment server falls over, hosted wins on this alone.
Privacy and control
Self-hosted gives you maximum control and data locality. Hosted depends on the vendor's design. With a privacy-first hosted service and a clean export path, the practical gap narrows: you control the data through export even if you do not run the box.
Cost
Self-hosted has no license fee but real infrastructure and labor costs. Hosted has a predictable price. Gabden is free up to 100,000 widget views per month per website, and Plus is 5 dollars per month per website for unlimited views. For most sites that is less than the cost of the server the self-hosted option would need, before you count your hours. See the pricing page for details.
Speed
A self-hosted widget can be light or heavy depending on the project. A hosted embed can be either too. Gabden's embed is about 10KB and loads asynchronously, so it does not block the page.
How to decide
Choose self-hosted if you already operate servers, want the code in your hands, and have someone whose job includes keeping it patched and backed up. Choose hosted if you would rather write and moderate than administer, and you can find a service whose privacy design you trust. The failure mode for self-hosting is a neglected, out-of-date install. The failure mode for hosting is picking a vendor that monetizes your readers. Both are avoidable if you go in with your eyes open.
Join the discussion