Sparks and OpenDesk

Sparks in your open stack

• Matrix and open standards

  Sparks builds on Matrix for chat and channels, like many open-stack solutions. If you already use Matrix or OpenDesk, Sparks 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. Sparks uses the same open protocols and can be integrated into this stack.

• Shared values with Sparks

  Sparks shares the focus on open protocols (Matrix, WebRTC), EU data, optional end-to-end encryption and self-hosting. So the collaboration of Sparks with OpenDesk is not competition but a meaningful complement: Sparks brings a modern, single interface for video, chat and calendar into your existing open stack.

Technical interfaces: How Sparks and OpenDesk work together

Sparks connects to your existing services via standardised protocols. If you already run OpenDesk or similar infrastructure, you can connect Sparks to the same backends – without duplicate structures.

• Matrix (chat and channels)

  Sparks uses Matrix for chat and channels – as do many OpenDesk installations. Your Matrix homeserver (Synapse or tuwunel) remains the central instance; the Sparks client connects to it. E2EE, federation and existing rooms/channels continue to work. If you already use OpenDesk with Matrix, Sparks can be used as an additional or alternative client.

• Video conferencing (WebRTC / LiveKit)

  Meetings run in Sparks via a WebRTC backend (e.g. LiveKit). OpenDesk deployments often have no video solution or a different one. Sparks 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

  Sparks 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 Sparks – appointments and files appear in the same interface as video and chat.

• Identity and SSO

  For enterprise and authorities: Sparks 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 Sparks.

Features in detail: What Sparks brings to the OpenDesk environment

Sparks 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.

Deployment: Who hosts what?

Sparks 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. Sparks 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 Sparks

  Minimal variant: Only the Matrix server stays with you (or with your OpenDesk partner); video, calendar and other services can be hosted via Sparks. So you start with little infrastructure effort and keep chat under your control.

• Sparks as managed service

  You use Sparks fully hosted by us – in the EU, with E2EE and clear contracts. Your OpenDesk components (email, files, optionally Matrix) stay where they are; Sparks is the interface for meetings and chat. Ideal if you don’t want to run your own video conferencing or Matrix infrastructure.

Why Sparks fits with OpenDesk

OpenDesk and Sparks share a focus on open technology and control over infrastructure. Sparks 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). Sparks uses the same base – connection to authority or OpenDesk infrastructures is possible in principle, including federation.

• Self-hosting and EU

  Sparks 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

  Sparks 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 Sparks as a modern alternative focused on communication.