Broken Here, Marker.io and BugHerd
Both are established and both are good. Broken Here is younger. Its tickets carry what actually broke, and nobody who reports has to make an account, whether that is a client, a colleague or a customer.
Priced by sites, not seats
With seat pricing, every designer, PM and account manager you put on the tool costs you more. Here the whole team is in, and you pay for the number of sites, whether they are client sites or your own product and admin app.
The reporter never makes an account
They press a button on the site, write one sentence, and leave an optional email for the status link. A client can have a login that shows every report on their own sites and where it stands, and nothing of your other clients, on every plan; a colleague on the admin app or a customer on the live site is never counted at all.
The ticket has the evidence
It lists failed requests, with their bodies when you turn that on, and errors thrown before the widget loaded, if you add the half-kilobyte pre-hook. The screenshot has the password field blurred before it leaves the browser. The developer opens the ticket and starts fixing.
- Priced by
- Broken HereSitesMarker.ioTeam membersBugHerdTeam members
- Reporters need an account
- Broken HereNoMarker.ioNo, as a guestBugHerdNo, as a guest
- Free plan
- Broken Here1 site, 50 reports a monthMarker.ioFree trialBugHerdFree trial
- Console errors in the ticket
- Broken HereYesMarker.ioYesBugHerdNot stated
- Failed requests, with request and response bodies (opt-in)
- Broken HereYesMarker.ioNetwork logBugHerdNot stated
- Errors thrown before the widget loaded (with the optional pre-hook)
- Broken HereYesMarker.ioNot statedBugHerdNot stated
- Screenshot with passwords, and any element you name, blurred before upload
- Broken HereYesMarker.ioScreenshotBugHerdScreenshot
- Client login scoped to their own sites
- Broken HereYesMarker.ioGuests per projectBugHerdGuests per project
- A review round that becomes one ticket
- Broken HereYesMarker.ioNot statedBugHerdA kanban board instead
- Status link for the reporter, no login
- Broken HereYesMarker.ioNot statedBugHerdNot stated
- Trackers
- Broken HereYours. If it is not connected yet, we add itMarker.ioJira, Linear, Notion, GitHub, GitLab, Asana and many moreBugHerdJira, Linear, GitHub, Asana, ClickUp, Trello and more
- Widget size
- Broken Here18.6 kB gzippedMarker.ioNot statedBugHerdNot stated
- Years in the market
- Broken HereUnder oneMarker.ioManyBugHerdMany
We wrote this from what their public pages said on 1 October 2026, and tried to be fair. “Not stated” means their pages do not say, and does not mean they lack it. If a cell is wrong, write in and we fix it. Their prices change, so see marker.io/pricing and bugherd.com/pricing;Broken Here pricing is one page and starts at zero.
When your own API fails
Tell the project which API is yours. When a request to it fails in front of a visitor, the widget can offer them a report with the failure already filled in. With no API named it never appears, and a wrong password or a form error never interrupts anyone.
When to pick them instead
Pick Marker.io if you want session replay and years of polish. A kanban board of feedback pinned to the page, with the client working the board too, is BugHerd's whole idea, and it does it well. Pick this one if you want the ticket to carry what actually broke, on a client's site, your own product or the admin app your team uses every day, and nobody who reports to make an account.
One at a time, with sources: BugHerd, Marker.io, Usersnap and Userback. For an agency with many client sites, what it costs; for every tool at once, the roundup.
See the difference on one report
The demo is a fake invoicing app carrying the real widget. Break it, then file it.