Open-source project
streamaserver/streama avatar
streamaserver/streama

Streama: a Grails and AngularJS media server whose player has only been tested in Chrome

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

9,822 stars978 forksJavaScriptMIT

At a glance

What is it?
Streama is a self hosted streaming media server that puts a personal film library behind a Netflix shaped web interface. The interface is well specified, the server side is an older Grails 3 and SpringSecurity stack on Bower, and several features the README mentions are still written in the future tense.
Who is it for?
Streama fits a household or small group that owns the files already and wants a private web player with progress tracking, and it fits best if your library is named the way its two default regexes expect. It does not fit a household that needs subtitles, several quality levels per episode, or a player verified outside Chrome, because the README writes subtitles and switching between video files as later work and says the player has only really been tested in Chrome.
Can I use it commercially?
Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
Is it still maintained?
Yes. The repository last received commits 3 days ago.
What is it written in?
Mainly JavaScript, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 13, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • streamaserver/streama9,822 ★ · +3
Star history
Repository2026-09-222026-11-13
streamaserver/streama9.8k9.8k

3 Stars in the last 52 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

Grails 3 and SpringSecurity behind an AngularJS front end

Streama is a web application, not a desktop player, and the stack is named in the README's technical section. The server side is written on Grails 3, SpringSecurity handles login and user handling, every front end component is AngularJS, and the player itself is completely HTML5 based. The repository matches that description: `grails-app/`, `src/`, `build.gradle`, `gradle.properties` and the `gradlew` wrapper scripts at the root.

Two build details are worth knowing before you clone it. Front end dependencies are declared in `bower.json` with a `.bowerrc` beside it, which is a pre-modern JavaScript package manager, so a build of this repository is not a plain npm install. And because the primary language on the repository is JavaScript while the server is Grails, a language filter will point you at the front end and hide the part that does the work.

There is also a `design/` directory, a `docs/` directory, `CHANGELOG.md` for history, `SECURITY.md` for vulnerability reports and `LICENSE.md` for the MIT terms. A `docker/` directory sits at the repository root next to `.dockerignore`, and a `.travis.yml` carries the build badge.

The first run lands on the settings page and validates before it saves

Getting Started links to one page, https://docs.streama-project.com/getting-started/installing/, and Downloads points at the GitHub releases page for stable and beta versions. If you have issues getting started, the README invites you to chat on Discord.

What the README does document is what happens the first time the application starts: you are redirected straight to the settings page, where you enter three values. The upload directory for video files, your theMovieDb.org API key, and a base URL you can change if you want, which the README calls useful for remote hosting.

Each value is checked before it saves. The API key is validated against theMovieDb.org to confirm it is valid, and the upload directory is checked for read and write permissions. That validation is narrow on purpose: a directory that passes the permission check tells you Streama can write there, not that your filenames will later be recognised. Nothing in the settings screen checks naming conventions, which is the subject of the matcher further down.

Continue Watching advances only while a video is actually playing

The dashboard shows recently watched shows and movies with the point each one was reached, and a user can resume from there. The README is specific about how that progress is kept: the Continue Watching feature works by periodically updating the database, only while watching of course, with information about the currently watched video and how far it has been seen.

Two consequences follow from that design. Progress is written during playback rather than derived from a viewing history, so a video watched outside the Streama player, played locally, or finished after the last write never registers.

The second consequence bites on the catalogue side. If a movie or an episode does not contain any video files, it will not show up on the dashboard at all. Metadata created through the admin panel therefore does not equal browsable content, and a library that has been catalogued but not yet uploaded can look empty to every user while the admin panel shows it as complete.

The episode browser shows empty episodes, the dashboard does not

The two halves of the interface treat missing video differently.

The episode browser selects the current video file's season by default, shows which other episodes exist in that season and how many seasons there are. Its extra behaviour is that a user sees all the added episodes even when no video files have been added to them, greyed out. Progress through an incomplete season is visible to the person watching.

The admin panel works from the other end. It makes heavy use of the theMovieDatabase.org API, which auto-fills episodes, shows and movies with information and images, so the person adding content types a show name once and receives a season's worth of episode records. Video files then go in by drag and drop for each episode.

So an episode exists in the database as soon as theMovieDb fills it in, appears greyed out in the browser, and is invisible on the dashboard. For an operator this is the practical question with Streama: the admin panel tells you what the API knows, not what your disk holds, and the two disagree for every episode you have catalogued ahead of uploading.

The HTML5 player has only really been tested in Chrome

The player is heavily inspired by Netflix, and the README is direct about both its reach and its edges. For shows there is a next episode button and an episode and season browser, and for the basics there is volume control, play and pause, and fullscreen. Then the limits: the player is HTML5 based and has only really been tested in Chrome so far.

The same paragraph lists the two missing capabilities in the future tense. Adding subtitles is something the author will add later down the road, and so is switching between video files, for instance for different quality uploads. Neither is present in the shipped player.

The practical effect is a per-episode, single-file model. With no switch between video files, an episode is one file, so adaptive streaming across several uploads of the same episode is not something the interface exposes, and a server that transcodes to several renditions has no place to show them. The browser restriction compounds it: an untested player on Safari, Firefox or a phone browser is exactly the case a household hits first. If subtitles matter to your household, that decision is made here, before the library is uploaded.

