Open-Source Website Feedback Tools by Workflow

“Open-source feedback tool” is not one product category. A visual bug report, a survey response, and a session replay produce different evidence and require different infrastructure. Start with the job after collection, then evaluate license and hosting details. OS-01 OS-02 OS-03

Shortlist by job

This documentation-based shortlist groups workflows; it does not claim that the products are interchangeable.

BugDrop: focused issue intake

BugDrop is the narrowest option here. A reporter can describe a problem, capture or select a screenshot, annotate or redact it, and create a GitHub Issue with page and browser context. The project is MIT licensed, and self-hosting uses a Cloudflare Worker plus a GitHub App. OS-01

That fit is strongest when GitHub already owns triage. It is weak when feedback must be aggregated into research, replayed as behavior, or presented on a public portal.

Formbricks: surveys and experience research

Formbricks describes website, in-app, link, and email surveys, targeting, templates, collaboration, integrations, and analysis. Its core is AGPLv3, while its repository also contains enterprise-licensed functionality. Review that boundary against your deployment and modification plans rather than treating “open source” as a single permission set. OS-02

Choose it over BugDrop when structured questions and response analysis are the product requirement. A survey can surface sentiment and demand; it does not automatically become a reproducible visual bug report.

OpenReplay: behavioral debugging context

OpenReplay describes self-hosted session replay, developer tooling, captured technical activity, privacy controls, and product analytics. Its repository notes that the monorepo uses several licenses, so inspect the exact components you plan to deploy. OS-03

Choose it over BugDrop when the team needs to reconstruct what happened before an issue or investigate behavior across sessions. Its documented session-replay workflow captures a different evidence set than a user-submitted screenshot. OS-03

Evaluation checklist

• Define whether the output should be an issue, survey dataset, or replay.
• Inspect the exact license for the deployed components and planned modifications.
• Map captured data, storage location, retention, access, and deletion.
• Estimate operations for authentication, databases, queues, object storage, upgrades, and backups.
• Confirm the destination fits the team that must act on the feedback.

For a screenshot-to-GitHub workflow, begin with BugDrop. For another job, choose the tool designed for that job rather than forcing a bug widget to become a research or observability platform.