suitenumerique/meet: Self-Hosted Video Conferencing with LiveKit

suitenumerique/meet: Self-Hosted Video Conferencing with LiveKit

Finding a video conferencing solution that balances performance, privacy, and control is a persistent challenge for engineering teams. Most options force trade-offs: proprietary platforms lock you into their infrastructure, while self-hosted alternatives often sacrifice stability at scale. suitenumerique/meet enters this space with a specific proposition—Zoom-level performance through LiveKit's infrastructure, delivered via an open-source stack you can fully control. For teams evaluating suitenumerique/meet, the project offers a Django and React^{↗ Bright Coding Blog}-based application with MIT licensing, active French government backing, and deployment flexibility ranging from Docker^{↗ Bright Coding Blog} Compose to Kubernetes.

What is suitenumerique/meet?

suitenumerique/meet is an open-source video conferencing application built on LiveKit, a WebRTC infrastructure platform known for production-grade media handling. The project is maintained by DINUM (Direction interministérielle du numérique), the French government's digital service, as part of its broader "La Suite" initiative for sovereign digital tools.

The repository reflects healthy open-source activity: 2,147 stars, 258 forks, Python^{↗ Bright Coding Blog} as the primary language, and consistent monthly commit activity. The MIT license ensures permissive use for commercial and non-commercial deployments alike. The project was notably deployed at national scale on January 29, 2026, when French Prime Minister Sébastien Lecornu announced full rollout to all French public servants—making it one of the more significant government-backed open-source video conferencing deployments to date.

Technically, suitenumerique/meet sits at the intersection of real-time media infrastructure and modern web application development. LiveKit handles the WebRTC heavy lifting—simulcast, selective subscription, SVC codecs—while the Django backend and React frontend provide a conventional, maintainable application layer. This architecture choice matters: teams can modify business logic, authentication flows, and UI components without diving into WebRTC internals. The project also carries Digital Public Goods (DPG) verification, indicating it meets criteria for open-source solutions that advance sustainable development goals.

Key Features

Large-meeting stability. The README explicitly claims optimization for meetings exceeding 100 participants—a threshold where many WebRTC implementations degrade. This stems from LiveKit's selective subscription model and SVC codec support (VP9, AV1), which adaptively stream appropriate quality tiers rather than forcing uniform bandwidth consumption.

Multiple concurrent screen shares. Unlike platforms that restrict screen sharing to a single presenter, suitenumerique/meet supports multiple simultaneous screen sharing streams. This fits collaborative scenarios—code reviews, design critiques, incident response—where multiple participants need to share visual context concurrently.

Non-persistent secure chat. Meeting chat exists only for the session duration, reducing data retention surface area. The README notes end-to-end encryption as "coming soon," indicating active development on zero-trust media paths.

Recording and transcription. Meeting recording is available, with transcription and AI-generated summaries currently in beta. These features position the tool for compliance-heavy environments—government, healthcare, legal—where documentation is mandatory.

Telephony integration. PSTN dial-in extends accessibility to participants without reliable internet or compatible devices.

Authentication and access control. The project implements "robust authentication and access control" per the README, with known production instances integrating ProConnect (French government SSO) for public servant access.

Customizable frontend styling. Organizations can apply their own visual branding, relevant for white-label deployments or institutional identity requirements.

LiveKit advanced features. The full LiveKit feature set is exposed: speaker detection, simulcast, end-to-end optimizations, selective subscription, and SVC codec support. These are not suitenumerique/meet innovations, but their integration and configuration represent meaningful engineering work.

Use Cases

Government and public sector deployment. The primary documented use case: French central and territorial administration. The visio.numerique.gouv.fr and visio.suite.anct.gouv.fr instances serve hundreds of thousands of public servants with ProConnect authentication. Sovereignty requirements—data residency, vendor independence, auditability—make self-hosted open source preferable to SaaS alternatives.

Enterprise self-hosting with compliance needs. Organizations subject to GDPR, HIPAA, or sector-specific regulations can deploy on owned infrastructure with full data control. The MIT license removes commercial usage restrictions. The Kubernetes and Docker Compose deployment options accommodate both cloud-native and traditional operations teams.

Community and cooperative platforms. The lasuite.coop demo instance resets monthly, suggesting suitability for temporary or trial deployments. Cooperatives and mutuals can run independent instances without per-seat licensing.

Integration into broader service offerings. Clever Cloud's "Openvisio" and mosa.cloud's offerings demonstrate suitenumerique/meet as embeddable infrastructure—platform teams white-labeling video conferencing within larger product suites.

Technical education and research. The open codebase, Django/React stack, and LiveKit integration make it a viable reference implementation for studying WebRTC application architecture or building custom educational platforms.

Installation & Setup

