StaticLayer vs the alternatives

You want comments on a static site, without Disqus. There are four common paths: a hosted SaaS (Disqus), a GitHub-backed commenter (Giscus / Utterances), a classic self-hosted server (Isso) — or StaticLayer, which runs inside your own Cloudflare account. Here is an honest comparison.

Comparison at a glance

StaticLayer vs Disqus

Disqus is the biggest managed network: zero infrastructure, huge moderation tooling, works anywhere. The trade-offs are exactly why many people leave it: your comments and your readers' data live on a third-party platform, the free tier has historically shown ads, and the widget is known for heavy tracking cookies. Choose StaticLayer if you want the comments and the data to belong to your site, with no ads and no tracking — and you're fine managing a small Cloudflare Worker instead of using a turnkey service.

StaticLayer vs Giscus & Utterances (GitHub-backed)

Both store comments inside your GitHub repository (Discussions for Giscus, Issues for Utterances): free, transparent, no tracking, and every comment is versioned next to your code — great for developer blogs whose readers all have GitHub. The limits are real though: visitors need a GitHub account to comment, which silently excludes a large share of non-technical readers; anti-spam and moderation are GitHub's, not yours; and reactions require sign-in too. Choose StaticLayer if you want anyone to comment with just a nickname, with your own moderation queue and built-in anonymous reactions and polls — at the cost of running a Worker + D1 instead of using your repo as storage.

StaticLayer vs Isso

Isso is the classic self-hosted commenter and philosophically the closest to StaticLayer: comments stay on infrastructure you control, no accounts, no SaaS. The difference is operational: Isso is a Python server you install, run and keep patched on a VPS; StaticLayer is the serverless equivalent — a Worker + D1 in your Cloudflare account, so there is no server to maintain, plus built-in reactions, polls and stronger anti-spam defaults (proof-of-work, single-use challenges, honeypot, time gate). Choose Isso if you prefer Python or a plain minimal tool on your own VPS; choose StaticLayer if you're comfortable with Cloudflare's generous free tier and want the same ownership without the operations.

Where StaticLayer doesn't win (honest)

• Comment text is not in your static HTML. Comments are rendered client-side by the widget, so crawlers that don't execute JavaScript won't see them. They are for your readers, not for SEO (see the FAQ).
• You need a Cloudflare account, and D1 writes are served from a single region.
• ELv2 is source-available, not OSI open source — you can read, modify and self-host it, but not resell it as a hosted service.
• Younger project: smaller community and fewer third-party integrations than Disqus or Isso.

When StaticLayer is the right fit

• Your site is static — Astro, Hugo, Jekyll, Next.js export, GitHub Pages, Cloudflare Pages…
• You don't want a comment SaaS and you don't want to run a server either.
• You want everyone able to comment with just a nickname — no account, no email.
• You want spam protection without CAPTCHA or third-party services.
• You want comments, anonymous reactions and polls in one privacy-first widget.