Userz

AI feedback → reviewable PR

Your users describe a issue.
Userz opens a PR.

Drop our widget into your app. End users send feedback with screenshots and console logs. An AI agent runs against your repo in an isolated sandbox and opens a reviewable merge request, every time.

runs against
  • Next.js
  • React
  • Remix
  • Vite
  • Svelte
  • Vue
  • Nuxt
  • Astro
  • Node.js
  • Bun
  • Deno
  • TypeScript
  • Python
  • Go
  • Rust
  • Ruby on Rails
  • Laravel
  • Elixir
  • GitHub
  • GitLab
  • Bitbucket
  • pnpm
  • yarn
  • uv
  • cargo
  • Next.js
  • React
  • Remix
  • Vite
  • Svelte
  • Vue
  • Nuxt
  • Astro
  • Node.js
  • Bun
  • Deno
  • TypeScript
  • Python
  • Go
  • Rust
  • Ruby on Rails
  • Laravel
  • Elixir
  • GitHub
  • GitLab
  • Bitbucket
  • pnpm
  • yarn
  • uv
  • cargo

the loop

Three steps. Zero glue code.

Everything between a user typing a sentence and you reviewing a diff, written, tested, and run in a sandbox you never have to think about.

  1. step 01

    Drop in

    One React component. Ten lines. Anonymous or signed JWT.

  2. step 02

    Capture

    Your users send feedback with screenshots, console, and network, automatic.

  3. step 03

    Review

    A reviewable PR lands in your branch. You merge. Or you don’t.

what we replace

From bug to fix, in a straight line.

User feedback usually crosses four teams and eight handoffs before it becomes code. Userz turns it into a reviewable PR before the user closes their tab, and then it waits for you.

the conventional loop
8 steps·4 teams·days of waiting
  1. U
    user
    hits a bug
  2. U
    user
    hunts for a support channel, email, live chat, or a form
  3. S
    support
    “can you send a screenshot?” - replies next day
  4. U
    user
    sends one - when they remember
  5. S
    support
    files a ticket, Zendesk, Jira, Linear
  6. P
    pm
    triages, lands in the backlog - next sprint, maybe
  7. E
    engineer
    reproduces, locates, writes, tests, opens the PR
  8. E
    engineer
    review round-trip with a teammate - merged eventually

And the user wonders if anyone heard them.

with userz
3 steps·1 handoff·<1 min to PR
  1. U
    user
    taps the widget, screenshot, console, DOM all captured
  2. userz
    drafts a PR with full context - clustered, scoped, ready for review
  3. Y
    you
    review and merge, or close it

From the user’s tap to your merge button. Nothing in between.

where your team already is

Meanwhile, in Slack.

Every submission lands in your channel with interactive buttons. Generate a PR with a click. Mark spam without opening the dashboard. The feedback queue is wherever your team is already looking.

SlackDiscordLinearsoonTeamssoon

ready when you are

Ship feedback,
not tickets.

Free plan, bring your own key — Anthropic, OpenAI, Moonshot, or z.ai. No credit card, no seven-day trial clock, no nagging emails. Just the pipeline.