mediamtx

bluenviron/mediamtx

Ready-to-use Media-over-QUIC / SRT / WebRTC / RTSP / RTMP / LL-HLS / MPEG-TS / RTP live media server and media proxy that allows to read, publish, proxy, record and playback real-time video and audio streams.

Ship status

Still shipping

Pushed in the last 30 days.

Last push
Oct 2, 2026
today
Ship score
99/100
How it is calculated →
Stars, last 7 weeks
Stars, weekly: 19,851 → 20,291 (Aug 18 – Sep 29, 2026)
+305 stars in the 28 days to 2026-09-29

Shipping: pushed in the last 30 days · slowed: quiet for 31–120 days · silent: no push in over 120 days.

Repo facts

What GitHub reports.

Stars
20.3K
Forks
2.4K
Open issues
199
Watchers
191
Primary language
Go
Created
Dec 28, 2019
Owner
bluenviron · Organization

Open issues are the issues and pull requests GitHub reports as open; watchers are the accounts subscribed to the repository. OSI-approved license — GitHub’s own license field, not legal advice. 99 startups in the directory ship primarily in Go.

Topics

#go#golang#hls#media-over-quic#media-server#moq#obs-studio#rtcp#rtmp#rtmp-proxy#rtmp-server#rtp#rtsp#rtsp-proxy#rtsp-relay#rtsp-server#srt#streaming#webrtc#webrtc-proxy

How it got here

What the classifier decided, and when.

Classified as an open-source startup by Jev, TypeSafe’s classifier, on Sep 22, 2026 — os_startup 74%, self-hostable 89%, hosted offering 45%. The classifier reads only the repository’s name, description and homepage; it can be wrong, and a probability under 0.5 puts a listing in the review queue rather than out of the directory.

Listed since the 2025-09 crawl. Answered by jev-1.13.0. How the classification works →

Embed your status

Put this badge on your README.

OSSEAN ship status: shipping — last push 2026-10-02This is the badge for bluenviron/mediamtx, as served from the URL below.
[![OSSEAN: shipping](https://ossean.com/badge/bluenviron/mediamtx.svg)](https://ossean.com/bluenviron/mediamtx)

Updates daily, from the last push GitHub saw.

Honest caveat: GitHub proxies README images through Camo and rewrites the anchor with rel=“nofollow”, so a README embed sends you referral traffic and brand, not link equity. The link is dofollow wherever you control the markup — your docs, your landing page, your blog. The snippet uses your frozen OSSEAN slug, so it survives a repo rename.