Orpheum
A self-hosted media server for video, comparable to Plex or Jellyfin, shipping as a single Go binary deployed via Docker with a beta opening in about a month. It reaches a home server from anywhere with no port forwarding, VPN, or paywall (even behind carrier-grade NAT), supports casting to any logged-in device, and watch-together playback with synced video and voice chat that can be mixed with casting. Playback features include dialogue boost and loudness levelling per film, adaptive quality tuned for a home's upload bandwidth, and hardware transcoding with full quality in supported browsers. The library scanner explains its matches and flags guesses, and shows missing disks instead of silently vanishing titles. Data ownership is emphasized: the database is a rebuildable index, metadata corrections write back as NFO files readable by Kodi and Jellyfin, and automatic backups preserve non-derivable data (watch state, preferences, shares). Security is a primary concern: the network-facing core never opens media files or runs FFmpeg; a separate network-isolated media node handles file reads and transcodes over Unix sockets; FFmpeg is sandboxed with Landlock and seccomp; there is a small allowlisted dependency tree with pure Go and no cgo, secrets sealed at rest, optional read-only library mounting so a compromise cannot encrypt or delete media, and a cryptographically signed chain for servers and releases.
What it addresses
Existing media servers impose paywalls, bandwidth limiting, crippled behavior, and required logins, and remote access usually demands port forwarding, a VPN, or tools like Tailscale; meanwhile the increasing pace of hacks, CVEs, and AI-assisted intrusion makes security a primary concern.
Shared over time
Each entry reflects what was shared on that date. Details may have changed since then.
Orpheum
A self-hosted media server for video, comparable to Plex or Jellyfin, shipping as a single Go binary deployed via Docker with a beta opening in about a month. It reaches a home server from anywhere with no port forwarding, VPN, or paywall (even behind carrier-grade NAT), supports casting to any logged-in device, and watch-together playback with synced video and voice chat that can be mixed with casting. Playback features include dialogue boost and loudness levelling per film, adaptive quality tuned for a home's upload bandwidth, and hardware transcoding with full quality in supported browsers. The library scanner explains its matches and flags guesses, and shows missing disks instead of silently vanishing titles. Data ownership is emphasized: the database is a rebuildable index, metadata corrections write back as NFO files readable by Kodi and Jellyfin, and automatic backups preserve non-derivable data (watch state, preferences, shares). Security is a primary concern: the network-facing core never opens media files or runs FFmpeg; a separate network-isolated media node handles file reads and transcodes over Unix sockets; FFmpeg is sandboxed with Landlock and seccomp; there is a small allowlisted dependency tree with pure Go and no cgo, secrets sealed at rest, optional read-only library mounting so a compromise cannot encrypt or delete media, and a cryptographically signed chain for servers and releases.
Problem: Existing media servers impose paywalls, bandwidth limiting, crippled behavior, and required logins, and remote access usually demands port forwarding, a VPN, or tools like Tailscale; meanwhile the increasing pace of hacks, CVEs, and AI-assisted intrusion makes security a primary concern.
Posted by @kstenerud · Original comment ↗
“I'm building a self-hosted media server for video, like Plex or Jellyfin. I'll be opening the beta in about a month.”