MistServer
Feed one camera, encoder, or file into MistServer and it republishes the same media in the formats your audience actually uses: HLS for phones, DASH for browsers, WebRTC for sub second playback, and RTMP or SRT for the next service in the chain. Publish from OBS over RTMP, SRT, or WHIP, then hand viewers a Meta Player embed that picks a working protocol on its own. Records run straight to disk for later on demand viewing, and push support relays finished streams to external platforms. Processes can repackage, encode, compose, or analyze media between ingest and delivery. A JSON API on the controller port covers configuration and status, stream keys authenticate incoming publishers, and triggers fire your own endpoints on stream events. Operational metrics export to Prometheus for retention and alerting. Access control rules and HTTPS support protect interfaces and media endpoints. File libraries become on demand catalogs with the same delivery rules as live channels. Every input, output, and process ships as a separate small binary, so an installation keeps only the protocol modules it actually serves, and analysers inspect media properties when a stream misbehaves. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Unlicense licensed.
Deploy