OpenTalk

🩺 Vitals

• 🟢 Last active: 2026-07-27
• 📦 Latest release: No tagged releases yet
• 🌟 Stars: 4

🏗️ Profile

• Official: opentalk.eu
• Source: gitlab.opencode.de/opentalk
• License: EUPL 1.2
• Deployment: Docker
• Data Model: PostgreSQL / Redis / Keycloak (identity) / Janus (media SFU)
• Jurisdiction: Germany 🇩🇪 / EU 🇪🇺 (OpenTalk GmbH, Heinlein Gruppe, Berlin)
• Compliance (SaaS): GDPR Ready | BSI IT Security Label
• Compliance (Self-Hosted): GDPR Ready (app-level controls; infrastructure user-managed)
• Complexity: Medium (3/5) - Docker Compose single-server; full stack adds Keycloak, PostgreSQL, Redis and a Janus SFU
• Maintenance: Medium (3/5) - Multiple services to patch and coordinated component releases
• Enterprise Ready: High (4/5) - Keycloak SSO/LDAP/AD and RBAC in the open build; multi-tenancy, HA scaling and audit-proof voting via the paid Enterprise edition

1. The Executive Summary

What is it? OpenTalk is a self-hosted, browser-based video conferencing platform: meetings, screen sharing, moderated rooms, shared notes, a whiteboard and polls or votes, all in one application. It is built by OpenTalk GmbH, part of the Heinlein Gruppe, the German operator behind mailbox.org, and is aimed squarely at the European public sector, education and privacy-conscious enterprises. The source is EUPL-licensed and published on openCode, the German public administration's official code platform. It runs as a managed SaaS (opentalk.eu) or self-hosted on your own infrastructure.

The Strategic Verdict:

• 🔴 For institutions that need turnkey high availability or multi-tenancy from the open build: Caution. The open-source Community Edition is framed for single-server deployment; multi-tenancy, automated and containerized scaling, audit-proof voting and vendor support require the paid Enterprise edition. A large body that wants HA out of the box is buying the Enterprise contract, not running the Community build alone.
• 🟢 For European public bodies and privacy-conscious organizations leaving Zoom or Teams: Strong Buy. A German GmbH outside US CLOUD Act reach, EUPL-licensed, GDPR-aligned, and the first video service to carry Germany's BSI IT security label. Self-host it for full data sovereignty, with Keycloak-based SSO, LDAP and Active Directory integration already in the open build.

2. The "Hidden" Costs (TCO Analysis)

3. The "Day 2" Reality Check

🚀 Deployment & Operations

• Installation: The ot-setup repository provides a Docker Compose deployment for a single server, the documented path for self-hosters. The stack is a set of services: the controller, PostgreSQL, Keycloak for identity, Redis and a Janus WebRTC SFU for media. Kubernetes-based scaling is under active development and bundled with the Enterprise edition.
• Scalability: A single-server Docker deployment comfortably serves a department or a mid-sized public body. Horizontal scaling and multi-tenancy move you toward the Enterprise edition. As with any WebRTC platform, the media layer (the Janus SFU) is the main capacity driver, so plan bandwidth and CPU around concurrent video, not registered users.

🛡️ Security & Governance (Risk Assessment)

• Jurisdiction & Sovereignty: OpenTalk GmbH is a Berlin-registered German company under the Heinlein Gruppe, which places the vendor, the data and the trademark squarely in the EU and beyond the reach of the US CLOUD Act. The hosted service earned Germany's BSI IT-Sicherheitskennzeichen (DIN SPEC 27008), the first video-conferencing service to do so, and the source lives on openCode, the German public administration's code platform. For a European public body, this is the uncommon case where the vendor's jurisdiction is a feature, not a risk to manage.
• The Compliance Shift: The hosted service is run by a German GmbH under GDPR, with the BSI label as an independent assurance signal. Self-hosting moves the ISMS burden to you: you secure PostgreSQL, Keycloak, Redis, the Janus media server and the host operating system. OpenTalk supplies the application-level privacy controls (data minimization, role-based access, Keycloak SSO/LDAP/AD), but a certified compliant posture on your own infrastructure is something your team configures and operates, not a badge inherited from the vendor.
• License & Open-Core Reality (EUPL): The core is EUPL 1.2, the EU's official copyleft licence, and its reach is AGPL-grade: the EUPL treats providing network access to the software as "communication," so a modified OpenTalk you offer as a service triggers the source-sharing obligation. The mitigating feature is the EUPL compatibility clause, a one-way path that lets combined works be distributed under the GPL, AGPL, LGPL or MPL, flexibility the AGPL does not offer. Separately, the open build is single-server by design: multi-tenancy, automated scaling and audit-proof voting are the genuine paywall, sold as the Enterprise edition. SSO and directory integration are not paywalled (they ship in the open build), so the open-core line here is scaling and governance-at-scale, not basic access control.

4. Market Landscape

🏢 Proprietary Incumbents

• Zoom: The dominant SaaS video platform, US-based and therefore subject to the CLOUD Act on data it controls. European public bodies switch to OpenTalk to escape per-seat costs and US data exposure in a single move.
• Microsoft Teams: The enterprise collaboration incumbent, bundled with Microsoft 365 and deeply tied to its telemetry and data-residency terms. OpenTalk is the sovereign, self-hosted answer for organizations that cannot accept those terms.

🤝 Open Source Ecosystem

• Jitsi Meet: The Apache-licensed, widely deployed self-hosted conferencing platform, but maintained by the US corporation 8x8. OpenTalk trades some of that ubiquity for an EU-sovereign steward and a public-sector compliance posture.
• BigBlueButton: The LGPL conferencing platform optimized for the virtual classroom. A better fit for structured teaching, where OpenTalk targets general public-sector meetings with integrated notes, whiteboard and voting.