IPTV Server Software: Xtream Codes, XUI, Stalker Compared

If you're a subscriber who just wants to watch live TV, none of this is something you need to touch — a provider runs this software on your behalf and hands you a username, password, and server URL. This guide is for the other audience: people trying to understand what actually powers an IPTV service, whether out of technical curiosity, because they're evaluating a provider's infrastructure, or because they're considering running their own server.

Where server software fits in the IPTV stack

IPTV server software doesn't operate in isolation — it's the middle layer of a chain that starts with a video source and ends on your screen:

Two of these stages get conflated a lot: the panel software (subscriber/account management, channel lists, EPG) and the streaming server (the actual real-time video delivery engine, using protocols like HLS, RTMP, or RTSP). A full IPTV server setup runs both together, but they're conceptually distinct — you can think of the panel as the "front office" handling accounts and metadata, and the streaming server as the "warehouse" actually moving video data. If you're specifically interested in how the encoding stage works — turning a raw camera or broadcast feed into the compressed stream this whole chain depends on — see our 4K IPTV encoder guide, and for how many channels get combined into one coordinated system, our IPTV headend architecture guide covers the full picture.

Xtream Codes and XUI.one

Xtream Codes is the panel system most current IPTV providers run, directly or through a fork. Its defining feature is a unified API: instead of a subscriber needing separate URLs for channels, an EPG feed, and a VOD catalog, Xtream Codes exposes all of it through one API endpoint authenticated by a server URL, username, and password. Apps like TiviMate and IPTV Smarters have first-class Xtream Codes support built in — you enter the three credentials once and everything (live channels, program guide, video-on-demand library, series) loads automatically.

The original Xtream Codes project has a complicated history — the original developers behind it were subject to a widely reported 2019 law enforcement action in Europe connected to unlicensed content distribution through the platform, which is separate from the panel software's underlying technology itself. In the years since, the ecosystem has continued through forks and successors, the most prominent being XUI.one, which most current-generation providers actually run. Functionally, XUI.one preserves the same API structure and credential model subscribers are used to, while adding a more actively maintained codebase and updated admin interface.

What the Xtream Codes API actually delivers

• Live channel list — organized by category, with stream URLs per channel
• EPG data — the electronic program guide, typically 7-14 days depending on the provider
• VOD catalog — movies, organized with metadata (poster art, description, year)
• Series — TV shows broken into seasons and episodes
• Catch-up / timeshift — on some providers, the ability to rewind recently aired live content

For the exact steps to connect to an Xtream Codes server in your app, see our dedicated Xtream Codes login and setup guide and the deeper technical explainer at Xtream Codes IPTV explained.

Stalker / Ministra middleware

Stalker Portal, now maintained and sold commercially as Ministra, is an older middleware platform with roots in the MAG set-top box ecosystem — Infomir's MAG boxes were historically the primary hardware built around Stalker as their native middleware. Where Xtream Codes exposes a relatively simple API that any modern app can integrate with, Stalker/Ministra uses a more involved portal-based architecture originally designed around dedicated hardware boxes rather than general-purpose apps.

Stalker/Ministra remains in active use today primarily in two contexts: legacy deployments that were built around MAG boxes years ago and never migrated, and hospitality/MDU (hotel, apartment building) installations where the operator wants tighter control over the portal experience — custom branding, restricted channel lists per room, welcome screens — that Stalker's architecture supports more natively than a bare Xtream Codes API. For a typical new consumer IPTV subscription in 2026, Stalker/Ministra is less common than Xtream Codes/XUI.one, but you'll still encounter it, particularly through certain regional and hospitality-focused providers.

M3U-based panels

The simplest tier of IPTV server software doesn't run a full API at all — it just generates an M3U playlist file, a plain-text list of channel names and stream URLs, optionally paired with a separate XMLTV URL for program guide data. Any player that understands the M3U format (VLC, Kodi, and virtually every IPTV app) can load it directly.

The tradeoff is convenience versus simplicity: M3U setup requires two separate URLs (playlist + EPG) instead of Xtream Codes' single API, VOD/series support isn't standardized the way it is with Xtream Codes, and updates to the channel list mean re-fetching the whole playlist. What M3U gains in exchange is universal compatibility — because it's just a text file, it works with essentially any media player ever built, including ones with no dedicated IPTV features at all. See our M3U playlist guide for the full setup walkthrough.

Comparing the three systems

Should you self-host your own IPTV server?

This question comes up most often from two different directions: people curious whether it's technically possible, and people considering it as a business. The honest answer is more nuanced than the software alone suggests.

Installing panel software like XUI.one on a VPS is not, by itself, technically difficult — it's a documented installation process that a reasonably technical person can complete in an afternoon. What the software alone does not solve is everything upstream and downstream of it:

• Content sourcing: the panel manages channels you already have access to — it doesn't provide them. You need legitimately licensed content sources, which is a substantial legal and commercial undertaking, not a technical one.
• Encoding infrastructure: turning a raw broadcast or camera feed into a compressed IP stream at the scale of a full channel lineup requires real encoding hardware — see our 4K IPTV encoder guide for what that involves.
• CDN capacity: a single VPS running panel software has no meaningful ability to serve thousands of concurrent viewers without a proper content delivery layer on top.
• Ongoing operations: channel feeds break, servers need monitoring, and subscribers need support — this is continuous work, not a one-time setup.

The realistic alternative: reseller panels

For the large majority of people who want to run an IPTV business without building infrastructure from zero, a reseller panel is the practical path — you get a management dashboard to create and manage subscriber accounts, but the underlying content sourcing, encoding, and CDN infrastructure is handled by the upstream provider. You're managing customer relationships and pricing, not running servers.

This sidesteps essentially every hard problem in the self-hosting list above except client acquisition, which is genuinely the part of the business that's yours to build. See our full IPTV reseller guide for how panel access, credit systems, and margins actually work.

What is a streaming server, specifically?

Within the broader "IPTV server" concept, the streaming server is the specific component handling real-time video delivery — as distinct from the panel software managing accounts and metadata. Streaming servers implement one or more delivery protocols:

Most consumer-facing IPTV servers deliver to your app via HLS specifically because of its near-universal compatibility and adaptive bitrate support — your stream automatically steps down in quality if your connection can't sustain the top tier, rather than freezing outright. For the deeper technical breakdown of these protocols, see our IPTV protocol guide.

Frequently Asked Questions