bugpot

Product

Everything Bugpot ships, in one overview

Five focused surfaces make up the product: the capture widget, the session context that rides with every report, sensitive-data masking, workspace analytics and optional AI triage. Skim them all here or dive into the one that matters today.

OpenIn progressResolved
clientsite.co.uk/checkout
Pay n…
Pay button clipped on mobileOpen
Safari 18 · iOS390 × 844/checkout?step=paymentTypeError: btn.rect is undefined
SRSarah (client) · just now

The five surfaces

One product, five deep dives

Bugpot is a small product with a wide surface area. Each pillar below has its own page — the summary sits here, the specifics live one click away.

The widget

One script tag, Shadow-DOM isolation, custom forms

The capture surface reporters actually see. Loads async, renders inside a closed Shadow DOM, and ships annotated screenshots with browser, OS, viewport, URL and console errors already attached.

  • Async loader, sub-150 KB gzipped, zero collisions with host CSS
  • Pixel-accurate DOM screenshot with a getDisplayMedia fallback
  • Custom forms per issue type — bug, suggestion, question, praise
Explore the widget

Session context

The last actions before submit, captured

Every report arrives with the technical context a developer would ask for anyway — a rolling buffer of console and network activity plus the exact environment at the moment the reporter opened the widget.

  • Rolling console log with full stack traces on unhandled errors
  • Recent network requests with method, URL and status
  • Browser, engine, OS, viewport, DPR, URL, locale and timezone
See session context

Data masking

Sensitive fields blanked before capture

Give the widget a list of CSS selectors and it blanks matching elements before the screenshot is taken. Card numbers, personal details and half-typed passwords never leave the reporter’s browser.

  • CSS selector allow-list, configured per project
  • Masks applied in-browser before screenshot capture
  • Console and network capture redact matching payload keys
How masking works

Analytics

Volumes, resolution times, team performance

A workspace-level view of what’s coming in and how fast it’s going out. Slice by project, issue type or assignee; watch resolution times trend; catch a project drifting before the client does.

  • Feedback volume by project, issue type and week
  • Median hours from open to resolved, trending over range
  • Resolved-per-assignee to see who’s clearing their queue
See analytics

AI triage

Optional AI, only when your workspace enables it

Turn on AI assistance and the inbox will suggest cleaner titles, rewrite messy reporter notes into clear descriptions, and translate reports from any language. Off by default; scoped per workspace.

  • Suggest — a concise, searchable title from the report body
  • Rewrite — turn a rambling note into structured reproduction steps
  • Translate — read any language report in your own
Read about AI triage

Under the hood

The things you don’t think about until they matter

Bugpot ships with the plumbing serious teams expect: signed webhooks, an audit log, a triage inbox with statuses and priorities, and integrations into the trackers your engineers already live in.

Triage inbox

Statuses, priorities, assignees, filters, keyboard shortcuts and a ⌘K palette across every project.

Webhooks & API

HMAC-signed deliveries with retry, a full delivery log, and a REST API for anything the UI can do.

Audit log

Actor, action, target, before and after — for every event. Filter, then export the whole view to CSV.

Integrations

Jira, GitHub, GitLab, Linear, Azure DevOps, Asana, Trello, ClickUp, Notion, Monday, Slack and Teams.

Custom issue types

Bugs, suggestions, questions, praise — each with its own colour, icon and form fields.

Workspace branding

Your logo, primary colour and launcher label on the widget so it looks like the client’s own site.

See the whole product on your own site

Start free, wire in the widget in two minutes, and click through the surfaces as real feedback arrives.