openDesk Partner Programme: What It Means for SMEs
Editorial note: The information in this article was compiled to the best of our knowledge at the time of publication. Technical details, prices, versions, licensing terms, and external content may change. Please verify the information provided independently, particularly before making business-critical or security-related decisions. This article does not replace individual professional, legal, or tax advice.
A sovereign workplace without Microsoft 365? WZ-IT operates Nextcloud, chat, video conferencing, wiki, project management and single sign-on as managed open source in Germany, see Nextcloud managed hosting. Book a meeting
On 23 September 2026, the Centre for Digital Sovereignty of Public Administration (ZenDiS) launched a partner programme for openDesk. The German federal government's office and collaboration suite had so far mainly been a topic for public authorities. Now, for the first time, private-sector cloud providers and IT service providers can build their own offerings based on the openDesk Enterprise Edition (ZenDiS press release).
For small and medium-sized enterprises, this raises the question of whether openDesk becomes a realistic alternative to Microsoft 365 and through which channel they could obtain it. This article summarises what openDesk is technically, how the partner programme is structured, which requirements and costs are stated in the published documents, and when a self-assembled stack of individual open-source applications is the better fit. All information reflects September 2026.
Table of Contents
- What openDesk is
- The partner programme at a glance
- Requirements and fees for approved partners
- Community Edition and Enterprise Edition
- What the programme means for SMEs
- Technical requirements for self-operation
- When a self-assembled stack fits
- Our approach at WZ-IT
- Further guides
What openDesk is
openDesk is a web-based office and collaboration suite that ZenDiS develops on behalf of the German federal government and has offered on the market since October 2024. ZenDiS is a limited company wholly owned by the federal government, based in Bochum; the shareholding is managed by the Federal Ministry for Digital Transformation and Government Modernisation (ZenDiS).
openDesk is not a newly developed product but an integration of established open-source applications behind a common portal with central user management and single sign-on. The components according to the deployment repository on openCode:
| Function | Component | Licence | Version in openDesk 1.18.2 |
|---|---|---|---|
| File storage | Nextcloud | AGPL-3.0-or-later | 33.0.9 |
| Groupware (mail, calendar, contacts) | OX App Suite (Open-Xchange) | GPL-2.0 (backend), AGPL-3.0 (frontend) | 8.51 |
| Browser-based office | Collabora Online | MPL-2.0 | 26.04.2 |
| Chat | Element with Nordeck widgets | AGPL-3.0, Apache-2.0 | 1.12.18 |
| Video conferencing | Jitsi | Apache-2.0 | 2.0.11146 |
| Project management | OpenProject | GPL-3.0-only | 17.7.2 |
| Knowledge management | XWiki | LGPL-2.1-or-later | 17.10.9 |
| Notes | Notes (Docs) | MIT | 4.4.0 |
| Diagrams | CryptPad with diagrams.net | AGPL-3.0-only | 2026.5.1 |
| Portal and identities | Nubus (Univention) | AGPL-3.0-or-later | 1.21.0 |
The deployment itself (Helmfile and Helm charts) is licensed under Apache-2.0. Minor versions are released monthly, major versions once a year in the third quarter (release management). Version 1.18 of 19 August 2026 added shared mailboxes, among other things, and moved to Nextcloud 33 (openDesk 1.18).
Several of these applications are also available individually: Nextcloud, Element based on Matrix, Jitsi, OpenProject and XWiki. This matters for the decision later on.
The partner programme at a glance
ZenDiS justifies the programme with demand from public administration and the private sector and the aim of accelerating the roll-out (openDesk blog). Since ZenDiS is owned by the federal government, partners are sought through an official approval procedure, a so-called open-house procedure: every applicant who meets the criteria is admitted on uniform, non-negotiable terms, and there is no selection between applicants (partner page).
| Category | Role | Core requirement | Approval procedure |
|---|---|---|---|
| Official Distributor | Value-add distributor, supplies subscriptions to cloud providers and IT service providers, supports resellers | proven experience in marketing open-source solutions | yes |
| Approved Sovereign Service Provider (ASSP) | operates openDesk as SaaS in its own cloud | including a BSI C5 attestation and SEAL level 3 of the European Cloud Sovereignty Framework | yes |
| Approved System Integrator (ASI) | full-service provider for setup and operation (on-premises, managed service) | open-source and Kubernetes expertise, openDesk experience | yes |
| Reseller | IT service provider with offerings based on the Enterprise Edition | no elevated criteria, supported through a distributor | no |
Further key facts from the procedure documents:
- Deadline: The procedure is open until 31 January 2027 for now.
- Further categories: ZenDiS plans additional categories in the coming weeks, including Approved Consulting Partners (ZenDiS press release).
- Role of ZenDiS: ZenDiS does not act as a provider towards commercial end customers itself. Sales, setup, operation and support are delivered by the downstream IT partners, who are the only level in the chain with a direct contract with the end customer.
- Licence flow: Distributors obtain the component licences directly from the vendors according to a uniform price list and pay ZenDiS a usage-based fee for the openDesk integration layer, billed quarterly.
- Public administration: Authorities keep procurement routes without a tender, for example via the govdigital cooperative.
Trade press has described the programme as an opening for private cloud providers (cloudmagazin).
Requirements and fees for approved partners
The model agreements for ASI and ASSP are published as downloads on the partner page. They show how high the bar is for the two approved categories.
| Criterion | Approved System Integrator | Approved Sovereign Service Provider |
|---|---|---|
| Annual fee to ZenDiS | 18,000 EUR plus VAT | 18,000 EUR plus VAT |
| Minimum term | 2 years, then renewed annually | 2 years, then renewed annually |
| Staff and certificates | at least 5 LPIC-3, at least 5 CKA/CKAD/CKS, at least 5 staff with 3 years of production Kubernetes experience | "CNCF Certified Kubernetes - Hosted" certification |
| openDesk experience | at least 5 projects with three- or four-digit user numbers, or work on reference implementations | at least 5 projects, or operation in a high-security environment |
| Management systems | ISO/IEC 20000-1 or equivalent, ISMS under ISO 27001 based on IT-Grundschutz (not required when operated at the customer's site), NIS-2 compliance | ISO/IEC 20000-1, ISO 27001 based on IT-Grundschutz, ISO/IEC 27017, ISO 9001 (each or equivalent, except ISO 27001), NIS-2 compliance |
| Cloud evidence | none | BSI C5 Type 2 (or comparable, e.g. SecNumCloud), SEAL-3 by self-assessment |
| Availability | no requirement | at least 99.9% monthly average |
| Support | German, 8x5, 24x7 for critical services with first response within 30 minutes | German, 9x5, 24x7 for business-critical services |
| Data location | EEA or Switzerland | data centres in Germany or the EEA, including backup |
| Liability insurance | at least EUR 1 million per claim | at least EUR 1 million per claim |
Two points matter for customers. First, the ASI and ASSP agreements only grant the right to use the respective designation in sales. Rights to use the software are not included; the partner obtains the licences through a distributor whose network it must belong to. Second, the criteria suggest that the approved categories will mainly be filled by larger system integrators and cloud providers already working for public administration. The annual fee and the licence costs feed into their offerings.
Community Edition and Enterprise Edition
openDesk is available in two editions. The Enterprise documentation in the repository describes the differences:
| Aspect | Community Edition (CE) | Enterprise Edition (EE) |
|---|---|---|
| Cost | free of charge | subscription, prices on request |
| Licences of core components | open source | the same open-source licences |
| Proprietary modules | none | including Collabora branding and load scaling, Element admin tools, Nextcloud Guard and enterprise patches, OX and Dovecot Pro modules |
| Distribution | public images and charts on openCode | separate registry and licence file |
| Support | community via openCode, no SLA | SLA-backed support, 2nd and 3rd level |
| Target size according to ZenDiS | smaller institutions, first experiences | large organisations with more than 500 users |
The target size is taken from the operating models page. According to that page, the Community Edition offers the same functionality as the Enterprise Edition, but without vendor support.
One detail with practical impact: security patches that Nextcloud releases exclusively for its Enterprise version are only available in the openDesk Enterprise Edition. openDesk also only moves to a new Nextcloud major version once the corresponding Nextcloud Enterprise release is available. That is why openDesk 1.18 runs on Nextcloud 33, while Nextcloud itself has moved on (see Nextcloud 35 upgrade).
What the programme means for SMEs
The partner programme creates a channel for companies that want to use openDesk Enterprise. For small and medium-sized enterprises, four points follow:
| Question | As of September 2026 |
|---|---|
| Can an SME buy openDesk Enterprise today? | Not yet through the programme. The first distributors are going through the approval procedure, and the partner list is empty. Reseller offerings require approved distributors. |
| Who will be the contact? | An IT partner (reseller, ASI or ASSP). ZenDiS does not contract with commercial end customers itself. |
| What does it cost? | Unknown. The distributor price list is confidential. |
| Does the Enterprise Edition fit the company size? | ZenDiS describes it for more than 500 users. How partners will package smaller environments is open. |
Companies looking for a mature alternative to Microsoft 365 from a single source get an integrated interface with one login for all applications in openDesk. This is offset by open points that will only be clarified with the first offerings: prices, minimum purchase volumes, contract terms and whether a partner will offer environments with 30 or 80 users economically.
According to the openDesk FAQ, there are also functional limits that may be relevant for companies:
- Audit-proof archiving is currently not included; integration with document management systems is planned.
- Specialist government applications are not yet connected. This concerns administration, but it shows that integrations with existing business software need to be checked case by case.
- Migration paths from Exchange environments to Open-Xchange are offered. Desktop and mobile apps are available for Nextcloud, Element and Collabora.
Technical requirements for self-operation
The Community Edition is the direct way for companies to use openDesk without a partner. The requirements, however, are designed for data centre operation:
| Area | Requirement according to the documentation |
|---|---|
| Platform | Kubernetes only, CNCF-certified distribution from 1.24, tested with kubespray |
| Hardware (evaluation) | at least 12 x86 CPU cores, 32 GB RAM, ARM not supported |
| Tools | Helm from 3.17.3 (below 4.x), Helmfile from 1.0.0, Helm Diff, yq |
| Network | ingress controller (HAProxy Ingress or ingress-nginx), TCP and UDP ports for Element calls |
| Storage | ReadWriteOnce provisioner, ReadWriteMany for scaling |
| Production | your own production-grade databases, object storage and cache instead of the bundled services |
| Updates | only the latest minor version is supported; minor versions may contain breaking changes |
For ongoing operation, this means monthly updates across ten applications, with migration steps announced in the release notes. If you do not run a Kubernetes platform today, openDesk means building one first. Whether that makes sense for your size is covered in Do we need Kubernetes?.
A current example of the operational effort: on 23 September 2026, ZenDiS reported that the keys for signing container images and Helm charts were accidentally made public during a CI change. All versions before 1.19.0 are affected. According to ZenDiS, no compromise is known. Operators should not obtain openDesk from third parties until then and should update immediately once 1.19.0 is released (security notice). As of late September 2026, 1.19.0 has not yet been released; the current releases are 1.18.2 and 1.17.4 (releases). Anyone running openDesk themselves needs to follow such notices and adjust signature verification.
When a self-assembled stack fits
openDesk bundles applications that are also available individually. For many SMEs, the question is therefore not "openDesk or Microsoft 365" but "integrated suite or selected individual applications".
| Criterion | openDesk (Enterprise via partner) | Stack of individual applications |
|---|---|---|
| Interface | one portal, one login, coordinated navigation | single sign-on via an identity provider, separate interfaces |
| Scope | fixed package with ten components | only the applications you need |
| Platform | Kubernetes | VM, container or Kubernetes depending on the application |
| Update cycle | monthly, set by ZenDiS | plannable per application |
| Choice of components | defined by ZenDiS | free, e.g. Mattermost instead of Element or a different mail server |
| Availability for SMEs | depends on partner offerings, none yet as of September 2026 | via vendors, service providers or self-operation |
A self-assembled stack fits when at least one of these points applies:
- Only part of the suite is needed. Many companies start with file storage and browser-based office. Nextcloud with an office component covers this; the choice between Nextcloud and its alternatives is covered in the file storage comparison.
- Existing tools should stay. If you already use Mattermost, a wiki or a ticket system, you do not replace everything at once.
- The number of users is well below 500. A stack of a few applications on virtual machines is then often easier to operate than a Kubernetes cluster.
- Specific components are already set. Examples: your own mail server (see Mailcow, Stalwart or Mailu), a particular wiki (see company wikis compared) or a project tool (see Jira alternatives).
openDesk is the better fit when an organisation has several hundred users, a uniform interface matters more than free choice of components, and a partner with enterprise support is available. For organisations that work closely with public authorities, compatibility with their openDesk environment can be an additional argument, for example with federated chat via Element.
The connecting element of an individual stack is the identity provider. With Keycloak or Authentik, users sign in once and reach all applications; the comparison of identity providers is covered in Authentik vs. Zitadel.
Our approach at WZ-IT
WZ-IT operates the individual open-source applications that make up a sovereign workplace.
- Assessment. Number of users, current tools, required functions, protection needs of the data and dependencies on Microsoft services.
- Classification. Check whether openDesk via a partner, the Community Edition in self-operation or a stack of individual applications fits the requirements.
- Choice of applications. For an individual stack: file storage, office component, chat, video conferencing, wiki, project management and identity provider according to usage.
- Setup and migration. Installation in Germany, single sign-on, data transfer from existing systems and a planned go-live.
- Operation. Updates, daily backups, technical 24/7 monitoring and support as managed open source from €129.90 net/month per workload. Required vendor licences are listed separately.
Where several applications should run on a container platform, Kubernetes is an option. For most SME environments, individual, separately operated instances are sufficient.
Further guides
- Nextcloud, Seafile, OpenCloud or ownCloud, file storage compared by licence, operation and ownership.
- Nextcloud 35 upgrade, upgrade path, PHP and database.
- Mailcow, Stalwart or Mailu, running your own mail server.
- Company wikis compared, BookStack, Wiki.js, XWiki and Docmost.
- Self-hosted Jira alternatives, OpenProject, Plane and Vikunja.
- Do we need Kubernetes?, when a container platform pays off.
- Managed open source, the hub with all managed applications.
Wait for openDesk or start now with individual applications? We assess your requirements and operate Nextcloud, chat, video conferencing, wiki and single sign-on in Germany. Book a meeting
Sources
- ZenDiS, press release: openDesk partner programme for cloud providers and IT service providers launches (23 Sep 2026)
- openDesk, become a partner: categories, procedure and documents
- openDesk blog, partner programme launches
- openDesk, operating models
- openDesk, FAQ
- openDesk blog, openDesk 1.18 (German)
- openDesk blog, security incident: new signing keys for openDesk 1.19.0
- openCode, openDesk deployment automation
- openCode, openDesk Enterprise Edition
- openCode, openDesk requirements
- openCode, openDesk release management
- openCode, openDesk releases
- cloudmagazin, openDesk opens up to private cloud providers (German, 27 Sep 2026)
Plan a sovereign workplace for your company
We assess whether openDesk or a stack of individual open-source applications fits your size, and we set up and operate the applications you choose.
Frequently Asked Questions
Answers to important questions about this topic
The Centre for Digital Sovereignty of Public Administration (ZenDiS) launched a partner programme for openDesk on 23 September 2026. For the first time, private-sector cloud providers and IT service providers can build their own offerings based on the openDesk Enterprise Edition. There are three approved categories (Official Distributor, Approved Sovereign Service Provider, Approved System Integrator) plus resellers without an approval procedure.
No, not exclusively any more. openDesk was developed for public administration, and according to ZenDiS the focus remains on federal authorities. With the partner programme, ZenDiS explicitly addresses demand from the private sector as well. The Community Edition was already free for any organisation to use.
Not for the Community Edition. It is available free of charge on openCode and can be operated under your own responsibility, with community support. For the Enterprise Edition with SLA-backed support, companies will go through partners from the programme.
As of late September 2026, no. According to opendesk.eu, the first Official Distributors are still going through the approval procedure, and the list on the partner page is empty. Resellers can only make offers once distributors are approved. The procedure is open until 31 January 2027 for now.
There are no public prices. The distributor price list is confidential and only provided after the approval review. What is known: Approved System Integrators and Approved Sovereign Service Providers pay ZenDiS 18,000 euros net per year for the right to use the designation, with a minimum term of two years. They obtain the software licences separately through a distributor.
Not in the sense of a product certification. The ASI and ASSP agreements only grant the right to use the respective designation in sales. The prerequisite is a criteria catalogue with evidence such as certified Kubernetes engineers, ISO/IEC 20000-1 and openDesk references. Rights to use the software are not part of these agreements.
No. According to the deployment documentation, openDesk is a Kubernetes-only solution and requires a certified Kubernetes cluster from version 1.24. For an evaluation, the documentation lists at least 12 CPU cores (x86, ARM is not supported) and 32 GB RAM. Production use requires your own production-grade databases and storage services.
ZenDiS describes the Enterprise Edition as designed for large organisations with more than 500 users. ZenDiS positions the Community Edition for smaller institutions and first experiences. For many SMEs, the number of users is therefore below the target size of the Enterprise Edition.
Not in every respect. openDesk covers email, calendar, files, browser-based office, chat, video conferencing, wiki and project management. According to the openDesk FAQ, audit-proof archiving is currently not included; integration with document management systems is planned. Business applications and integrations need to be checked case by case.
On 23 September 2026, ZenDiS reported that the keys used to sign container images and Helm charts were accidentally made public during a CI modernisation. All versions before 1.19.0 are affected. ZenDiS is not aware of any compromise. The recommendation is not to obtain openDesk from third parties and to update to 1.19.0 immediately once it is released.
Written by
Timo Wevelsiep
Co-Founder & CEO
Co-Founder of WZ-IT. Specialized in cloud infrastructure, open-source platforms and managed services for SMEs and enterprise clients worldwide.
LinkedInLet's Talk About Your Idea
Whether a specific IT challenge or just an idea - we look forward to the exchange. In a brief conversation, we'll evaluate together if and how your project fits with WZ-IT.
Arrange a callback
Companies worldwide trust WZ-IT
