Read-only mirror of codeberg.org/beebuzz/beebuzz
See the codeSupported tools encrypt alerts before sending, so only your paired devices can read them. For services that connect directly, trusted delivery keeps setup simple.
Hosted flow, showing setup in BeeBuzz and delivery in Hive side by side.
Sign in, create a pairing code, pair Hive, create a token, and deliver the first notification.
For developers, homelabbers, and small teams sending notifications from systems they control. Not chat, not a team inbox, not a general messaging platform.
Two delivery modes, chosen by one question: can the sender encrypt before it talks to BeeBuzz?
|
|
|
End-to-end encrypted delivery (recommended). The sender encrypts locally. BeeBuzz stores ciphertext only and never sees the content. BeeBuzz can't read the message.
Trusted delivery (when needed). The sender sends plaintext. BeeBuzz reads to route, then delivers to your devices. BeeBuzz can read the message to prepare delivery.
In both modes, Web Push transport is encrypted in transit between BeeBuzz and the receiving browser.
BeeBuzz.app is the hosted BeeBuzz SaaS.
Hosted access has Free and Hosted plans. Self-hosting remains free, open source, and available under the AGPL license.
Start here: BeeBuzz quickstart.
Use trusted mode when the sender cannot encrypt before sending:
curl https://push.beebuzz.app \
-H "Authorization: Bearer $TOKEN" \
-F title="Hello from BeeBuzz" \
-F body="Trusted mode test"
Install the CLI from the latest release or with Go:
go install go.beebuzz.app/cli/cmd/beebuzz@latest
Then connect the CLI and send an encrypted notification:
beebuzz connect
beebuzz send "Hello from BeeBuzz"
In E2E mode, the CLI fetches paired device public keys, encrypts the payload
locally with age, and sends ciphertext as
application/octet-stream. Hive fetches and decrypts the notification on the
receiving device.
beebuzz CLI for sending end-to-end encrypted notifications from terminals, scripts, and automation.BeeBuzz supports production self-hosting with Docker Compose. The supported minimal stack, DNS requirements, upgrades, and data-backup requirements are documented in the self-hosting guide.
BeeBuzz is licensed under the GNU Affero General Public License v3.0 only. See LICENSE.
Third-party dependencies are tracked in the Go and frontend dependency manifests.
Read-only mirror of codeberg.org/beebuzz/beebuzz
See the codeSupported tools encrypt alerts before sending, so only your paired devices can read them. For services that connect directly, trusted delivery keeps setup simple.
Hosted flow, showing setup in BeeBuzz and delivery in Hive side by side.
Sign in, create a pairing code, pair Hive, create a token, and deliver the first notification.
For developers, homelabbers, and small teams sending notifications from systems they control. Not chat, not a team inbox, not a general messaging platform.
Two delivery modes, chosen by one question: can the sender encrypt before it talks to BeeBuzz?
|
|
|
End-to-end encrypted delivery (recommended). The sender encrypts locally. BeeBuzz stores ciphertext only and never sees the content. BeeBuzz can't read the message.
Trusted delivery (when needed). The sender sends plaintext. BeeBuzz reads to route, then delivers to your devices. BeeBuzz can read the message to prepare delivery.
In both modes, Web Push transport is encrypted in transit between BeeBuzz and the receiving browser.
BeeBuzz.app is the hosted BeeBuzz SaaS.
Hosted access has Free and Hosted plans. Self-hosting remains free, open source, and available under the AGPL license.
Start here: BeeBuzz quickstart.
Use trusted mode when the sender cannot encrypt before sending:
curl https://push.beebuzz.app \
-H "Authorization: Bearer $TOKEN" \
-F title="Hello from BeeBuzz" \
-F body="Trusted mode test"
Install the CLI from the latest release or with Go:
go install go.beebuzz.app/cli/cmd/beebuzz@latest
Then connect the CLI and send an encrypted notification:
beebuzz connect
beebuzz send "Hello from BeeBuzz"
In E2E mode, the CLI fetches paired device public keys, encrypts the payload
locally with age, and sends ciphertext as
application/octet-stream. Hive fetches and decrypts the notification on the
receiving device.
beebuzz CLI for sending end-to-end encrypted notifications from terminals, scripts, and automation.BeeBuzz supports production self-hosting with Docker Compose. The supported minimal stack, DNS requirements, upgrades, and data-backup requirements are documented in the self-hosting guide.
BeeBuzz is licensed under the GNU Affero General Public License v3.0 only. See LICENSE.
Third-party dependencies are tracked in the Go and frontend dependency manifests.