Free to download is not free to run
Self-hosted comment systems are appealing for good reasons. The software is often open source, you keep your data on your own server, and there is no monthly bill for the tool itself. But "the tool costs nothing" and "comments cost nothing" are different claims. Once you run the software yourself, you take on every job that a hosted service would otherwise do quietly in the background. Some of those jobs cost money. Most of them cost time. Adding them up gives you the real number, and it is rarely zero.
The infrastructure line
Comment software has to run somewhere. That usually means:
- A server or container to host the application, sized to handle traffic spikes when a post does well.
- A database to store comments, plus the storage and backups that go with it.
- Bandwidth for every widget load, which grows with your traffic.
- Possibly a mail service so the system can send notification and confirmation emails.
None of these are large on their own. Together they are a recurring bill that scales with your success, which is the opposite of what you want from an "off the shelf" feature. And if your site is on a static host or a platform with no backend, you are adding infrastructure you did not otherwise need at all.
The time line, which is bigger than it looks
The infrastructure cost is visible on an invoice. The time cost hides in your calendar, and it is usually the larger number.
Updates and security
Self-hosted software needs patching. A comment system takes untrusted input from the public internet, which makes it a target. Skipping updates is how a small blog ends up with a compromised server. Someone has to watch for releases, apply them, and test that nothing broke.
Spam
Spammers find open comment endpoints fast. Out of the box, most self-hosted systems need tuning, filter lists, and ongoing attention to keep junk out. That work never really ends because the spam keeps evolving.
Backups and uptime
If the server goes down, your comments go with it until you fix it. If the database is lost and there is no good backup, the comments are gone for good. Both are your responsibility, at whatever hour they happen to break.
The download is free. The Saturday afternoon you spend patching a security hole is not.
Put a number on your time
Add up a realistic monthly figure: server and database hosting, backups, mail, and an honest estimate of the hours you spend on updates, spam, and the occasional outage. Multiply the hours by what your time is worth. For most independent sites and small teams, the total lands well above what a hosted service costs, and that is before counting the stress of being on call for your own comment section. We break down the broader tradeoff in self-hosted vs hosted commenting.
What a hosted service replaces
A hosted comment system rolls all of that into one predictable line. Gabden runs the servers, applies the updates, filters the spam, and keeps backups, so none of it lands on you. The embed is about 10KB and loads from our infrastructure, so it adds nothing to your hosting bill and does not slow your pages. You still own your data: Gabden lets you export everything as JSON or CSV whenever you want, which answers the main reason people choose self-hosting in the first place. And on privacy, there are no tracking cookies, no fingerprinting, and no cross-site tracking, so hosting elsewhere does not mean handing your readers to an ad network.
When self-hosting still makes sense
If you have a platform team that already runs services, strict rules that require data to stay on specific hardware, or you simply enjoy operating your own stack, self-hosting can be the right call. The point is not that it is wrong. The point is to count the full cost before you decide, so "free" does not turn into a second job.
Where to start
Tally your realistic monthly total for hosting plus maintenance hours, then compare it to a flat per-site plan. 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. See the details on the pricing page and weigh it against your own number.
Join the discussion