Buzz: Human-Agent Workspace for Auditable Projects

A self-hostable project workspace where humans and AI agents collaborate in signed rooms that unify conversation, code patches, workflow events, and approvals into one searchable, auditable event log.

Internal ToolDeveloper & IT OperationsFlat-fee relay hosting
MVP time5-8 weeks
DifficultyHard
Infra cost$35-$240
RevenueFlat-fee relay hosting
Review the decision summary
5,521 views
Updated August 2, 2026

Decision snapshot

Is this worth validating?

Build this if

Your team already runs AI coding agents alongside human engineers and needs a shared, signed audit trail of decisions, patches, and approvals.

Avoid this if

Your team only needs standard chat or a code forge without agent coordination or a unified event log.

Validate first

Deploy the relay on Railway, invite two humans and one agent identity to a room, attach a patch and an approval, and confirm the event log is searchable and immutable.

Problem and target customer

Why this exists

Customer problem

Engineering teams scatter project context across chat tools, code forges, CI dashboards, and review systems with no single durable record of decisions, evidence, and agent actions.

Who pays

Software teams and engineering leads who coordinate both human contributors and AI coding agents and need an auditable, self-hosted record of who did what and why.

Business model

Self-hosted community edition for technical teams; paid managed relay per workspace or team, with retained event history, access controls, audit search, and enterprise support.

Editorial note

Buzz is a project workspace where human and agent actions share one searchable event log. Conversations, code patches, workflow runs, and approvals become related records instead of separate fragments across chat, repositories, and CI dashboards.

The paid product is the managed relay: teams pay for a hosted workspace that retains their event history, controls access, and keeps agent identities connected without operating the relay themselves. Self-hosting remains a useful adoption path, while enterprise support and private deployment serve teams with stricter control requirements.

The MVP should validate one auditable room containing a conversation, a patch, a workflow result, and an approval. It should not try to replace a full chat suite, code forge, or project-management platform in the first release.

Choose your next step

What do you need next?

Evaluate the operating tradeoffs quickly, or inspect how to build the MVP.

Evaluation preview

What would it take to run?

Directional infrastructure estimates for the current 20,000 workspace events assumption. Open the full calculator when you are ready to change it.

Open full cost and deployment
ManagedSelected
$133-$271/ month

Managed app, database, and worker capacity for the beta workload.

Lowest operating effort
Lean self-hosted
$133-$261/ month

A lower fixed-cost deployment with more setup and maintenance.

Lowest baseline cost
More control
$148-$326/ month

More control over service placement and operational capacity.

Most separation and control

Build blueprint

Build the first paid use case

Product goal

Who it serves and what it must change

Target user
Engineering leads coordinating human developers and AI coding agents on shared projects
Problem
Project context is scattered across chat, code forges, CI dashboards, and review tools with no single auditable record of decisions and agent actions
Measurable outcome
A team can create a room, invite humans and agents, record patches and approvals, and search the full event history to reconstruct a decision

MVP scope

What ships now and what waits

Included

  • Signed rooms with human and agent identities
  • Message posting and threading
  • Patch attachment and display
  • Workflow run event recording
  • Approval issuance tied to events
  • Event search by type, author, and keyword
  • Self-hosted relay with durable storage

Excluded

  • Mobile-native approval flows
  • Hosted multi-tenant pricing
  • Canvas and media annotation
  • Automated agent permission management UI

UX and user flow

Screens, actions, and states

Room view

Display threaded messages, patches, workflow runs, and approvals in a unified event feed

Post messageAttach patchView workflow runIssue approval
Search panel

Filter and search across all room events by type, author, and keyword

Filter by event typeFilter by authorKeyword searchOpen event detail
Identity manager

Create and manage scoped human and agent identities with signing keys

Create human identityCreate agent identityAssign room permissionsView key fingerprint
Room settings

Configure room access, allowed event types, and relay connection

Invite memberSet event type permissionsView relay status

Primary flow

  1. Create community and room
  2. Invite humans and agents with scoped identities
  3. Post messages and attach patches
  4. Record workflow run events
  5. Issue approvals
  6. Search event history

Loading, empty, and error states

  • Room empty
  • Events loading
  • Event posted
  • Patch attached
  • Workflow run recorded
  • Approval issued
  • Search results returned
  • Relay disconnected

Core entity outline

Entities and business rules

Community

Top-level grouping that contains one or more project rooms

Fields
id, name, created_at, owner_identity_id
Relations
has many Rooms, has many Identities
Room

A signed collaboration space where humans and agents post events

Fields
id, community_id, name, created_at, allowed_event_types
Relations
belongs to Community, has many Events, has many Identities via membership
Identity

A scoped human or agent participant with an independent signing key

Fields
id, community_id, display_name, kind, public_key, permissions
Relations
belongs to Community, has many Events, has many Approvals
Event

A signed, immutable record of a message, patch, workflow run, or approval

Fields
id, room_id, identity_id, event_type, payload, signature, created_at
Relations
belongs to Room, belongs to Identity, has one Approval (if approval type)
Approval

A recorded approval tied to a specific event such as a patch or workflow run

Fields
id, event_id, approver_identity_id, status, created_at
Relations
belongs to Event, belongs to Identity

Business rules

  • Every event must be signed by the identity that authored it
  • Agent identities must have their own keys separate from human identities
  • Approvals must reference an existing event in the same room
  • Event signatures must be verified before storage in the relay
  • Event types not in a room's allowed_event_types list must be rejected

