Install once
One shell command pulls the CLI, links fuze-base, and opens the guided setup.
Keybase-style trust. Terminal-native chat.
Encrypted team comms without setup hell.
Fuze Base gives private teams terminal chat, public identity proofs, encrypted invites, and a hosted discovery layer that never needs your message plaintext or team secret.
Signed devices
Public proofs
X25519 invites
Encrypted sync
fuze-base chat routefusion-founders
encrypted sync
09:41colton pricing memo is ready. sending invite now.
09:42sam got it. proof verified, key accepted.
09:42system sam joined routefusion-founders via encrypted key box.
09:43colton no relay tokens. no shared room secret in Slack. finally.
What it does
It replaces the sketchy bootstrap work around private team chat.
Claim your identity
Your device creates a signed account chain, then you attach a public GitHub or domain proof.
Invite a real person
Team keys move through encrypted X25519 key boxes, not pasted shared secrets.
Chat from the terminal
Messages are signed locally, encrypted locally, and synced as ciphertext through the server for every member of the team.
Trust model
The server coordinates. Your laptops hold the secrets.
Server sees: usernames, public account links, public proof metadata, team membership, timestamps, and encrypted payloads.
Server does not need: message plaintext, private device keys, team secrets, or invite plaintext.
Your client owns: signing keys, decrypt keys, local chat history, and whether another identity is trusted.
curl -fsSL https://fuzebase.io/install.sh | sh
fuze-base onboard
fuze-base chat routefusion-foundersTerminal-first today