Built for the sites that
still talk to their readers.

Lipwalk is pre-launch, so you won't find a wall of borrowed logos here. What you will find is exactly what Lipwalk does for six kinds of sites, with every claim mapped to a shipped feature.

Blogs & publications

Leave Disqus without leaving your readers

The classic migration: a blog that wants threaded comments back without shipping its readers to an ad network. One script tag replaces the widget, your accent color applies on first paint, and anonymous commenting stays on, protected by Turnstile and rate limits instead of a login wall. No ads, no trackers, and no selling reader data.

AI moderation keeps the queue civil. Clearly fine comments publish instantly, borderline ones wait for you (with an email), and spam never surfaces. Reply notifications bring readers back, each with one-click unsubscribe.

What this uses

  • Threaded comments
  • Reactions
  • AI moderation
  • Email notifications

Product & review sites

Rating stars that show up in search

Reviews are only worth collecting if they work for you. Lipwalk stores every rating as a normalized fraction and emits AggregateRating JSON-LD once a page has real volume, so your products can earn stars in search results.

Pick the scale that fits your catalog (3, 5, or 10 stars) and change it later without corrupting history: a 4/5 becomes an 8/10, never a 4/10. Reviews carry titles and text alongside the stars.

What this uses

  • Configurable rating scales
  • AggregateRating SEO schema
  • Review text

Docs & changelogs

Find out which page is failing your users

Comments on documentation are a feedback channel with intent: people tell you exactly where they got stuck. Stable page IDs keep each thread attached to its page through reorganizations, and votes float the genuinely helpful answers upward.

Wire comment.created into Slack through a signed webhook and your team sees confusion shortly after it happens, with session replay showing the rage-clicks that led there.

What this uses

  • Stable page IDs
  • Votes
  • Webhooks
  • Session replay heatmaps

Communities with their own accounts

Your login, Lipwalk comments

If your readers already sign in to your site, they should never see a second login. With site SSO you sign a token server-side and Lipwalk trusts your identity, so names and avatars come from your system.

Turn anonymous posting off and the API enforces it (a curl request gets a 401, not just a hidden form). Moderator roles let your team run the queue without touching site settings.

What this uses

  • Site SSO
  • Anonymous toggle (server-enforced)
  • Moderator roles

AI agents & automation

The first commenting system built for the agent era

Lipwalk ships an MCP server, so an agent can work the same comment data your dashboard does. Point Claude Code, Claude Desktop, or a scheduled bot at a site and it can watch the comments, summarize the conversation, reply in-thread, and moderate, all through a scoped agent key you issue and revoke.

The key is scoped to what you grant: read-only for a daily digest, or read and write for a bot that triages the queue and answers routine questions. Every action an agent takes runs through the same moderation pipeline and shows up in the audit trail, so a bot cannot do anything a moderator could not.

What this uses

  • MCP server
  • Scoped agent keys
  • In-thread replies
  • Agent moderation

High-traffic moments

Survive the launch-day spike

Comment payloads are cached at the edge, and cached reads cost you nothing, so the difference between a quiet Tuesday and the front page of Hacker News is the comments people write, not the million reads.

Per-IP rate limits and the moderation pipeline absorb the drive-by noise, the credit model means no surprise overage bill, and replay heatmaps show you what all those new readers actually did.

What this uses

  • Edge caching
  • Credit-based pricing
  • Rate limiting
  • Heatmaps

Sound like your site?

Join the early list and be one of the names that belongs on this page.