head to head · open source

neko vs iptv

neko has 22,315 GitHub stars, 1,628 forks, 151 open issues and last shipped 8 days ago. iptv has 737 stars, 241 forks, 9 open issues and last shipped 3 days ago. neko leads on adoption by 2,928% (22,315 vs 737 stars). neko is written in Go under Apache-2.0; iptv is written in JavaScript under GPL-3.0. neko has attracted 7% as many forks as stars, iptv 33%. iptv was the more recently maintained of the two, and both are self-hostable with no licence fee.

Two open source projects, one decision. Both are free and self-hostable — the differences are community size, license terms, language stack and release pace.

neko ★ 22K iptv ★ 737 category Miscellaneous

← all 8884 open source comparisons

Side by side

neko iptv
GitHub stars ★ 22K ★ 737
License Apache-2.0 GPL-3.0
Written in Go JavaScript
Last push 2026-09-10 2026-09-15
Forks ⑂ 1.6K ⑂ 241
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

full neko profile →

pick iptv if

  • You want the iptv feature set and don't need the biggest community
  • You prefer the GPL-3.0 license terms
  • Your stack matches JavaScript
  • You evaluated both and iptv fits your workflow better

full iptv profile →

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.

read the full neko overview →

About iptv

iPTV is a self hosted, modular IPTV live source management and distribution system that aggregates more than 800 channels from sources such as 央视频, 咪咕, Bilibili, Huya, Douyu and regional broadcasters, then de duplicates and re publishes them as clean M3U/TXT playlists with an EPG guide; it is aimed at NAS owners and home theatre users who want a channel lineup they control.

read the full iptv overview →

More in Miscellaneous

firecrawl ★ 182K Godot ★ 117K Home Assistant ★ 91K OpenCut ★ 90K OpenBB ★ 73K Jellyfin ★ 57K

Related comparisons

jellyfin vs neko jellyfin vs invidious jellyfin vs navidrome jellyfin vs kodi jellyfin vs nuclear jellyfin vs peertube jellyfin vs iptv-sources jellyfin vs ansible-nas firecrawl vs godot godot vs home-assistant firecrawl vs gdevelop firecrawl vs monogame firecrawl vs sbox godot vs gdevelop godot vs monogame godot vs sbox firecrawl vs home-assistant firecrawl vs cratedb firecrawl vs gladys-assistant home-assistant vs opencut godot vs cratedb godot vs gladys-assistant home-assistant vs cratedb opencut vs cratedb

More Media & Streaming projects

Compare either of these against the rest of the Media & Streaming field.

neko vs Jellyfin neko vs Invidious neko vs Navidrome neko vs Kodi neko vs Nuclear neko vs PeerTube neko vs iptv-sources neko vs ansible-nas neko vs Anthias neko vs tvheadend neko vs Ghosten-Player neko vs BookWyrm

Frequently asked questions

Is neko or iptv more popular?

neko has 22,315 GitHub stars and iptv has 737. neko has the larger community by that measure.

Are neko and iptv free?

Both are open source. neko is licensed under Apache-2.0 and iptv under GPL-3.0. Neither carries a licence fee.

What is the difference between neko and iptv?

neko is written in Go and iptv in JavaScript. 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?

Choose neko if you want the larger community (22,315 stars) or its Apache-2.0 licence terms. Choose iptv if its feature set, stack or GPL-3.0 licence fits better. Both are self-hostable.