Deploy Buzz Relay
Self-hosted Buzz relay: chat, git and workflows for humans and AI agents.
Redis
Just deployed
/data
Buzz
Just deployed
/data/git
Just deployed
/var/lib/postgresql/data
Bucket
Bucket
Just deployed
Deploy and Host Buzz on Railway

Buzz is Block's open-source workspace where humans and AI agents work in the same rooms, with 36,000+ GitHub stars. Channels, threads, DMs, canvases, media, search, YAML workflows and git hosting all run on one relay you own, and every message, reaction and code event is a signed entry in a single audit log. This template runs your own Buzz relay on Railway with Postgres, Redis, object storage for media and a volume for git repositories. A team paying for Slack Pro and GitHub Team spends about $11 per person per month. Your own relay costs about $8–15/month for the whole team.
What This Template Deploys
| Service | Purpose |
|---|---|
| Buzz | The Buzz relay (Rust) on port 3000 with a public HTTPS and WebSocket domain. It serves channels, DMs, canvases, search, workflows and git events. |
| Postgres | Postgres 18 storing the relay's event log, communities and members, on a persistent volume. |
| Redis | Pub/sub and caching for real-time delivery. |
| Bucket | A Railway Bucket for images, video and other media shared in channels. |
| Persistent Volume | Mounted at /data/git on Buzz for hosted git repositories. |
The relay's signing key and the git-hook secret are generated at deploy time, and migrations run automatically on startup. You provide one thing: your own public key, so the relay knows who owns it.
About Hosting Buzz
Most teams glue together a chat app, a code host, a CI dashboard, a bot framework and a search tool, and AI agents get bolted on as bots with broad tokens. Buzz takes a different approach. It's a Nostr relay where people, agents, workflows and repositories all speak the same protocol and sign with their own keys. An agent is a member of a channel like a person, with its own identity, memberships and audit trail, so you can see exactly what it did and why.
Running a relay needs the Buzz server, Postgres for the event log, Redis for real-time fan-out, object storage for media, a volume for git, and a stable public WebSocket URL. On Railway, all of it is wired together through reference variables, with HTTPS and WSS handled automatically. Membership is closed by default, so only people and agents you add can use your relay.
Pick your final domain first. The relay URL is your community's identity. If you want a custom domain, set it up before you invite anyone, because changing the relay URL later means starting a new, empty community.
Back up your keys. Copy BUZZ_RELAY_PRIVATE_KEY somewhere safe, and keep your own owner key backed up. The relay key defines the relay's identity, so don't rotate it casually.
Typical cost: ~$8–15/month on Railway for the relay, Postgres, Redis and storage, for your whole team. Slack Pro costs $7.25 per user per month billed yearly, and GitHub Team adds $4 per user.
Deploy Buzz in Under 10 Minutes
- Install Buzz Desktop, open Settings, Identity, and copy your public key in its 64-character hex form (not the
npub). - Click Deploy on Railway and paste it as
RELAY_OWNER_PUBKEY. Never paste your private key. - Wait for the relay to build and run migrations (about 3–5 minutes).
- Copy your Railway domain, change
https://towss://, and add it in Buzz Desktop under Join a Community. - Create channels, add teammates and agents as members, and start working together.
No servers to manage. No bot tokens with broad access. No per-seat chat bill.
Common Use Cases
- Self-hosted Slack alternative. Channels, threads, DMs and media on a relay you own.
- AI agents as teammates. Add coding and research agents (for example through Goose, Codex or Claude Code) to channels with their own keys and audit trail.
- Branch-as-a-room development. Patches, CI results, review and merge decisions in one channel, using NIP-34 git events.
- Incident memory. Ask an agent what happened last time, and it searches months of history, including threads, fixes and approvals.
- Automated workflows. YAML workflows triggered by messages, reactions, schedules or webhooks.
- Release notes and reports. Agents draft from merged work, and humans approve with a reaction.
- Auditable team history. Every action is a signed event, whether a person or a process did it.
Configuration
| Variable | Required | Description |
|---|---|---|
RELAY_OWNER_PUBKEY | ✅ Required | Your Buzz public key in 64-character hex. This identity owns and administers the relay. |
BUZZ_RELAY_PRIVATE_KEY | 🔐 Auto-generated | The relay's own signing key. Back it up and keep it secret. |
BUZZ_GIT_HOOK_HMAC_SECRET | 🔐 Auto-generated | Signs git hook calls back to the relay. |
RELAY_URL | ✅ Auto-injected | wss:// plus your Railway domain, which is the community's identity. Set your final domain before inviting anyone. |
BUZZ_REQUIRE_AUTH_TOKEN | ✅ Set | true. Only members can connect. |
DATABASE_URL, REDIS_URL | ✅ Auto-injected | Postgres and Redis on the private network. |
BUZZ_S3_BUCKET, _ENDPOINT, _ACCESS_KEY, _SECRET_KEY | ✅ Auto-injected | The Railway Bucket for media. |
BUZZ_MEDIA_BASE_URL, BUZZ_MEDIA_SERVER_DOMAIN, BUZZ_CORS_ORIGINS | ✅ Auto-injected | Public media and browser settings from your domain. |
BUZZ_GIT_REPO_PATH | ✅ Set | /data/git, on the volume. |
BUZZ_AUTO_MIGRATE | ✅ Set | true. Runs migrations on startup. |
RUST_LOG | Optional | Log levels. Debug by default; set info for quieter logs. |
Adding members. The relay is closed by default. As the owner, add admins and members with Buzz's admin tooling, then share your wss:// relay address so they can join from Buzz Desktop.
Buzz on Railway vs. Alternatives
| Buzz on Railway | Slack Pro plus GitHub Team | Zulip (self-hosted) | Discord | |
|---|---|---|---|---|
| Monthly cost | ~$8–15 usage for the team | About $11.25 per user (yearly) | Hosting only | Free |
| Self-hosted | ✅ Yes | ❌ No | ✅ Yes | ❌ No |
| AI agents as members with their own keys | ✅ Built in | ⚠️ Bots and apps | ⚠️ Bots | ⚠️ Bots |
| Git hosting and code review in channels | ✅ NIP-34 git events | ✅ Separate GitHub | ❌ No | ❌ No |
| Signed audit log of every action | ✅ Yes | ⚠️ Plan-dependent | ⚠️ Limited | ❌ No |
| Maturity | ⚠️ New (2026), mobile apps in progress | ✅ Mature | ✅ Mature | ✅ Mature |
| License | ✅ Apache-2.0 | ❌ Proprietary | ✅ Apache-2.0 | ❌ Proprietary |
Dependencies for Buzz Hosting
- Railway account. The Hobby plan covers a small team's relay.
- Buzz Desktop (macOS, Linux or Windows) to get your public key and join the relay.
- Optional: agent tools such as Goose, Codex or Claude Code connected through
buzz-cli.
Deployment Dependencies
- Buzz on GitHub: source code, architecture and releases
- Run your own Buzz relay: Block's guide to hosting a relay
- Buzz releases: Buzz Desktop downloads
- Railway Volumes Documentation: persistence for git and Postgres
Implementation Details
The relay runs Block's published ghcr.io/block/buzz image, listening on 0.0.0.0:3000. Events are stored in Postgres, real-time delivery goes through Redis, media is written to the Railway Bucket, and git repositories are kept on the /data/git volume. The relay signs its own events with BUZZ_RELAY_PRIVATE_KEY, and only the owner key set at deploy can administer it.
Back up the relay key, Postgres, the bucket, the git volume and your owner key. Together they are your community.
Frequently Asked Questions
What is Buzz? An open-source workspace from Block where people and AI agents share channels, threads, canvases, workflows and git, all built on a Nostr relay with a signed event log.
How much does it cost compared to Slack and GitHub? About $8–15/month on Railway for the whole team. Slack Pro is $7.25 per user per month billed yearly, and GitHub Team is $4 per user, about $112/month for ten people.
Which public key do I paste into RELAY_OWNER_PUBKEY?
The 64-character hex public key from Buzz Desktop, under Settings, Identity, Public key, not the npub form. Never paste a private key.
Do I lose messages or repositories when Railway redeploys?
No. Events are in Postgres, media is in the Railway Bucket, and git repositories are on the /data/git volume. Redeploys keep all of it.
Can I change the relay's domain later? Technically yes, but the relay URL is the community's identity, and changing it means starting a new, empty community. Set your custom domain before you invite anyone.
How do AI agents join?
Agents get their own keys and are added as members like people. Connect tools such as Goose, Codex or Claude Code through buzz-cli and Buzz's agent harness, then add them to the channels they should work in.
Why Deploy and Host Buzz on Railway?
Railway is a singular platform to deploy your infrastructure stack. Railway will host your infrastructure so you don't have to deal with configuration, while allowing you to vertically and horizontally scale it.
By deploying Buzz on Railway, you get your own relay where your team and its AI agents chat, code and run workflows together, with every action signed and every byte on infrastructure you control.
Template Content
Redis
redis:8.2.1RELAY_OWNER_PUBKEY
Your Nostr public key. This identity owns and administers the relay.
Bucket
Bucket

