openDesk is intended to help public agencies bring information together across office applications and keep working without a connection to the public internet. On October 9, Germany’s Center for Digital Sovereignty in Public Administration, known as ZenDiS, announced two proofs of concept for that purpose. For government organizations, the particular appeal is that AI assistance and the choice of operating environment are being considered together.
Key takeaways
- ZenDiS will demonstrate prototypes for AI assistance and isolated openDesk operation at the Smart Country Convention in Berlin on October 13–15, 2026.
- A daily briefing is designed to combine information from email, calendars, project management, and notes.
- An MCP interface connects the language model and applications. It does not replace carefully configured access rights.
- Both projects are on the roadmap. That does not establish a generally available AI rollout or a specific model choice.
From an office portal to shared work context
openDesk already brings together different tools for everyday government work. Its official product overview lists Nextcloud for files, Collabora Online for documents, OpenProject for projects, and OX applications for email, calendars, and contacts. This matters for the new AI concept: The potential benefit lies between applications, rather than just in an additional chat window.
Preparing for a meeting is one possible example. A calendar contains the appointment, an email records the latest agreement, and project management holds outstanding tasks. People currently have to gather this information themselves. A useful briefing could shorten that preparation while showing the context behind each item. This is a possible application of the approach, not a productivity improvement we have measured.
ZenDiS is working with a development team from Open-Xchange on the AI connection, with support from OpenProject. Beyond summaries, the plans include sequences of actions across applications. Whether the result is a new task, a changed appointment, or merely a suggestion makes a substantial difference in everyday work. The announcement describes a direction, but does not yet provide a complete feature list for a finished product.
A sensible first trial for a public agency would therefore have a limited scope: a briefing for a clearly defined area of work, with results that employees can compare against the underlying entries. The measure would be whether the overview reliably saves time and makes unresolved issues visible. An impressive demonstration alone does not answer that question.
What MCP connects and what it leaves open
MCP stands for Model Context Protocol. In simple terms, it standardizes how an AI application accesses data and tools in other programs. The official architecture distinguishes the AI application, its connections, and the servers that provide context or functions. Such a server can run locally or remotely. The MCP label therefore does not establish where data is stored.
For openDesk, this shared interface is interesting because each connection does not have to be reinvented from scratch. It can make integrating different components easier. At the same time, the protocol does not determine how an application uses its language model or processes the context it receives. Which information goes to which model remains a decision made in the specific implementation.
Access rights do not automatically follow from an open interface, either. The MCP tools specification requires server-side access controls and recommends visible inputs and human confirmation for sensitive operations. For a government assistant, that would mean, for example, that reading an existing appointment and sending a new invitation require different permissions. This is a design requirement, not an already demonstrated property of the openDesk prototype.
Choosing an appropriate language model therefore involves a separate decision. Our overview of Aleph Alpha’s open Kolibri model explains another element of this debate. However, the openDesk announcement does not identify that model as a component. Openness of the model, office software, and their connection are related but separate questions.
Working without the internet does not automatically mean local AI
The second proof of concept concerns isolated operation, often described as an air gap. In this setup, an environment is physically or logically separated from the public internet. ZenDiS plans to demonstrate a local openDesk server accessed by several tablets. According to the organization, all openDesk functions remain available in this demonstration.
The scope of that statement matters. Local collaboration between accessible devices is different from communicating with arbitrary organizations outside the isolated network. Without an appropriate connection, for instance, a new message from the public internet will not arrive. An air gap can separate a working environment, but does not replace its power supply, an accessible server, or maintained datasets.
Nor do the two demonstrations announced alongside each other establish that the AI assistant runs entirely offline using a local language model. That would require information about the model, computing resources, and data paths. The announcement does not make that specific commitment. Procurement should therefore address isolated office operation separately from isolated AI.
Who should take a closer look
The project is particularly relevant to public IT service providers and organizations that want to operate their collaboration systems themselves or reduce dependencies. According to its operating-model overview, openDesk supports deployment on an organization’s own infrastructure as well as managed cloud offerings. A freely available Community Edition also serves smaller organizations that want to gain their own experience. However, this does not promise that the announced AI prototypes are already included in that edition.
At the trade show, it is therefore worth examining specific workflows: Which sources appear in the briefing, which permissions apply, and which action remains a suggestion? A clear explanation of what actually works inside the isolated network would be equally revealing. Progress would become tangible if connecting existing office applications produced understandable relief for employees while allowing the administration to continue making its own operating decisions.