head to head · open source

LiveKit vs Vibe-Workflow

LiveKit has 21,000 GitHub stars, 2,354 forks, 189 open issues and last shipped yesterday. Vibe-Workflow has 588 stars, 150 forks, 1 open issues and last shipped 3 days ago. LiveKit leads on adoption by 3,471% (21,000 vs 588 stars). LiveKit is written in Go under Apache-2.0; Vibe-Workflow is written in JavaScript under MIT. LiveKit has attracted 11% as many forks as stars, Vibe-Workflow 26%. LiveKit 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 Vibe-Workflow ★ 588 category Productivity & Utilities

← all 20902 open source comparisons

Side by side

LiveKit Vibe-Workflow
GitHub stars ★ 21K ★ 588
License Apache-2.0 MIT
Written in Go JavaScript
Last push 2026-09-19 2026-09-17
Forks ⑂ 2.4K ⑂ 150
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 Vibe-Workflow if

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

full Vibe-Workflow 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 Vibe-Workflow

Vibe Workflow is a free, MIT licensed, node based AI workflow builder in JavaScript for creative professionals, studios, developers and researchers who design, edit and compose generative image and video pipelines — positioned as the self hostable alternative to Weavy AI, Krea Nodes, Freepik Spaces and FloraFauna AI.

read the full Vibe-Workflow 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 Vibe-Workflow more popular?

LiveKit has 21,000 GitHub stars and Vibe-Workflow has 588. LiveKit has the larger community by that measure.

Are LiveKit and Vibe-Workflow free?

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

What is the difference between LiveKit and Vibe-Workflow?

LiveKit is written in Go and Vibe-Workflow 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, LiveKit or Vibe-Workflow?

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