Liman and OpenDesk
OpenDesk is a collaborative workspace built on open source, often used by authorities and public institutions. Liman adds professional video conferencing, Matrix chat with E2EE and a single interface for video, chat and calendar – same philosophy: open standards, EU data, self-hosting possible. On this page you will find the technical and organisational details of how they work together.
Liman in your open stack
-
Matrix and open standards
Liman builds on Matrix for chat and channels, like many open-stack solutions. If you already use Matrix or OpenDesk, Liman fits your architecture – federation and self-hosting are possible.
-
Video and collaboration
WebRTC meetings with breakout rooms, whiteboard and lobby. One interface for all communication needs, without proprietary cloud services.
-
Data sovereignty
Hosting in the EU, optional end-to-end encryption and self-hosting. Ideal for authorities and enterprises that chose OpenDesk for openness and control.
What is OpenDesk?
OpenDesk is an open collaboration and office environment built on free software, often used in public authorities, education and organisations with high requirements for data protection and independence. Typical components include email, calendar, files, chat and sometimes video conferencing – often in combination with Matrix, Nextcloud, Open-Xchange or similar components.
-
Target audience and use
OpenDesk targets organisations that deliberately use open source: public administration, education providers, associations, companies with compliance or sovereignty requirements. Control over data and infrastructure is the priority.
-
Technical components
Depending on deployment, an OpenDesk stack typically includes Matrix (chat/channels), email and calendar servers (e.g. Open-Xchange), file storage (e.g. Nextcloud via WebDAV), identity (e.g. Keycloak) and optionally own video solutions. Liman uses the same open protocols and can be integrated into this stack.
-
Shared values with Liman
Liman shares the focus on open protocols (Matrix, WebRTC), EU data, optional end-to-end encryption and self-hosting. So the collaboration of Liman with OpenDesk is not competition but a meaningful complement: Liman brings a modern, single interface for video, chat and calendar into your existing open stack.
Technical interfaces: How Liman and OpenDesk work together
Liman connects to your existing services via standardised protocols. If you already run OpenDesk or similar infrastructure, you can connect Liman to the same backends – without duplicate structures.
-
Matrix (chat and channels)
Liman uses Matrix for chat and channels – as do many OpenDesk installations. Your Matrix homeserver (Synapse or tuwunel) remains the central instance; the Liman client connects to it. E2EE, federation and existing rooms/channels continue to work. If you already use OpenDesk with Matrix, Liman can be used as an additional or alternative client.
-
Video conferencing (WebRTC / LiveKit)
Meetings run in Liman via a WebRTC backend (e.g. LiveKit). OpenDesk deployments often have no video solution or a different one. Liman complements here: a professional meeting interface with lobby, breakout rooms, screen sharing and optional E2EE – without changing the rest of your OpenDesk infrastructure.
-
Calendar and files
Liman supports multi-backend calendar (CalDAV, Exchange, Open-Xchange) and files via WebDAV. If you already use Nextcloud, Open-Xchange or similar in your OpenDesk environment, these sources can be connected in Liman – appointments and files appear in the same interface as video and chat.
-
Identity and SSO
For enterprise and authorities: Liman can be connected to identity providers such as Keycloak (SAML/OIDC). So user management stays central in your OpenDesk or authority infrastructure; one login for all services including Liman.
Integration scenarios: three typical approaches
Depending on your situation, you can combine Liman and OpenDesk in different ways. The following scenarios describe the most common variants.
-
Scenario A: Liman as frontend to your existing Matrix/OpenDesk infrastructure
You already run a Matrix server (Synapse/tuwunel), optionally LiveKit and Keycloak. Liman is integrated as client and middleware: users work in Liman for video, chat and calendar; the backends (Matrix, video, calendar, identity) remain unchanged. OpenDesk components such as email or files continue to run as before; Liman adds the communication layer with a single, modern interface.
-
Scenario B: OpenDesk and Liman in parallel
You don’t want to replace OpenDesk immediately but complement it gradually. Liman can be introduced in parallel: e.g. first only for video meetings, later for chat and channels. Calendar and files from your existing OpenDesk environment (Nextcloud, OX, etc.) can be displayed in Liman. So you try Liman without a big bang and decide later on further use.
-
Scenario C: Liman as communication hub, OpenDesk for the rest
Liman takes over video, chat and channels completely; email, file management or other OpenDesk modules stay in your familiar environment. Users have a clear split: communication in Liman, rest in OpenDesk – with optional display of calendar and files from OpenDesk in Liman so everything is visible in one place.
Features in detail: What Liman brings to the OpenDesk environment
Liman provides a full communication and meeting interface that fits seamlessly into open stacks. The following points summarise the main features.
-
Matrix chat with E2EE
Full end-to-end encryption for Matrix messages. Only sender and recipient can read – ideal for confidential discussions in authorities and enterprises. Threads, @mentions, rich text and files in chats and channels.
-
Video meetings (WebRTC)
Professional meetings with lobby, breakout rooms, screen sharing and optional E2EE. Web and desktop, without proprietary clients. Based on LiveKit or similar WebRTC backend – operable in your data centre or with an EU hosting partner.
-
Channels, tabs and widgets
Project and topic channels with tabs for files (e.g. WebDAV/Nextcloud), whiteboard (Excalidraw), tasks and embedded web content. So teams work in a structured way – also across organisational boundaries when Matrix federation is used.
-
Calendar and AI assistant
Multi-backend calendar from Nextcloud, Exchange or Open-Xchange in one view. Optional: AI agent for scheduling, meeting preparation and project reports – with your own API key or self-hosted AI, without sharing data with third parties.
Authorities and the public sector
OpenDesk and similar open-source collaboration are used in authorities, defence, healthcare and public institutions. Liman uses the same technical base as established government messengers and can be integrated into these ecosystems.
-
Same base as BwMessenger, Tchap, gematik TI-Messenger
Matrix and WebRTC are the technical foundation of many government and public messengers (e.g. BwMessenger, Tchap, gematik TI-Messenger). Liman builds on the same base – federation or connection to authority Matrix instances is possible in principle, provided the respective security and certification requirements are met.
-
Requirements for VS-NfD, BSI and compliance
For use in environments with high security levels (e.g. VS-NfD), additional certifications and measures are required. Liman can be run in your own infrastructure or with certified partners; the open architecture allows adaptations for authority requirements. We discuss specific certifications and use cases in dialogue.
-
Data protection and EU hosting
Data in the EU, no transfer to third countries without your control. GDPR-compliant processing, optional end-to-end encryption and transparency about storage locations and access – in line with the requirements of authorities and public procurers.
Deployment: Who hosts what?
Liman can be used as SaaS from us or run in your own infrastructure or with your hosting partner. The line between "we host" and "you host" is flexible – especially in combination with OpenDesk.
-
Fully with you or your partner
You run Matrix (Synapse/tuwunel), LiveKit (or equivalent), optionally Keycloak and calendar/files. Liman provides client and server middleware; everything runs in your data centre or with a certified partner. Maximum control and sovereignty.
-
Hybrid: Matrix with you, video and rest with Liman
Minimal variant: Only the Matrix server stays with you (or with your OpenDesk partner); video, calendar and other services can be hosted via Liman. So you start with little infrastructure effort and keep chat under your control.
-
Liman as managed service
You use Liman fully hosted by us – in the EU, with E2EE and clear contracts. Your OpenDesk components (email, files, optionally Matrix) stay where they are; Liman is the interface for meetings and chat. Ideal if you don’t want to run your own video conferencing or Matrix infrastructure.
Liman and OpenDesk compared
Liman and OpenDesk pursue similar goals (openness, data sovereignty) but cover different focuses. The following overview helps with classification.
| OpenDesk | Liman | |
|---|---|---|
| Focus | Collaboration and office environment (email, files, calendar, optionally chat/video) | Communication: video, chat, channels, calendar – one interface |
| Chat / channels | Often Matrix-based, depending on deployment | Matrix (Synapse/tuwunel), E2EE, federation |
| Video conferencing | Default: Jitsi (toolbar: lobby, raise hand, live streaming; recording via optional Jibri; background/transcription disabled in reference deployment) | Core feature: WebRTC (LiveKit), lobby, breakout, optional E2EE |
| Calendar / files | Own module (e.g. OX, Nextcloud) | Connection to existing sources (CalDAV, WebDAV, Exchange) |
| Self-hosting | Yes, typical for authorities/enterprise | Yes, in own infrastructure or with partner |
| Target audience | Authorities, education, enterprises with open stack | Anyone wanting open communication with focus on video/chat – including OpenDesk users |
Why Liman fits with OpenDesk
OpenDesk and Liman share a focus on open technology and control over infrastructure. Liman adds a powerful video and chat layer that fits into existing Matrix and open ecosystems.
-
Same technical base
Matrix is used by many public and open solutions (e.g. BwMessenger, Tchap, gematik TI-Messenger). Liman uses the same base – connection to authority or OpenDesk infrastructures is possible in principle, including federation.
-
Self-hosting and EU
Liman can be run in your own infrastructure or with a trusted hosting partner, like OpenDesk. No dependency on US clouds; data in the EU, GDPR-compliant.
-
Complement, not replacement
Liman doesn’t necessarily replace OpenDesk – it can be used as a dedicated interface for video, chat and calendar while OpenDesk covers other aspects of collaboration. Or you use Liman as a modern alternative focused on communication.
Typical use cases
Organisations that use OpenDesk or similar open-source collaboration often have high requirements for data protection, transparency and independence. Liman addresses these requirements.
-
Authorities and public administration
OpenDesk is used in authorities for secure collaboration. Liman adds video conferencing (including lobby, breakout rooms), E2EE chat and optional connection to authority Matrix instances.
-
Enterprises with open-source strategy
You deliberately use open standards and don’t want proprietary communication clouds. Liman provides a full meeting and chat interface in your stack – with calendar and file integration (e.g. Nextcloud, WebDAV).
-
Hosting partners and data centres
You offer OpenDesk or Matrix-based services. Liman can be integrated as an additional offering for video and chat – same target group, extended feature set.