Choose where your feedback lives.
Some tools start with a widget. Some start with a recording or a canvas. Feedbacks starts with a screenshot, a pencil mark and a discussion your team and agent can follow on your own server.
Several tools here also offer MCP, self-hosting or both. Each page links to the vendor's own description, and makes the tradeoffs clear.
Open source
BugPinTwo self-hosted visual feedback tools with different capture and storage
choices.FasterFixesBoth can put visual feedback in an agent's hands. Their deployment
paths differ.SitePingA drop-in website widget and a separate review workspace solve different
setup problems.OpenReplay + SpotA replay-led bug report and a marked screenshot preserve different kinds
of evidence.
Hosted tools
BugHerdBoth make website feedback visible. The difference is where the product
runs and when work becomes a task.Marker.ioMarker.io routes feedback into existing task systems; Feedbacks keeps the
first discussion in your own workspace.MarkUp.ioMarkUp spans creative formats. Feedbacks is built around website review
and agent-readable discussion.Markup HeroQuick screenshot annotation and an ongoing team review workspace serve
different moments.Redpen.aiTwo browser-based ways to report a website issue, with different
ownership of the review record.PastelBoth connect feedback to coding agents. Pastel organizes canvases;
Feedbacks provides a self-hosted team slate.RuttlRuttl covers several design surfaces. Feedbacks concentrates on the
website conversation and its agent context.SuperflowSuperflow puts collaboration on the site. Feedbacks makes the captured
thread portable to your own server.UsersnapUsersnap collects many kinds of product evidence. Feedbacks keeps visual
website review focused.UserbackBoth provide visual reports and MCP. Userback also runs a broad product
feedback loop.AtarimAtarim connects client requests to site work. Feedbacks keeps the review
evidence in an open stack.