What's bugging you?
Turn the bug reports your users, customers, and teammates send by email into triaged GitHub issues — screenshots carried across, routed to the right repo, with status synced back when you close them. The person reporting never needs a GitHub account.
Early access — connect your repo and we'll help you onboard. No credit card.
How it works
From inbox to GitHub in three steps
Point your bug-report address at BugMonkey, install the GitHub App, and every emailed report becomes a properly filed issue in the right repo.
-
1Connect GitHub & claim your address
-
Install the BugMonkey GitHub App on the repos that should receive issues, and get your team's unique bug-report email address.
-
2Set your routing rules
-
Decide which incoming reports land in which repo — by the address they hit, the sender, or the subject. One team, many repos, one inbox.
-
3Forward bugs by email
-
Anyone — a customer, a teammate, a QA tester — emails a report, screenshots and all. BugMonkey scans it, files it as a GitHub issue in the right repo with the attachments intact, and tells the reporter when you close it.
Built for teams who ship
Everything you need, nothing you don't
Email in, GitHub issue out
The person reporting never needs a GitHub account. They just send an email; you get a filed issue.
Screenshots ride along
Attachments and pasted screenshots are pulled from the email and attached to the filed issue — no re-uploading, nothing lost on the way over.
Per-tenant routing rules
Send each report to the right repo automatically — by intake address, sender, or subject. One inbox, many repos.
Status synced back
Close the issue and the reporter is notified automatically — the loop closes itself, so people keep reporting instead of assuming it went into a void.
Multi-tenant from the ground up
Separate intake addresses, repos, and routing per team — isolated by design, not bolted on.
Scanned on intake
Every report is scanned on the way in before it's filed, so what lands in your repo is the signal, not the noise.
Sound familiar?
The manual relay is where reports die
Your users hit bugs, but they don't have GitHub accounts and won't make one. The reports that do reach you scatter across a support inbox, Slack DMs, and "hey, can you look at this?" emails with a screenshot pasted in. So someone on the team becomes the human router — copy-pasting the email into a GitHub issue, re-uploading the screenshot, picking the right repo, and then (maybe) remembering to email the person back when it's fixed.
That manual relay is where reports die. The screenshot gets lost on the way over. The issue lands in the wrong repo. Nobody closes the loop with the reporter, so they assume it went into a void and stop reporting. BugMonkey replaces the human router: point your bug-report address at it, install the GitHub App on your repos, and every emailed report becomes a properly filed, attributed GitHub issue in the right repo — and when you close that issue, the reporter hears about it automatically.
BugMonkey does one workflow well: email in, GitHub issue out, status back. It is not a full helpdesk, a ticketing suite, or an in-app feedback widget. If you need a customer support portal with SLAs, live chat, and a knowledge base, Zendesk or Intercom are the right call. And if your issues don't live in GitHub, BugMonkey isn't for you today — we file into GitHub repos through the GitHub App, full stop. What it does that a shared support inbox can't is turn the email your users already send into triaged, attributed, status-tracked GitHub issues, without anyone on your team playing copy-paste router.
Stop being the human router.
Free to connect one repo and route bug reports by email — no credit card. Paid per-tenant plans add multiple repos, advanced routing rules, and higher volume.