Will people actually use a feedback widget?

Far more than use a support portal, because the cost is one tap on the page they are already on. The determining factor is not the widget design, it is whether reporting requires an account — and here it never does.

What does it cost as I grow?

One flat plan with unlimited projects, widgets and submissions, so the bill does not move when a launch sends ten thousand people at you. There is no per-seat and no per-tracked-user axis.

Can my AI coding agent use the reports?

Yes. An MCP server exposes your inbox to Claude Code, Cursor or any MCP client over OAuth, so the agent can pull a report with its stack trace and steps and start on the fix directly.

For indie hackers

Ship, get told what broke, and tell them when you fixed it.

You launch, a few hundred people show up, and the ones who hit a problem simply leave. They will not open a support portal, they will not register on a roadmap board, and they will not find your email address. They will press a button if there is one on the page.

Start freeNo credit card required.

The situation

What this usually looks like

Launch traffic does not come back
The spike from a launch post is the only time many of these people will ever visit. If the friction to report something exceeds about fifteen seconds, whatever they noticed is lost with them.
Feedback is scattered across five places
Some in X replies, some in a Discord thread, some in email, some in a form you built in an afternoon. None of it is in one list you can work through.
Free tiers run out at the worst moment
Most tools in this category cap submissions or seats exactly when the product starts getting traction, which is the point where you least want to stop and re-evaluate vendors.
You have four products, not one
Per-project pricing turns a habit of shipping experiments into a monthly bill that grows with your curiosity.

Why this fits

What changes for indie hackers

No account for the person reporting: They press the button, type a sentence, and optionally leave an email if they want an answer. Nothing about the flow asks them to become a user of a second product first.
Bugs and feature requests in one button: They pick a type when they submit. Bug reports carry the browser details, errors and steps automatically; ideas arrive clean. Both land in the same inbox with the same five statuses.
The reply is automatic: Move a request to shipped and whoever asked for it gets an email in their own language. That single message is what turns a one-off launch visitor into somebody who tells you the next thing.
Unlimited projects on one plan: Every product you own gets its own widget, key, inbox and allowlist, on the same flat price. The next weekend project costs nothing to instrument.

Who this is not for

Save yourself the trial

If your product has no users on the web — a CLI, a mobile-only app, a desktop tool — this cannot help you, because the widget lives on a web page. And if you want a public voting board as part of your marketing, Canny or Featurebase do that properly and this does not do it at all. The comparison pages say which tool we would send you to instead.

FAQ

Questions

Will people actually use a feedback widget?: Far more than use a support portal, because the cost is one tap on the page they are already on. The determining factor is not the widget design, it is whether reporting requires an account — and here it never does.
What does it cost as I grow?: One flat plan with unlimited projects, widgets and submissions, so the bill does not move when a launch sends ten thousand people at you. There is no per-seat and no per-tracked-user axis.
Can my AI coding agent use the reports?: Yes. An MCP server exposes your inbox to Claude Code, Cursor or any MCP client over OAuth, so the agent can pull a report with its stack trace and steps and start on the fix directly.

Put it on your site today.

One script tag. Unlimited projects, widgets and reports on one plan, and your users never make an account.

Start free Read the docs