Multica vs Buzz — One person, many agents
Two open-source platforms for coordinating a squad of agents running in parallel, dissected by architecture, operating model, and token cost. Plus a third option: replicate the model with Hermes Agent on a Telegram group.
Quick summary
- Two platforms solve the same need — one person coordinating many agents across parallel projects — but choose two different primitive units. Choosing the wrong primitive means choosing the wrong platform.
- Multica: primitive is the issue. Buzz: primitive is the signed event. Both are already present in the Hermes ecosystem.
- Multica shows token usage per run, agent, issue — see which run is expensive and cut exactly there.
- Buzz: every action is a signed Nostr event, hash-chain audit log, identity via keypair.
Key takeaway
Choosing the wrong primitive means choosing the wrong platform — Multica sees work as tickets, Buzz sees work as signed events.
Inside this playbook
- 01Conclusion first, evidence secondTwo platforms, two primitives, three decision questions
- 02Multica — technical profileMultiplexed Information and Computing Agent, Go backend, 44k+ stars
- 03Multica — orchestrating multiple agentsSquad, autopilot, data boundaries, self-host
- 04Buzz — technical profileSelf-hosted workspace, Nostr relay, Rust, Apache-2.0
- 05Buzz — operations and workflowChannel, workflow trigger, hash-chain audit, self-admitted limitations
- 0614-criteria comparison tableReadable even in black-and-white print
- 07Where tokens go — seven saving leversBased on documentation, not speculation
- 08Third option: Hermes Agent + Telegram groupYou don't have to pick one — there's a path combining all three
- 0930-day roadmapFrom zero to a parallel agent squad
- 10Sources & what could not be verifiedAll numbers sourced, with a list of acknowledged gaps
Conclusion first, evidence second
Two platforms solve the same need — one person coordinating many agents across parallel projects — but choose two different primitive units. Multica: the issue. Buzz: the signed event.
Three decision questions
- Does your work have a "ticket" shape? If work splits into discrete parts with clear done-criteria, Multica fits.
- How deep do you need audit? Buzz gives hash-verifiable signed events. Multica answers "how much"; Buzz answers "who signed, can't be altered".
- How many discrete tasks can you tolerate? Multica runs near-daily releases but the license isn't pure OSI.
Third option
Both are already in the Hermes ecosystem. Multica lists hermes as one of 20 runnable CLI agents, and Hermes lists Buzz as an official messaging channel. You don't have to pick one — there's a path combining all three.