For solo developers

You are the whole support team. Stop being the transcription layer too.

When you build alone, a bug report costs you twice: once to read it and once to work out what it actually means. Three emails later you have a browser version and a rough idea of the page. The widget collects all of that before the person finishes typing, and your agent can read the result without you copying anything.
Start freeNo credit card required.

The situation

What this usually looks like

  • Reports arrive as one sentence

    Somebody emails "the export button is broken" from an address you do not recognise, on a browser you cannot guess, on a page you have to infer. Getting to a reproducible bug takes two days and four replies.

  • You are the one retyping it

    You paste the email into your editor, add what you remember of the context, and describe the browser from memory. That transcription step is pure overhead and it is where the details get lost.

  • Nobody reports the second bug

    The user who told you about the first one never heard back, concluded the message went nowhere, and quietly stopped telling you things. You are now shipping blind to your most engaged customers.

  • A real tool costs more than the project earns

    Per-seat pricing on a team of one is absurd, and the free tiers cap reports at exactly the point the product starts working.

Why this fits

What changes for solo developers

One script tag, no backend work
There is no package, no SDK, no webhook to receive and nothing to deploy. You paste a tag before the closing body tag and the reports start arriving in a hosted inbox you did not have to build.
The report is already complete
Browser, operating system, window size, time zone, up to ten JavaScript errors with stack frames, the last fifty things they did, and a screenshot if they attached one. You never ask a follow-up question to get any of it.
Your agent reads it directly
The MCP server exposes three tools over OAuth, so Claude Code or Cursor can list reports, read one in full and mark it done — without you pasting a single line into a prompt.
One flat price, unlimited projects
Solo developers usually have four side projects, not one. Every project you own gets its own widget and its own inbox on the same plan, so the fifth idea costs nothing to instrument.

Who this is not for

Save yourself the trial

If you have no users yet, you do not have a feedback problem — you have a distribution problem, and this will sit there collecting nothing. And if you need error monitoring rather than user reports, run Sentry: it catches the thousands of exceptions nobody bothers to report. The comparison pages say which tool we would send you to instead.

FAQ

Questions

Is this overkill for a side project?
It is one line of HTML and no infrastructure, so the setup cost is a few minutes. The question is whether you have users who hit bugs — if you do, the alternative is losing those reports, which is more expensive than the tag.
Do I have to run anything myself?
No. The widget is served from a CDN and the inbox is hosted, so there is no server, no database and nothing to keep patched. Removing it later is deleting one line from your HTML.
Can I use it across all of my projects?
Yes. Projects, widgets and reports are unlimited on the single plan, so instrumenting a new experiment costs nothing extra. Each project gets a separate key, inbox and domain allowlist.

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 freeRead the docs