Video conferencing for the public sector and for political organizations. Operated securely, either independently in-house or hosted in Germany, and fully GDPR-compliant, of course.
Your data protection airbag - OpenTalk is GDPR-compliant and provides true information security, data protection, and digital sovereignty. The latest authentication and encryption technologies shield your data and that of all other users.
OpenTalk is Open Source software, supported by security experts and our community. Code review & BSI certification are on our roadmap.
This is how public money should drive public code - Made in Germany
Thanks to a great user interface, well-integrated functionality and intuitive operation, OpenTalk drives productivity and user acceptance.
Build-in use cases like podium discussions or audit-compliant voting are specifically designed for the public sector and political organizations.
Personalization offers an enjoyable conferencing experience, and promotes user acceptance.
OpenTalk provides a comprehensive set of open APIs and can be fully integrated with existing systems. This includes provisioning as well as user and room management.
OpenTalk can integrate external streaming services to broadcast sessions to a wider audience.
Operate OpenTalk at your own premises or benefit from our secure SaaS offer, hosted on servers in Germany.
„OpenTalk is intuitive to use for participants and moderators alike.“
Solutions for politics and the public sector
The Dashboard presents important information in a structured fashion. This includes all scheduled meetings (your own and those you are invited to attend), clearly presented and arranged in a calendar view.
Recurring or important meetings can be highlighted and accessed through dashboard shortcuts. New meetings can be created instantly, using predefined templates.
OpenTalk supports multi-moderator meetings. Conferences, workshops, and plenary debates can be conducted more effectively if the effort of moderating these sessions is shared among several privileged moderators. For example, this would resemble the tasks carried out by a council of elders in parliament, or the main board members in a general assembly meeting.
An event console, which is visible to the moderator team, helps coordinate all pending tasks and messages. There is also a separate chat window for exclusive use by the moderation team.
Video and audio streams can be recorded after consent has been obtained by all attendees of a session. The related media files can then be downloaded afterwards.
The whiteboard and chat contents can be included in a recording.
Whether anonymously or not, as a quick way of gauging the mood in the room, or audit-proof for real commitment and impact: OpenTalk is ideal for data protection-compliant, secure decision-making. When it counts, for example at association, advisory board or political meetings.
Participants cannot vote more than once, and results cannot be manipulated by moderators. Even when voting anonymously, participants can use their "voting tokens" to double-check that their vote was counted correctly.
Every conference benefits from good time management. If conferences are time-limited, the remaining time can be emphasized with a color, and displayed in addition to the regular time (Like a "scrum clock"). Participants can be assigned a speaking time to avoid individual speakers to overrun their allocated timeslot - this also works with auto moderation and talking stick activities.
OpenTalk can keep track of speaking times, even if there are many participants in a session, and automatically call everyone in turn to contribute. While one participant is still speaking, the next speaker will receive a visual indication that they are up next. Helping you to conduct meetings efficiently without confusion - that's OpenTalk.
Participants who are added later will be included in the current list of speakers appropriately, or automatically added to the end of the list. A moderator can also manually rearrange the list of participants to allow individuals to speak earlier or later, if required.
In addition to the common "Raise hand" gesture, OpenTalk supports many more features, such as choosing from different levels of urgency, which can be used to raise a point of order, or request topics to be added to the agenda, for example.
OpenTalk comes with speaker lists built in, so that moderators can manage individual speaker contributions as intended and give everyone the speaking time they are entitled to.
In virtual instruction, teachers can measure the engagement level in their classroom by inspecting and reordering the participant list to see the total speaking time for each participant, for example.
OpenTalk comes with a dedicated telephony feature - beside using the regular client over the Internet, participants can also dial in using a regular phone (audio only). OpenTalk can also be connected as a SIP client to an existing in-house telephone system or an external SIP provider. By doing so, conferences can be allocated a dedicated telephone number, and participants can dial in exclusively by phone or in combination with a computer that uses an Internet connection.
On our roadmap:
Future support for multiple phone numbers per conference, to offer dial-in worldwide. Registered participants to be automatically identified by their telephone number, and to have their name displayed accordingly.
Video streams can be exported to external streaming providers. Primarily, RTMP(S) is used, which is supported by Youtube and many other streaming services. As an alternative to exporting to an external service, OpenTalk also provides a dedicated light-weight streaming server that can be accessed through a web browser. All available authentication options can be implemented, if required. On request, features such as a "chat board", or "question board" can be implemented for external participants, while passive stream participants can submit questions to the moderator outside of the "official" stream of chat messages.
OpenTalk comes with open and well-documented APIs. Clearly specified interfaces enable seamless integration into existing platforms and products. All access to features is subject to strict authentication and authorization.
REST-based APIs are available for provisioning of users and rooms, configuration, metrics, and reporting.
This enables a rich set of use cases beyond pure video conferencing and makes OpenTalk a versatile video communication solution for third-party applications.
OpenTalk supports the operation of conferences in a cluster of federated conference servers, which enables the creation of security zones. A new conference can be bound to a specific conference server, which hosts the meeting. Participants need to access this specific server to attend the meeting. This way, some conferences can be accessed only from pre-defined locations, such as the computers of your in-house network. Thus, any security-sensitive content will be protected by an additional level of security.
On the other hand, open conferences with external participants can be held in a way that optimizes traffic, using video bridge servers that are freely accessible over the Internet.
OpenTalk is based on an architecture that has been developed from scratch and that reflects the current state of the art in security, authentication, encryption, scalability and flexibility.
A central "controller" supervises the logon and authentication of all users and confirms their authorization to access sessions. After the initial authentication has been successful, another authorization check is performed on the basis of an OpenID Connect token, for each access: Whether it is retrieving video streams from an ongoing conference or transmitting required control information, chat messages, voting participation or using any other feature within the scope of participation. Nothing takes place without token-based authorization.
Only after logging in will the client connection be internally forwarded to the specific video bridge from which the respective conference content is accessible. The bridge will only ever receive authorized RTC connections, which ensures that only trustworthy and authorized audio/video data are being disseminated. The internal systems can thus be protected and hardened against unauthorized access and denial-of-service attacks by way of a multi-level system ("onion skins").
Control commands, such as microphone on/off and camera on/off, are first authorized by the user client and sent to the controller, which then forwards them to the responsible video bridge with the help of a so-called message broker. The message broker has been designed for high-performance scaling and can also simultaneously process the message volumes that occur in those conferences that have a very high number of participants.
For each new conference, a separate video bridge instance is started in a container, which processes all security-sensitive data locally within the container. This protects against unauthorized access from other installations/conferences and, by dismantling the conference container upon termination, also ensures that all data stored at runtime is securely and reliably deleted at the end of the conference.
in terms of streaming quality, modern standards and license-free open source video codecs such as VP8, VP9 or AV1 are efficient when it comes to data consumption and facilitate a good, low-latency conference experience, even with limited or fluctuating available network bandwidths. The connection quality is continuously monitored and the connection parameters are dynamically adjusted to the available bandwidth.
For OpenTalk, a completely new architecture was developed from scratch that offers the latest in security, authentication, encryption, scalability, and flexibility: A state-of-the-art architecture from the 2020s.
Since clients subscribe and receive only those video streams that are currently played back, the feeds of those participants that are not displayed have only negligible impact on client scale-out in terms of computing resources and bandwidth. On the server side, they generate incoming bandwidth, but computing-wise, OpenTalk scales very efficiently since there is no image processing required on the server side.
Since any number of video bridges can be used, and each conference is launched in its own container on a horizontally scalable Kubernetes infrastructure, large scale-out will only be limited by the provision of further Kubernetes nodes by the operator. There is support for utilizing cloud providers for this, and these can be automatically connected.
A large number of (passive) viewers can be reached by connecting streaming platforms such as NC3 or Youtube. This is planned for an upcoming release.