Lydo vs Buzz: two answers to humans and agents on one team
Lydo vs Buzz (Block's open-source Nostr workspace) compared: managed workspace vs self-hosted relay, confidential-by-design vs searchable-by-design, and where each one wins.
Buzz is Block’s new open-source team workspace — announced in July 2026, Apache-2.0 licensed, and built on the Nostr protocol. The pitch is genuinely interesting: one self-hosted relay replaces your chat, forum, DMs, git hosting, and automation; humans and AI agents join as equal, cryptographically-signed members; and your identity is a keypair you own, portable to any relay. If you follow Jack Dorsey’s decentralization work, Buzz is that philosophy applied to the team workspace.
We like a lot of it. Agents as first-class teammates is the same premise Lydo is built on, and their engineering is serious — a Rust relay, formal verification on the multi-tenancy model, a real git forge. But the two products make opposite bets on the questions that matter most for a working team: who runs the infrastructure, who can read your messages, and whether the product is finished. This comparison is based on Buzz’s own published docs and repository as of July 2026 — it’s early software and moving fast, so check their repo for the latest.
Lydo vs Buzz at a glance
| Lydo | Buzz | |
|---|---|---|
| What it is | AI-native managed workspace | Self-hosted, Nostr-based relay workspace |
| Who runs it | Lydo runs it; you sign up | You (or a host) run the relay |
| Identity | Normal account; phone sign-in; recoverable | Nostr keypair you manage yourself |
| Getting started | Invite link; minutes | Deploy a relay (or find one), bring a keypair |
| Apps | Web, iOS, Android, desktop | Desktop-first (Tauri); mobile and web earlier-stage |
| Chat, calls, boards, notes, calendar | Built in | Chat, forum, DMs, huddle voice; no boards/notes/calendar |
| Git hosting | No — integrates with your forge | Yes — built-in git forge, a core strength |
| Agents | Joby free in every Space; Claude, GPT, Gemini managed; BYOK on Business+ | Agents join as members via their own keys (ACP/MCP) |
| Message privacy | Confidential Mode: erase-for-everyone today; MLS end-to-end encryption rolling out | Server-managed encryption; relay indexes messages for search and eDiscovery |
| Human approval of agent writes | Approve-then-apply queues, shipped | Signed approval events in the design docs |
| Pricing | Free; Pro $23/mo, Business $79/mo | Free and open source; you carry hosting and ops |
| Best for | Teams who want it to just work | Self-hosters and open-protocol communities |
Buzz details from its public repository and vision documents, July 2026. It’s v0.x and evolving — verify current state before deciding.
The same premise, opposite bets
Both products start from the same observation: AI agents are becoming teammates, and the workspace should treat them that way — named, accountable, working alongside people rather than bolted on as a sidebar.
From there, the paths split. Buzz bets on sovereignty. Your identity is a cryptographic keypair. Your community is a relay you (or someone you trust) operates. Everything — every message, reaction, git push, and agent action — is a signed event in one log. If the host disappears, you re-point your domain at a new relay and keep going. It’s a coherent, principled architecture, and for open-source projects and communities that already live in that world, it’s compelling.
Lydo bets on the working team. Most teams don’t want to operate a relay, hold unrecoverable keys, or ask a new hire to generate a keypair before they can say hello. They want an invite link, apps on every device their team already carries, calls that just connect, and an AI that already knows the project. Sovereignty is a real value — but for most teams, so is Tuesday.
Buzz’s own docs are candid about the onboarding tax: most developers don’t have a Nostr keypair, and losing your key means losing your identity — there’s no account recovery, by design. That’s the cost of the sovereignty bet, and Buzz accepts it deliberately. Lydo makes the opposite trade: normal accounts, phone sign-in, recovery when someone loses a device mid-quarter.
Privacy: the bet that can’t be reversed
This is the deepest difference, and it’s architectural, not a feature gap.
Buzz’s vision docs state the model plainly: “Server-managed encryption covers every channel, every DM, every event — eDiscovery works on everything. End-to-end encryption (NIP-44) is a future consideration for DMs.” The relay encrypts data at rest and in transit, but it can read your team’s messages — it has to, because relay-side full-text search and eDiscovery are core features. That’s a legitimate design for compliance-driven deployments. It also means whoever operates your relay can read everything your team says, and that isn’t a toggle — it’s what the search and compliance features are built on.
Lydo is built toward the opposite end. Confidential Mode ships today: tap Confidential on any message and the text, files, reactions, and AI traces are erased from devices and servers — not archived, erased. Timed disappearing messages work the same way. And true end-to-end encryption, built on the open MLS standard (RFC 9420), is rolling out — private by architecture, not by promise.
If your requirement is “legal must be able to search everything,” Buzz’s model serves it — so does Lydo’s standard mode, where Spaces are searchable by your team and its agents. But if your requirement is “some conversations must stay only ours,” that has to be built in from the start. It’s the one row on the table neither product can borrow from the other later.
Agents: members with keys vs teammates with receipts
Buzz’s agent model is elegant: an agent gets its own keypair, presents an owner-signed capability, and joins the community as a member. Remove the owner and their agents lose access with them. Agent actions are signed events, so attribution is cryptographic. If you’re building agent-driven automation around a git forge, it’s a strong foundation.
Lydo’s model is built around a working team’s day. Joby is free in every Space and has the whole Space as context — the chats, notes, boards, files, and meeting recaps. Every approved model — Claude, GPT, Gemini, or your own keys — works from that same shared context and cites its sources. Agents show up in the member list next to the people, named and owned.
And when an agent wants to change something — move board cards, write into the vault, post on your behalf — Lydo runs it through an approval queue that’s live in the product today: the agent proposes, a human approves, then it happens. Buzz’s design documents describe signed approval events for its forge, and it’s a good design; in Lydo, approve-then-apply is something your team already clicks every day.
The workspace: a forge vs a place to run the team
Buzz’s deepest surface is the software forge: repos served from the relay, branch-as-channel development, CI agents posting into the branch’s channel, review and merge as signed events. If your team’s life is code review, that integration is real and differentiated — GitHub plus Slack collapsed into one self-hosted thing.
A working team needs more surfaces than a forge. In Lydo, the same Space that holds your chat holds video calls with recaps, voice huddles, boards with 12 column types and five views, a shared notes vault with backlinks, a calendar with external sync, and file storage — with Joby reasoning across all of it. Buzz has chat, a forum, DMs, and huddle voice today; boards, notes, and calendar aren’t part of the product, and its mobile and web clients are still early alongside the desktop app. Lydo ships native apps on web, iOS, Android, and desktop.
When Buzz is the better choice
Fair is fair. Buzz wins when:
- You’re an open-source project or community that wants public presence, chat, and git hosting on one self-hosted domain you control.
- Sovereignty is the requirement: your own relay, portable cryptographic identity, no platform dependency — and you have the ops capacity to run it.
- Your collaboration centers on code review and agent-driven CI, where branch-as-channel and signed merges shine.
- You’re all-in on Nostr and want your team’s work on the same protocol as your identity.
When Lydo is the better choice
Lydo wins when:
- You want a workspace that’s running in five minutes — invite link, phone sign-in, apps on every device — with no relay to operate and no keys to lose.
- Your team needs more than chat and code: calls, boards, notes, calendar, and files in one Space, with AI across all of it.
- Confidentiality matters: erase-for-everyone today, MLS end-to-end encryption rolling out — not a relay that indexes everything by design.
- You want agents with guardrails your team already uses: shared context, source citations, and approve-then-apply queues that are shipped, not specified.
FAQ
Is Lydo a good alternative to Buzz?
If you like Buzz’s humans-and-agents premise but want a managed workspace — normal accounts, native mobile apps, calls, boards, notes, and built-in AI without running a relay — yes, that’s exactly the trade Lydo makes. If you specifically want self-hosted, Nostr-native infrastructure, Buzz is the one making that bet.
Is Buzz free?
The software is free and open source (Apache-2.0). Running it isn’t zero-cost: you host the relay, storage, and media yourself or rely on someone who does. Lydo is free to start with flat per-Space pricing — Pro $23/month, Business $79/month — and your whole team joins free.
Can the people running the server read your messages?
On Buzz, yes by design — its docs describe server-managed encryption with relay-side search and eDiscovery over everything, with end-to-end encryption listed as a future consideration for DMs. In Lydo, Confidential Mode erases messages from devices and servers on demand today, and MLS end-to-end encryption is rolling out for true operator-blind conversations.
Do both support AI agents?
Yes, differently. Buzz admits agents as cryptographically-signed community members — strongest around its git forge. Lydo ships Joby free in every Space plus managed Claude, GPT, and Gemini (BYOK on Business and up), all working from the Space’s shared context, with citations and human approval queues built in.
Want the agent-native workspace without running the infrastructure? Open a free Space → Your whole team joins free. Part of our guide to the best team chat alternatives. See also: Lydo vs Slack, Lydo vs Discord, and why we charge per Space, not per seat.