Backchannel vs Meetily

Who said what

This used to be a capability gap; it is now a pricing one. Meetily shipped diarization in Pro 1.8.2, live as you record and on imported audio -- but it stays out of the MIT Community Edition, so the free version still produces unattributed transcripts and speaker labels cost $120 a year. Backchannel ships diarization free, in the MIT codebase -- Silero VAD segments speech and WeSpeaker embeddings assign each segment to a voice, live, with dual-track capture giving you and remote participants separate identities. If a transcript without names is half a transcript to you, this decides it.

Notes after vs insights during

Meetily's output is the record: transcripts and LLM summaries after the meeting. Backchannel also keeps the record, but its center of gravity is the call itself: five live insight agents -- consolidated analyst, objection handler, synthesizer, opportunity specialist, and strategic signals -- run on their own triggers during the meeting and push questions worth asking, objection responses, opportunities, and action items while you can still use them, followed by a three-agent briefing pass when the call ends. No actively maintained open-source meeting tool ships this today. Amurex (AGPL-3.0) did, and it has had no commits since May 2025.

Desktop app vs server

Meetily is a native desktop app -- great installers, GPU-accelerated local ASR, everything on one machine. Backchannel is a server: a FastAPI backend and PostgreSQL behind a browser UI, so one deployment can serve a team, keep a shared archive, and be reached from any machine with a browser. One is an appliance, the other is infrastructure; pick by how many people need it.

The offline story

Both clear the air-gap bar now. Meetily's Ollama-first design means transcription and summarization can run with zero external calls, out of the box. Backchannel gets to the same place with one more moving part: diarization is always local, transcription runs offline with local ONNX models, the insight agents can point at any OpenAI-compatible server you host (Ollama, LM Studio, vLLM, LiteLLM), and interim captions can run on-device -- so an air-gapped Backchannel runs end to end with Privacy First on. Meetily's setup is simpler; Backchannel asks you to run a model server but keeps the live agents in the deal.

Free vs open-core

Both cores are MIT. Meetily has routed its best features -- diarization, chat with meetings, self-hosted deployment, enhanced accuracy, templates, advanced exports -- into a $10/user/mo Pro tier. Backchannel has no Pro tier to route anything to: diarization, agents, exports, and multi-user deployment are all in the public repo.

Maturity and community

Meetily wins, clearly. 26.4k stars, hundreds of thousands of downloads, polished releases, and an active content presence. One neutral observation for anyone betting on the open core: development of the MIT Community Edition has been quiet since v0.4.0 on 2026-06-05, while the commercial Pro line has continued shipping. Backchannel is younger and smaller; what it offers is capability that is not in Meetily's free edition at all. Weigh community support against shipped features according to your own risk tolerance.

Meetily: download an installer, pick a Whisper model, optionally point it at Ollama. Backchannel: git clone, docker compose up --build, add a Gemini API key (or a local ONNX transcription model and a self-hosted endpoint for the agents), open localhost in a browser -- or use a desktop bundle for Windows, macOS, or Linux -- like Meetily's installers, an ungated direct download. The quickstart is honest that the first start builds images and downloads models -- Meetily's install experience is smoother on both counts; Backchannel's payoff is a shared, multi-user server once it is up.