A self-hostable chat/workspace platform, built on a Nostr relay, where humans and AI agents share the same rooms — messaging (NIP-01), authenticated presence (NIP-42, Schnorr-signature), git collaboration (NIP-34: patches, repo announcements, status events), and media (Blossom protocol) all ride the same relay. Publicly released by Block, Inc. (formerly Square) but explicitly not the internal-production version employees are told to use — see Capture Risk. Grew extremely fast for its age: repository created March 2026, already ~29,700 GitHub stars / ~3,800 forks by this story's drafting (August 2026). README frames it as under active development — some features (relay, channels, DMs, search) work today, others (mobile clients, approval gates) are in progress, and some (web-of-trust reputation, culture features) remain conceptual.
StackRust workspace (Axum web framework for the relay); PostgreSQL (events, full-text search); Redis (caching/pubsub); S3/MinIO (Blossom media storage); React frontend (desktop via Tauri, plus web)
FundingBlock, Inc. (corporate, publicly traded parent)
Last Investigated Aug 22, 2026
Topology view
This tool in the centre and the things it is directly related to. Each line names the kind of relationship.
Nostr (Tool): Built on, Speaks protocol, Stores in
OriginsHuman+AI-agent collaborative workspace — a Nostr-relay-based chat/coordination substrate designed for humans and AI agents to share rooms, extended with git-collaboration events (NIP-34)
Data FormatsNostr events (NIP-01 core, NIP-34 git events, NIP-42 auth); Blossom media blobs (S3/MinIO-backed)
Collaborative Live EditingN/A
Rich Text EditingLikely (chat/workspace UI; not itemized in README)
Mobile SupportIn progress (README lists mobile clients as under development, not yet shipped)
Web SupportYes (React web frontend)
Native AppsYes (React + Tauri desktop app)
TermsFree / self-hostable (Apache-2.0); Block's own internal build is private and not the OSS release
FundsUndisclosed (internal Block project, no separate funding round)
Based OnNostr (NIP-01 core relay, NIP-42 Schnorr-signature auth, NIP-34 git-over-Nostr events, Blossom media protocol)
Use Case CategoryTeam chat / workspace — humans and AI agents sharing rooms; secondary git-collaboration surface via NIP-34
User Interface TypeWeb + native desktop (React, Tauri)
Offline CapabilitiesNot stated in README
Collaboration FeaturesChannels, DMs, search (working today per README); git patches/repo/status events via NIP-34; approval gates (in development)
Data PortabilityHigh in principle — standard Nostr events (NIP-01/34/42), portable to any compliant relay/client; Blossom media likewise protocol-defined
Integration EcosystemNostr ecosystem (any NIP-01/34/42/Blossom-compliant relay or client); shares the NIP-34 git-over-Nostr surface with this project's existing ngit entry, though the two are distinct products — ngit is a focused git CLI/frontend, Buzz is a general chat/workspace platform where git is one event type among several
Web2 Data ExportNot stated
Prosocial CoherenceMixed — open protocol foundation (Nostr) and Apache-2.0 license, but single-corporate-maintainer control and an explicit gated internal-vs-OSS split cut against full openness
Economic FlowsNo
Governance & Decision MakingCentralized (Block, Inc. controls the roadmap and the OSS/internal split)
Media / PublishingYes (Blossom media protocol for file/image sharing)
Knowledge ManagementNot a primary focus per README
SensemakingNot stated
Project ManagementPartial (git-workflow events via NIP-34: patches, PRs, status)
Communication ModelReal-time chat/channels/DMs, relay-mediated
Network ResilienceDepends on relay availability; self-hostable so not dependent on a single Block-run relay, but no stated multi-relay redundancy pattern (unlike ngit's explicit multi-git-server redundancy)
Discovery MechanismNostr relay-based
Max ParticipantsNot stated
Data SovereigntyHigh if self-hosted (Apache-2.0, self-hostable via Docker Compose/Railway); low if using Block's own hosted/internal instance
Relationships
How this tool connects to other tools and organizations, from relationships reviewed by the OpenHaven data steward. They describe how projects connect, not how good they are.