About Phlix

Philosophy

Phlix is built on the belief that your media library belongs on your hardware, under your control. No subscription fees, no data harvesting, no vendor lock-in. Just a PHP media server that does what you need it to do — stream to your devices, keep in sync, and stay out of your way.

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.

Contributing

Phlix is developed in the open at GitHub. Issues, pull requests, and plugin contributions are welcome.

FAQ

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.