In the first quarter of 2023, Ant Media ran a Real-Time Streaming Hackathon. Seventy-six participants registered, including established startups, contributors to Ant Media Server itself, and developers from the wider open-source streaming community.
RTC LEAGUE entered as team RTC Mavericks. We took first place.
The project was an OBS extension that brought Ant Media WebRTC into a workflow that had never supported it properly. It is listed on the Ant Media Marketplace as RTC Studio, and this is the account of what it does and why it mattered enough to win.
The Problem We Entered to Solve
OBS Studio is the default broadcasting tool for an enormous share of the people who stream anything. It is open source, it is capable, and it is everywhere.
It is also built around RTMP, a protocol released in the early 2000s. RTMP is reliable and widely supported, and it carries latency measured in seconds rather than milliseconds. For a broadcaster pushing content one direction to an audience that will never respond, seconds are acceptable. Nobody notices a delay in a conversation that is not happening.
The moment interaction enters the picture, that calculation breaks down entirely.
A live auction where bids arrive seconds after the item is called is not a functioning auction. A telehealth consultation with a visible lag between question and answer feels broken to the patient. A live shopping stream where the host responds to comments several seconds late loses the immediacy that makes the format work at all.
WebRTC solves this. It was designed for real-time, bidirectional communication, and it operates in a latency range that preserves the feeling of a live exchange. But WebRTC and OBS did not meet. Broadcasters who wanted OBS, with its scenes, its sources, and its production capability, were giving up real-time latency to get it. That gap is what we built into.
What We Built
The extension connects OBS directly to Ant Media Server over WebRTC, replacing the RTMP path rather than sitting alongside it.
Ant Media’s own marketplace listing describes the result as ultra-low latency of 20ms peer-to-peer streaming, with high-quality media server streaming at scale. That figure is their published measurement of the integration, not a projection from us.
The practical consequence is that a broadcaster keeps everything OBS gives them and stops paying the RTMP latency cost. The production setup does not change. The protocol underneath it does.
It was submitted under the name OBS WebRTC Castify. If you encountered the project under that name, or simply as OBS Castify, RTC Studio is the same work under the name it carries in the Ant Media Marketplace today.
What Ant Media Said
Announcing the result, Ant Media credited the extension with unlocking the full potential of streaming, delivering what they described as unparalleled 20ms P2P latency and smooth, high-quality media server streaming at scale using Ant Media Server with OBS.
Their public comment on the judging singled out two things: the innovation of the solution itself, and the breadth of business use cases it opened up.
That second point is worth sitting with, because it says something about what the judges were actually weighing. A hackathon can reward technical cleverness that has nowhere to go. The feedback here pointed at the opposite, that the work mattered because of how many real situations it applied to.
The Full Results
Place | Team | Participants |
First | RTC Mavericks | |
Second | Twiddle | Richárd Ádám Dr. Vécsey, Axel Ország-Krisz Dr. |
Third | Growcify | Meghraj S. |
Seventy-six registrations across startups, Ant Media Server contributors, and the open-source community. Ant Media described the competition as fierce, and the field supports that reading.
From Hackathon Entry to Marketplace Product
Winning a hackathon and shipping a product are different achievements, and most hackathon projects never make the crossing.
RTC Studio did. It is now listed in the Ant Media Marketplace with installation documentation, a support path, and a demo request route. The requirements are straightforward: an active Ant Media Server license, the RTC Studio client on a PC or Mac, and your Ant Media WebSocket URI and Stream ID.
Setup runs through OBS itself. Open the settings panel, select Stream, enter the WebSocket URI and Stream ID in the corresponding fields, and select h264 from the video codec dropdown for optimal compatibility. Configure your microphone and camera as normal, then start streaming. The output arrives on your Ant Media Server or on a custom player built against the Ant Media API.
The gap between a demo that impresses judges and software someone else can install and depend on is substantial. Closing it is the part that does not fit into a hackathon weekend.
What This Tells You About How We Work
We write a lot about real-time infrastructure on this blog, and most of it concerns latency. Where it accumulates, how to measure it stage by stage, and why a faster language model rarely fixes a slow pipeline.
This project is where that preoccupation came from. The entire value of the extension sits in a latency difference, and nothing about the user-facing experience changes except how quickly things arrive. That is usually what real-time engineering amounts to: not new capability, but the same capability arriving fast enough to be useful.
It also reflects how we tend to approach problems. The extension did not replace OBS or ask anyone to adopt an unfamiliar tool. It changed the transport underneath a workflow people already had, which is a smaller intervention than it first appears and generally the one that gets adopted.
Our CTO, built the winning entry, also holds the top ranking on the LiveKit Global Community Leaderboard. The through line between the two is the same: real-time media transport, done at the protocol level rather than the application level.
Where to Find RTC LEAGUE
RTC LEAGUE is listed on the Ant Media Marketplace, with full installation steps, requirements, and a demo request path.
If you are evaluating real-time streaming architecture more broadly, or working on something where latency is the constraint rather than a detail, our WebRTC development practice covers that work directly.






