Stacks / Meetings
Medium
LiveKit / Jitsi
Realtime voice and video you host. LiveKit and Jitsi are Apache-2.0. SMS still needs a carrier — this page does not pretend otherwise.
The problem
Twilio meters voice, video, and SMS by the minute and the segment. LiveKit is Apache-2.0 WebRTC rooms. Jitsi is Apache-2.0 meetings. Neither is an SMS gateway: self-hosting SMS still requires a carrier, a SIM gateway, or a provider you pay. n8n can fan out the webhooks you already have.
Replaces
Twilio
Estimated SaaS saved
$2,400
per year, small team, before lock-in
Start on Railwayn8n + Postgres for notification workflows
Placeholder: LiveKit server (or Jitsi) plus TURN if you need it. SMS is not a Railway one-click. Notification workflows can sit on /stacks/n8n-automation.
The stack
Cost table
| You stop paying | Typical / year | Self-host instead |
|---|---|---|
| Twilio voice / video / SMS (small team) | $2,400 | LiveKit or Jitsi; SMS still via a carrier |
Agent setup prompt
Replace Twilio realtime with LiveKit (preferred) or Jitsi. Do not claim a self-hosted SMS replacement. SMS needs a carrier, a GSM modem, or a paid gateway. - LiveKit: server + keys, bind HTTP/WebRTC. Jitsi if the job is a meeting room, not an SDK. - Webhook fan-out can live on /stacks/n8n-automation. Write AGENT_PROMPT.md.
Also as markdown: /stacks/livekit-comms.md
FAQ
- Can I drop Twilio SMS?
- Not with open source alone. You still buy segments from a carrier or a gateway. This page replaces Programmable Voice/Video. Keep a thin SMS provider if you must send texts.
- LiveKit or Jitsi?
- LiveKit if you are embedding rooms in an app. Jitsi if people just need a meeting URL.