A close look at LayerDock, a browser based tool for collecting website feedback with no install and no account for reviewers. What it does, how the pin and Dock system works, what it costs, and where it still falls short.
Most website feedback still travels as a screenshot and a comment, sent over email or Slack. None of that tells a developer which browser was open or whether a console error fired at the time. LayerDock just moves the review into the browser. You pin a comment on the actual element of a live page, and the technical context comes with it, no install and no account for the reviewer.
We went through LayerDock's docs, pricing page, and its public GitHub project, and checked it against BugHerd and Marker.io, the two tools doing roughly the same job. Here is what we found.
LayerDock is a feedback tool that runs inside the browser. You send someone a link. They open it, click on whatever they want to flag, and the comment sticks to that exact spot. No sign-up screen, no extension to install.
The company's reasoning: most website feedback gets lost between a screenshot and a Slack thread. So the review happens in the browser, with the technical detail already attached. That part holds up.
It is a small team, led by Zain Khan, and LayerDock calls itself an early product on its own site. You see that in the integration list and the review volume, both thinner than older tools, more on that below. The pin mechanic works, though. It grabs real technical context without anyone having to ask for it.
A Dock is a review space. Point it at a URL, share the link, and anyone who opens it can start pinning comments. There is no account step for the reviewer. That sounds minor until you remember that is usually the moment a client gives up and just emails you a screenshot.
Pins attach to the element itself, not a fixed x and y spot on the page. A comment left on a button stays on that button even after a deploy reshuffles the layout around it. LayerDock says pins carry over across deployments because of this.
Each pin comes with a screenshot from the moment it was left, the page URL, the browser and device, and the viewport the reviewer was on. A developer opens it and sees what the reviewer saw. No piecing it together from two lines in Slack.
Every pin fires a screenshot automatically and records the specific element it was placed on, down to spacing, applied styles, and the box model, so a developer can inspect the actual markup instead of guessing from a picture.
On the paid tiers, LayerDock captures console errors and network requests from around the moment the pin was left. For a bug report, this is usually the difference between fixing something on the first try and asking the reporter to reproduce it again.
Reviewers record their screen with narration instead of writing out the steps. Useful for bugs that only break after a specific sequence of clicks.
A reviewer can flip between desktop, tablet, and mobile views inside the Dock. If a layout bug only shows up on mobile, the pin already knows that.
Arrows, highlights, and freehand notes can be drawn directly on the captured screenshot, which covers the cases where pointing at one element is not enough to explain what is wrong.
LayerDock runs an MCP server that connects its pins to AI coding agents: Claude Code, Cursor, Codex CLI. MCP is the standard that lets an agent pull live context from another tool on its own. A developer does not have to type the details in by hand. We build this same kind of connection for clients who want AI agent workflows wired into their real data.
Pull a pin into Claude Code or Cursor and the agent already has the screenshot, the element, and any console errors. A developer would otherwise have to go dig all of that up by hand. LayerDock's framing is that this shrinks the distance between a bug getting reported and an agent fixing it.
The same thing applies outside LayerDock. Bug trackers and feedback tools already hold the context an agent needs to act on, so they are often the first place agents get plugged into a dev workflow. If you want a clear answer on whether that is saving your team real time, a short AI consulting engagement usually settles it.
LayerDock runs three tiers, a free plan and two paid ones, each billed monthly with a 14 day trial on the paid tiers. A credit card is required to start the trial. Figures below are what LayerDock publishes on its own pricing page.
| Plan | Price | Docks | What's included |
|---|---|---|---|
| Free | $0/month | 2 | 35 feedback submissions a month, a client share link on a single Dock |
| Pro | $19/month | 5 | Unlimited feedback, 25 recordings a month, full third-party integrations, up to 7 members |
| Agency | $69/month | Unlimited | 100 recordings a month, console and network diagnostics, full MCP access, up to 20 members |
Pricing as published on layerdock.io at time of writing. Check the vendor's pricing page for the current numbers before you budget against them.
All three pin feedback to a live page and attach technical context to it. The real differences come down to how long each one has been around and where it puts its effort.
| Aspect | LayerDock | BugHerd | Marker.io |
|---|---|---|---|
| Reviewer setup | Open a link, no account, no extension | Browser extension or shared link | Browser extension or embedded widget |
| Market position | New, small team, closed source | Established, large review base | Established, developer-focused |
| Technical diagnostics | Screenshot, console, network, element inspection on paid tiers | Screenshot and browser metadata | Console logs, network requests, environment data |
| AI coding agent integration | Native MCP server for Claude Code, Cursor, Codex CLI | Not a core feature | Not a core feature |
| Project tool integrations | Slack, Jira, Linear, GitHub, Trello, ClickUp | Jira, Trello, Asana, GitHub, Slack, and more | Jira, Linear, Asana, GitHub, GitLab, Slack, among others |
| Entry price | Free plan, then $19/month | No free plan, Standard from about $39/month | No free plan, Starter from about $59/month |
BugHerd and Marker.io pricing above comes from third-party roundups published in 2026. Confirm it on their own pricing pages before you commit to either one.
LayerDock fits small and mid-sized teams best. A lot of the people giving feedback, clients, founders, non-technical stakeholders, are not going to install a browser extension. For them, opening a link and clicking on something is already pushing it.
Teams already running Claude Code or Cursor get something extra out of it too. Right now, someone has to read a bug report and type it into the agent by hand. The MCP connection skips that.
Bigger engineering teams with a mature Jira or Linear setup, permissions, audit trails, the whole structure, are a tougher sell. BugHerd and Marker.io have had more years to build that depth. LayerDock's integration list covers the basics and nothing past that.
LayerDock calls itself early, and the product backs that up. The integration list covers the basics: Slack, Jira, Linear, GitHub, Trello, ClickUp. It trails what BugHerd and Marker.io have built over more years. Use a tool outside that list and you are waiting on a native connection or routing through Zapier.
Recordings are capped by tier. 25 a month on Pro, 100 on Agency. Fine most months, tight if a QA pass leans on screen recordings. Console and network diagnostics, probably the single most useful thing here for a developer, sit behind the Agency plan only.
It is closed source too. The public GitHub repository holds the project page and documentation. The application itself is not there, so auditing or self-hosting it is off the table. These are normal trade-offs for a product this young. Better to know now than mid-trial.
A tool like LayerDock gets you clean feedback. It does not get you a shipped fix. Turning a client's notes into a working fix in days, not a slow back-and-forth, is the part we handle when we run a project as a client's dedicated development team or through an agile pod.
LayerDock's MCP connection is one small example of that kind of automation already working for a team's daily tools. Get in touch if you want our take on whether it is worth setting up for yours.
Yes, LayerDock has a free plan that includes two Docks and up to 35 feedback submissions a month, with a client share link on a single Dock. It is enough to try the core pin workflow, but recordings, full integrations, and diagnostics require the Pro or Agency plan.
No, reviewers do not install anything. A reviewer opens the shared Dock link in any browser and starts pinning comments right away, with no browser extension and no account required. That is the main thing that sets it apart from tools built around a browser extension.
Yes, LayerDock ships an MCP server that connects its pins to AI coding agents including Claude Code, Cursor, and Codex CLI. Full MCP access is included on the Agency plan, so a pin's screenshot, element, and diagnostics can become working context for the agent without manual copying.
Yes, it is one of the better fits for that use case. Non-technical clients can leave feedback without creating an account, and the free and Pro tiers cover a small agency's typical review volume before the pricing jumps to the Agency plan.
No, it is not built to replace a project tracker. LayerDock is a feedback capture layer that sits in front of your existing tools and pushes pins into Jira, Linear, GitHub, Trello, ClickUp, or Slack, rather than acting as the system of record itself.
If your actual problem is vague feedback with no technical context, LayerDock is worth a trial. The no-account flow is the right default, and the MCP connection to coding agents is something neither BugHerd nor Marker.io has right now. What you give up is a shorter integration list and a couple of features locked behind the top tier. Normal for a product this young.
Run the free plan on your next client project before paying for anything. One review cycle tells you whether people actually use the pin flow, and that is the only test worth running here.
More Reading
We build the AI agent workflows and dedicated engineering teams that turn client feedback into shipped fixes fast. Tell us what you are working with and we will tell you straight what is worth automating.
Schedule a Call