Skip to content

About IPTV Factory

A working reference for the two authentication models behind almost all IPTV middleware, with tooling attached.

The problem this addresses

Documentation for Xtream Codes and Stalker portals barely exists. What circulates is vendor marketing on one side and forum replies that assume you already know the terminology on the other, so people troubleshoot by guessing.

This site writes down what the exchange actually consists of: which endpoint returns what, which field the server checks, and which failures look identical from the outside but have entirely different causes.

How the pipeline works

Datasets live as spreadsheets in object storage, with a second provider configured as a fallback so a single outage does not take the tool down. The browser streams the file, reports genuine byte progress, then parses it in a Web Worker.

A region index is built at parse time — a map of region name to row offsets — so filtering is a lookup instead of a full scan across tens of thousands of rows.

Nothing is uploaded and nothing is logged. Selection happens entirely on your device, and no record exists of which row any visitor drew.

What verification does and does not prove

A successful check means the panel answered and the credential pair authenticated at that moment. It does not mean the account has connection slots free, that upstream sources are alive, or that the bitrate is usable.

Public endpoints change state constantly. Treat any result as valid for minutes, not hours.

Scope

We do not host, stream or rebroadcast anything, sell subscriptions, or take money from any provider. A publicly circulating credential is not a licence — if you want dependable access to content, buy it from someone entitled to sell it.

Who runs it

IPTV Factory is operated by Mohcin Bajja. Questions, corrections and takedown requests go to hello@iptv-factory.com.