Ruttl alternatives: 8 tools compared for 2026
Ruttl describes itself as “One tool for all types of website feedback”: comments on live websites, mobile apps, images and PDFs, from one workspace. Broken Here, which we make, is a bug-reporting widget for websites whose tickets carry what actually broke. Below are the 8 alternatives, then the two side by side, from what each said on its own pages on 7 November 2026.
The 8 alternatives
- Broken Here: for teams whose bugs are found by clients, colleagues and customers, with the console errors and failed requests in every ticket and a free plan for one site.
- BugHerd: agencies whose clients want to work the feedback with them, on a kanban board of notes pinned to the page.
- Marker.io: teams that want session replay beside each report, and can put the developers who need it on its higher plans.
- Usersnap: product teams that want NPS and CSAT surveys, a feature-request board and bug reports in one tool.
- Userback: product teams that want surveys, NPS, a feature portal and session replay beside bug reports, in one product.
- Ybug: small teams that want a feedback widget with annotation and video, and can pay for the plan that records the console.
- Pastel: getting a client's sign-off on a page, an image or a PDF through a shared link, with nothing installed.
- Jam: software teams filing their own bugs, as a recording with the logs attached, from an extension.
Ruttl and Broken Here, row by row
| Ruttl | Broken Here | |
|---|---|---|
| Priced by | Per user, with users and projects limited by tier; guests unlimited | By sites. The whole team is in, reporters are never counted |
| Free plan | Yes: up to five users, one project, five pages, ten private comments | Yes: one site, 50 reports a month, no card |
| Reporter needs an account | No: clients give feedback without signing up | No account, ever: a button on the site and one sentence |
| Captured with each report | Comments on the live page; technical details not stated | Page, browser, device, window size, the element, a screenshot with passwords blurred |
| Console errors and failed requests | Not stated on their pages | Console errors and failed requests in every ticket, on every plan, including Free |
| Install | Works with WordPress, Shopify and custom sites; an npm package for mobile apps | One script tag, or a WordPress plugin |
| Trackers | Trello, Slack, Asana, Jira, Zapier and ClickUp | Yours. If it is not connected yet, we add it; GitHub for the coding agent's pull requests |
Ruttl’s column is what its own pages said on 7 November 2026: ruttl.com, ruttl.com/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
The ticket carries what broke
Ruttl is built around comments on the work. Broken Here is built around the bug: the element, the browser, the console errors and the failed requests are in the ticket without anybody asking.
Priced by sites, not users
Nobody on your team is left off the tool to save a seat; the price follows the sites you look after.
50 reports a month, free
One site with no cap on its pages, for as long as you like, with the same capture as the paid plans.
When to pick Ruttl instead
Pick Ruttl if you review mobile apps, images and PDFs as well as websites, and want them in one workspace. Pick Broken Here if you want bug reports from a website with the evidence attached.
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. The comparison table puts Broken Here, Marker.io and BugHerd side by side.