gwuhaolin/livego

live video streaming server in golang

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 60 minutes ago
Added to GitGenius on September 6th, 2026
Created on May 28th, 2017
Open Issues & Pull Requests: 139 (+0)
GitHub issues: Enabled
Number of forks: 2,013
Total Stargazers: 10,182 (-1)
Total Subscribers: 224 (+0)

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Issue API getrepoissuespagesummary failed: 429 Rate limit exceeded. Please try again later.

Detailed Description

Livego is a live video streaming server written in Go.

The tool addresses the need for a straightforward, performant streaming infrastructure by implementing a server that accepts incoming video streams and distributes them to multiple viewers. It works by receiving video pushed via RTMP protocol, transcoding or relaying the stream through supported formats, and making the content available for playback across multiple protocols and delivery methods.

Livego suits projects requiring a self-hosted streaming solution with minimal operational complexity. It works well for scenarios where you control both the broadcast source and viewing infrastructure, such as internal streaming applications, event broadcasting, or development environments. The tool's pure Go implementation means it compiles to a single binary deployable across platforms without external dependencies, and Docker support enables containerized deployment. Installation is straightforward: download a precompiled binary, run it, obtain a channel key via HTTP, push video to an RTMP endpoint, and consume the stream via RTMP, HTTP-FLV, or HLS playback URLs. The server supports HTTPS for HLS delivery by placing SSL certificates alongside the executable and toggling a configuration option.

Development activity shows consistent maintenance with regular updates addressing bug fixes and feature improvements. The project demonstrates active engagement with user issues and pull requests, indicating responsiveness to community feedback. Code contributions are accepted and reviewed, suggesting an open approach to external participation. The codebase maintains focus on core streaming functionality without scope creep into tangential features.