Pangom offers a publicly accessible, ready-to-use version of PanPlay for free use on this domain, referred to as the PanPlay CDN.
This is an easy way to set up a PanPlay stream. A self-hosted PanPlay offers more control and individual options, and is the recommended setup, but the CDN has clear advantages of its own:
Things to know before you use it
The CDN isn’t the right fit for everyone. A few real trade-offs to weigh against a self-hosted setup:
- No own domain or branding. Your stream runs under
play.pangom.net, not your own domain, and UI/theme customization is limited to the options built into PanPlay itself. - Shared, central configuration. Server-side add-ons such as the Content Protection Mechanism are configured once for the whole CDN and can’t be tuned per stream the way they can on a self-hosted copy.
- You depend on Pangom’s infrastructure and decisions. Uptime, update timing, and the CDN’s own version-support schedule are outside your control. When an older CDN build reaches the end of its support window, it’s automatically redirected to a currently supported version instead of staying exactly as it was, unlike a self-hosted copy, which stays exactly as you left it until you choose to update it.
- Whoever runs the server sees the traffic that server handles. Any check that runs on the server side, such as the Content Protection Mechanism, runs on whichever server is actually running PanPlay. On the CDN, that’s Pangom’s own server; self-hosted, it’s yours (or whichever host you choose) instead.
One thing that’s the same either way: PanPlay, whether on the CDN or self-hosted, never proxies or stores the actual audio itself. Playback is always loaded directly by the listener’s own browser from the original source, for example laut.fm’s own servers, or wherever a direct audio file is hosted.
Get your link
The link generator builds a ready-to-use PanPlay CDN link for your laut.fm station or direct audio stream, with all the available parameters explained along the way.
