BugHQ

Turn production errors into fixes

Group duplicate failures, preserve the context that matters, alert the right team, and close the loop from regression to resolution.

Capture your first error Choose an SDK

Stable issue grouping

Normalize volatile messages and stack data so repeated failures become one issue instead of a wall of events.

Debugging context

Keep releases, environments, users, tags, breadcrumbs, sessions, and structured context beside each failure.

From alert to pull request

Notify email, Slack, or Discord, then optionally prepare a guarded GitHub Autofix pull request.

Choose a path

Follow the quick start to create a project and send a test error.
Choose an integration for browser JavaScript, Stacks and stx, Vue and Nuxt, or PHP and Laravel.
Learn how grouping, status, and regressions work in issues and triage.
Use the HTTP API reference for custom clients and automation.

The error lifecycle

An SDK sends an event to POST /errors with the project's public ingest key.
BugHQ validates limits and calculates a stable fingerprint.
The event creates a new issue or increments an existing issue.
New issues and regressions can notify email, Slack, or Discord.
Owners and project members investigate, assign context, and resolve or ignore the issue.
An owner can optionally connect GitHub and run a guarded AI Autofix workflow.

BugHQ is under active development. Verify deployment and SDK behavior against the version you run before relying on it for a production incident process.