Architecture and data flow

Components, integrations, and controls

Nostr relay

Receive, verify, store, and serve signed events for all rooms

Frontend client

Render rooms, event feeds, search, and identity management; sign events with user or agent keys

Event storage

Persist signed events durably and support filtered search queries

Identity key store

Manage signing keys for human and agent identities with scoped permissions

Integrations

  • Git webhooks via Make for patch events
  • CI workflow run events via Make
  • NIP-34 event protocol for signed project events
  • Railway for relay hosting

Data flow

  1. External git or CI event enters via Make and is signed and posted to relay
  2. Frontend signs user or agent actions and posts to relay
  3. Relay verifies signature and stores event
  4. Frontend queries relay for room events and search results

Failure handling

  • Relay disconnection shows offline state and queues events locally
  • Invalid signature events are rejected with an error to the client
  • Search returns partial results with a warning if storage is temporarily unavailable

Security

  • All events cryptographically signed by author identity
  • Agent keys scoped to permitted event types per room
  • Relay rejects unsigned or mismatched-signature events
  • Self-hosted relay under team's operational control

Rate limits

  • Per-identity event posting rate configurable per room
  • Relay query rate limited to prevent search abuse

Deliverables and acceptance

Definition of done for the MVP

Deliverables

  • Self-hostable relay deployed on Railway
  • Frontend with room view, search panel, identity manager, and room settings
  • Signed event creation and verification pipeline
  • Approval flow tied to patches and workflow runs

Acceptance criteria

  • A human and an agent identity can post messages to the same room and both appear with distinct signatures
  • A patch can be attached to a room and an approval can be issued referencing that patch event
  • A workflow run event can be recorded and is visible in the room feed
  • Searching by event type, author, and keyword returns matching events from the room history
  • The relay rejects events with invalid signatures and returns a verification error

Recommended stack

Enough technology for the first version

Frontend

Lovable

Rapidly build the room interface, event feed, and search panel without custom frontend scaffolding.

Relay and event storage

Self-hosted Nostr relay on Railway

The product is built around a Nostr relay with signed events; Railway provides documented deployment for self-hosting.

Automation glue

Make

Optional bridge to route git webhook and CI events into the relay as signed events without writing custom integrations for every source.

Why this is sufficient

Buzz centers on a Nostr relay that stores signed events from both humans and agents. The relay is the core; the frontend renders rooms and search; Make optionally pipes external git and CI events into the relay. Railway hosts the relay for teams that want a quick self-hosted path.

Not required for the MVP

LLM orchestration framework as a core dependencyMulti-tenant SaaS billing infrastructureMobile-native application
Next stepTurn the blueprint into an execution plan

Copy the build prompt, model the operating cost, and choose where to deploy.

Build and ship

Execution

Build, price, and deploy the MVP

Once the blueprint is clear, use the prompt, cost model, and deployment options to start building.

Build prompt

Copy this into a builder

Lovable

Build prompt

Your build prompt is ready

Open the prompt pack whenever you are ready to take this blueprint into your builder.

Based on the blueprintReady for your builderFollow-up steps included

Cost calculator

Model the MVP operating cost

A technical run-cost estimate for the first production version. Team, acquisition, payment fees, and business COGS are excluded.

Estimated monthly total$133-$271

$33-$68 per 5,000 workspace events

Workspace events / month20,000 workspace events
Selected pathEasiest
Pricing checkedAug 2, 2026

Usage assumptions

Use beta workload metrics when available.

Infrastructure approach
Managed app, database, and worker capacity for the beta workload.
Cost breakdown

$133-$271 per month

Low and high values allow for usage variance and plan headroom.

Managed application stack

Managed app, database, and worker capacity for the beta workload.

40K workspace events included, then $5-$20 per 40K workspace events
$5-$25
Agent workspace calls (GPT-5.4 mini)

Model calls for project search, code review, release drafting, and workflow assistance.

20K workspace events x 5K input + 1K output tokens
$124-$206
Event and artifact storage

Storage for signed workspace events, patches, media references, and audit history.

0 included, then $0.02-$0.2 per 100 workspace events
$4-$40

Included

  • Application hosting
  • Database and background processing
  • Required product modules

Not included

  • Labor
  • Marketing
  • Taxes and legal review
  • Enterprise compliance work

Pricing basis

The estimate combines the selected infrastructure path, required operating modules, selected optional modules, and usage above included monthly allowances. Taxes and regional uplifts are excluded.

Deployment options

Pick the operational tradeoff

Choose based on operating preference, not only the headline price.

EasiestRecommended

Railway

Run the web app, database, and background jobs with a small operational footprint.

$5-$25/month plus usage modules

Good fit

  • Managed beta
  • Fast deployment
  • Background jobs

Limitation

Service usage and background workloads can exceed the base plan.

Cheapest

Vultr

Run the app, worker, and database on one small Vultr VPS with Docker Compose and explicit backups.

Varies by selected stack

Good fit

  • Hands-on operator
  • Small pilot
  • Low fixed cost

Limitation

You manage more setup, backups, monitoring, and upgrades.

More control

DigitalOcean

Separate application, worker, data, storage, and backup responsibilities as the workload grows.

$10-$60/month plus usage modules

Good fit

  • Dedicated capacity
  • Custom services
  • Operator control

Limitation

Security updates, backups, observability, and scaling remain your responsibility.