Garrul
Self-hosted comments for static sites and blogs. Runs on Cloudflare
Workers + D1 + KV + Turnstile. One Worker per site, no per-comment
billing, your data stays in your account.
Try the live demo →
Self-hosted, but not the hard kind: there is no container, no VPS, and
no database server. Nothing to patch, no uptime to monitor, no TLS to
renew, and Cloudflare keeps point-in-time backups of D1 for you. It is
one Worker, and keeping it current is a single dry-runnable command per
release. Two credentials to get started (a Turnstile key pair, from one
dashboard page); every other integration is optional.
- Threaded comments: markdown, reactions, an edit/delete window, and
a newest/oldest/top sort readers can switch
- OAuth sign-in (GitHub, Google, Facebook, X, Discord) plus anonymous
posting, rate-limited and Turnstile-gated
- Embeddable widget: CI-capped at 30 KB gzipped, Shadow-DOM isolated,
themeable (visual theme builder), with an
iframe alternative
- Reply notifications by email, built in: readers opt in from the
widget, confirm by double opt-in, get a debounced digest, and leave in
one click from Gmail's own Unsubscribe button. Bring a Resend key
(
docs/notifications.md)
- Moderator notifications by email: a digest of what's queued or
reported. Off by default; one switch in Settings → Moderation
- Layered anti-spam: Turnstile, rate limiting and a strict markdown
sanitizer always on, four tunable heuristics and an optional classifier
on top, everything routed to the queue
(
docs/ANTISPAM.md)
- Import from Disqus, Remark42, Comentario, isso or Cusdis: upload the
export in the admin UI — the
.xml.gz Disqus hands you, the
userbackup-<site>-<ts>.gz Remark42 writes nightly, or Comentario's JSON
export, no unzipping — or run
npm run import-disqus -- ./export.xml.gz --dry-run /
npm run import-remark42 -- ./userbackup.gz --dry-run /
npm run import-comentario -- ./export.json --dry-run first. The Comentario
reader also takes a legacy Commento export. isso and Cusdis ship no export
at all, so they're two steps — npm run dump-isso -- ./comments.db --out dump.json or npm run dump-cusdis -- ./db.sqlite --out dump.json to read
the SQLite store, then either npm run import-isso / npm run import-cusdis -- ./dump.json --dry-run or upload that same dump.json on
the admin UI same as the other sources (see
docs/importing.md). Idempotent, so a re-run inserts
nothing; closed threads stay closed and spam stays out of the public tree
- Admin UI: moderation queue, user management, and settings you
change without a redeploy
- RSS feeds, comment counts, permalinks
- Webhook out on every comment event: generic, Slack, Discord, or
Telegram
- Telegram operator bot: moderate from your phone with inline
buttons,
/queue and /stats, optional daily digest
- Pinned comments — moderators pin one top-level comment per post; it
shows first on page one
- Staff badge — moderators and admins can mark a comment as posted by
staff; the label is configurable
- Choose your reactions — pick which of 12 reaction emoji appear on
comments and on the page bar, in any order
- Reactions-only mount —
data-mode="reactions" renders just the page
reaction/vote bar, in one request
- Full-site export — admins download every post, comment and user as
JSON, or comments as CSV
- One-command install —
npm run setup asks two questions, then creates
resources, secrets and the hostname, migrates, deploys and checks health
Every doc in the repo, grouped by task:
docs/README.md.
Screenshots
What your readers see, rendered inside a Shadow DOM so the host page's CSS
can't collide with it:
The admin dashboard, with counts at a glance, your embed snippet ready to
copy, and 30-day comment volume:
The moderation queue, where comments are approved, marked spam or deleted
inline:
More, including dark mode, mobile, and the rest of the admin UI:
docs/screenshots.md.
Architecture
One Worker serves the widget, the API and the admin UI; a cron pass on the
same Worker sends notifications:
The Worker, cron handler, D1, KV and edge cache run in your Cloudflare
account; everything else is an outside service. Component-by-component notes:
docs/architecture.md.
Install
Deploying to production takes ~20 minutes the first time, and then
npm run upgrade per release: one command with a --dry-run that prints
its plan before touching anything. That is the whole maintenance story;
there is no OS to patch and no service to restart.
여기까지가 README 앞부분입니다. 나머지는 원문에서 읽을 수 있습니다. README 전문 보기 ↗
