Every layer native.
Rust servers, QUIC voice forwarding, a Flutter client with Rust underneath. No Electron, no embedded browser. The figures on this page are sourced and dated in the notes.
The stack
Three layers. Each one native.
Layer 3
Client
A native desktop and mobile app. Flutter draws the interface; audio, video and cryptography run in Rust through FFI. No embedded browser engine.
- Windows, macOS, Linux, iOS, Android
- Rust FFI for audio, video, crypto
- One process, not one per view
Layer 2
Core
Rust servers in every region: gRPC for signaling and chat, a QUIC selective forwarding unit for voice and video. The server forwards audio without decoding it.
- gRPC signaling, QUIC media forwarding
- PostgreSQL, ScyllaDB, Valkey, NATS
- Scales out: more pods, more regions
Layer 1
Transport
QUIC over UDP with TLS 1.3. The key exchange is hybrid X25519 + ML-KEM-768, chosen against harvest now, decrypt later attacks.
- QUIC, no head-of-line blocking
- TLS 1.3, hybrid post-quantum handshake
- Voice keys from MLS (RFC 9420)
Regions, measured memory, what runs today
Voice network
Configured regions, as of 2026-06-143
Where voice servers run, and where they are planned.
7
Deployed
20
Planned
4
Countries, deployed
4
Providers, deployed
Nuremberg
Deployed
Falkenstein
Deployed
Helsinki
Deployed
Berlin
Deployed
Limburg
Deployed
Beauharnois
Deployed
Bern
Deployed
Hillsboro
Planned
Ashburn
Planned
Singapore
Planned
Gravelines
Planned
Strasbourg
Planned
Marseille
Planned
Prague
Planned
Vienna
Planned
Zurich
Planned
Frankfurt
Planned
Amsterdam
Planned
London
Planned
Montréal
Planned
Washington D.C.
Planned
San Francisco
Planned
Los Angeles
Planned
Tokyo
Planned
Singapore
Planned
Sydney
Planned
Frankfurt
Planned
Idle memory
Windows 11, friends list open2
About a third of the memory. Measured, not estimated.
Voidcom
Native client, idle
~170MB
Discord
Electron client, idle
~560MB
Conservative end of five runs on one machine. When our number moves, the page moves with it.
Read the methodologyWhat we operate
Four things. Said plainly.
Voice & videoLive
Voice frames travel over QUIC to the nearest forwarding unit and out again without being decoded. The Low Latency preset cuts frames to 5 ms; audio is 48 kHz throughout.
- QUIC transport, packet-loss recovery
- 5 ms frames, Low Latency preset
- 48 kHz audio
- Screen share and webcam
Servers & chatLive
Servers, channels, roles and permissions, custom emoji. Replies, reactions, mentions, pins, full-text search and file sharing. Invites with limits, moderation with a role hierarchy.
- Channels, roles, per-channel overrides
- Replies, reactions, threads, pins
- Full-text search
- Kick, ban, mute
EncryptionLive
Direct messages and voice are end-to-end encrypted with a hybrid X25519 + ML-KEM-768 exchange and XChaCha20-Poly1305. Voice keys come from MLS and rotate on every join and leave. Server channels use transport encryption.
- E2E: DMs and voice
- Hybrid post-quantum key exchange
- MLS 1.0 (RFC 9420) for voice
- Transport encryption for server channels
Bots & APIIn development
A Discord-compatible REST and gateway surface so existing bots can move over. The API exists; the developer portal that issues tokens does not ship yet.
- REST /api/v10 and gateway
- Slash commands, webhooks
- Developer portal: pending
- Frame size on the Low Latency preset; other presets use larger frames. Measured end-to-end latency depends on your route to the region.
- Idle memory, measured 2026-04-26 on Windows 11 with the friends list open, conservative end of five runs. Method and all runs: measurement methodology.
- Region list is deployment configuration, last confirmed 2026-06-14 and updated with each release. It is not a live status feed. Account data is hosted in the EU; voice is end-to-end encrypted on every region.
Apply for the Beta
Voice, chat, servers and encryption are free, and Abyss is there if you want more storage and HD video. Make Voidcom the chat app you always wished for, and get in before everyone else does.
No spam. No tracking. No ads. We only email about beta access.