A Marker.io alternative
Marker.io describes itself as “The website feedback tool for bug reporting, QA, and UAT”: a mature feedback widget with a long list of integrations, and developer context (console, network, session replay) on its higher plans. 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.
| Marker.io | Broken Here | |
|---|---|---|
| Priced by | Users, per tier, with extra users added; guests limited by tier | By sites. The whole team is in, reporters are never counted |
| Free plan | A 15-day free trial; no free plan stated | Yes: one site, 50 reports a month, no card |
| Reporter needs an account | No: reporters are free and unlimited | No account, ever: a button on the site and one sentence |
| Captured with each report | Screenshot, annotations, environment details | Page, browser, device, window size, the element, a screenshot with passwords blurred |
| Console errors and failed requests | Console logs, network requests and a session replay of the last two and a half minutes, on the Team and Business plans | Console errors and failed requests in every ticket, on every plan, including Free |
| Install | A JavaScript snippet, a WordPress plugin or a browser extension | One script tag, or a WordPress plugin |
| Trackers | Jira, Linear, Notion, GitHub, GitLab, Asana, Trello, ClickUp, Azure DevOps and many more | Yours. If it is not connected yet, we add it; GitHub for the coding agent's pull requests |
Marker.io’s column is what its own pages said on 1 October 2026: marker.io, marker.io/pricing, Marker.io session replay. 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
Marker.io keeps console logs and network requests for its Team plan and up. Broken Here puts console errors and failed requests in every ticket, Free included, along with errors thrown before the widget loaded if you add its half-kilobyte pre-hook.
Priced by sites, not seats
Nobody on your team is left off the tool to save a seat; the price follows the sites you look after.
Built for the round, not only the report
A team member's findings during one review become one ticket, the reporter gets a status link with no login, and a report can be handed to a coding agent that opens the pull request.
When to pick Marker.io instead
Pick Marker.io if you want session replay: it has years of polish behind it. Pick Broken Here if you want the developer context in every ticket 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, Usersnap and Userback, and the comparison table puts Broken Here, Marker.io and BugHerd side by side.