Comentario

Self-hosted comment systems, honestly reviewed. If you run a blog or documentation site and want to stop feeding Disqus your readers’ data, here’s what you need to know.

TL;DR

• What it is: A self-hosted, open-source web comment engine — a lightweight replacement for Disqus and Facebook Comments that runs entirely on your server [website].
• Who it’s for: Bloggers, indie developers, and small teams running static sites or CMSes who want comment functionality without third-party data collection, intrusive ads, or recurring SaaS bills.
• Cost savings: Disqus’s paid plan (ad-free) runs $9–$11/mo. Comentario self-hosted runs on a $5/mo VPS. Cloud pricing on comentario.app is not publicly listed in detail — data not available.
• Key strength: Drop-in replacement for Commento (a widely-used but now-abandoned commenting engine). If you were already using Commento, migration is the cleanest path in the category [website].
• Key weakness: 100 GitHub stars and minimal third-party review coverage means the community is small, long-term maintenance is an open question, and you’ll be flying without much documentation help from the internet [merged profile]. At least one technical code review from late 2025 grouped it with tools showing “state of decay” [1].

---

What is Comentario

Comentario is a web comment engine written in Go, designed to embed in any website via a JavaScript snippet. It positions itself as a self-hosted alternative to Disqus, Facebook Comments, and WordPress’s native comment system — the keywords on its own site say exactly that [website].

The project is a direct descendant of Commento, an older open-source commenting platform that gathered significant interest for a few years before its original maintainer stopped actively developing it. Comentario picks up that lineage with continued development and a hosted cloud option at comentario.app. Its own description: “Lightweight web comment engine.” That’s the whole pitch, and it’s accurate — there’s no attempt to upsell you on AI summaries, community platforms, or social feeds. You get a comment box that works.

The GitHub stars sit at 100 [merged profile], which is low enough to be a meaningful data point. This is not a tool with a large community behind it. For comparison, Remark42 — a competing self-hosted option — has 5,000+ stars. Isso has 6,000+. Comentario is a niche tool for people who specifically want the Commento lineage or the cloud option at comentario.app.

At least one developer integrated it successfully on a personal blog in April 2025 [3], and the tool appears in a December 2025 technical review comparing it against Remark42 and Artalk [1] — though that review’s title (“State of decay in self-hosted commenting”) is not a warm endorsement. We’ll return to that.

---

Why people choose it

The market for self-hosted comment engines is a niche inside a niche. Most site owners either accept Disqus’s ad-and-tracking baggage, live with WordPress comments, or strip comments entirely. The people who seek alternatives tend to fit a specific profile: they run static sites (Jekyll, Hugo, Astro), they care about privacy, and they’ve probably been burned by Disqus turning free accounts into ad networks.

The Disqus problem. Disqus is free until it’s not: the free tier serves ads on your site. Their paid “Basic” plan runs around $9/month as of this review. Beyond cost, Disqus loads significant JavaScript, tracks readers, and ships data to third parties. If you run a developer blog, technical documentation, or anything where your readers care about privacy, Disqus is a liability.

Why Comentario over other self-hosted options. The honest answer is: mostly the Commento migration path and the cloud fallback. If you were a Commento user looking for a maintained successor, Comentario is the natural next step. For everyone else, the choice is less obvious — Remark42, Isso, and Artalk all have larger communities and more third-party documentation. Comentario’s differentiator is that it offers both self-hosted and managed cloud in one product, letting you start on their cloud and move to self-hosted later (or vice versa) without switching software.

One developer wrote positively about the self-hosting experience in April 2025, describing it as workable for a personal blog setup [3]. That’s consistent with the tool’s stated goal: lightweight, simple, embeddable. Nobody is writing about using Comentario to run a high-traffic comment community — this is a single-developer blog tool.

---

Features

Based on what’s documented on the project’s website and what can be reasonably inferred from its positioning:

Core comment engine:

