Capture website feedback with screenshots, comments, and context so your team can fix issues faster.
Pre-Beta Live Now

Nothing to install on your site. No code changes. Every round of feedback stays pinned where it was left, so the next visit picks up where the last one stopped.
Drop in your site URL. A Dock is one website, one QA workspace, one place every round of feedback lands.
Every Dock can hold multiple Layers, so you can review different states of the site side by side without losing history.
Send the client link. They install the extension once, type a name, and start pinning. No account, and your internal notes stay private.
Each pin arrives with the element, the screenshot and the diagnostics attached. Assign it, track it, mark it resolved.
The workflow is the same everywhere — what changes is who is on the other end of the link and what they need attached to the pin.
Every pin arrives carrying what a developer would otherwise have to ask for — it is still there on the page the next time anyone opens it, and your coding agent can read it without you.
Open the site tomorrow and every earlier pin is still on the element it was about. When the DOM changes under it, Layerdock re-finds the element by selector, then by its text, then by matching the shape and position it had — through shadow DOM included. Nobody reports the same bug twice.
Every pin carries the console errors and the failed or slow requests from the moment it was reported, timed against the screenshot, with the element, page URL, viewport, browser and OS. Nothing to reproduce, nothing to ask for.
Connect the MCP server once and your agent reads the pin itself — selector, screenshot and console trace included — then replies on the thread and marks it resolved without you leaving the editor.
Review every layout from one toolbar — the three presets, or drag the frame to any width in between. Each pin records the width it was left at. No DevTools, no second device.
Connect a dock once and every new pin, reply, status change and assignment is pushed through, with the screenshot and the console trace attached.
Reviewers are unlimited and free on every plan here, including the trial. Most of the category meters them, which is what makes a client round expensive to run.
| Tool | Entry price | What that buys |
|---|---|---|
| Layerdock | $19/mo | Pro — per workspace, unlimited reviewers, 5 docks |
| BugHerd | $50/mo | 5 members, unlimited projects, +$8/mo per extra member |
| Marker.io | $39/mo | Billed annually, 3 users. Console + network on the $149/mo Team plan |
| MarkUp.io | $79/mo | Pro — unlimited users, 1 workspace, 500GB storage |
| Userback | $39/mo | Team — 5 seats, 5 projects ($29 billed annually) |
Entry pricing read from each vendor's own pricing page on 29 August 2026. Layerdock is not the cheapest tool in the category.
Full comparisonsAlternativesBilling questions — proration, annual billing, cancellation — are answered on the pricing page.
No. They open the share link, install the browser extension once, type a name and start pinning. Nothing to sign up for, and no password to reset three weeks later when the next round starts.
No. There is no script tag and no code change, which is also why it works on a staging site or a client site you have no deploy access to. The feedback layer comes from the browser extension, not from your page.
Nothing. You never re-collect a round of feedback after shipping, and a client coming back to the same link finds their earlier pins where they left them rather than an empty page.
One site, one review workspace, one shareable link. Every round of feedback for that site lands in the same place, and a dock can hold multiple layers so you can review different builds without losing the earlier rounds. More on docks.
Chrome, Edge, Brave and Arc — every Chromium browser. The reviewer installs it once and it works on every dock they are sent afterwards.
They are captured on every pin regardless of plan, but reading them is part of the $49 Agency plan. Because capture is never gated, upgrading reveals the full history rather than starting from empty.
One link. Every pin still on the element it was about, redeploy after redeploy.