What Silo Server on Synology NAS Does for Your Media
Silo Server on a Synology NAS is a self‑hosted media streaming platform that serves movies, shows, music, and books from your NAS to your devices with support for direct play, remuxing, and hardware‑accelerated transcoding for efficient, flexible media delivery.
Think of Silo as a modern media server setup that lives entirely on your NAS. You point it at your media folders and it streams content at home or away, using a built‑in web client and admin interface. It can support multiple household profiles and parental controls, and it even offers Jellyfin/Emby‑compatible APIs so your existing apps can keep working alongside its own.
This guide is for you if you already use a Synology box as storage and want a more efficient media server that can use NAS hardware transcoding when the model supports it. The one big caveat: you need basic comfort with Docker and Portainer because deployment is driven by a Docker Compose stack.
Prerequisites and Hardware Transcoding Checks
Before you touch any configuration, you need to confirm that both your software and hardware are up to the job. Silo Server relies on Docker and Portainer for deployment, and hardware transcoding depends on whether your Synology NAS actually exposes the right GPU devices.
First, install Portainer and make sure you are on the latest version, or keep going if you already have it installed. You will use Portainer’s Stacks feature to paste and deploy the Silo Docker Compose configuration. In File Station, open the docker folder and plan to create a dedicated silo directory; this keeps all the Silo containers and data in one place.
Next, use the provided compatibility link to check if your Synology NAS model supports hardware transcoding. If your model does not appear on that list, you can still deploy Silo, but you should follow the non‑hardware‑transcoding Silo Server Synology setup instead. That distinction matters because the hardware‑accelerated Silo stack mounts GPU device nodes such as /dev/dri/renderD128 and /dev/dri/card0 specifically for NAS hardware transcoding.
Step‑by‑Step Silo Server Deployment with Hardware Transcoding
You only deploy Silo once, but the order you follow keeps you from breaking permissions or losing your media paths. The stack uses several containers—a database, Redis cache, search engine, and the Silo app itself—so treat the configuration as one atomic unit.
- Create folders: In File Station, open the docker folder and create a new folder named silo (all lowercase). Inside silo, create ten folders: catalog-seeds, compat, db, media, meilisearch, plugins, redis, rustfsdata, rustfslogs, and transcode (all lowercase).
- Prepare Portainer: Log into Portainer, click Home, then Live connect to your Synology environment. On the left sidebar, click Stacks, then + Add stack.
- Name the stack: In the Name field, type silo (lowercase) so Portainer manages the stack consistently with your folder structure.
- Paste the stack file: Copy the Silo stack (Docker Compose) configuration into the Web editor. The stack defines services for db, redis, meilisearch, and the silo application container.
- Edit core environment values: Before you deploy, change TZ to your time zone, change MEILI_MASTER_KEY to your own 42‑character secret, and update PUID/PGID to match your NAS user and group. Also set a unique SECRET_KEY value for Silo.
- Map media paths: In the volumes section for the Silo container, update the media path to point to your real media folder; for example, /volume1/docker/silo/media if that is where your content lives.
- Add hardware devices: In the hardware‑transcoding variant, ensure the silo service includes devices like /dev/dri/renderD128 and /dev/dri/card0 for Intel/AMD hardware transcoding.
- Deploy the stack: Scroll down and click Deploy the stack. Wait a few minutes for the images to download and containers to start; Portainer will display “Stack successfully deployed” when it is done.
- Log into Silo: When deployment completes, browse to the Silo port you exposed. If everything worked, you will first see the RustFS Login page, then the Silo dashboard once you sign in.
- Create your library: In the Silo interface, add a new library, give it a name, and set its folder to /mnt/media so Silo can index your content.
Two mistakes trip people up more than anything else: using uppercase letters for folder names and leaving the default secret values in place. The folder names must be lowercase to match the paths inside the stack, and the TZ, MEILI_MASTER_KEY, PUID, PGID, and SECRET_KEY values must be customized before you deploy. If you skip the media path update, Silo will start but it will not see any of your movies, so always double‑check the /volume1 path mapping.
What to Expect After Deployment and Why It’s Worth It
When the stack finishes and you load Silo for the first time, you will see the RustFS Login page, which confirms the backend file system and services are running. After signing in and adding your first library, the Silo dashboard gives you a clean overview of your media and server state—your “Silo dashboard at a glance”.
From there, Silo becomes your Synology media serving hub. It streams your movies, shows, music, and books through its web client and admin interface, with direct play, remuxing, and hardware‑accelerated transcoding working behind the scenes to adapt content to your devices. Because deployment is done through a single Docker Compose stack, updates and tweaks stay manageable once you have the initial configuration dialed in.
If you ever need to redeploy, keep a backup of your docker/silo folder and your customized stack file. The main thing to watch over time is that your secrets and PUID/PGID values stay consistent, and that any new media you add uses the same volume paths you configured during setup. When those pieces stay aligned, your personalized Silo Server will keep serving media reliably on your NAS for the long haul.