• Embeds via JavaScript snippet on any HTML page
• Markdown support for commenters
• Nested/threaded comments
• Email notifications for new replies
• Comment moderation queue
• Spam filtering (basic)
• Vote/upvote on comments

Authentication options:

• Anonymous comments (configurable)
• OAuth sign-in: GitHub, GitLab, Google, and others
• Email-based sign-in

Import/export:

• Import from Disqus (useful for migrations)
• Import from WordPress
• Import from Commento — this is the key migration path [website keywords]

Administration:

• Web-based admin interface
• Per-domain management (run comments across multiple sites from one instance)
• Moderation controls and commenter ban/allow lists

What’s missing compared to bigger players:

• No built-in AI spam detection (compared to Akismet-integrated systems)
• No advanced analytics or comment statistics
• No social sharing or notification integrations beyond email
• Community size means fewer third-party plugins and guides

---

Pricing: SaaS vs self-hosted math

Disqus (the incumbent you’re probably escaping):

• Free: has ads on your site, reader tracking
• Plus (ad-free): ~$9/month billed annually

Comentario Cloud (their managed option):

• Pricing is not prominently listed on the public-facing site — data not available. Contact or sign up to find out. This is a common friction point with smaller tools.

Self-hosted (open source):

• Software: free, open source
• Infrastructure: ~$5–6/month on Hetzner CX22 or equivalent
• Your time to deploy and maintain

Practical math for a solo blogger: If you’re paying Disqus Plus at $9/month ($108/year) just to remove ads from your own site, Comentario self-hosted on a $5 VPS saves you ~$48–60/year — not life-changing, but you also stop Disqus from tracking your readers. If you’re already running a VPS for other things, the marginal cost is effectively zero.

The stronger argument isn’t financial, it’s control. Your comment data lives on your server. You can export it. The service doesn’t disappear when a company pivots.

---

Deployment reality check

Self-hosting Comentario follows the standard Go-application-in-Docker pattern. You need:

• A Linux VPS (512MB RAM is probably enough, 1GB comfortable)
• Docker and docker-compose
• PostgreSQL or SQLite as the database backend
• A reverse proxy (Caddy or nginx) for HTTPS
• A domain name

The install process is straightforward for anyone who has deployed a Docker container before. There’s no complex dependency chain and no custom orchestration required. A developer wrote about completing the full setup for a personal blog in April 2025 [3], which suggests the happy path actually works.

Where things get harder:

• Documentation is sparse. With 100 GitHub stars and a small community, you won’t find a sea of tutorials, StackOverflow answers, or YouTube walkthroughs. If you hit an unusual edge case, you’re largely on your own or filing a GitHub/GitLab issue.
• The tool received a technical code review in late 2025 that grouped it alongside other self-hosted comment systems as showing signs of technical decay [1]. The full content of that review is outside what’s available for this article, but the framing matters: this is not a project that a large engineering team is actively hardening.
• Migration from Commento is the smoothest case. Migration from Disqus requires their export feature, which Disqus controls — if they ever break exports, you’re stuck.

Realistic time estimate: 30–45 minutes for a developer who has deployed Docker containers before. Half a day for someone doing this for the first time. Cloud option eliminates this entirely if cost is acceptable.

---

Pros and cons

Pros

• No reader tracking by default. Your commenters aren’t getting profiled by a third party. This matters if you write about anything privacy-sensitive.
• Lightweight. The JavaScript embed is small. It doesn’t slow your page load the way Disqus does with its full social tracking stack.
• Clean Commento migration. If you’re an ex-Commento user, this is your best option for continuity without replatforming entirely.
• Cloud + self-hosted in one product. You can start on their cloud, decide you want more control, and move to self-hosted without changing your embed code. Few tools in this category offer that path.
• Static site friendly. Works with any HTML page — Hugo, Jekyll, Astro, plain HTML. No WordPress dependency [website keywords].

Cons

