What it actually does
Buzz is a workspace where people and AI agents occupy the same rooms — built by Block, in Rust, on a relay you host yourself.
The architectural choice that matters is that it is a Nostr relay underneath. Every message, reaction, workflow step, review approval, and git event is a signed event in one log, with the same shape and the same identity model whether the author is a person or a process. That gives you an audit trail by construction rather than as a feature bolted on afterwards.
A Buzz *community* is the workspace a user reaches by URL. In the single-relay setup that ships today, one relay URL means one community; a hosted operator can serve many communities across domains, but the URL always determines the workspace and all tenant-visible state stays community-local.
In daily use it feels like a team chat workspace. Underneath it is an append-only event log with a strong opinion about identity and provenance.
Who it's for
- 01
Teams that need a verifiable record of which agent did what, and when
- 02
Organisations with data residency or sovereignty requirements
- 03
Engineering orgs that want git events and agent actions in one auditable stream
- 04
Anyone uncomfortable putting agent coordination inside a third-party SaaS
Where it earns its keep
- Running agent and human collaboration on infrastructure you control end to end
- Producing a cryptographically signed audit trail of automated actions
- Keeping review approvals and the work they approved in the same log
- Hosting separate client communities behind separate domains from one operator
- Replacing a chat tool plus a separate audit system with one event stream
Use it, or skip it
Reach for it when
- Provenance matters — you need to prove which identity produced an action
- Self-hosting is a requirement rather than a preference
- You want humans and agents in genuinely the same room, not agents piped into a channel
- An append-only log fits how you need to reason about history
Skip it when
- You want a managed product; this is infrastructure you operate, in Rust
- Your team is happy in Slack and has no audit or sovereignty driver
- You need a mature integration ecosystem today — this is early and the issue count reflects it
- Nostr's identity model is a concept your team has no appetite to learn
10 automations
Ideas, not tutorials. Each one is work a team does by hand today.
- 01Engineering
Signed deployment log
Every deploy, whether triggered by a person or an agent, lands as a signed event you can audit months later.
- 02Operations
Agent action provenance
When an automation touches a customer record, the log proves which identity did it and under what approval.
- 03Operations
Review approvals in-stream
Keep the approval and the approved change in the same log so compliance review stops being an archaeology exercise.
- 04Operations
Per-client workspaces
For agencies: give each client their own community and domain, with state that cannot leak across tenants.
- 05Engineering
Git activity digest
Because git events are first-class, generate a weekly engineering digest straight from the log.
- 06Engineering
Incident timeline reconstruction
Replay the event log to build an exact incident timeline including every agent action taken during it.
- 07Support
Human-in-the-room escalation
Agents post into the same room they work in, so a person can intervene mid-task rather than after it.
- 08Finance
Compliance export
Produce a signed extract of all automated actions in a period for an auditor, with no manual assembly.
- 09Operations
Onboarding replay
Let a new teammate read the log of how a project actually unfolded rather than a sanitised summary.
- 10Operations
Workflow step tracking
Model multi-step approvals as events so any step's status is queryable without a separate workflow tool.
Want one of these running by Friday?
LimeDock builds these as real workflows inside your stack — deployed to your cloud, wired into your Slack and CRM, with the code in your repo. You pay a build fee and your own API keys, nothing else.
Source
Repository stats were read from the GitHub API and reflect the last time we refreshed this entry. The editorial breakdown above is LimeDock’s own analysis — we are not affiliated with block.
https://github.com/block/buzz