The project supports multiple deployment methods. The maintainers use Kubernetes in production, with Docker Compose as the primary alternative. Community contributions include Nix and YunoHost packages.

Prerequisites: Review the installation documentation for current requirements. The README notes that advanced features—recording, transcription—currently lack comprehensive documentation, with guides in active development.

Docker Compose path:

# Clone the repository
git clone https://github.com/suitenumerique/meet.git
cd meet

# Follow Docker Compose instructions in docs/installation/README.md
# Specific compose commands are documented there

Kubernetes path:

# Review production deployment patterns
# The maintainers' production instance runs on Kubernetes
# See docs/installation/README.md for manifests and Helm references

Post-deployment configuration:

• Configure LiveKit server connection (self-hosted or LiveKit Cloud)
• Set up authentication provider (ProConnect, OIDC, or local)
• Adjust frontend styling per organizational requirements
• Enable/disable recording, transcription based on infrastructure capacity

Getting help: The project encourages GitHub issues for bugs and the Matrix channel (#meet-official:matrix.org) for real-time discussion. The README explicitly notes that maintainers prefer early contact before substantial PRs, especially for AI-assisted contributions.

Real Code Examples

The README does not contain embedded code snippets for API usage or configuration. This section reflects the current documentation state rather than inventing examples. Below are the structural elements that would typically be configured, based on the project's technology choices:

Django settings pattern (inferred from stack):

# Configuration would follow Django conventions
# LiveKit connection parameters, authentication backends,
# and feature flags for recording/transcription
# See docs/installation/README.md for actual configuration files

Frontend component structure (React-based):

// React components using LiveKit React SDK
// @livekit/components-react provides pre-built video room UI
// Customization happens through React Aria for accessibility
// Actual component code is in the repository src/ directory

The absence of inline code examples in the README suggests the project prioritizes operational deployment documentation over developer API tutorials. Teams integrating suitenumerique/meet programmatically should examine the source directly and engage via the Matrix channel for architecture guidance.

Advanced Usage & Best Practices

Capacity planning for large meetings. The 100+ participant claim depends on LiveKit server sizing and selective subscription configuration. Monitor participant bandwidth distribution; SVC codecs reduce aggregate load but increase server CPU for encoding ladders.

Authentication architecture. Production instances use ProConnect for French government SSO. For other deployments, plan OIDC integration early—the Django backend supports standard authentication backends, but custom flows require backend development^{↗ Bright Coding Blog}.

Feature flagging for beta capabilities. Transcription and summarization are beta features. The README suggests these may have incomplete documentation; enable incrementally and verify operational stability before organization-wide rollout.

Frontend customization scope. "Customizable frontend style" implies CSS/theming and potentially component overrides via the React layer. Major UX changes require frontend build pipeline familiarity (Vite.js per credits).

Community engagement protocol. The maintainers' contribution guidelines emphasize relationship-building over transactional PRs. For significant changes—especially those AI-assisted—contact @antoine.lebaud:matrix.org before substantial effort investment.

Comparison with Alternatives

Trade-offs: Jitsi offers longer track record and broader community; BigBlueButton excels in education-specific features (polling, breakout rooms, LMS integration). suitenumerique/meet's LiveKit foundation provides more modern WebRTC architecture for media handling, but the ecosystem is younger. The French government deployment provides production validation at scale that few alternatives can match for sovereign use cases.

FAQ

Is suitenumerique/meet free to use commercially? Yes, MIT licensed. No usage restrictions.

What LiveKit knowledge is required? Basic deployment understanding; deep WebRTC expertise not needed for standard use.

Can I run this without Kubernetes? Yes, Docker Compose is officially supported. Community packages exist for Nix and YunoHost.

Is end-to-end encryption available? Listed as "coming soon" in the README. Not currently implemented.

How active is development? Monthly commit activity per shields; last commit July 15, 2026.

What authentication methods work? ProConnect (French government SSO), with extensible Django authentication backends.

Can I contribute AI-generated code? Yes, with transparency and maintained understanding of the code's purpose and mechanics.

Conclusion

suitenumerique/meet occupies a specific niche: teams needing production-grade video conferencing with full infrastructure control, modern WebRTC performance, and permissive licensing. The French government deployment validates its scalability claims, while the Django/React stack ensures accessible customization for most engineering teams.

It is best suited for: organizations with sovereignty requirements, teams already invested in Python/React ecosystems, and platforms embedding video conferencing as a component rather than standalone product. It is less suited for: teams wanting immediate turnkey SaaS with zero operational overhead, or those requiring mature end-to-end encryption today.

The project welcomes contribution beyond code—documentation, translation, community support—and maintains an unusually explicit stance on building sustainable human relationships around the software. For teams evaluating self-hosted video infrastructure, explore the repository, join the Matrix channel, or request a demo to assess fit for your requirements.