Matrix server integration
Already running a Matrix homeserver or planning one? Sparks connects to your existing server – no migration needed. You can also connect your own LiveKit for video conferencing. This page covers both.
Use your own Matrix server
An existing Matrix server can be reused as is. The Sparks client connects to your homeserver via the Matrix protocol; E2EE, federation, existing rooms, and Element interop (polls, tags, knock, ignored users) continue to work.
-
Compatible homeservers
Any compatible Matrix server can be used. These include Synapse, Tuwunel, Dendrite, Conduit and other implementations. An overview is available on the official Matrix website.
-
No data migration
Your chat history, rooms and channels stay on your server. Sparks is another client – like an app that logs into your existing service.
-
Interop with Element / federation
Sparks meetings run primarily on LiveKit. Incoming Element Call / MatrixRTC calls can be answered in Sparks. On chat: inbound polls, stickers, voice messages, chat tags, and blocked contacts (ignored users) – federated with Element and other clients.
Your own LiveKit for video conferencing
If you already run LiveKit (or another compatible WebRTC backend) alongside your Matrix server, you can connect it to Sparks. Video meetings then run in your infrastructure – Sparks uses your LiveKit instead of a hosted service.
-
Connect LiveKit to Sparks
Sparks supports LiveKit as the video backend. You configure your LiveKit instance (API URL, keys) in the Sparks configuration; meetings, lobby, breakout rooms and screen sharing then run via your own backend.
-
One interface for chat and video
Matrix provides chat and channels, LiveKit provides video conferencing – both appear in one Sparks interface. Ideal for organisations that want to run both chat and video entirely on their own.