It arrives
Support email, the in-app form, a public report link or a webhook — all one endpoint.
AI bug triage for product teams
Every bug,
routed in seconds.
Bug Router takes every report from every product you ship, has AI read and rank it, and drops it on the right board with the right owner — before anyone opens a ticket.
Unlimited products, workspaces and reporters · live in an afternoon · no card required
Live triageBUG-2481
- 1
Ingest
Email, form and n8n webhook land in one inbox.
- 2
Analyze
Claude reads the report, dedupes it, writes repro steps.
- 3
Route
Product, space and owner picked from the rules you set.
- 4
Resolve
Lands on the board with context already attached.
Sourcesupport@ → /api/ingest
P1 · checkout 500s◆duplicate merged◆routed to Platform◆repro steps written◆P3 · copy typo◆owner assigned◆SLA on track◆screenshot attached◆
Triaging bugs for teams that ship every day
- Northwind
- Arcadia Labs
- Fieldstone
- Halcyon
- Broadside
The workspace
Every triaged bug, already on the board.
Boards, lists, calendar and analytics — one source of truth across every product in your workspace.
How it works
A report comes in. Everything after that is automatic.
AI reads it
Product, severity, duplicates and repro steps, filled in from the raw text.
Rules route it
Your mapping decides the space, the list and the owner. No inbox roulette.
The team ships
It lands on the board with full context. Analytics track the rest.
Unlimited
products & workspaces
< 30s
report to routed ticket
0
manual triage meetings
100%
tickets with repro steps
Features
Built for the way your team actually works.
01
One inbox for every product
Email, in-app reports, public report links and webhooks all land in the same queue — across every product and workspace you run.
02
AI does the triage
Severity, product, duplicate detection and clean repro steps — written before a human reads it.
03
Routing you control
Rules map product and severity to a space, a list and an owner. Change them without shipping code.
04
Board, list, calendar, timeline
Every view reads from one source of truth, so a status change on the board is a status change everywhere.
05
Notifications that mean something
You hear about the bugs assigned to you and the P1s in the products you own. Nothing else.
06
Analytics per product
Where bugs come from, how fast they route, how long they live — per product, per team, or across the whole portfolio.
07
Record a meeting, leave with tasks
Capture screen and audio in the browser. It gets transcribed, and every action item comes back as a task you approve in one click.
How you’ll use it
Same pipeline. Four very different days.
Forward the email. That's the whole job.
No form to fill, no product to guess at, no owner to look up. Anything that lands in the support inbox becomes a triaged ticket.
- Forward or file from the in-app widget
- AI writes the title, severity and repro steps
- Suspected duplicates are flagged against the original
- You get the ticket link back to reply with
What customers say
The first hour of Monday, back.
Monday triage used to eat the first hour of the week. Now the board is already sorted when we open it.
Duplicates were the real tax. Five people filing the same crash five different ways — it collapses them before we ever see it.
Every ticket arrives with repro steps. I stopped writing 'can you share a screenshot?' entirely.
FAQ
The questions everyone asks first.
As many as you need. Add a product per app, per client or per team, group them into workspaces, and give each one its own routing rules and report link. There is no cap on products, spaces, boards or people filing bugs.
No. Bug Router sits in front of the boards you already use — spaces, folders, lists and statuses stay exactly as they are. The only thing that changes is that tickets show up already sorted.
It reads the raw report and fills in product, severity, a clean title, repro steps, and whether it duplicates an existing ticket. Routing itself is your rules — the model suggests, your mapping decides.
Every field it writes is editable, and a correction is one click on the ticket. Nothing is locked, and nothing is auto-closed.
A support inbox, the in-app widget, a public report link, or any webhook — all hitting one ingest endpoint. Anything that can send an email or POST JSON can file a bug.
Yes. Each product gets a public report link you can share with customers, testers or clients. They never see your workspace — only the form and a confirmation.
No. Reports go to the model provider for analysis and come straight back. Your data stays in your workspace, isolated at the database level by row-level security.
An afternoon. Create a workspace, add your products, point an inbox or webhook at the ingest endpoint, and set the routing rules. No migration and no engineering work required.
Stop triaging. Start shipping.
Create a workspace, add your products, and point your first report at it. You’ll see the difference on day one.