Beacone
Beta - limited capacity

Only the GitHub notifications that matter.

Beacone watches the repositories you choose and forwards what needs you to a private chat on Telegram or Slack.

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

Setup in less than 5 minutes

Can be used perpetually after the initial setup.

  1. Create your Beacone account

    Get started with GitHub. That one authorization creates your account and connects your notifications.

  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.

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

Available now

Review requestedYou were asked, by name, to review a pull request.
MentionsSomeone wrote your @handle.
AssignedAn issue or pull request was assigned to you.
Reviews on your PRsCompleted reviews on a pull request you opened.
Review thread commentsConversation comments, replies and standalone inline comments on your pull requests. Comments submitted as part of a review are never sent individually.
CI failuresFailed workflows you triggered, pull requests you opened, or repositories you follow.

The bots are already muted

Every new account starts with these on its mute list. A bot Beacone meets later is muted the first time it appears, and unmuting one is remembered: the next sighting does not mute it again.

  • dependabot[bot]
  • renovate[bot]
  • github-actions[bot]
  • codecov[bot]
  • sonarcloud[bot]
  • vercel[bot]
  • netlify[bot]
  • snyk-bot

  • Mute an account or a repository

    Nothing from it is delivered, whatever the reason. Accounts Beacone has already seen are listed, so a noisy one is a click away from being muted.

  • Hide an installation

    Pauses a whole GitHub account or organisation at once, for when a project goes quiet or you do.

And a nudge about what is still open

Once a day or once a week, at a local time you pick, Beacone sends one message listing the pull requests still waiting on you.

  • Your open pull requests

    Authored by you, not a draft, still open.

    is:pr is:open draft:false author:@me

  • Your drafts

    The ones you started and have not put up yet.

    is:pr is:open draft:true author:@me

  • Reviews asked of you

    Requested from you by name. A team you belong to does not count.

    is:pr is:open review-requested:@me

You choose the cadence, the time, the timezone, and which repositories it covers. If there is nothing to report, nothing is sent.

The digest is assembled at the moment it goes out, and none of its contents are stored: no title, no repository name, and nothing added to your activity history.

When GitHub changes, your message catches up

Somebody deletes a comment that mentioned you, or closes a pull request after asking for your review.

Beacone reaches back into the message it already sent and strikes it through, with a note saying who deleted the comment, closed the pull request, or merged it. If the pull request reopens, the original message is restored.

The content of the original message is never stored. The amended message is generated on the fly from the metadata.

🔔 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, but impossible to change your work.

  • No contents access

    It cannot read or clone your code.

  • No GitHub OAuth scopes

    Your first GitHub authorization proves who you are and stores an encrypted, rotating App credential. Repository permissions still come only from installing the App.

  • 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. What Beacone can read comes from installing the GitHub App and the repositories you tick there, private ones included. The GitHub authorization itself asks for no OAuth scopes.

Can I use both Telegram and Slack?

Yes, you can connect both if you like. One destination is active at a time, and you can switch it from Account settings without disconnecting the other.

Do I have to sign in with GitHub?

Yes. New Beacone accounts are created with GitHub, and that same authorization connects your notifications. You can link a Google account from Account settings afterwards, and it becomes another way to sign back in.

How fast is it?

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

Do I need to install anything or keep my computer running?

No. Beacone runs on its own servers. GitHub posts events straight to them, so a message reaches your chat whether your computer is on or off.

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.

My organisation already installed the App. Do my teammates see my notifications?

No. One installation can serve a whole team, but delivery stays personal. Each member signs in with their own GitHub, chooses their own destination, and receives only what their own repositories and rules produce.

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.

Where is my data stored?

In the European Union, backups included. GitHub, Telegram, and Slack each handle the parts they need under their own terms. Beacone does not sell personal data, serve advertising, or use third-party analytics.

Can I turn it off for a while?

Yes. Untick reasons, mute a bot, an account or a repository, or hide an installation: delivery stops and your history stays. GitHub cannot be unlinked, so deleting your account from Account settings is how you leave, and every trace of your data goes with it.

Stop reading emails to find out you were mentioned.

Setup takes less than 5 minutes.

Checking availability…