1. Drop in one script tag
Add the widget to your preview builds. No framework, no dependencies, no host CSS to fight.
Comments on every preview deploy.
Pin feedback to the exact element on a Vercel preview. Your designers and clients don't need a GitHub seat — and your comment bodies don't have to live on our servers.
Get started Where comments live
<script
src="https://cdn.gutternote.com/v1/widget.js"
data-gutternote-key="pk_live_..."
defer></script>How it works
2. Anyone can comment
Designers, PMs and clients leave pinned comments without a GitHub seat or an account.
3. Threads land where you work
Sync to the pull request, resolve on merge, and block the deploy on unresolved feedback.
Your comments, your call
A comment has two halves. Where it points on the page, and what it says. Gutternote always stores the first so pins render instantly. You choose where the second lives.
Gutternote Postgres
Bodies and anchors both in Gutternote. Full feature set: attachments, edits, guest authors, instant reads.
Your GitHub repo
Comment bodies become issue comments in your repo. Gutternote keeps only the pin coordinates and an issue number.
Your own endpoint
Bodies POST to a signed HTTP endpoint you run. Nothing but positions ever reaches our infrastructure.
Backends differ in what they can do — the GitHub backend can't hold attachments, for instance. The widget reads each project's capabilities and hides what it can't honour. Full comparison →