ML-powered noise gate
A Silero voice-activity model runs in an audio worklet to gate out coughs, sneezes, keystrokes, and room noise while letting every vocal range through. Natural and Strict modes.
Private voice & text chat
with a 3D world
CVB is an invite-only hangout for friend groups: crystal-clear voice, end-to-end encrypted messages and calls, a shared 3D lounge, collectible pets, a listen-together music dock, and native screen sharing. And the server can’t read your messages or hear your voice.
Invite-only · self-hostable · free · Windows, Mac, Linux
What’s inside
A full hangout, not just a chat box.
End-to-end encrypted chat & voice
Messages, replies, edits, and file shares are encrypted on your device with X25519 + XSalsa20-Poly1305. Voice calls too: each Opus frame is encrypted before it reaches the server, which forwards audio it can’t read. The server routes opaque ciphertext.
A persistent 3D world
Walk a shared lounge with synced avatars. Doorways map to voice channels, holo-screen “TVs” show your friends’ streams, and the space is themeable.
Collectible pets
Fifty monsters across five rarities to feed, play with, bathe, and evolve. They wander the world, greet you, and level up through a Tamagotchi-style care loop.
Listen together
A music dock per voice channel: a classic bot, local files, URLs, internet radio, YouTube watch-together, Spotify group playback, a shared soundboard, and real MIDI playback.
Native screen & game sharing
Windows Graphics Capture with custom quality ladders up to 1080p60, graceful bandwidth adaptation, and per-streamer TVs in the 3D lounge. Not a browser getDisplayMedia hack.
Popout & picture-in-picture
Pop voice meters, docs, and floating widgets into their own always-on-top windows so you can keep an eye on the room while you play.
Signed auto-updates
Updates are ed25519-signed and verified against a pinned key before anything is written. An admin panel handles invites, users, channels, and recovery.
Security, honestly
CVB was built privacy-first, then audited, then fixed. Here is exactly what is protected, and what isn’t yet.
What’s protected
- End-to-end encrypted chat. Messages, replies, edits, and reactions use
crypto_box(X25519 Diffie-Hellman + XSalsa20-Poly1305), sealed once per recipient. - Signed messages. Since v1.35.0, each chat message is also Ed25519-signed by the sender’s identity key; receivers verify it against the pinned pubkey on the roster and flag any message whose signature does not verify.
- End-to-end encrypted voice. Each Opus frame is encrypted on your device before it reaches the SFU, which forwards encrypted audio it cannot read. Voice keys are sealed per recipient through the same
crypto_boxpath and rotated whenever someone joins or leaves. - Encrypted file shares. File bodies are encrypted with AES-256-GCM under a random key, which is itself sealed per recipient via
crypto_box. - Keys in your OS keyring. Your ed25519 signing key and X25519 encryption key live in Windows Credential Manager (DPAPI), never written as plaintext files.
- Argon2id password hashing. The server never sees your plaintext password and stores only an Argon2id hash.
- Challenge-response auth. Sessions authenticate by signing a server-issued challenge with your ed25519 key, not by sending a password over the wire.
- Recoverable identity. A 24-word BIP-39 phrase reproduces your keys, and an Argon2id-encrypted backup export carries your server list to a new device.
- Signed updates. Every update is verified against a pinned ed25519 public key before it touches disk.
What to know
- Voice and video are end-to-end encrypted. Since v1.29.0, CVB encrypts each Opus frame before it reaches the SFU. Since v1.31.0 the same applies to webcam and screen-share video: VP8 payload descriptors stay unencrypted so the SFU can still switch simulcast/SVC layers, while AV1 and VP9 payloads are fully encrypted and routed via their Dependency Descriptor. (H.264 screen-share encrypts on send and the receiver decrypts successfully, but a known decoder issue currently leaves the picture black; we are investigating and will close this gap.) The server forwards encrypted media it cannot read, the same property your chat already has. The transport hop is additionally protected by WSS + DTLS-SRTP.
- The server sees metadata. It routes who talks to whom, when, and the shape of encrypted blobs, even though it cannot read their contents.
CVB vs Discord
CVB’s text, file shares, voice, and video are end-to-end encrypted by default. Discord’s text isn’t, though Discord did catch up on E2EE voice and video in 2026. Discord is ahead on a few things too (mobile, web, forums, bots). Here’s the full picture, feature by feature, honestly.
| Feature | CVB | Discord |
|---|
Discord column reflects public Discord documentation as of mid-2026. Discord rolled out end-to-end encrypted voice/video (the DAVE protocol) across DMs, group DMs, server voice channels, and Go Live during 2026; text chat remains not end-to-end encrypted.
Changelog
Release notes, straight from the app.
Loading release notes…
Get CVB
Invite-only, so grab a code from whoever runs your server. The app keeps itself up to date after install.
Download CVB