Invidious

Why it's ranked here

Judge this one on operational reality, not on the feature list. It reads undocumented YouTube endpoints, so upstream changes break playback and the fix cycle never really ends, and stream loading has been split into a separate companion program that operators must run and key themselves. Against that, continuous integration builds across a long span of compiler releases plus a nightly, boots the container image and requests a page from it before passing. The maintainers also state in writing that contributor supply is thin because of the language choice. Strong for a private front end. Fragile as set and forget.

What's good

The operator surface is documented inline: each option carries accepted values, a default, and a note on when it becomes mandatory behind a reverse proxy. The container image creates a dedicated account and runs the binary as that unprivileged user under a small init process. Static linking is available, and the project can be compiled without the web interface for API-only deployments. Health checks gate startup order between the application and its database. The spec suite, a formatter check and a linter all run in continuous integration, and translation work happens on a hosted platform instead of in the repository.

Tradeoffs

The build is heavy. Player dependencies resolve at compile time behind a printed warning that it may take more than twenty minutes, and the container image compiles OpenSSL from source to work around a reported memory leak. Version strings are captured from git during compilation, so repository history has to be present in the build context. The test setup requires parsing helpers and data modules but not the routing layer, so route behaviour is not covered there. Crystal is a small ecosystem and the maintainers say most of the work lands on them. Operators also inherit legal exposure the project explicitly disclaims.

How to use it well

Best for someone who already runs a small Linux server and wants YouTube without the account graph: a home lab, a privacy-minded group, a classroom. Budget an afternoon for the database, the reverse proxy and the companion process, then expect to patch on upstream breakage rather than on your own schedule. The API is worth a look if you want to script feeds or embed video without third-party trackers. It does not download or archive video for you, it does not cover other platforms, and it will not make running a public instance legal where you live.

Observed

License

AGPL-3.0-only

Language

Crystal

Datastore

PostgreSQL

Interfaces

Self-hosted web front end plus a JSON HTTP API

Install surface

Build from source, Docker Compose, or use a third-party public instance

Runtime

Linux server; container image runs as a non-root user

Data source

YouTube internal endpoints, not the official YouTube API

Kubernetes

Helm chart maintained in a separate repository