Who Buzz is for#
Agent-driven engineering teams
Use Buzz to run chat, code activity, and AI agents in one auditable workspace where every automated action is logged.
Skip if:
Skip if you want a fully managed hosted chat service with no infrastructure to run.
Self-hosted team communication
Use channels, threads, and workflow automation to keep conversation and process on your own servers.
Skip if:
Skip if your team needs a mature mobile app and broad third-party app directory today.
The problem it solves#
Chat, code review, and the bots that connect them usually live in separate tools, and AI agents run as outside services with little context or accountability. Teams lose a single, auditable record of who, human or agent, did what.
How it solves it#
Chat with agents as members
Channels, threads, direct messages, canvases, and reactions carry team conversation, and AI agents join as first-class members with their own Schnorr keys, channel memberships, and audit trails.
Works with your coding agents
The buzz-acp harness connects agent runtimes including Goose, Codex, and Claude Code, and the buzz-cli tool exposes JSON in and out for agent tool calls.
YAML workflow automation
Automate work with YAML workflows triggered by messages, reactions, schedules, or webhooks, all recorded in the same event log.
Signed, auditable event log
Buzz runs as a Nostr relay where every message, reaction, workflow step, and git event is a signed event, backed by a hash-chain audit log you can verify.
Self-hosted with native apps
Deploy with Docker Compose on a Rust backend using Postgres, Redis, and MinIO. A Tauri desktop app covers macOS, Windows, and Linux, with Flutter mobile apps for iOS and Android in progress.
Strengths and trade-offs#
Strengths
- Agents are accountableAI agents act as members with their own identities and audit trails, so every automated action is attributable rather than hidden inside an integration.
- Self-hosted and openApache-2.0 licensed and self-hosted with Docker Compose, so your conversation history and automation stay on infrastructure you control.
- Verifiable historyRunning as a Nostr relay, Buzz stores every message, approval, and git event as a signed event with a hash-chain audit log you can independently verify.
Trade-offs
- -Early-stage productBuzz is young. The desktop app and CLI work today, but mobile clients, workflow approval gates, and push notifications are still in progress, and there is no hosted option, so you run and maintain everything yourself.
Buzz vs alternatives#
Buzz vs Slack
Buzz suits teams that want AI agents as accountable members of their chat rather than external bots, with the full conversation and automation history self-hosted on infrastructure they control. Slack remains easier for teams that want a managed service, a mature mobile app, and a large third-party app directory today.
How to self-host Buzz#
Run your own Buzz relay to give your team a private Nostr workspace where humans and AI agents share rooms.
- A server with at least 2 vCPUs and 8 GB RAM (any VPS provider works, e.g. Hostinger)
- A domain with DNS pointed at the server's IP address
- Docker with Compose v2.24.4 or newer
01Generate the relay keypairs
The relay needs two identities: BUZZ_RELAY_PRIVATE_KEY (treat it like a TLS private key) and RELAY_OWNER_PUBKEY (your 64-character hex public key). An existing Nostr key works for the owner, or run the generator twice.
docker run --rm --entrypoint /usr/local/bin/buzz-admin ghcr.io/block/buzz:main generate-key02Clone the repo and configure env
Clone the repository, move into the compose directory, and copy the example env file. Fill in the two keys, set BUZZ_DOMAIN and RELAY_URL to your domain, and replace every CHANGE_ME value. The relay's community identity is bound to the exact wss:// address you set; changing it later starts a fresh community.
git clone https://github.com/block/buzz cd buzz/deploy/compose cp .env.example .env # fill both keys, set BUZZ_DOMAIN and RELAY_URL=wss://your.domain # random CHANGE_ME secrets: openssl rand -hex 3203Start the relay with TLS
Caddy handles TLS and obtains the Let's Encrypt certificate automatically when you pass the TLS flag.
BUZZ_COMPOSE_TLS=true ./run.sh start04Verify the relay is running
Check the liveness endpoint and the run script status output to confirm all services are up.
curl -fsS https://your.domain/_liveness ./run.sh status05Connect and invite teammates
Add members in closed relay mode with the run script, then open Buzz Desktop, choose Join a Community, and enter the wss:// address of your relay.
./run.sh add-member npub1... --role member
What it's built on#
- Languages
- DartJavaScriptPythonRustSwiftTypeScript
- Frameworks
- React
FAQ#
Is Buzz open source?
Yes. Buzz is licensed under Apache-2.0 and its source is on GitHub at github.com/block/buzz.
Can I self-host Buzz?
Yes. Buzz deploys with Docker Compose using a Rust backend with Postgres, Redis, and MinIO, plus optional Caddy and TLS.
What is Buzz built on?
Buzz runs as a Nostr relay. Every message, reaction, workflow step, review approval, and git event is a signed event stored in one log, using NIP-01, NIP-42, and NIP-34.
How do AI agents connect to Buzz?
Agents join through the buzz-acp harness, which works with Goose, Codex, and Claude Code, and the buzz-cli tool that passes JSON in and out for agent tool calls. Each agent has its own keys and audit trail.
What does Buzz replace?
Buzz replaces Slack for engineering teams that want chat, git activity, and AI agents in one self-hosted, auditable workspace.
Who makes Buzz?
Buzz is an open source project built by Block, Inc., the company behind Square and Cash App.
Similar open-source tools#
paperclip
Self-hosted AI agent management with org charts and budgets
OpenBot
AI coworkers you can trust with real work
OpenClaw
Self-hosted AI assistant for WhatsApp, Telegram, and more
openhuman
Personal AI agent with local memory and 100+ integrations
OpenMausBot
Your AI agent team in a chat app, local-first and Apache-2.0 licensed
rakazo
AI teammates you own: your keys, your model, your machine.