NymphCast — Self-Hosted, Open-Source

Turn your choice of Linux-capable hardware into an audio and video source for a television or powered speakers

License: BSD-3-Clause. Built with: C, C++, Shell, Objective-C, M4, Makefile, Python, Java, Assembly, Ragel, CMake, Perl, Meson, DIGITAL Command Language, Inno Setup, CSS, Rust, Batchfile, AngelScript, HTML, QMake, Roff, Awk, NSIS, Metal, QML, JavaScript. Website: http://nyanko.ws/nymphcast.php. Source: https://github.com/MayaPosch/NymphCast.

Installation

-h --help Get this help message. -c --configuration Path to the configuration file. -a --apps Path to the NymphCast apps folder. -w --wallpaper Path to the wallpapers folder. -r --resources Path to the GUI resources folder. -v --version Output NymphCast server version and exit.

Why self-host NymphCast

Self-hosting gives you three things SaaS can’t: data ownership (the files live on disks you control), cost predictability (a one-time setup vs. recurring per-seat fees that grow with your household or team), and longevity (open-source means the app keeps working even if the maintainers move on, since you can pin a working version). The trade-off is that you take on the operational work of running a server, applying updates, and handling backups.

Hardware notes

Memory requirements depend on the NymphCast Server configuration: by default the ffmpeg library uses an internal 32 kB buffer, and the server itself a 20 MB buffer. The latter can be configured using the (required) configuration INI file, allowing it to be tweaked to fit the use case.

Where to go from here

Last verified: 2026-04-21