Questions people ask before they start.

An AI debug engineer. When a customer says something broke, Bugwalk shows you their visit (what they clicked, what your app did, and the error), finds the line of code that failed, and opens a pull request with a fix for you to review.

A web app or API, and a GitHub repository for its code. You add a small SDK to the app so visits are recorded, and connect the repository so Bugwalk can read the code that was live.

Most people are sending their first event within minutes. Run the wizard from your app, approve it in the browser, and the SDK and project key are written for you. Connecting GitHub is one more click.

React, Next.js, Vue, Nuxt, SvelteKit and Angular on the frontend. Express, NestJS, Fastify, FastAPI, Django, Go and more on the backend. Java, .NET, Ruby and PHP connect through OpenTelemetry. The frameworks page lists them all.

Yes. The live demo is a real shop we run, with the real dashboard in front of it. Break checkout yourself and watch the failure land. No account needed.

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.

You still get the investigation: who hit it, what they did, where it failed and why. A pull request is opened only when the report qualifies. A run that fails before it finishes is not charged.

Yes. Bugwalk connects through a GitHub App, and only to the repositories you grant. Uninstalling the app revokes access at once.

Your customer hit the bug in the version they were using, and your code may have changed since. Bugwalk checks that exact version, so the lines it points to are the ones that really ran. Ask your developer to switch on version tracking once, and it works from then on.

No. Passwords, tokens, cookies, card numbers and authorization headers are removed in your app, before an event leaves the process. They never reach Bugwalk, and you cannot turn that protection off.

No. The SDK does not read keystrokes, form values, localStorage, sessionStorage or IndexedDB. It records page views, clicks, requests, errors and log lines.

Yes. Add field names to drop in Project, Privacy, filter or sample events in your own code, or skip identify() and people stay anonymous.

Pro keeps 30 days of events and Team keeps 90. Older events are removed automatically.

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.

Nothing is billed extra. When a project uses its included events, investigations or pull requests, those pause until the next period or until you move to a larger plan.

Any time, per project, from Account in the profile menu. Changes are prorated for the rest of the billing period.

The SDKs and the server are Apache 2.0. The hosted product adds accounts, the AI agent and pull requests.

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.

Use the contact form and a person will reply by email. The docs also have a troubleshooting page for the common problems, like no events arriving.