Website: openmoq.org GitHub: openmoq

Overview

An industry consortium advancing MOQ-based technology through high-performance, open-source software. Mission: deliver practical implementations that enable the next generation of media transport.

Members

Charter Members

  • Akamai
  • CDN77
  • Cisco
  • RED5
  • Synamedia
  • YouTube

Standard Members

  • Ateme
  • Bitmovin
  • Nano Cosmos
  • Qualabs
  • Vindral
  • Wowza

Academic Members

  • University of Klagenfurt
  • Özyeğin University

Repositories

openmoq/moxygen (moqx)

  • GitHub: openmoq/moxygen
  • Fork of Meta’s moxygen relay, serving as the buffer repo for the planned moqx server/relay
  • C++
  • Default version set advertises draft 14/16 as a stable “floor relay” (draft-18 excluded by policy); the codebase also carries draft-18 message handling and a qmux listener. See Recent Highlights and Interop.

openmoq/moq-relay-test

mondain/moqxr

  • GitHub: mondain/moqxr
  • Origin Publisher, Contribution, and Ingest CLI for OpenMOQ (C++), maintained by Paul Gregoire (mondain)
  • draft-18 support shipped May 16–18, 2026 — the third open-source implementation to ship draft-18, after moq and imquic
  • Capabilities added since: a live-object publish API, an optional MSF media timeline track, an SRT MPEG-TS ingest path (fMP4 repackaging → MoQ objects), and a prebuilt static-library SDK (picoquic/picotls bundled) consumed by mondain/moq2ts
  • Latest release: v0.2.1 (Apr 17, 2026) — draft-16 interop fixes (release tag predates the draft-18 work); v0.2.0 (Apr 15) added a draft-16 SUBSCRIBE KVP parser, dropped the WebTransport subprotocol for draft-14, and made control-message handling non-blocking

red5pro/moq-playa (planned)

  • Player component for OpenMOQ
  • Not yet publicly available (as of 2026-04-10)

Goals

  • Distribute development costs across organizations
  • Accelerate MOQ through collective expertise
  • Ensure interoperability via standardized implementations
  • Lower market barriers for new use cases beyond media (financial feeds, gaming, IoT, AR/VR)

Development Status

Core infrastructure development is ongoing. The consortium has completed industry alignment, established a technical roadmap, and finalized legal structure and governance.

Recent Highlights

Day-by-day PR/issue history lives in the wiki log; this section keeps only durable milestones.

  • Alan Frindell’s OpenMOQ consulting arrangement disclosed (July 20, 2026) — in an IETF “Change in employment disclosure” to the MoQ list, Alan Frindell noted he has moved from full-time to part-time at Meta (Meta still sponsors his IETF participation, which remains on Meta’s behalf), and in his non-Meta hours now runs a consulting business contracted with OpenMOQ to build open-source software — specifically the moqx relay. This formalizes the sponsorship behind the moqx work he has driven on the fork, and gives OpenMOQ a named, funded relay project.
  • Multi-threaded relay scalingAlan Frindell (afrind, Meta) drove a sustained effort (late May–June) making moqx deployable with threads > 1: a cBPF reuseport worker-steering filter, recvmmsg batch receives, per-thread local forwarders, and a relay_thread config knob, plus follow-on lock-free-mode relay-correctness hardening.
  • CAT-token authenticationPaul Mondain’s PR #264 (merged June 3, the largest single moqx merge) added opt-in CAT-style token auth/authorization for MOQT relay services, verifying signed CWT/HMAC exp/moqt/moqt-reval claims; afrind then refactored it into per-session auth filters, and a CAT4MOQ / C4M issuer utility followed.
  • Floor-relay version policy — moxygen (moqx) deliberately defaults to advertising draft 14/16 and excludes draft-18 (June 16–17), staying a stable floor relay while moq-rs-draft-18 carries the at-target draft-18 interop cells. A known hazard (Issue #472) is that the default version order can cap negotiation at 16 even when 18 is mutually supported.
  • London hackathon (June 9) — afrind brought the relay up as a public draft-18 endpoint and shipped moq_decode.py, a standalone draft-18 wire decoder for interop debugging, entering London with CAT-token auth, auto-regression CI, and the multi-thread stack in place.
  • draft-18 codebase capabilities — although the default relay stays on 14/16, the codebase gained draft-18 message handling (akash-a-n’s SUBSCRIBE_TRACKS port, PR #411) and a qmux listener (PR #420), the latter landing the same day moq added its own qmux listener.
  • Observability + deployment hardening (July) — afrind added a self-contained live Prometheus metrics dashboard and perf-test client metrics; gmarzot added in-memory PKCS#12 TLS bundle support (PR #460), a no-sudo onboarding quickstart, and native Debian/Ubuntu build support.
  • Contributor footprint — Tim Evens (Cisco) joined on the build system (CPM dependency migration, Debian + macOS toolchain fixes), widening Cisco’s MoQ footprint; most moqx churn is afrind’s, with gmarzot, akash-a-n, peterchave, and mondain also contributing. Meta’s moxygen upstream stayed comparatively sparse as this work landed on the fork.
  • Governance incident resolved — an April OpenMOQ dispute involving Mike English and Giovanni Marzot (a “suspicious AI PR” on the interop runner) was resolved May 18, with Marzot returning as an active contributor.

Interop

  • openmoq/moxygen (moqx) in the interop-runner since Apr 2026 — strong results as a relay: moq-dev-js ↔ moqx 6/6, moq-rs-draft-16 ↔ moqx 5–6/6, moq-rs ↔ moqx all pass.
  • moxygen relay endpoint at fb.mvfst.net:9448 on versions 14/16/18 — the first publicly-announced draft-18 relay endpoint (brought up June 9); see interop-endpoints.
  • First cross-impl draft-18 interop attempt: mondain/moqxr ↔ imquic (May 19–20) surfaced a bidi-vs-uni SETUP-stream divergence, fixed within ~10 hours.

Related