Two regexes decide what Bulk-Create can match

Adding an existing library without uploading every file is the Local File feature. You define a local directory in settings, the README notes the author keeps one full of symlinks to mounted drives, and then you browse it from any movie or TV show, or use the bulk-create path. Customizing the matcher works, as the README puts it, like in Emby or Kodi: the pattern is yours to alter.

The two defaults are a year in brackets for films and a season and episode pair for episodes:

yml
streama:
  regex:
    movies: ^(?<Name>.*)[_.]\(\d{4}\).*
    shows: ^(?<Name>.+)[._]S(?<Season>\d{2})E(?<Episode>\d{2,3}).*

The consequences sit in those patterns. The show pattern wants S and E markers with a two digit season and a two or three digit episode, so S1E2 does not match and neither does an episode named with a single digit. The movie pattern wants a four digit year in parentheses, so a bare year without brackets does not match. Anything outside those shapes is either a regex you rewrite or a file Bulk-Create skips.

The customization lives in `application.yml` under `streama.regex.movies` and `streama.regex.shows`, and the repository root also contains a `CustomRegex.yml`, so the change is a file you edit rather than a setting in the interface.

Bulk-Create can invent a show that was never in the database

The bulk-create path exists because of a specific gap. The README attributes it to an issue, Batch Add Files #241, and the workflow it describes is: run the matcher, preview the result, then add a single matched file or add files in bulk.

One line in that section decides how you should approach a first run. The TV show does not have to be present in order for this to work; everything is created by the backend. Bulk-Create is therefore not a matching tool over an existing catalogue but a catalogue generator driven by filenames, which is the feature for someone who already owns a season of files and does not want to type in episodes.

It also means the preview step is the only checkpoint between your directory layout and your database. A regex that is too greedy under `Name` will create records with the wrong titles. Use the matcher preview on one directory before pointing it at a mount full of drives.

The local file browser has the smaller dependency worth remembering: it is reachable from any movie or TV show, but only after you have defined the local directory in the settings, so that value is a prerequisite rather than a preference.

Users are non-admins by default and playlists are still on the roadmap

The user model is deliberately small. Users are invited and managed in the admin panel, they are non-admins by default, a non-admin can only view videos and not create them, and an admin is made with the press of a button. Per-user profiles and playlists do not appear anywhere in the application section of the README; playlists are named as something the author plans to add.

That sets the ceiling on what Streama is today: a shared library with one visible kind of user.

Release history explains part of the shape. The repository is not archived, the last push was on 2026-10-26, and the latest release entries are v1.11.2 on 2026-10-26, v1.11.0 on 2026-01-02 and v1.10.6 on 2025-12-18. Licensing is MIT in `LICENSE.md`, and there is a live demo at https://streama.demo-version.net/ with the credentials demoUser and demoUser, reset every night, which is the cheapest way to see whether the current release still behaves as the README describes before you deploy one.

Editorial conclusion

Streama fits a household or small group that owns the files already and wants a private web player with progress tracking, and it fits best if your library is named the way its two default regexes expect. It does not fit a household that needs subtitles, several quality levels per episode, or a player verified outside Chrome, because the README writes subtitles and switching between video files as later work and says the player has only really been tested in Chrome. Verify before deploying: the settings validation only proves the API key and directory are readable and writable, not that your file names match the matcher, so run the matcher preview against one season first, and confirm on the docs page at https://docs.streama-project.com/getting-started/installing/ whether your platform is covered before you plan around it.

Frequently asked questions

What is Streama?

Streama is a self hosted streaming media server for a personal library of shows and movies, presented as what the README calls your own personal Netflix. It is web based, with the server side written on Grails 3, SpringSecurity for login and user handling, AngularJS for the front end, and an HTML5 player.

How do I install Streama?

Getting Started links to https://docs.streama-project.com/getting-started/installing/, and the Downloads section points at the GitHub releases page for stable and beta versions. A `docker/` directory sits at the repository root for anyone packaging it themselves.

Does Streama need a theMovieDb.org API key?

Yes. On the first run you are redirected to the settings page, where you enter an upload directory, your theMovieDb.org API key and, if you want, a different base URL. The application validates the key against theMovieDb.org and checks the directory for read and write permissions before saving.

Can Streama play subtitles or switch video quality?

Not yet, according to the README. It says a feature to add subtitles and switch between video files, for instance for different quality uploads, will be added later down the road, and that the HTML5 player has only really been tested in Chrome so far.

Can several people use Streama with different permissions?

Users can be invited and managed in the admin panel. By default they are non-admins, which means they can only view videos and not create them, and you can make them admins with the press of a button.

Official sources

  1. Issues
  2. License: MIT
  3. README
  4. Releases
  5. streamaserver/streama on GitHub
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/streamaserver-streama.svg)](https://hysenlabs.com/projects/streamaserver-streama)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/streamaserver-streama.svg)](https://hysenlabs.com/projects/streamaserver-streama)

Was this useful?