The Void

Philosophy

Phlix exists for those who want their media to live on their own hardware, under their own control. No subscriptions, no third-party clouds, no data harvesting. Your library is your library — it stays on your server until you decide otherwise.

The project is built in PHP because PHP runs everywhere and is understood by a wide developer base. Workerman provides the async runtime. FFmpeg handles transcoding. The result is a stack that is auditable, self-hostable, and designed to last.

License

Contributing

The project lives at GitHub. Open issues for bugs and feature requests. Pull requests welcome. The maintainer responds to the detain GitHub org.

Frequently Asked Questions

Is Phlix like Plex / Jellyfin / Emby?

Yes — same job, different stack. Phlix is built in PHP 8.3+ on Workerman, ships with a versioned plugin contract, and includes a hub for accessing remote servers behind NAT without a third-party tunnel.

Do I need to expose my server to the internet?

No. Run Phlix on your LAN and use the Phlix Hub's reverse-tunnel relay to reach it from your phone or Roku at a friend's house. You can self-host the hub, or use the public one.

What formats are supported?

Anything FFmpeg can read. Direct play when the client supports it; transcoded HLS otherwise. Per-device quality profiles pick the right bitrate automatically.

Is there a mobile app?

Yes — React Native, available on iOS and Android. Currently in beta.

Can I write plugins?

Yes. Implement LifecycleInterface, ship a manifest, drop it in the plugins directory. See phlix-plugin-example for the smallest working starter.

What's the license?

Phlix Server and the Hub are MPL-2.0 — open source, and you can build on them commercially. If you modify a Phlix file, that file stays open; anything you add alongside it is yours. The shared libraries, plugins, and clients are MIT so you can build on them freely.