Comparison
Both of us put people and agents in the same rooms, and both speak ACP and MCP. Then we part ways: Buzz's memory is a signed event log — everything that happened, forever. vahue's memory is what the room knows — distilled, channel-owned, and injected into your agent before it lifts a finger.
Buzz is a self-hostable team workspace on the Nostr protocol, built at Block, Inc. — chat, a git forge, workflows, voice, the works. vahue is deliberately narrower: channels, memory, and the record. Fewer features, more remembering.
| Axis | vahue | Buzz |
|---|---|---|
| Core bet | The room remembers: channels own distilled, scoped, trusted memory | The protocol is the product: one signed Nostr event log for everything |
| Agent execution | Always local, on the owner's machine, under the owner's credentials — a defended rule, not a default | Local by default; pooled community compute (Mesh) and remote agents are planned |
| Agent identity | A run is attributed to the person, the agent kind, and the model | Each agent has its own Nostr keypair and signs every event — cryptographic attribution |
| Shared memory | Channel-scoped context database; tiered entries (abstract / overview / detail); human trust ranks above agent inference; correction by supersession | The searchable signed event log itself, plus per-(agent, owner) encrypted engrams — agent memory is private to that pair, not channel-owned |
| How work becomes memory | The agent distills at the end of the turn via the capability rail, with mandatory provenance (run, model, author) | The agent publishes to the channel (the log is the record) and keeps private engrams via CLI, at its own discipline |
| Capability scoping | Structural: one MCP rail per channel, the channel is in the URL | Membership-based: channel access is enforced on the relay; the tool surface is uniform |
| Scope of product | Channels, memory, runs, artifacts — deliberately nothing else | Chat + forum + DMs + git forge + workflows + voice huddles + media — a full workspace OS |
| Tenancy | One organization per deployment; workspaces isolated by PostgreSQL row-level security | Multi-community relay with formally verified isolation (TLA+, Tamarin) |
| Maturity | Hosted SaaS, free for teams up to 5 · open-source self-host | v0.5.x with shipped desktop releases, in production at Block |
A credible comparison admits what the other side does better. Here's the part where we do that, and mean it.
Every message, reaction, workflow step, and git push is a signed event with a hash-chained audit trail. Per-event attribution is built into the substrate, not layered on top. That's genuinely impressive, and we're not shy about saying so.
Built-in git hosting on object storage, branches as channels, patches and reviews as first-class events. vahue stays out of code hosting on purpose — your forge already exists and you're not leaving it.
Desktop, web, mobile, CLI, voice — plus formally verified multi-tenancy and real production mileage inside Block. Buzz is much further along. Credit where due.
A searchable log answers "what happened" — if someone goes digging. vahue's channel memory answers "what do we know" — distilled entries with trust levels and provenance, pushed to the agent before every turn. Knowledge that shows up uninvited, like a good colleague, instead of waiting in an archive.
Buzz's engrams are encrypted to one agent–owner pair; when either leaves, the knowledge leaves with them. In vahue the channel owns the memory, so a colleague's different agent starts where yours stopped. Departure-proof by design.
vahue is a Rails app, a desktop client, and your local agent — no relay, no Redis, no event protocol to babysit. Self-host in one command, or run nothing at all: the hosted workspace is a signup, free for small teams.