Does Invidious use the YouTube API?
No. It reads YouTube's public pages itself instead of calling the official API, which is also why a YouTube change can break playback until you update the container.
Browse YouTube without ads or tracking through a front-end you host. Subscriptions, playlists and watch history live in your own database, and the player works with JavaScript turned off.
The key facts for Invidious.
| Requirement | Invidious |
|---|---|
| Price | Free |
| Licence | AGPL-3.0 |
| Web UI | Yes |
| Minimum hardware | 2 GB RAM · 20 GB |
| Docker Containers | 3 (app + Invidious companion, Postgres) |
| Database | Postgres |
| Architecture | x86 + ARM |
| Tech stack | Crystal |
| Docker | Yes |
| Linux package | Yes |
No. It reads YouTube's public pages itself instead of calling the official API, which is also why a YouTube change can break playback until you update the container.
Yes. The docs ask for a restart at least once a day, hourly if you can, because memory use and YouTube's handling of long-lived sessions degrade over time. A restart policy or a cron job covers it.
Yes. Import subscriptions from YouTube, NewPipe or FreeTube and export them again whenever you like. They are kept in your own Postgres database rather than a Google account.
Put a single login and a second factor in front of your self-hosted apps: your reverse proxy asks Authelia whether each request is allowed. Rules match by domain, user, group or network, and the portal handles passwords, WebAuthn keys and TOTP.
One login in front of every app you host, from an identity provider that speaks OIDC, SAML, LDAP and proxy auth. One account and a second factor then open Jellyfin, Nextcloud and the rest of the stack.
Scan files on your server for viruses, trojans and other malware with an antivirus daemon, while freshclam keeps the signature database current. A mail gateway can feed it mail to scan, and a file server can run clamscan on the host. Once its socket is shared, other services on the box can call clamd too.
Put one login in front of a dashboard of your self-hosted apps, and show each person only the tiles they should see. Accounts come from local users, LDAP, OIDC or your reverse proxy. New containers found in Docker, Traefik, Nginx or Unraid wait in a list for you to publish.
Apps such as Nextcloud, Jellyfin and Grafana authenticate against LDAP, and LLDAP gives them a small directory server with a web page for users, groups and passwords. The data sits in SQLite unless you point it at PostgreSQL or MariaDB, and Authelia or authentik can use it as the user source.
One passkey can sign you into the apps you connect through OpenID Connect, with Pocket ID as the provider behind the login. Each app sends its users to it, and it returns a token once the passkey checks out and any group restriction is met.
Run a private metasearch instance on your own server that pulls results from many search services.
Tinyauth puts one login screen in front of the apps on your network. It checks the session for Traefik, Caddy or Nginx and signs people in from users you define, an LDAP server or an OAuth provider, and it also serves OpenID Connect for apps that support it.