Dapols
PlansAI employeesAI integrationPricingToolsBenchmarksBlog
Sign inFind my AI workflow
Dapols

The job big companies pay a forward-deployed engineer six figures to do — as a tool, for two figures.

AI price watch — free weekly email

Which AI tools changed price, and what launched — for small businesses. Verified from vendor pages. No spam, unsubscribe anytime.

Product

  • AI Deployment Plans
  • AI Plan Finder
  • AI skills library
  • AI tools
  • Pricing

Offerings

  • AI Deployment Plans
  • AI integration
  • Bigger or more complex? Tell us.
  • Bigger or more complex?

Company

  • Blog
  • AI model tracker
  • Submit a tool
  • Contact
  • Privacy
  • Terms of Service

Trust & methodology

  • About
  • Methodology
  • How we rank AI tools
  • Forward-deployed AI
  • Affiliate disclosure
  • AI tool pricing updates
  • Security & data privacy

© 2026 Dapols. All rights reserved.

support@dapols.comX

Put AI to work—one measurable workflow at a time.

Dapols
All articles

English · 7 min read

Buzz puts AI agents in your team chat as real members — should a 6-person business care yet?

Block's new Buzz gives AI agents their own identities inside a group chat, alongside people. What that actually changes for a small team, what it costs to run, and the honest verdict on whether to wait.

The short answer: no, not yet — unless you already have someone technical who runs your tools. But the idea inside Buzz is the one to pay attention to, because it will land in the chat app you already pay for within a year or two, and it changes how you'll manage work.

Facts below verified 29 July 2026 against buzz.xyz, the block/buzz repository, and launch coverage. Buzz is moving fast; check the repo before acting on anything here.

What launched

On Tuesday 21 July 2026, Block — Jack Dorsey's company — released Buzz. Dorsey described it on X as "a new groupchat platform for teams of people and agents of all sizes, built to reduce our dependency on slack and github. model-agnostic, decentralized, self-sovereign, and open source."

Every outlet covered it as "Dorsey takes on Slack" (TechCrunch, TechRadar). That framing is true and mostly uninteresting if you run a six-person business. The interesting part is one design decision.

The one thing that's genuinely new

In Buzz, an AI agent is not a bot integration bolted onto a channel. It's a member, with its own cryptographic key. The project's own README puts it plainly: agents get "their own keys, their own channel memberships, and their own audit trail. Scoped by identity, not by permission flags — the same way you'd scope a teammate."

That sounds like a technical detail. It isn't. It's the difference between two management realities:

  • Today, in most tools: an AI assistant acts as you. It uses your login, your permissions, your API key. If it does something wrong at 2am, the log says you did it. You cannot give it less access than you have, and you cannot fire it without changing your own password.
  • In the Buzz model: the agent is its own entity. You add it to the two channels it needs and no others. Everything it did is attributable to it, permanently, in the same log as everything the humans did.

If you have ever hesitated to let an AI tool touch your inbox, your CRM, or your invoices, that hesitation was about exactly this. "Give the agent its own identity and its own limited access" is the answer, and Buzz is the highest-profile product built around it from day one.

It's the same instinct behind giving agents scoped, auditable access to your systems rather than handing over the master key — the thinking we walk through in how to make your business readable to AI agents.

What Buzz actually is under the hood

Two facts change the calculation for a non-technical team.

It's built on Nostr. Buzz's relay is a Nostr relay: per the README, every message, reaction, workflow step, review approval and git event is a signed event in one log — same shape whether a person or a process wrote it. That's what makes the single audit trail possible. It also means it's not a website you sign up for.

It's a self-hosted app, not a service. The desktop app is a real download — macOS .dmg, Windows .exe, Linux .AppImage/.deb — but by default it connects to ws://localhost:3000, a relay on your own machine. There is no "start a free workspace" button on buzz.xyz. Block employees get an internal build pre-wired to Block's own relay; everyone else stands one up. The repo's production path is a Docker Compose bundle with Postgres, Redis, MinIO and optional Caddy for TLS.

This is where "open source and free" needs an asterisk. Buzz is Apache 2.0 licensed and costs nothing to download. But "free" only holds if someone hosts it. A server, a database, object storage, TLS certificates, backups, updates, and somebody who notices when it breaks. If that person doesn't exist on your team, Buzz's price is a contractor's monthly retainer, not zero. That's the same trap as "free" open-weight AI models — the weights are free, the operating is not, which we cover in when cheap AI models beat ChatGPT.

Note also what Buzz supplies and what it doesn't: it connects to agent harnesses like Goose, Codex and Claude Code through an ACP bridge that speaks MCP. Buzz is the room the agents work in. The agents — and their model bills — are still yours to provide.

How finished is it?

Eight days old, and the makers are refreshingly upfront. buzz.xyz labels it DEVELOPER PREVIEW and says "come test the early stages with us." The latest packaged build at the time of writing is v0.5.0.

The README carries a three-column status table. Working today: relay, channels, threads, DMs, canvases, media, search, audit log, the desktop app, YAML workflows, git events. Still "being wired up": mobile clients (iOS and Android) and push notifications. Workflow approval gates are listed as infra-exists-glue-still-drying. The repo's own words on the speculative column: "Please do not plan your compliance program around the 💭 column yet."

No mobile app and no push notifications is not a small caveat for a small business. For most six-person teams, chat is the phone.

The verdict

Who should try Buzz now

  • Software teams — it is explicitly aimed at replacing Slack and GitHub, and the git-native features (patches, reviews, merges living in the channel) are the strongest part.
  • Anyone with a technical person who already self-hosts things and is happy running a Docker Compose stack.
  • Businesses with a real reason to keep conversation data on infrastructure they control. Self-sovereign and self-hostable is a genuine differentiator, not marketing.

Who should wait

  • Any team without an in-house operator. The hosting is the whole cost.
  • Any team that lives on phones. Mobile clients aren't finished.
  • Anyone considering it as a Slack replacement on price. You're trading a per-seat bill for an ops burden — often a worse trade at six people, sometimes a better one at sixty.

What everyone should take from it

Start asking your existing vendors the Buzz question: can I give an AI agent its own limited identity in this tool, or does it have to borrow mine? That question is about to sort AI tools into trustworthy and not. Buzz is currently the clearest demonstration of the right answer — it just isn't, yet, a product most small businesses can run.

If the underlying goal is "get AI agents doing real work in my business without handing them the keys," that's the decision our free 2-minute AI plan finder and our business AI plans are built to make — starting from what you actually run today, not from what launched last Tuesday.

Get the weekly AI price watch

One short email a week on AI tool pricing changes for small businesses.

Get your AI plan

Your best tools, quick wins, and budget — in two minutes.

Take the quiz