A BugHerd alternative
BugHerd describes itself as “Getting client feedback on websites – made ridiculously easy”: pinned feedback on the page, turned into tasks on a kanban board your team and your clients work together. Broken Here is a bug-reporting widget for websites whose tickets carry what actually broke. The table compares the two from what each says on its own pages.
| BugHerd | Broken Here | |
|---|---|---|
| Priced by | Team members, in fixed-size tiers; clients unlimited | By sites. The whole team is in, reporters are never counted |
| Free plan | A 7-day free trial; no free plan stated | Yes: one site, 50 reports a month, no card |
| Reporter needs an account | No: clients comment through a link | No account, ever: a button on the site and one sentence |
| Captured with each report | Screenshot, browser, operating system, screen size, the element, the URL; video the reporter records | Page, browser, device, window size, the element, a screenshot with passwords blurred |
| Console errors and failed requests | Not stated on their feature pages; session replay through their FullStory and LogRocket integrations | Console errors and failed requests in every ticket, on every plan, including Free |
| Install | A JavaScript tag or a browser extension; a WordPress plugin | One script tag, or a WordPress plugin |
| Trackers | Jira, Linear, GitHub, Asana, ClickUp, Trello, Monday.com and more, several on higher tiers | Yours. If it is not connected yet, we add it; GitHub for the coding agent's pull requests |
BugHerd’s column is what its own pages said on 25 September 2026: bugherd.com, bugherd.com/pricing, bugherd.com/features. We left prices out because they change; see theirs, and Broken Here pricing. If a cell is wrong, write in and we fix it.
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.
Where Broken Here is different
The ticket carries what broke
BugHerd captures where the feedback is and what the browser was. Broken Here adds what the developer opens developer tools for: the console errors and the failed requests around the moment of the report, on every plan.
Priced by sites, not seats
Seat tiers make you choose who gets to be on the tool. Here the designer, the PM and the account manager are all in; the price follows the sites you look after.
A free plan, not a trial
One site with 50 reports a month, for as long as you like, with the same capture as the paid plans.
When to pick BugHerd instead
Pick BugHerd if the kanban board is the point: feedback pinned to the page and worked as tasks with your clients, and integrations with Asana, ClickUp, Trello or Monday.com. Pick Broken Here if what you need is the bug's evidence in a ticket in your tracker, and a team that is not counted.
See it on one report
The live demo is a page built to break, carrying the real widget. Break it, report it, and read the ticket. Or check one of your pages for the errors a report would carry. We wrote the same page for Marker.io, Usersnap and Userback, and the comparison table puts Broken Here, Marker.io and BugHerd side by side.