Oryx (formerly SRS Stack) is an all-in-one, open-source video solution designed for creating online video services, including live streaming and WebRTC. It targets developers and businesses looking for a self-hostable or cloud-based platform with support for multiple streaming protocols and advanced features like transcoding and AI integration.

How It Works

Oryx is built on a robust stack including Go, React.js, SRS (Simple Realtime Server), FFmpeg, and Redis. It supports RTMP, WebRTC, HLS, HTTP-FLV, and SRT protocols, enabling flexible ingestion and playback. The architecture emphasizes ease of use with an HTTP Open API for management, automatic HTTPS, and integrations with OpenAI for AI-driven features.

Quick Start & Requirements

• Install/Run: docker run --restart always -d -it --name oryx -v $HOME/data:/data -p 80:2022 -p 443:2443 -p 1935:1935 -p 8000:8000/udp -p 10080:10080/udp ossrs/oryx:5
• Prerequisites: Docker. For WebRTC WHIP, avoid localhost; use a private/public IP or domain.
• Setup: Single Docker command. Data persistence requires volume mounting (-v $HOME/data:/data).
• Docs: Getting Started, Tutorials

Highlighted Details

• Supports RTMP, WebRTC, HLS, HTTP-FLV, and SRT protocols.
• Features include authentication, multi-platform streaming, recording, transcoding, virtual live events, and AI assistant integration.
• Offers automatic HTTPS via Let's Encrypt (LEGO).
• Provides an HTTP Open API for management and control.

Maintenance & Community

• Project is actively developed, with a focus on expanding features like GB28181 and WebRTC chat.
• Community support is available via Discord. Sponsorship options are offered for direct assistance.
• OpenCollective for sponsorship.

Licensing & Compatibility

• Licensed under the MIT license.
• Uses FFmpeg, Redis, and youtube-dl, which have their own licenses.
• Compatible with commercial use and closed-source linking due to the permissive MIT license.

Limitations & Caveats

The project is undergoing active development, with some features marked as planned or in progress. While the core streaming functionality is robust, advanced features like WebRTC face-to-face chat are still under development. The README notes that using localhost for WebRTC WHIP is not recommended.