Annot8 - Website feedback pinned to the exact spot that's broken

by•
Annot8 is website feedback and bug reporting for teams. Add one script tag to any site. Teammates and clients click anything on the page and leave a comment pinned to that exact spot, with an optional screenshot or recording. Guests join by link, no account needed. Reports include URL, browser, screen size, console logs and failed requests so developers can reproduce them. Connect GitHub and the AI Agent can open a draft PR for your team to review. Free to start; Agent requires a paid plan.

Add a comment

Replies

Best
Maker
📌
Hi Product Hunt! 👋 We built Annot8 to make website feedback less painful for everyone involved — reviewers, clients, testers, and especially developers. You add one script tag to your website. Anyone reviewing it can click directly on the part that looks wrong, whether it’s a button, a heading, or an entire section, and leave a comment right there. No more vague messages like “the thing on the homepage is broken.” Guests can join through a review link without creating an account, and reviewers can attach screenshots or recordings. Every report also captures useful technical context automatically, including the page URL, browser, screen size, console logs, and failed network requests. So developers get more than just a screenshot and a vague description. We also wanted to go beyond collecting feedback. AI can help organize your inbox, suggest priorities, summarize discussions, and draft replies. And if you connect a GitHub repository, Resolve with Agent can use a report’s context to propose a code change and open a draft pull request on a separate branch. Your team stays in control — review, approve, merge, or reject. Annot8 never merges or deploys code automatically. You can get started for free with a few projects and teammates. The Agent and advanced features are available on paid plans with monthly Agent credits. We’re launching Annot8 because we think reporting a website issue should be as simple as pointing at it — and fixing it should start with the right context. I’d love to hear from you: what’s the one thing that most often gets lost between someone reporting a bug and a developer fixing it? Thanks for checking us out! ❤️