Beacone
Beta - limited capacity

Only the GitHub notifications that matter.

Beacone watches the repositories you choose and forwards to your selected private destination the notifications that matter.

Checking availability…
Beaconebot
🔔 Review requestedacme-analytics/ingest-api#412 — “Retry failed webhook deliveries with backoff”
15:38
Message

Three steps, then never again

Setup once, use forever.

  1. Create your Beacone account

    Continue with GitHub or Google. Either one can create your account and bring you back next time.

  2. Install the Github App

    Choose the GitHub account whose notifications you want. Then install the App on your account or an organisation, for all repositories or a handful.

  3. Choose Telegram or Slack

    One deep link opens the bot and links the chat. There is no ID to copy and nothing to type.

You decide what counts as important

GitHub already tells us why it notified you. Beacone turns that reason into a switch. Tick the ones worth a buzz, leave the rest on github.com where they belong.

Choose the ones that matter, and disable the rest.

(Un)mute any bots, account, or repository.

Available now

  • Review requestedYou were asked, by name, to review a pull request.
  • MentionSomeone wrote your @handle.
  • AssignedAn issue or pull request was assigned to you.
  • CI failuresFailed workflows you triggered or repositories you follow.

Coming next

These notification reasons are planned, but are not available in Beacone yet.

  • Team mention
  • Watched repository

A deleted comment doesn’t leave a lie in your chat

Somebody @-mentions you, thinks better of it, and deletes the comment.

Beacone reaches back into the message it already sent and strikes it through, with a note saying who removed it.

🔔 You were mentionedacme-analytics/ingest-api#412 — “Retry failed webhook deliveries with backoff”💬 @priya-raman said:@you the backoff caps at 30s here. Is that deliberate before we cut 4.2?
🗑️ Comment deleted by priya-raman15:47

See what reached you, day by day

Your dashboard totals the notifications delivered over the last seven days and breaks them down by day, so you can spot a busy week at a glance.

A recent-deliveries list shows what prompted each message and when it arrived.

Read-only permissions. That is the entire ask.

Beacone is built to keep its access and stored data to a minimum.

  • Read-only GitHub App permissions

    Enough to receive the notifications you choose, never enough to change your work.

  • No contents access

    It cannot read or clone your code.

  • No GitHub OAuth scopes on sign-in

    Sign-in establishes your identity; App access is separate.

  • Notification metadata only

    In Beacone's database: not the diff, not the comment body.

  • Your data leaves with your account

    If you decide to delete it, its stored account data goes with it.

Frequently Asked Questions

Does it work with private repositories?

Yes. Access comes from installing the GitHub App on the account, not from your sign-in. Private repos are included if you tick them.

Do I have to sign in with GitHub?

No. You can create and sign in to your Beacone account with GitHub or Google. GitHub is only needed separately to connect the notifications you want delivered.

How fast is it?

GitHub pushes the event the moment it happens and the message is on its way in the same request.

Can I use it on an organisation?

Install it there like any GitHub App. If you are not an owner, GitHub files the request with the people who are.

What will it cost?

It is completely free right now. More tiers will be added in the future, but their pricing and features have not been decided.

Can I turn it off for a while?

Untick every reason, mute the repository, or disconnect the account entirely. Disconnecting takes one button, and every trace of your data goes with it.

Stop reading emails to find out you were mentioned.

Free while in beta. Setup takes less than 5 minutes.

Checking availability…