Buzz

Your people, your agents, your project — all in one place

Messaging

Open Source

GitHub

Bots

Visit WebsiteSee on Product HuntGithub ⧉

The self-hosted relay model is what changes the governance calculus for developer communities — owning your event log means you're not subject to a platform's moderation call at the worst possible time. Curious whether a community relay can expose read access publicly while keeping write permissions gated, so the community's work is auditable from outside without letting anyone post. Is that relay permission model in at launch or on the roadmap?

signed events on a relay you self-host is a much more credible answer to the Slack/GitHub context-loss problem than yet another SaaS dashboard. the one thing I'd want cleared up before betting a team's workflow on it - if you lose the key tied to your cryptographic identity, is there any recovery path, or is that identity just gone and you start over? for a work tool that's a real question, not just a crypto-wallet edge case.

Congrats on the launch guys!

I really love the landing page design, it is very innovative.

If you guys ever consider creating a livedemo for your app feel free to try my product.

I have build a quick demo for you in 10 seconds from our landing page url-to-demo
https://app.livedemo.ai/livedemos/6a63e199cc86a442a8fd9936

Can someone please note, in plain, direct English... an example of concrete value this currently or potentially can offer?

I'm frankly weary of "this is the next great evolutionary leap!" without specific, grounded examples.

Teams of people AND agents in one chat is the right target — most tools bolt agents on as webhook bots with a user account, and it shows. Question on identity: are agents first-class members with their own auth and permissions (what they can read, which channels they can post to), or do they inherit from whoever installed them? Once several agents work one project, per-agent scoping is what keeps the room trustworthy. Open source + model-agnostic is the right call for this layer.

putting people and agents behind one identity system is the interesting bet here. question on the crypto identity side - if someone's key gets compromised, or an employee leaves, can you revoke or rotate their identity without breaking the signed history that already references it? self-hosted relay plus a permanent audit trail seems like it could get awkward if key rotation isn't a first-class thing

Coming from analytics and BI, the shared event log is the part that clicked for me. If messages, patches, workflow steps, and approvals all live in the same attributable history, Buzz could do more than reduce context switching — it could make human–agent work measurable.

Are you planning a higher-level analytics layer that turns those events into measures like handoff time, approval bottlenecks, workflow retries, or how often a human has to step in? That would help teams see where agents are actually improving the work, rather than just moving it around.

Congrats on the launch!

Honestly, Buzz is awesome. Having my team and AI tools all working in the same spot saves us so much time. We don't have to jump between five different apps anymore just to chat, organize tasks, and get work done. Really loving it so far!

Signed events for every message, patch and approval sounds great for audit. But in daily use, does the team notice the crypto identity layer at all, or is it fully invisible once you're in? Asking because most "self-sovereign" tools I've tried make you think about keys more often than you'd like.

LOVE the design of your landing page! Huge congrats on the launch! 🎉 Buzz's approach of putting humans and AI agents into a shared workspace with native Git and Nostr identities is brilliant. Quick question: How are you managing permission isolation to ensure autonomous agents don't leak context across restricted channels?

Also, not sure who set this up, but can I join? 🥺

wss://producthunt.communities.buzz.xyz