head to head · open source
neko vs iptv-sources
neko has 22,315 GitHub stars, 1,628 forks, 151 open issues and last shipped 8 days ago. iptv-sources has 8,974 stars, 1,535 forks, 1 open issues and last shipped yesterday. neko leads on adoption by 149% (22,315 vs 8,974 stars). neko is written in Go under Apache-2.0; iptv-sources is written in TypeScript under GPL-3.0. neko has attracted 7% as many forks as stars, iptv-sources 17%. iptv-sources was the more recently maintained of the two, and both are self-hostable with no licence fee. The two share 1 topic tag (docker), so they are genuine substitutes rather than adjacent tools.
Two open source projects, one decision. Both are free and self-hostable — the differences are community size, license terms, language stack and release pace.
← all 8884 open source comparisons
Side by side
| neko | iptv-sources | |
|---|---|---|
| GitHub stars | ★ 22K | ★ 9.0K |
| License | Apache-2.0 | GPL-3.0 |
| Written in | Go | TypeScript |
| Last push | 2026-09-10 | 2026-09-17 |
| Forks | ⑂ 1.6K | ⑂ 1.5K |
| Self-hosting | Yes | Yes |
| Data ownership | Your server | Your server |
pick neko if
- You weight community size — 22K stars and counting
- You want the Apache-2.0 license terms
- Your stack matches Go
- You value the larger contributor base for long-term maintenance
pick iptv-sources if
- You want the iptv-sources feature set and don't need the biggest community
- You prefer the GPL-3.0 license terms
- Your stack matches TypeScript
- You evaluated both and iptv-sources fits your workflow better
About neko
Neko is a self hosted virtual browser that runs inside a Docker container and streams its desktop to several people at once over WebRTC, built for developers testing web applications, privacy conscious users, and teams who want to browse, watch or present together in one shared session.
About iptv-sources
iptv sources is a TypeScript application that automatically updates IPTV source lists and publishes them as M3U playlists and EPG data. It lives in the IPTV and media streaming ecosystem, where clients such as Kodi, TVBox, and DIYP compatible players consume M3U playlists and electronic program guide files. The project collects channel lists from a set of upstream repositories, including iptv org/iptv, YueChan/Live, YanG 1989/m3u, fanmingming/live, qwerttvv/Beijing IPTV, joevess/IPTV, and cymz6/AutoIPTV Hotel, and it gathers EPG data from fanmingming/live, 112114.xyz, and epg.51zmt.top:8000. It is released under …
read the full iptv-sources overview →
More in Miscellaneous
Related comparisons
More Media & Streaming projects
Compare either of these against the rest of the Media & Streaming field.
Frequently asked questions
Is neko or iptv-sources more popular?
neko has 22,315 GitHub stars and iptv-sources has 8,974. neko has the larger community by that measure.
Are neko and iptv-sources free?
Both are open source. neko is licensed under Apache-2.0 and iptv-sources under GPL-3.0. Neither carries a licence fee.
What is the difference between neko and iptv-sources?
neko is written in Go and iptv-sources in TypeScript. The practical differences are community size, licence terms, language stack and release cadence — all compared in the table above.
Which should I choose, neko or iptv-sources?
Choose neko if you want the larger community (22,315 stars) or its Apache-2.0 licence terms. Choose iptv-sources if its feature set, stack or GPL-3.0 licence fits better. Both are self-hostable.