streamaserver/streama

Self hosted streaming media server. https://docs.streama-project.com/

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 44 minutes ago
Added to GitGenius on September 6th, 2026
Created on July 29th, 2015
Open Issues & Pull Requests: 352 (+0)
GitHub issues: Enabled
Number of forks: 977
Total Stargazers: 9,823 (+0)
Total Subscribers: 293 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 28.1 hours
Mean response time: 343.2 days
90th percentile: 2230.0 days
Tracked items: 15

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 8
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 820 days
Stale 30+ days: 8
Stale 90+ days: 8

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • Enhancement (1)
  • More Info required (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Streama is a self-hosted streaming media server that lets you run your own video platform without relying on external services.

The tool solves the problem of centralizing personal or organizational video collections by providing a server you control entirely. It handles media ingestion, organization, and delivery to clients, allowing you to stream video content across devices on your own infrastructure. The approach centers on giving users full ownership of their media library and viewing experience rather than depending on third-party platforms.

Streama suits anyone wanting to host video content privately—whether for personal media libraries, small organizations, or scenarios where data sovereignty matters. It works well for setups where you have server capacity available and prefer managing your own deployment. The project is appropriate when you need basic streaming functionality without the complexity of enterprise media platforms, though you should evaluate whether the feature set and maintenance burden align with your specific requirements.

The project shows consistent maintenance with regular updates addressing bugs and compatibility issues. Development activity demonstrates responsiveness to user-reported problems, with fixes being merged into the codebase. The codebase receives ongoing refinement to keep dependencies current and resolve issues that emerge from real-world usage. Contributors engage with issues raised by users, indicating an active feedback loop between the maintainers and the community relying on the tool.