PROVIDER - Self-hosted comment engine

Remark42

Remark42 is a self-hosted comment engine written in Go that runs from one binary plus a database, covering anonymous and social logins, email notifications and a built-in moderation console for blogs and static sites.

Community & Forum Russia 2026.11.20
3.6pts

Detailed Notes

Pros 5 items

1 binary plus an embedded BoltDB store is enough to run, and a small server can serve several sites at once
Anonymous commenting and more than 8 social login providers are supported, each of which can be enabled or disabled per site
A built-in moderation console handles reports, user blocking, data export and backups from 1 interface
One embed.js snippet and 1 container node drop the widget into any static site regardless of the backend language
MIT licensed with 0 traffic-based billing, so comment data stays in your own database

Cons 4 items

Comments only, with no boards, direct messages or member profiles, so it cannot replace a full forum
There is no managed hosting, which leaves OAuth app registration, email deliverability and backups to the operator
The admin permission model is simple, so multi-moderator workflows and tiered roles need extra tooling
Full-text search and cross-site analytics are limited, and larger operations need external reporting tools

Service Overview

Remark42 is an open source comment engine led by developer Umputun, with remark42.com as its home, source on GitHub, an MIT licence and a Go implementation. It is deliberately narrow: commenting is the only problem it solves, and it solves it as a standalone service. A site adds 1 container node and one embed.js snippet, while storage, login, notifications and moderation all belong to the service, so the site's own language and whether it is statically generated do not matter.

Within the Community & Forum category it sits at the light-interaction end. Third-party comment platforms keep data on the vendor side and often drag in blocked scripts and tracking; Remark42 moves comments back onto your own server, where the database is an embedded BoltDB file and a backup means copying 1 directory, with no third-party tracking script in the page.

That shape defines the boundary. It handles comments, replies, notifications and moderation well, and it will not give you boards, direct messages, member profiles or complex permissions. For keeping reader discussion on-site without adopting a full forum, onboarding is cheap; for running a multi-board community, it is at best a supporting tool.

Key Strengths

  • Light to deploy: a single binary with an embedded database, a small Docker image, and 1 vCPU with 1 GB of memory serving a mid-sized site, while 1 instance can host several sites.
  • Many login options: anonymous commenting is allowed or blocked per site, and social login covers Google, GitHub, Facebook, X, Yandex, Patreon, Telegram and email codes, so teams can enable only GitHub and email.
  • Real moderation: the admin console handles pending comments, reports, user blocking and data export in one place, and keyword filters with rate limits stop spam before it renders.
  • Zero coupling: the front end needs 1 config script and 1 container node, which works for static sites, SPAs and multilingual sites, with re-initialisation on route change.
  • Data ownership: MIT licensing, no usage-based billing, and comments plus users stored in your own database with exports that no vendor can withhold.

Product Ecosystem

Platform capabilities

Comments support Markdown, image uploads, voting, pinning, collapsing and threaded replies. Notifications cover email subscriptions to new replies, Telegram pushes and in-page unread markers. The admin side reports by site, user and time, exports comments to JSON and imports from other comment systems. Abuse controls include IP and user blocks, rate limits, an anonymous toggle and an optional third-party anti-spam service.

Integrations

The front end injects an iframe widget through embed.js, and SPAs must call the initialiser after route changes. Each login provider needs its own OAuth application with client id and secret, notifications use SMTP or a Telegram bot, and images can land in a local directory or object storage. In production the service usually sits behind a reverse proxy with automatic HTTPS and a scheduled backup job.

Typical scenarios

Technical blogs and documentation portals replacing third-party comments, content sites keeping reader discussion on their own domain, annotation-style discussion inside internal documentation, static site generators adding interaction, and European sites with privacy requirements.

Limitations

  • Comments only, with no boards, direct messages, member profiles or follow relationships, so full community needs turn it into an accessory.
  • No managed hosting, which means OAuth app registration, certificates, email deliverability and backups are all yours, and incidents end in documentation and logs.
  • The admin permission model is thin, so collaborative moderation and delegated roles require extra process or a proxy layer.
  • Search and analytics are limited, and at high comment volume cross-site reporting and full-text search need external tools.

