RUSEON Core vs go2rtc
go2rtc by AlexxIT is a fantastic, lightweight streaming gateway designed primarily for the Home Assistant ecosystem and personal smart homes. It excels at WebRTC streaming, HomeKit integration, and camera dashboard widgets.
RUSEON Core takes low-latency WebRTC streaming to an enterprise-grade, high-density infrastructure level with native crash-resilient multi-camera archival, lock-free concurrency, and hardware failure isolation.
🏗 Key Comparison Points
1. High-Density Scaling (100+ Streams)
- go2rtc: Perfect for 5–20 smart home cameras on Raspberry Pi or mini-PCs. As stream counts scale past 40–50 cameras, memory pressure and channel queue contention can cause stream stuttering and frame drops.
- RUSEON Core: Engineered specifically for 100+ concurrent RTSP camera inputs and ~7,000 requests/sec. Uses pre-allocated lock-free RingBuffers and non-blocking channel drop semantics (
select + default) to guarantee 0 dropped frames.
2. Built-in Long-Term Storage & Archiving
- go2rtc: Focuses almost exclusively on live stream multiplexing and proxying. Archiving requires third-party tools (like Frigate, Home Assistant recorder, or external FFmpeg scripts).
- RUSEON Core: Features an enterprise-ready fMP4 Smart Recorder built into the core engine. Automatically writes fragmented MP4 chunks, evicts page cache via
POSIX_FADV_DONTNEED, and provides instant web timeshift without storing duplicate HLS segments on disk.
3. Failure Domain & Slow Consumer Isolation
- go2rtc: If a client connection or recording backend experiences severe latency, internal buffers can fill up, occasionally affecting other active consumers.
- RUSEON Core: Every consumer (WebRTC viewer, HLS muxer, disk recorder) is strictly isolated. If a hard disk or network storage freezes during write, the recorder drops frames on its own channel while all live WebRTC viewers continue streaming with sub-50ms latency.
⚡ Feature Comparison
| Feature | RUSEON Core | go2rtc |
|---|---|---|
| Primary Focus | High-Density CCTV & Video Infrastructure | Smart Home & Home Assistant Gateway |
| Throughput Benchmark | 100 Cams / 7,000 RPS / p95 1.7ms | ~20-50 Cams |
| Built-in fMP4 Archiver | ✅ Native with Direct I/O | ❌ External recorder needed |
| WebRTC Protocol | WHEP & DataChannels (Pion v4) | WebRTC, MSE, HomeKit |
| Database | Embedded BadgerDB (LSM-tree) | Config file / Memory |
| Multi-Camera Web UI | ✅ React 19 Glassmorphism Dashboard | Minimalist HTML status page |
🚀 When to Use Which?
- Use go2rtc if: You are running Home Assistant for your home with 4–10 cameras and need two-way audio or HomeKit integrations.
- Use RUSEON Core if: You are building commercial CCTV surveillance, Safe City deployments, industrial facilities, or multi-tenant video backends requiring 24/7 rock-solid storage, high RPS, and zero memory leaks.