← Directory

Silo

Silo is a self-hosted media server for your films and series, with audiobooks and ebooks available in beta.

  • Media Applications
  • Media Servers
  • Tools & Utilities
Silo is a self-hosted media server for your films and series, with audiobooks and ebooks available in beta. Point it at your media folders and stream to your devices at home or away, with direct play, remuxing and hardware-accelerated transcoding handled automatically. A full-featured web client and admin interface ship with the server, and an optional Jellyfin/Emby-compatible API lets you keep using clients you already own, such as Infuse, VidHub and Findroid. Household profiles give each member their own watch state and parental controls, while metadata is matched through installable plugins including TMDB and TVDB. Silo is pre-release, so APIs, configuration and database migrations may change before 1.0 - back up your deployment before updating.

    Platform availability

    Available on 2 of 9 platforms

    • Unraid
    • TrueNAS (not listed)
    • Umbrel (not listed)
    • ZimaOS (not listed)
    • Proxmox
    • Helm (not listed)
    • Mac (not listed)
    • Windows (not listed)
    • Linux (not listed)

    Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

    73/100 Good

    Maintained
    100last commit 7 days ago
    Popular
    54517 GitHub stars
    Easy to install
    452 install platforms, install notes, Docker image
    Light to run
    701 GB minimum RAM

    Availability: platform listings confirmed today, links checked 16 days ago

    GitHub stars
    517
    Open issues
    475
    Last commit
    2026-10-06
    License
    AGPL-3.0
    Activity
    rising

    Checked 7 days ago - source: GitHub (Silo-Server/silo-server)

    Resources & Compatibility

    Minimum requirements: 1 GB RAM, 500 MB disk.

    Checked 15 days ago - source: Docker Hub image tags and published docs

    First-install notes

    • Add an agent profile before starting tasks Before you ask Silo to start a task using an agent, open Settings → Agents and create at least one profile (a saved agent configuration). Without one, Silo may say there are no agent profiles and stop before the task starts. source
    • Install extensions by published ID If you want an add-on, open a terminal and run silo install <extension id>, replacing the brackets with the published ID (a short name that identifies the extension). Use silo uninstall <extension id> to remove it later, so you don’t have to delete files by hand. source
    • Install a local extension from a folder For a local extension folder, make sure it includes the ready-to-run file called dist/index.js, then use Settings → Extensions → Install from folder… . If that file is missing or the folder is wrong, Silo won’t be able to load the extension. source
    • Database and cache requirements Silo needs a PostgreSQL 18 database with the pgvector extension and Redis 6.2 or newer. Install the Silo-PostgreSQL template from the repository, then install any generic Redis container from Community Applications (or use an existing Redis service), and set DATABASE_URL and REDIS_URL to point at them. source

    Fetched 7 days ago - each note links to its source

    Alternatives

    No alternatives collected yet.

    Common questions

    Can I keep using existing media clients with Silo?

    It provides an optional Jellyfin/Emby-compatible API, so clients such as Infuse, VidHub, and Findroid can be used.

    What playback processing does Silo handle automatically?

    It supports direct play, remuxing, and hardware-accelerated transcoding.

    Where does Silo store its durable state?

    Postgres is used for durable state, while Redis is used for coordination and caching.

    What should I collect when reporting an install, playback, or performance issue?

    The troubleshooting documentation explains what to collect for install, playback, or performance reports.

    Answers sourced from github.com, siloserver.org, zackreed.me

    Community

    Collected 15 days ago - public community threads