Less chasing. More fixing.

Bug reports, straight to your GitHub Project.

A Report Bug button for your web app. Users type a title and description, and each report becomes a draft item in your GitHub Project. No screenshots, no recording.

Try Starter for $1 for 14 days. All plans at launch prices.

See pricing

Paste one snippet into your app.

See how it works · Read the install guide

A small button. A useful report.Interactive demo
your-application.com
YOUR APPLICATION

Make yourself at home.

Go on, give it a try
Right where you work

Try it. Nothing is sent.

Your credentials stay privateOpen-source browser SDK
From “something broke” to a report

Three steps.
Then back to building.

Set it up once. Your users do the reporting.

01

Register your application

Sign in with GitHub and add an application. Give it a name and list the exact HTTPS origins that may show the button, one per line, including the port. Reporters do not need a Bug Beacon account or a GitHub account.

02

Connect a GitHub Project

Connect a GitHub Project with a personal access token. A personal Project uses a classic token with the project scope. An organization Project uses a fine-grained token with organization Projects write permission, and the organization may require approval. Bug Beacon encrypts that token on the server and never sends it to the widget.

03

Add the report button

Paste the script tag https://bugbeacon.ai/widget/v1.js and the bug-beacon element, or install the open-source package @bugbeacon/browser. Use Node.js 24 or later for that package. The public project ID is not a credential. Each report becomes a draft item in your GitHub Project. When GitHub confirms delivery, the dashboard shows Delivered. If delivery fails or stays uncertain, fix the GitHub connection before you retry, so you do not create a duplicate item.

Read the install guide

If your team needs recordings, console logs, or annotated screenshots, use a capture tool. Bug Beacon is a typed report.

What a report contains

A report contains the title and description the reporter types.

A report contains the site origin, such as https://app.example.com. The stored origin excludes the path and the query. That origin is not the full page address.

The Bug Beacon button and form do not read page content, cookies, or browser storage. They do not take screenshots or recordings. They do not fingerprint the browser.

Cloudflare Turnstile processes the reporter IP address plus browser and device signals. The form uses Turnstile to check that the reporter is a person. The service stores a keyed digest of the IP address to enforce rate limits. The service does not store the IP address itself.

Reporters choose what they type, and the form asks them not to include passwords or other secrets.

Reports contain only what your users type and the site’s origin

Questions

What is an in-app bug report widget?

It's a button inside your web app that opens a short report form. With Bug Beacon, your users click Report Bug, type a title and a description, and the report becomes a draft item in your connected GitHub Project. Your team reviews it where you already plan work, without a separate feedback dashboard.

How is Bug Beacon different from session replay tools?

Session replay and visual feedback tools capture screenshots, recordings, console logs or browser details. Bug Beacon doesn't. A report contains what your user types plus the site origin it came from. The form doesn't read your page content, full page address, cookies or browser storage, and it doesn't take screenshots or recordings.

Where do Bug Beacon reports go?

Reports go to the GitHub Project you connect. When GitHub confirms delivery, the dashboard shows Delivered and a new draft item appears in that Project. That's a Project draft item, not a repository issue. You can check the latest delivery status on your application's settings page.

Do my users need a GitHub account to report a bug?

No. Bug Beacon's install guide says reporters don't need a Bug Beacon or GitHub account. They use the form on your site. You, the customer, sign in with GitHub and connect a GitHub Project with a token. Bug Beacon encrypts that token on the server and never sends it to the widget.

How do I add a bug report button to my web app?

Sign in with GitHub and add an application with the exact HTTPS origins allowed to show the button. Connect a GitHub Project with a personal access token. Paste the script tag and bug-beacon element, or install the open-source npm package. Then submit a test report and check for Delivered.

How much does Bug Beacon cost?

Starter is $40 a year at launch pricing, and you can try it for $1 for 14 days. Pro is $9 a month and Team is $29 a month, both at launch prices. Prices are flat with no seats. Launch prices stay while your subscription stays active. Regular prices start February 3, 2027.

Pricing

Flat prices. No seats.

Try Starter for $1 for 14 days. All plans at launch prices.

Starter

Launch price

$40/year

Regular price $60/year

Pro

Recommended

Launch price

$9/month

Regular price $12/month

Team

Launch price

$29/month

Regular price $39/month

Compare plans

Try Starter for $1 for 14 days. All plans at launch prices.

Read the install guide