lebaudantoine
7369379106
On rooms with the `trusted` access level, any authenticated user connected to the meeting can now manage the lobby. Requested by several organizations, and a step toward generalized lobby management once hubs and groups land (same organization only). Being authenticated is not enough to grant the capability: a `trusted` room means "trusted to join", not "trusted to decide who else joins from outside the call". The new `CanManageLobby` permission therefore also requires the requester to be currently connected to the meeting, verified against LiveKit and failing closed, like `IsPresentInMeeting`. The access level itself is never cached and always read fresh, so an owner switching the room back to `restricted` revokes the capability on the very next request - the one guarantee we did not want to trade for performance. Performance is traded elsewhere: the waiting list is polled by every lobby manager, and on a trusted room that audience grows from a few admins to potentially the whole meeting. Hitting LiveKit once per poll per participant would not survive that fan-out, so presence is memoized in Redis (`PresenceCache`, `PRESENCE_CACHE_TIMEOUT`, 1h). Entries are created lazily because only the minority of participants who actually manage a lobby ever need one, and only positive answers are cached because a sticky negative would lock out someone joining right after a miss for the whole TTL. Eager invalidation on `participant_left`, `room_finished` and admin kick keeps the cache honest; the TTL is the safety net when an event is lost, and its value bounds how long a departed participant could still act. Trade-offs in this v0: * `PRESENCE_CLEAR_ON_PARTICIPANT_LEFT` gates the eager invalidation on `participant_left`: its cost is one Redis DELETE per departure, for every departure, so we want to be able to measure it in production and turn it off independently of the feature. When disabled, invalidation relies on `room_finished` and the TTL only, widening the stale window above. * This can put non-trivial pressure on the cache at scale; the rollout will need to be monitored closely. * The `participant_left` webhook must be enabled in the LiveKit deployment, otherwise eager invalidation silently degrades to the TTL-only behavior.
LiveKit - Chat with us - Roadmap - Changelog - Bug reports
La Suite Meet: Simple Video Conferencing
Powered by LiveKit, La Suite Meet offers Zoom-level performance with high-quality video and audio. No installation required—simply join calls directly from your browser. Check out LiveKit's impressive optimizations in their blog post.
Tip
New here? Start by introducing yourself in our Matrix channel: https://matrix.to/#/#meet-official:matrix.org
We’re happy to discuss ideas, answer questions, and help to deploy LaSuite Meet.
Features
- Optimized for stability in large meetings (+100 p.)
- Support for multiple screen sharing streams
- Non-persistent, secure chat
- End-to-end encryption (coming soon)
- Meeting recording
- Meeting transcription & Summary (currently in beta)
- Telephony integration
- Secure participation with robust authentication and access control
- Customizable frontend style
- LiveKit Advances features including :
- speaker detection
- simulcast
- end-to-end optimizations
- selective subscription
- SVC codecs (VP9, AV1)
La Suite Meet is fully self-hostable and released under the MIT License, ensuring complete control and flexibility. It's simple to get started or request a demo.
We’re continuously adding new features to enhance your experience, with the latest updates coming soon!
🚀 Major roll out to all French public servants
On the 29th of January 2026, Prime Minister Sébastien Lecornu, announced the full deployment of Visio—the French government’s dedicated Meet platform—to all public servants. (Source in English)
Table of Contents
Get started
Docs
We're currently working on both technical and user documentation for La Suite Meet. In the meantime, many of the essential aspects are already well covered by the LiveKit documentation and their self-hosting guide. Stay tuned for more updates!
Self-host
La Suite Meet is easy to install on your own servers
We use Kubernetes for our production instance but also support Docker Compose. The community contributed a couple other methods (Nix, YunoHost etc.) check out the docs to get detailed instructions and examples.
Questions? Open an issue on GitHub or join our Matrix community.
Note
Some advanced features (ex: recording, transcription) lack detailed documentation. We're working hard to provide comprehensive guides soon.
Known instances
We hope to see many more, here is an incomplete list of public La Suite Meet instances. Feel free to make a PR to add ones that are not listed below🙏
| Url | Org | Access |
|---|---|---|
| visio.numerique.gouv.fr | DINUM | French public agents working for the central administration and the extended public sphere. ProConnect is required to login in or sign up |
| visio.suite.anct.gouv.fr | ANCT | French public agents working for the territorial administration and the extended public sphere. ProConnect is required to login in or sign up |
| visio.lasuite.coop | lasuite.coop | Free and open demo to all. Content and accounts are reset after one month |
| mosacloud.cloud | mosa.cloud | Demo instance of mosa.cloud, a dutch company providing services around La Suite apps. |
| Clever Cloud | clever cloud | Openvisio is a sovereign video conferencing solution based on LaSuite Meet offered by Clever Cloud. |
| Email.eu | Email.eu | Sovereign business workspace. |
Contributing
We <3 contributions of all kinds big or small and we’re genuinely glad you’re here. 🌱
Start by saying hi
The best first contribution is simply to come say hi.
Before opening a PR, especially a larger one, or one written with the help of AI, we encourage you to reach out to a maintainer on our Matrix channel (@antoine.lebaud:matrix.org).
Getting in touch early helps us align on goals, avoid duplicated or wasted effort, and build a community that stays active, welcoming, and fun to be part of. There are no silly questions here: whether you’ve shipped hundreds of PRs or you’re just getting started, you’re welcome.
AI contributions
AI-assisted contributions are welcome. But code is never the end goal. What matters most is building relationships, sharing knowledge, and growing a sustainable community over time.
If your contribution has been heavily generated with AI, please be transparent about it. This helps maintainers review it with the right context and respects the time they invest in the project.
Using AI does not transfer ownership of the contribution: you should still fully understand the code, the problem it solves, and the reasoning behind the approach you propose. In short, even if AI helped write it, the why should still be yours.
Contributions beyond code
Not technical? We need you too. Open source is much more than code. Writing documentation, improving onboarding, translating content, answering questions, reporting bugs, or simply helping others feel welcome all make a huge difference.
Ways to contribute
When you’re ready, here are a few ways to get involved:
- 👋 Say hello and share your ideas with the community and maintainers on our Matrix channel
- 🛠️ Open a PR by following our guide to develop La Suite Meet locally
- 💡 Suggest an idea by opening a feature request
- 🐛 Report a bug by opening a bug report
Thank you for helping build something open, useful, and human. 💙
Community call
We host a community call on the first Friday of every month to share updates, discuss ideas, and connect with contributors.
Whether you’re actively contributing or just curious about the project, you’re welcome to join. More details are shared on the Matrix channel.
Philosophy
We’re relentlessly focused on building the best open-source video conferencing product—La Suite Meet. Growth comes from creating something people truly need, not just from chasing metrics.
Our users come first. We’re committed to making La Suite Meet as accessible and easy to use as proprietary solutions, ensuring it meets the highest standards.
Most of the heavy engineering is handled by the incredible LiveKit team, allowing us to focus on delivering a top-tier product. We follow extreme programming practices, favoring pair programming and quick, iterative releases. Challenge our tech and architecture—simplicity is always our top priority.
Open-source
Gov 🇫🇷 supports open source! This project is available under MIT license.
All features we develop will always remain open-source, and we are committed to contributing back to the LiveKit community whenever feasible. To learn more, don't hesitate to reach out.
Help us!
Come help us make La Suite Meet even better. We're growing fast and would love some help.
Contributors 🧞
Credits
We're using the awesome LiveKit implementation. We're also thankful to the teams behind Django Rest Framework, Vite.js, and React Aria — Thanks for your amazing work! This project is tested with BrowserStack.
License
Code in this repository is published under the MIT license by DINUM (Direction interministériel du numérique). Documentation (in the docs/) directory is released under the Etalab-2.0 license.