Menu

How We Built Post-Quantum Encrypted Video Conferencing

DEV Community: encryption·H33.ai·6 months ago
#XQqkUNSe
#dev#strong#v100#article#video
Reading 0:00
15s threshold

Originally published at v100.ai

At V100 , we build AI video infrastructure entirely in Rust. 20 microservices. 0.01ms server processing. 220,000+ requests per second. Post-quantum encryption on every call.

This post is a deep dive into our architecture and the engineering decisions behind it.

Why Rust for Video Infrastructure?

Video infrastructure has unique constraints that make Rust the ideal choice:

Zero GC pauses — Real-time video processing can't tolerate garbage collection stops

Memory safety — Buffer overflows in media pipelines are a security nightmare

Performance — Our gateway processes requests in 10 microseconds, not 10 milliseconds

Small binaries — Our meeting signaling server is a 2MB binary serving WebRTC at scale

Our Stack

Component Technology

Web Framework Axum + Tokio

Database PostgreSQL + TimescaleDB

Cache Redis + Cachee (in-process)

Media FFmpeg (sidecar)

Crypto ML-KEM-768 + ML-DSA-65 (post-quantum)

Infra Docker + AWS ECS Fargate

The Numbers

20 Rust microservices —…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.