Kyoo vs Silo

Editor take

Choose Kyoo for a library with no folder structure and for numbered releases. Choose Silo for the Jellyfin and Emby clients you already use and for books.

Editor

Where they differ

Only what is true of one of them and not the other. Each app's weak spots are the other app's strengths.

Kyoo

Where Kyoo is stronger

  • No folder structure neededPoint it at a folder and bad naming counts as a bug; Silo asks for a Title (Year) folder for each film and S01E01 episodes.1
  • Tagged releases past 5.0Kyoo ships numbered releases and is past 5.0; Silo is pre-release, so its APIs and database migrations can change before 1.0.2

Silo

Where Silo is stronger

  • Jellyfin and Emby clientsSpeaks the Jellyfin and Emby API, so VidHub, Findroid and Infuse connect, though those apps play films and TV only; Kyoo has its own API.3
  • Books and manga in one libraryAudiobooks, ebooks and manga in one catalogue, beta and outside the 1.0 promise; Kyoo serves films, series and anime.4
  • Offline downloads in the appsDownloads for offline viewing in its iPhone, iPad and Android apps; Kyoo's offline downloads are not back in v5.5

Kyoo vs Silo: specs side by side

Every spec for both apps in one table, so you can check install options, hardware and client apps before you pick one.

Spec
PriceFreeFree
LicenceGPL-3.0AGPL-3.0
Media typesMovies, TVMovies, TV, Audiobooks, Books, Podcasts
TranscodingHardware (NVENC, QSV, VAAPI)Hardware (NVENC, QSV, VAAPI)
Watch statePer-user accountsPer-user accounts
Watch partyNoSynced playback (beta)
Remote accessSelf-managed (reverse proxy or VPN)Self-managed (reverse proxy or VPN)
Offline downloadsNo–
Live TVNoNo
Web UIYesYes
iOS–Yes
AndroidYesYes
Android TVYes–
DockerYesYes
Tech stackGoGo
Docker Containers7 (app + front, auth, api, scanner, transcoder, traefik, postgres)3 (app + PostgreSQL, Redis)
DatabasePostgresPostgreSQL
Architecturex86 + ARMx86 + ARM

Common questions

Sources: Kyoo docs and Silo docs.

Updated