NimRTC
Latest release: v1.0.2 (Stable) — patch release fixing the WebTransport ALPN mismatch and the oversized Windows bundle, and shipping the signing public key with the release (v1.0.1 remains published and unchanged; the v1.0.0 tag is retained as source milestone only and was never published as a GitHub Release). Public API frozen per ADR-015; NIMRTC_API_VERSION = 10002, NIMRTC_API_VERSION_PRE_RELEASE = "". Chrome ↔ NimRTC data exchange (DC-1) via the Chrome WebTransport JS API (new WebTransport(url), not RTCPeerConnection.createDataChannel()) over QUIC PASS E1–E6 via tests/chrome_interop_harness/run_webtransport_harness.py + interop/chrome/test_chrome_webtransport.html against examples/demo-wtserver (datagram + bidi-stream echo). EngineConfig::datachannel_backend defaults to "web_transport"; the "sctp" backend was retired from the public selectors in v1.2.0 (it was an in-process loopback socket that could never reach a peer). See CHANGELOG.md ## [1.0.2] and docs/plan/v1.0-plan.md §3 + §12.3.6.
Current main (post-v1.0.2, unreleased): the trunk is ahead of the published tag by the
v1.1 release, which consolidates the former v1.1 / v1.2 / v1.3 drafts into one
version target: the packaging + benchmark track, the transport / media / DTLS hardening
track, and the quality-line items (shared adaptive jitter strategy, src/modules/jb_strategy;
a simplified Goog-CC-style BWE — delay + loss hybrid estimation, not a full
trendline port; RTCP feedback loop; engine-level ref_frame and video stats; GMSSL vendoring
as a submodule + the SRTP backend seam; engine source split).
Local suite on Windows/MSVC Debug: 651/651 PASS (measured 2026-11-04).
The packaging rules (NIMRTC_INSTALL=ON → include/ + lib/ + lib/cmake/NimRTC/) are landed
on main and will ship in the next release; the published v1.0.2 bundle does not contain
them yet. See Current progress and
Roadmap for the full picture.
🌐 Other languages: Simplified Chinese · Try the live demo: nimrtc.github.io/nimrtc/wasm
A native C++ WebRTC alternative — embeddable, scene-assembled, swappable backends.
One source tree ships a P2P client, a relay gateway, and runs on embedded Linux aarch64.
DTLS / RTP / 3A codecs are all pluggable; the DTLS crypto path can swap to GMSSL for GM/T-regulated
deployments without forking the trunk.
Note on terminology: the gateway shipped by this source tree is the
relay profile — single-strategy forwarding with compile-time L2 codec
skip, per docs/zh/architecture.md §7.1. A from-scratch SFU module is
not a deliverable: the §7 pre-1.0 decision window for SFU-1 / DC-3 /
BENCH-1 closed as NO (BDFL, 2026-10-19 — SFU is not a project core goal;
see docs/plan/v1.0-plan.md §7 + §12.5). The profiles/sfu.json and
profiles/sfu-agent.json files remain in the tree as unregistered JSON —
they carry the sfu_enabled marker and the sfu-relay transport
strategy, but there is no kProfileSfu constant and they are not part of
the shipped Profile set.
Why NimRTC? · Who is it for · Quick Start · Hello, World · Architecture · Benchmarks · Roadmap · FAQ
Why now?
WebRTC moved on, but the dominant implementation didn't.
- libwebrtc is the de-facto engine, but its build is multi-GB, its crypto and codecs are black-box, and the codebase is monolithic. Embedding it on aarch64 or auditing it against GM/T regulations is an exercise in pain.
- AI Agents / teleop / embodied-AI robotics need things libwebrtc doesn't expose cleanly — a pre/post-3A PCM tap, intra-scheduler strict-priority ordering (DC-2, see
sched.hpp Scope note; not a wire-level cross-connection guarantee under the default web_transport backend), and a capture-to-decision frame-time API.
- Xinchuang / regulated environments need a swap-in path to GM/T cryptography, not a fork.
NimRTC is a from-scratch C++20 implementation that keeps the wire-level interop you need (verified against Chrome: Case D media over DTLS-SRTP, Case E data over the Chrome WebTransport JS API) and replaces the opaque monolith with a compile-time layered, plugin-adapted engine you can read, swap, and ship on aarch64.
여기까지가 README 앞부분입니다. 나머지는 원문에서 읽을 수 있습니다. README 전문 보기 ↗
