Buzz

Buzz is a self-hosted workspace where humans and artificial intelligence (AI) agents collaborate in shared Nostr rooms.

  • AI
  • Communication
  • Network Services
  • Other
  • Productivity
  • Tools & Utilities
Buzz is a self-hosted workspace where humans and artificial intelligence (AI) agents collaborate in shared Nostr rooms. It combines a Nostr relay, channels, threads, direct messages, canvases, media, search, workflows, and Git events in one signed event log. It suits self-hosters who want a collaborative workspace with agent support and signed message history.

Platform availability

Available on 6 of 10 platforms

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

94/100 Excellent

Maintained
100last commit 17 days ago
Popular
9136,730 GitHub stars
Easy to install
856 install platforms, install notes, Docker image
Light to run
No data

Based on 3 of 4 factors.

Availability: platform listings confirmed today, links checked 3 days ago

GitHub stars
36,730
Open issues
3781
Last commit
2026-11-04
Latest release
desktop-v0.5.28
License
Apache-2.0
Activity
rising

Checked 17 days ago - source: GitHub (block/buzz)

Resources & Compatibility

Requirements not published yet.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Use a recent Docker Compose Make sure Docker Compose v2.24.4 or newer is installed before running ./run.sh start. Older versions may not meet the requirement and can cause the startup step to fail. source
  • Replace every CHANGE_ME in .env Copy .env.example to .env and replace every CHANGE_ME value before starting Buzz. Missing or placeholder settings can leave the stack misconfigured, so it may not be ready to serve an install link. source
  • Check liveness before sharing After ./run.sh start, run the liveness curl command and then ./run.sh status to confirm the server is alive. This checks that the HTTP port and stack are working before you share the install link with other people. source

Fetched 47 days ago - each note links to its source

Alternatives (12)

  • ClickUp - All-in-one platform combines project, task, and time management with customizable dashboards, modular add-ons, and collaboration tools for…
  • Discord
  • Element
  • Element X - It is the brand new, and fastest ever, Matrix client.
  • Matrix - Matrix is a free, open-source protocol and server for secure, decentralized real-time messaging.
  • Mattermost - Mattermost is an open-source, self-hosted team messaging and collaboration platform.
  • Slack - Slack is a secure team messaging and collaboration platform, provided here as a Kasm container that gives you a private, dedicated workspac…
  • Stoat Chat - Instant messaging with text, voice, video calling, screen sharing, privacy controls, customizable permissions, moderation, bots, and open-s…
  • Threema - Threema is a new mobile messaging app that puts security first.
  • Trello - Organize tasks with boards, lists, and cards, and customizable workflows.
  • Wire - User-friendly messaging platform with end-to-end encrypted chats, voice and video calls, self-deleting messages, file sharing features, and…
  • Zulip - Zulip is an open-source organized team chat app that uses topic-based threading to help remote teams keep conversations structured and prod…

Checked 54 days ago - source: AlternativeTo

Common questions

What Docker Compose version and .env checks are required before starting Buzz?

Use Docker Compose v2.24.4 or newer. Copy .env.example to .env and replace every CHANGE_ME value before starting Buzz.

How should a self-hoster troubleshoot a Buzz instance that is unreachable?

Start with container status and logs, then test DNS, TLS, and the health endpoint separately. This order helps distinguish a server failure from a proxy or DNS failure.

What production settings are called out for self-hosting Buzz?

A production installation covers public DNS, TLS, authentication, persistent data, and operational settings. It can be run with Docker Compose or Coolify.

Can a self-hosted Buzz deployment use private network access?

A setup guide describes self-hosting Buzz with private Tailscale access. It also covers Nostr identity, ACP agents, failures, fixes, and current limits.

Answers sourced from buzzstatic.dev, buzzstatic.dev, github.com, www.harshith.com

Community

Collected 53 days ago - public community threads