# Onlay compared

> Onlay next to the tools people already use for feedback, and when each one is the better choice.

- [Onlay vs Claude Code shared artifacts](/compare/claude-code-artifacts): Claude Code can publish an HTML or Markdown artifact to a claude.ai link and read comments from your organisation. How that compares with Onlay, and when each is the better choice.
- [Onlay vs Google Docs for reviewing agent-written documents](/compare/google-docs): Pasting your agent's report into Google Docs gets you comments and suggestions, but loses the HTML. When a Google Doc is the better home, and when Onlay is.
- [Onlay vs Notion for sharing agent output](/compare/notion): Notion is a good home for a team's wiki and can now read comments through its MCP server. When an agent's page belongs in Notion, and when it belongs on Onlay.
- [Onlay vs Vercel preview comments](/compare/vercel-preview-comments): Vercel's toolbar puts comments on preview deployments, and Vercel's MCP server lets an agent read and resolve them. When that is the better fit, and when Onlay is.
- [Onlay vs website feedback tools (BugHerd, Marker.io, Pastel, Markup.io)](/compare/website-feedback-tools): BugHerd, Marker.io, Pastel, Markup.io and others put comments on a live website, and several now have MCP servers. How they differ from Onlay, and when each fits.
- [Onlay vs static HTML hosts (tiiny.host, Netlify Drop, GitHub Pages)](/compare/static-html-hosts): tiiny.host, Netlify Drop, GitHub Pages and surge put an HTML file online. None of them collect feedback. When plain hosting is all you need, and when it is not.
- [Onlay vs Proof by Every](/compare/proof): Proof lets an agent share Markdown and read readers' comments and suggestions back through an HTTP API. How it compares with Onlay, and when each fits.

---

This page as HTML: https://onlay.io/compare. Everything for agents: https://onlay.io/llms.txt