Silo-Server / silo-server

Silo 
 A self-hosted media server for films, series, audiobooks, ebooks, podcasts, and manga.
 Quick start 
 · Documentation 
 · Builds & releases 
 · Discord 
 · Support Silo 
 · Contributing 
---
> [!WARNING]
> Silo is pre-release. APIs, configuration, and database migrations may change
> before the first stable release. Back up your deployment before updating.
## 1.0 release scope
The 1.0 milestone covers movies and
series. Audiobooks, ebooks, and Audiobookshelf compatibility keep working as
they do today and are labeled **beta**: they are outside the 1.0 support
promise and will be replaced by a consolidated Books effort with no assigned
release date. The broader capabilities below include those beta
implementations, not a promise that every media type is supported in 1.0.
Existing library data is preserved when upgrading.
## What Silo does
 Play 
 Direct play when possible, remux when needed, transcode otherwise, with
 VA-API, Quick Sync, and NVENC hardware acceleration.
 Organize 
 One catalog for films, series, audiobooks, ebooks, podcasts, and manga,
 matched through metadata plugins such as TMDB and TVDB.
 Connect 
 Use the included web app, or the Jellyfin/Emby-compatible API with clients
 such as VidHub ,
 Findroid , and
 Infuse . Client coverage varies.
 Share 
 Household profiles with their own watch state, library access, and
 parental controls.
 Manage 
 Libraries, users, providers, storage, search, and playback are configured
 in the admin interface, not in config files.
 Scale 
 Start with one integrated server; split proxy and transcode roles across
 shared PostgreSQL and Redis when you need to.
## Quick start
Requires Docker Compose 2.24 or newer. The default stack runs Silo, PostgreSQL
with pgvector, and Redis.
 [code] 
Set `MEDIA_ROOT` in `.env` to the absolute path of your media, then:
 [code] 
Open and complete onboarding.
The user manual covers the rest, starting with
installation: backing up `SECRET_KEY`,
storage, GPU acceleration, Meilisearch, external PostgreSQL and Redis,
transcode nodes, PostgreSQL tuning, backups, and updates.
## Builds and releases
Until the first release, default-branch images carry an ordered `build-N` tag
and a short commit SHA alongside `latest`. Build numbers order published images;
they are not release versions. Release versioning
defines each tag and the SemVer contract.
## Documentation
- User manual — installing, configuring, and running Silo
- Development guide — source setup, builds, tests, migrations
- Settings API, Downloads API, and Apple Push Display Token — client contracts
## Community and contributions
Questions and discussion: Discord.
Bugs, install problems, and performance issues: the
GitHub issue forms,
which ask for reproduction steps and raw logs.
Native clients are developed in
`silo-apple` and
`silo-android`. Client-visible
API, authentication, playback, or metadata changes should consider both.
Right now, the most helpful way to contribute is a clear, accurate issue. We
im