Use Cases

  • Technical blogs and documentation sites (★★★★☆) - Cheap to integrate with self-held data, and replacing a third-party widget keeps page loads clean.
  • Static sites adding interaction (★★★★☆) - Independent of the site backend, 1 deployment covers the whole domain.
  • Internal documentation annotation (★★★☆) - Login restrictions and a site allowlist produce a semi-private discussion area.
  • Privacy-sensitive deployments (★★★☆) - No third-party tracking scripts and no data leaving your infrastructure, though each login provider still needs a compliance review.
  • Multi-board community operations (★★) - Without boards or a member system it is not a primary community platform.

Pricing

Item Price Notes
Remark42 software Free MIT licence, public source, no licence or usage fees
Server Provider rate 1 vCPU and 1 GB starts a small site, images and backups grow with comment volume
Domain and certificate Annual fee A dedicated comments domain is recommended, free certificates work
Email and push services Usage based SMTP carries reply notifications and codes, Telegram bots are free

Software cost is zero and spending concentrates on servers and email. Budget for OAuth upkeep, because every login provider needs its own application and renewal, and a provider shutting down has to be disabled promptly or users stall at login.

FAQ

Can Remark42 replace Disqus?

For commenting, yes: anonymous comments, social login, notifications and moderation are covered and the data stays with you. What is missing is Disqus-style cross-site recommendations, ad slots and turnkey managed hosting.

How does a static site integrate it?

Place 1 container node and the config script on the page and point them at the deployed comment service. SPAs and on-demand renderers must re-initialise after route changes, otherwise the thread does not follow navigation.

Does it handle Chinese comments and moderation?

Yes. The interface ships multiple locales, comments are stored as UTF-8, and Chinese keyword filters and moderation work normally. Word segmentation search is not a strength, so full-text retrieval needs an external engine.

How do backups and migration work?

The embedded database is a directory, so a scheduled archive is enough, and the admin console can export JSON for import into a new instance. Carry over the site id and secret, otherwise existing comments will not attach to the migrated site.

Code Examples

Start the comment service with Docker

export REMARK_URL="https://comments.example.com"
export SITE="example.com"                 # site id, comma-separated for multiple sites
export SECRET="$REMARK_SECRET"            # JWT signing secret, keep it backed up
export ADMIN_PASSWD="$REMARK_ADMIN_PASS"  # admin console password

docker run -d --name remark42 \
  -p 8080:8080 \
  -e REMARK_URL="$REMARK_URL" \
  -e SITE="$SITE" \
  -e SECRET="$SECRET" \
  -e ADMIN_PASSWD="$ADMIN_PASSWD" \
  -e AUTH_GITHUB_CID="$GH_CLIENT_ID" \
  -e AUTH_GITHUB_CSEC="$GH_CLIENT_SECRET" \
  -e AUTH_ANON=true \
  -e NOTIFY_EMAIL="$NOTIFY_EMAIL" \
  -e SMTP_HOST="$SMTP_HOST" \
  -v "$PWD/var:/srv/var" \
  ghcr.io/umputun/remark42:latest

Rotating SECRET invalidates every signed session and forces all users to log in again, so keep the original value in the backup.

Embed the comment widget in a page

<div id="remark42"></div>

<script>
  var remark_config = {
    host: "https://comments.example.com",  // comment service URL, must match REMARK_URL
    site_id: "example.com",                // must match the backend SITE value
    components: ["embed"],
    url: window.location.href,
    locale: "en"
  };
</script>
<script src="https://comments.example.com/web/embed.js" defer></script>
<noscript>Please enable JavaScript to view the comments.</noscript>

A site_id that disagrees with the backend shows an empty thread instead of an error, which is the most common integration problem.

Community & Resources

Communities and official channels

Learning resources and tools

Visit Remark42 Website → https://remark42.com/
Visit Website ↗