Feedback on your live website — not in your inbox
Point at the problem. Leave feedback. It stays pinned.
Clients, testers and teammates click anything on your site — a button, an image, a whole page — and say what's wrong, what's missing, what to change. The feedback is pinned to that exact thing, survives your next redesign, and lands in a board your team can triage. No screenshots with arrows. No “which page?” emails.
What you get
Everything a feedback tool should do — in one widget.
Point and comment
Click anything on the page and flag it — a button, an image, a whole section. Drag to circle a region, or leave a comment about the page itself. Clients and testers never need an account.
Show, don't describe
Attach a screenshot or record a short video of what you're seeing — and it arrives with the screen size, browser and page it happened on. No more three-round “can you reproduce it?”
A board to work it
Feedback lands in a board grouped by status, type or priority. Drag cards, assign, resolve — or push an item to Linear straight from the page.
It stays where it was left
Redesign the page and feedback still points at the thing it was left on, not at an outdated screenshot. When it isn't sure of the spot, it says so instead of guessing.
Invisible until opened
One small script, silent on your page. No launcher, no clutter — nothing even loads until someone you've invited opens it. Your real visitors never see it.
What it feels like
One script tag. No account for the person leaving feedback.
They point and say it
A toolbar, not a form. Click anything, drag a box around a region, or capture the whole page when the problem is everywhere. No one leaving feedback ever signs up.
They record the repro
“Share session” records the page into the webm the team watches later — the masked canvas, not the raw pixels, so a private region stays private in every frame. Mic to narrate, pen to point, and it lands in the inbox like any other note: nothing is live, nothing is filed until they send it.
It arrives with the evidence
The screen size and browser it broke in, the page it happened on, and the last console messages if you opt in. “It's broken” with nothing attached is what makes a bug impossible to reproduce.
You work it like a board
Cards you can drag, grouped by status, type or priority. Every one links straight back to the live thing it was left on.
Proof, not promises
“Feedback stays on the thing” — measured, not promised.
The anchoring engine is open source and MIT licensed, so the part your feedback depends on is the part you can read. How the matching works →
Put it on a site this afternoon.
One script tag, one key. It stays completely invisible until the people you invite open it — no launcher, no clutter, no effect on your visitors. From there it's the whole loop: they point, they say, you triage, you ship.