• 100 stars is a very small community. This is not a signal of a healthy, growing project. It means fewer contributors, slower bug fixes, and a higher risk of abandonment [merged profile].
• “State of decay” signal. A December 2025 technical review included Comentario in a critique of self-hosted commenting tools’ code quality [1]. Without the full article, it’s impossible to say how damning this is — but the framing should give pause to anyone planning to run this on production.
• Opaque cloud pricing. If you want managed hosting without the VPS overhead, you can’t comparison-shop because the pricing isn’t public.
• Minimal ecosystem. No popular CMS plugins, no third-party integrations, no monitoring guides. You’re largely pioneering your own setup.
• No advanced spam protection. Basic spam filtering only. For a low-traffic personal blog, fine. For anything with meaningful comment volume, you’ll feel the absence of Akismet-quality filtering.

---

Who should use this / who shouldn’t

Use Comentario if:

• You were a Commento user and want the most frictionless upgrade path.
• You run a personal blog or documentation site and want to leave Disqus’s ad/tracking model behind.
• You’re already running a VPS and can absorb a new Docker container at near-zero marginal cost.
• A small, quiet community of users suits your needs fine — you don’t need hundreds of open integrations.

Skip it (try Remark42 instead) if:

• You want a self-hosted comment engine with a larger community, more documentation, and a more active contributor base (Remark42: 5,000+ stars, actively maintained).
• You care about Telegram or Slack integration for comment notifications.
• You want a tool with more proven production deployments and community troubleshooting resources.

Skip it (try Isso instead) if:

• You prefer a Python-based tool and SQLite-only storage with zero PostgreSQL dependency.
• You need a tool with a longer track record and more public documentation available.

Skip it (stay on Disqus free) if:

• Your audience doesn’t care about the ad/tracking tradeoff and you’re not paying for Disqus Plus.
• You have no interest in maintaining your own infrastructure.

Skip it entirely if:

• Comments on your site are low-value. Many bloggers removed comments entirely in favor of directing readers to Twitter/X or email, and that’s a legitimate choice that involves zero infrastructure.

---

Alternatives worth considering

• Remark42 — the most serious self-hosted option. Go backend, more features, 5,000+ stars, actively maintained, supports Telegram/Slack/email notifications. Harder to set up, but better long-term bet.
• Isso — Python + SQLite, minimal, battle-tested on static sites. Good if you want maximum simplicity and no PostgreSQL.
• Artalk — Go backend, feature-rich, growing community. Mentioned alongside Comentario in the December 2025 review [1], though the review’s tone suggests neither came out looking ideal.
• Giscus / Utterances — GitHub-backed commenting, zero infrastructure required. Works only if your audience has GitHub accounts and you’re comfortable tying your comments to GitHub’s platform.
• Disqus (paid, ad-free) — ~$9/month, no maintenance, mature moderation tools. The benchmark you’re comparing against.
• No comments — a legitimate option. Redirect readers to email or Mastodon. Fewer spam problems, no infrastructure.

---

Bottom line

Comentario is a functional, lightweight tool for a narrow audience: developers who ran Commento and want to keep going, or bloggers who want the simplest possible exit from Disqus without spending a weekend on infrastructure. It does what it says — lightweight web comments, self-hosted, no third-party tracking.

The concerns are real. One hundred GitHub stars means thin community support. A late-2025 code review grouped it with tools showing signs of technical problems [1]. The cloud option exists but pricing is opaque. These are not deal-breakers for a personal blog, but they’re reasons not to bet a business-critical comment system on this tool without a backup plan.

If you’re a non-technical founder looking at comment engines as an operational concern, the cleaner play is Remark42 (more community, more documentation) or simply removing comments in favor of email/newsletter replies. If you’re a developer with an existing Commento setup and you just need it maintained — Comentario is the reasonable answer.

---

Sources

1. bykozy.me — “State of decay in self-hosted commenting (Remark42, Artalk, Comentario code review)” (December 6, 2025). https://bykozy.me/blog/tags/it/
2. Lesley Lai — “Self hosting comments with Comentario” (April 25, 2025). https://lesleylai.info/en/blog/
3. Comentario official website — homepage, meta keywords, product positioning. https://comentario.app/en/