The Scoreboard
Philosophy, license, contributing guide, and the FAQ — all the numbers behind the run.
Why We Built It
Phlix is MPL-2.0 (server and Hub) and MIT (clients, plugins, and shared libraries). The server, the clients, the plugin API, the Hub relay — all open. No hidden paid tiers, no feature-gated licenses, no "contact sales" for basic functionality. The community has the keys.
No account required. No telemetry. No phone-home. Your media habits stay on your hardware. Hub is opt-in and uses end-to-end encryption — even we cannot see your library.
Every millisecond matters. Hardware transcoding, intelligent pre-loading, and lazy metadata fetching are not optimizations — they are core promises. Your media server should never be the bottleneck.
Phlix does not chase trends. We build for the person who sets up a server once and expects it to run for five years. Stability over features, quality over quantity, simplicity over power.
Legal
Mozilla Public License 2.0 (MPL-2.0) — Phlix Server and Phlix Hub MIT License —
Clients, plugins, and shared libraries Phlix Server and Hub: MPL-2.0 — if you modify a
file, that file stays open; anything you add alongside it is yours. Clients, plugins,
shared: MIT — build on them freely, no copyleft restrictions. Full license text:
https://www.mozilla.org/en-US/MPL/2.0/
Use Phlix commercially. Modify the code. Distribute your builds. Deploy it in a product. As long as you disclose source changes to MPL-2.0 files and keep the license and copyright notices in place — it is yours to use.
If you modify MPL-2.0 files, you must make the source available. MIT-licensed code can be used in proprietary products. Keep notices in place and state your changes clearly.
Get Involved
Phlix is built by the community. Code, documentation, plugins, bug reports, and feature requests are all welcome contributions.
Server in PHP 8.3+ with Workerman 5.x, clients in their native toolkits (Swift/Kotlin/Electron). Pull requests welcome. Check the GitHub issue tracker for labeled "good first issue" items.
Build a plugin and share it. The community plugin repo accepts submissions via pull request. Docs, examples, and the SDK are all in the main repo.
Every missing comma in the docs is a contribution. If you found a step confusing, open a PR — the next person will thank you.
Report bugs with server logs, steps to reproduce, and your setup. The more specific, the faster the fix. Feature requests belong in GitHub discussions.
Common Questions
A server with 1GB RAM, a dual-core CPU, and 10GB of storage. It runs on a Raspberry Pi 4, an old laptop, or a dedicated NAS. Hardware transcoding requires a GPU with Quick Sync, NVENC, or VCE support.
Go to the admin panel, click Library → Add Folders, and point Phlix to your media directories. Phlix scans for content, fetches metadata automatically, and organizes everything by show and season.
Yes — iOS, Android, and Android TV apps are available in their respective app stores. All three support offline downloads for watching on the go without a connection.
SyncPlay uses WebRTC for peer-to-peer synchronization when devices are on the same network, and routes through Hub when remote. The Hub relay only sees encrypted metadata — it cannot read or alter playback.
Tested to 20 simultaneous viewers with sub-100ms sync accuracy. Beyond that, network conditions and relay capacity become the limiting factors. For party-sized sync, a local-area setup is recommended.
All common video codecs: H.264, H.265/HEVC, VP8, VP9, AV1, MPEG-1, MPEG-2, and more. Audio: AAC, MP3, FLAC, DTS, Dolby Digital, Dolby Digital Plus, Dolby Atmos. Subtitles: SRT, SSA/ASS, VTT, PGS.
Yes. Phlix provides a Caddy configuration example and supports nginx with proper WebSocket forwarding. The admin panel has a built-in SSL certificate generator via Let's Encrypt if you want direct HTTPS access.
Yes. Phlix automatically detects and uses Intel Quick Sync (QSV), NVIDIA NVENC, AMD VCE, and Apple VideoToolbox. Set your quality preference in the admin panel and Phlix handles the rest.