AI debug engineer
An AI debug engineer finds why a customer got stuck and opens the pull request. You review it.
A small bug takes about four hours to find and fix by hand. With Bugwalk it is one pull request to review.
Nothing open yet.
Works with the stack you already run
One SDK for the browser, one for the server. Same visit.
The message does not say who, or which line. Finding that out takes hours. Then you still write the fix.
01
An error. No name on it.
02
What they clicked is in another tool.
03
The file you have open may not be the one that failed.
04
After all that, you still write it yourself.
Without Bugwalk
With Bugwalk
An AI debug engineer does those hours. You review the pull request.
Drag to compare.
Without Bugwalk
With Bugwalk
Their visit, the reason, and a pull request you review. The numbers are what a plan includes.
01
4h
About four hours of finding and fixing by hand, now one pull request to review.
02
100
A month on Pro. 1,000 on Team.
03
5
A month on Pro. 20 on Team.
04
$39
Team is $149, about eighty hours back every month.
Every fix arrives as a pull request on its own branch. You decide when it ships.
Three real-looking support messages from a small shop. Click one and watch the agent read the code, find the line and open the fix.
Click a ticket to start.
Nothing open yet.
An AI debug engineer read what they did, named the line that was live, and opened the pull request.
Read the visit
What they did, and where it failed.
Fix the code
The line that failed, and nothing else.
Open the pull request
The request is ready before you debug.
You review it
You decide when it merges.
fernhill/checkout
src/checkout/total.ts
- return subtotal * (1 - discount.percentage / 100);+ if (!discount) return subtotal;+ return subtotal * (1 - discount.percentage / 100);
About four hours, looking it up by hand
5 places
Logs · Requests · What they did · GitHub · The live version
Reviewing the one request
Five places to check, then one request to review.
Five links, kept together on one visit. Break any one and you are back in five tabs.
The email they sent you opens their visits.
Every click, in order, on one timeline.
The request and the error, on the same visit.
The release that was live, not the file on your screen.
A pull request written against that version.
Everything about one failure sits on a single page. No more switching between your logs, a session tool, and GitHub.
01
What broke: the click, the request, and the error, in order.
02
Why it broke: the file and line, from the version that was live.
03
How to fix it: a pull request you can read and review.
Every reason points at something that happened, or at a line in your code. If the proof is thin, the report says so.
See who hit it, what they did, and why. Fix it once.
Move the sliders. A small bug takes about four hours by hand, so the hours, the money and the plan all follow the number of bugs you pick.
Best plan for this volume
Pro $39
5 pull requests a month
Team $149
20 pull requests a month
Enterprise Custom
No monthly cap
Hours back a month
32h
8 bugs × 4h = 32h of engineering
Worth of time back
$2,560
Team costs $149 a month. That leaves you about $2,411 ahead.
3-day trial · Card required · Not charged for 3 days
Fernhill is a small shop we run. Break something in the shop, then watch it appear in Bugwalk with the click, the request and the error on one page. No account needed.
On your own project, Bugwalk goes one step further. It finds the line and opens the pull request for you.
The last day: who showed up, what failed, and which visits just ended.
Search the email or id you already have, then open someone and read their visits.
One visit: the pages, what they did, what your app did, and where it failed.
The same failure, grouped: who hit it, what they did, and why.
A written answer: what happened, why, how sure it is, and what to change.
How Bugwalk is connected to your product, what it may read, and your plan.
Connect your app and the code it runs, then watch the next failure on the version that was live.
Point your existing OpenTelemetry agent at the Bugwalk OTLP endpoint. No Bugwalk library goes into those services at all.
OTEL_EXPORTER_OTLP_ENDPOINT=https://api.bugwalk.appBugwalk reads the failure and opens a pull request for you to review. Nothing ships until you say so.
Passwords, card numbers, and API keys are removed before anything is sent. You cannot turn that off.
Each fix comes on its own branch. Your main branch only changes when you merge it.
No. Every fix arrives as a pull request on its own new branch. Your main branch only changes when you merge that pull request. Bugwalk does not merge, comment, or write to your database.
The visit that failed and the repositories you chose, at the commit that was live when it failed. Passwords, card numbers and keys are removed inside your app before anything is sent.
Every finding cites an event or a file and line, so you can check it yourself. If a finding cites nothing it actually saw, the whole report drops to low confidence and says why. Treat a low-confidence report as a lead.
Per project. Pro is $39 a month with 100 investigations and 5 pull requests. Team is $149 a month with 1,000 investigations and 20 pull requests. Enterprise is custom.
Yes. Pro and Team start with a 3-day trial. A card is required so the plan continues without a gap, and you are not charged until the trial ends. Cancel before day 4 and you pay nothing.
Self-hosting is coming soon. Until then, Bugwalk runs as a hosted service. If self-hosting matters to you, tell us through the contact form and we will let you know when it is ready.
The SDKs and the server are open source. Self-hosting is coming soon. Ask us anything.
Bugwalk reads the visit and your code, finds the cause, and opens the fix. All you do is review the pull request.
Card required. 3 days before you are billed.