A Userback alternative
Userback describes itself as “Collect and act on user feedback 10x faster with Userback”: a user-feedback platform, with a feedback widget (screenshots and video), surveys and NPS, a feature-request portal, and session replay. 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.
| Userback | Broken Here | |
|---|---|---|
| Priced by | Seats (team members with a login) and feedback projects, per tier | By sites. The whole team is in, reporters are never counted |
| Free plan | Yes: two feedback projects, with feedback available for seven days | Yes: one site, 50 reports a month, no card |
| Reporter needs an account | No: reporters are unlimited on every plan | No account, ever: a button on the site and one sentence |
| Captured with each report | Annotated screenshot, video recording, browser and device, user attributes | Page, browser, device, window size, the element, a screenshot with passwords blurred |
| Console errors and failed requests | Console logs, network requests and session replay, on the Business plan and up | Console errors and failed requests in every ticket, on every plan, including Free |
| Install | A widget on the site, or a browser extension | One script tag, or a WordPress plugin |
| Trackers | Jira, Linear, GitHub, GitLab, ClickUp, Asana, Azure DevOps, Notion, Zendesk, Intercom and more | Yours. If it is not connected yet, we add it; GitHub for the coding agent's pull requests |
Userback’s column is what its own pages said on 1 October 2026: userback.io, userback.io/pricing. 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
Developer context on every plan
Userback keeps console logs, network requests and session replay for its Business plan and up. Broken Here puts console errors and failed requests in every ticket, Free included.
Priced by sites, not seats and projects
Nobody on your team is left off the tool to save a seat; the price follows the sites you look after, and a report on the free plan stays readable, where theirs is locked after a week until you upgrade.
One job: the bug
Userback also runs surveys, NPS and a feature portal. Broken Here does bug reports only, and puts everything a developer needs in the ticket, in the tracker the team already uses.
When to pick Userback instead
Pick Userback if you want surveys, NPS, a public feature portal and session replay beside your bug reports, in one product. Pick Broken Here if what you need is bug reports that reach your tracker with the evidence attached, without paying per seat for it.
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 BugHerd, Marker.io and Usersnap, and the comparison table puts Broken Here, Marker.io and BugHerd side by side.