Where your users' feedback goes
A hosted feedback tool works by receiving what your users report (screenshots, logs, the page they were on) on its own servers. That's the design, and each of these vendors says so openly. Here's where, in their own words, with a link to each source.
Checked 24 September 2026 against each vendor's published pages; prices checked 25 September 2026. Something out of date? Write to hello [at] quibble [dot] fyi and we'll correct it.
Comparison
| Tool | Where reports are stored | Console and network capture | Self-hosted option | DPA and subprocessors | Starting price |
|---|---|---|---|---|---|
| Marker.io | Vendor's cloud: AWS, eu-west-1 (Ireland) source | Yes, through its SDK source | Not published | DPA source; subprocessor list source | $39 a month, billed yearly, for 3 users source |
| BugHerd | Vendor's cloud: Heroku on AWS, us-east-1 (N. Virginia) source | Not published | Not published | DPA on request; subprocessor list source | $42 a month, billed yearly, for 5 members source |
| Userback | Vendor's cloud: AWS, United States source | Yes source | Not published | DPA source; subprocessor list source | Free for 2 seats; then $29 a month, billed yearly, for 5 source |
| Jam | Vendor's cloud: Google Cloud, Central US source | Yes source | No: recordings can't be sent to your own storage source | DPA in its terms source; subprocessor list source | Free; then $14 per creator a month, billed yearly source |
| BugDrop | Your GitHub repository; the hosted widget passes each report through the vendor's Cloudflare Worker source | Console logs only, if the reporter opts in source | Yes, free: your own Cloudflare Worker and GitHub App source | DPA not published; a list of service providers in its privacy policy source | Free, MIT licence; no paid tiers source |
| FasterFixes | Hosted tier: EU, Frankfurt source | Yes source | Yes, free: run its dashboard, database and storage yourself source | DPA not published; a short list of services in its privacy policy source | Free to self-host, or for 1 hosted project; then $20 a month source |
| quibble | Your issue tracker. quibble runs inside your app and has no servers details | Yes, off until you turn it on details | Nothing to host: it's a package in your app and a script tag | No additional DPA or subprocessor: quibble never receives your data | Free for individuals and small companies; larger companies, email us details |
Every row is a statement the vendor publishes. Where we couldn't find one, it says not published, which means we didn't find it, not that it doesn't exist. Plans and features change; the linked pages are the authority. The evidence behind this table is kept with the site's source.
What each one does
quibble loses some of these rows, and we've left them in. It has no drawing on the screenshot, no session replay, no message back to the reporter yet, and its server side is Python, with other languages either on one machine through quibble serve or by implementing its schema. It wins where the rest need something else running: quibble runs inside your app, takes the reporter from your own sign-in, and routes to several repositories.
| Capability | quibble | BugDrop | FasterFixes | Marker.io | BugHerd | Userback | Jam |
|---|---|---|---|---|---|---|---|
| Draw on the screenshot | ◐ screenshot, no drawing details | ✓ source | ◐ pinned comment, no drawing source | ✓ source | ✓ source | ✓ source | ✓ source |
| Session replay | — | — source | not published source | ✓ Team plan up source | — video and replay-tool links source | ✓ Business plan up source | ✓ source |
| Tells the reporter when it's fixed | — planned | — shows the issue link source | ◐ status sync, no notice source | ✓ Team plan up source | ◐ not public reporters source | ◐ when staff resolve source | not published source |
| Console and network | ◐ off by default; failures only details | ◐ console, opt-in source | ✓ source | ✓ Team plan up source | — source | ✓ Business plan up source | ✓ source |
| Points at the element | ✓ details | ✓ source | ✓ source | not published source | ✓ source | not published source | not published source |
| Any web app stack | ◐ Python; others on one machine through quibble serve, or via the backend contract details | ✓ source | ◐ React widget source | ✓ source | ✓ source | ✓ source | ✓ source |
| Issue trackers | GitHub, GitLab, Gitea, Forgejo, Jira Cloud, Linear | GitHub | GitHub, Linear, Jira Cloud | 15+, incl. Jira, GitHub, GitLab, Azure DevOps | 9, incl. Jira, GitHub, Linear | Jira, Linear, ClickUp, GitHub | 9+, incl. Jira, GitHub, GitLab, Azure DevOps |
| Nothing new to run | ✓ runs inside your app details | ◐ vendor Worker, or your own Worker and GitHub App source | — hosted, or Postgres, S3, jobs and email source | — hosted service source | — hosted service source | — hosted service source | — hosted service source |
| Reporter from your own sign-in | ✓ details | — typed name and email source | — reviewer links source | ✓ source | ◐ email only source | ✓ source | ◐ custom metadata source |
| Several repos from one install | ✓ details | — one repo per embed source | — one repo per project source | not published source | not published source | not published source | ✓ picked per report source |
✓ yes · ◐ partly · — no · not published: not on the vendor's own pages. Checked 26 September 2026. Some ticks apply only to paid plans, as marked; quibble's column describes quibble 1.40.0.
Rather keep it in your own tracker?
quibble is in early access. Send an email to hello [at] quibble [dot] fyi if interested.