// the find
security-union/videocall-rs
media streaming framework and teleconferencing system written in rust
videocall.rs is a Rust video conferencing and streaming framework that replaces the WebRTC stack with WebTransport (QUIC/HTTP3), forwarding media through a Rust server over NATS instead of doing peer-to-peer ICE/STUN/TURN negotiation. It targets three groups: devs building custom video apps on a Rust API, robotics/IoT people streaming from Pis and Jetsons via the CLI, and teams who want to self-host their own conferencing stack with Helm charts.
Genuinely simpler transport story than WebRTC — no ICE, STUN, TURN, or SDP offer/answer dance, just a QUIC handshake, which removes a whole category of NAT-traversal bugs. The media pipeline is pure Rust end to end (VP9 encode/decode, Opus via ropus instead of libopus/libvpx bindings), so you're not fighting C toolchain issues on cross-compiles. Test coverage is unusually serious for a project this size: a three-layer wasm-bindgen-test pyramid for the UI, actix-api integration tests against real Postgres/NATS (not mocked), and a Playwright E2E suite. The Nix-based native dev loop (process-compose, hot reload, zero Docker) is a real engineering investment, not just a README claim.
No Firefox support at all — that's not a rounding-error gap, it rules out a meaningful chunk of any general audience. Media is encrypted client-to-relay but not end-to-end; the relay sees decrypted frames, which the README is upfront about but is easy to miss if you skim past the FAQ. It's explicitly the youngest option next to LiveKit/Jitsi/mediasoup and it shows: no recording, no mature SFU ecosystem, no broad client integrations, and the project self-describes as Beta for 'non-critical workloads.' Meeting management (ownership, waiting rooms, host controls) is still gated behind a feature flag, so the parts you'd actually want for a real product are the least battle-tested.