head to head · open source

LiveKit vs loopx

LiveKit has 21,000 GitHub stars, 2,354 forks, 189 open issues and last shipped yesterday. loopx has 5,903 stars, 559 forks, 102 open issues and last shipped today. LiveKit leads on adoption by 256% (21,000 vs 5,903 stars). LiveKit is written in Go under Apache-2.0; loopx is written in Python under Apache-2.0. LiveKit has attracted 11% as many forks as stars, loopx 9%. loopx 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.

LiveKit ★ 21K loopx ★ 5.9K category Productivity & Utilities

← all 20902 open source comparisons

Side by side

LiveKit loopx
GitHub stars ★ 21K ★ 5.9K
License Apache-2.0 Apache-2.0
Written in Go Python
Last push 2026-09-19 2026-09-20
Forks ⑂ 2.4K ⑂ 559
Self-hosting Yes Yes
Data ownership Your server Your server

pick LiveKit if

  • You weight community size — 21K 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 LiveKit profile →

pick loopx if

  • You want the loopx feature set and don't need the biggest community
  • You prefer the Apache-2.0 license terms
  • Your stack matches Python
  • You evaluated both and loopx fits your workflow better

full loopx profile →

About LiveKit

LiveKit is an open source realtime infrastructure project for voice, video, and physical AI agents, and it lives in the WebRTC, media server, and voice AI ecosystem. The repository contains the LiveKit server, a scalable distributed WebRTC SFU written in Go and built on Pion WebRTC. It moves realtime audio, video, and data between people, devices, and AI models, while SDKs, agent frameworks, and companion services are provided separately.

read the full LiveKit overview →

About loopx

LoopX is an open, provider neutral, local first control plane for long horizon AI agents that preserves objectives, gates, todos, evidence, quota, and handoffs across turns for developers and teams running durable, governed work on harnesses such as Codex, Claude Code, and Cursor.

read the full loopx overview →

More in Productivity & Utilities

n8n ★ 205K Excalidraw ★ 132K RustDesk ★ 124K LocalSend ★ 92K AppFlowy ★ 77K OBS Studio ★ 76K

Related comparisons

n8n vs langchain n8n vs browser-use firecrawl vs browser-use n8n vs langgraph n8n vs frigate n8n vs lightpanda n8n vs proxmoxve n8n vs activepieces openclaw vs khoj open-webui vs open-notebook open-webui vs khoj appflowy vs affine appflowy vs memos appflowy vs plane appflowy vs joplin mem0 vs memos n8n vs obs-studio n8n vs sharex n8n vs kap excalidraw vs obs-studio n8n vs snapify excalidraw vs sharex excalidraw vs kap excalidraw vs snapify

More Automation projects

Compare either of these against the rest of the Automation field.

LiveKit vs n8n LiveKit vs ProxmoxVE LiveKit vs ActivePieces LiveKit vs amis LiveKit vs Windmill LiveKit vs Botpress LiveKit vs mitosis LiveKit vs Automatisch LiveKit vs puck LiveKit vs Typebot LiveKit vs cadence LiveKit vs local-deep-research

Frequently asked questions

Is LiveKit or loopx more popular?

LiveKit has 21,000 GitHub stars and loopx has 5,903. LiveKit has the larger community by that measure.

Are LiveKit and loopx free?

Both are open source. LiveKit is licensed under Apache-2.0 and loopx under Apache-2.0. Neither carries a licence fee.

What is the difference between LiveKit and loopx?

LiveKit is written in Go and loopx in Python. The practical differences are community size, licence terms, language stack and release cadence — all compared in the table above.

Which should I choose, LiveKit or loopx?

Choose LiveKit if you want the larger community (21,000 stars) or its Apache-2.0 licence terms. Choose loopx if its feature set, stack or Apache-2.0 licence fits better. Both are self-hostable.