openDesk partners and Open Productivity: who will run the suite
The openDesk partner programme and Open Productivity Software GmbH change who runs the suite. What the terms mean for Swiss and EU buyers, and what to do.
On 13 October 2026, Germany’s Centre for Digital Sovereignty (ZenDiS) announced the first approved partners of its openDesk partner programme: STACKIT, to offer the suite as a service, and B1 Systems and DACHS IT, as system integrators. The same day, six of the suite’s component vendors announced Open Productivity Software GmbH to take openDesk to businesses and international markets. On 15 October, Handelsblatt quoted ZenDiS co-managing director Leonhard Kugler as saying that ZenDiS had to turn down a large share of requests in the past year. For a Swiss or EU organisation weighing openDesk, the software is not what is scarce: the question is who operates it, to what standard and where.
This post covers the announcements, the suite, the partner terms, the Swiss routes, what running it takes and what to do. Most sources are in German, so translations are ours, and facts are as of 24 October 2026.
What did ZenDiS and Open Productivity announce in October 2026?
ZenDiS, wholly owned by the German federal government, launched openDesk in October 2024. On 23 September 2026 it opened a partner programme that lets private cloud and IT service providers build their own openDesk Enterprise offers for the first time. The model agreement states the shift plainly: ZenDiS intends “in future no longer to act itself as an operational service provider to end customers”, and set-up, integration, operation and support pass to the partners (documents on openDesk’s partner page).
| Date | What | Source | Status |
|---|---|---|---|
| 23 September 2026 | Partner programme opens, in three categories | ZenDiS | Decided |
| 13 October 2026 | First approved partners: STACKIT (SaaS), B1 Systems and DACHS IT (integrators) | ZenDiS | Decided |
| 13 October 2026 | Collabora, Element, Nordeck, Open-Xchange, Univention and XWiki announce Open Productivity | Open Productivity | Vendor statement |
| 15 October 2026 | Licences for “more than 200,000” office workplaces sold; a large share of requests turned down | Handelsblatt, citing ZenDiS | Reported |
| Early 2027 | STACKIT’s production offer to start | ZenDiS | Planned |
| 31 January 2027 | Partner applications close, “initially” | ZenDiS | Set by ZenDiS |
The figures measure different things: Handelsblatt’s are licences sold, while ZenDiS’s release of 13 October says 100,000 administration workplaces are equipped. Kugler’s explanation, as the paper quotes it: with its previous set-up, ZenDiS “could not meet the enormous demand”. Handelsblatt credits the International Criminal Court’s choice of openDesk with making the suite known overnight (see our post on the ICC sanctions). Handelsblatt also reports, as Linux-Magazin relayed on 19 October, that Deutsche Telekom, IONOS and Bechtle are to follow as partners; as of 24 October 2026 we found no ZenDiS announcement of them.
Open Productivity targets companies and critical infrastructure operators, with Adfinis, the msg group and Smile as launch partners. Its partner model calls for “a single point of contact for each customer project” for consulting, migration, integration and operations, and its “planned deployment options include the customer’s own infrastructure and cloud environments”.
What is in openDesk, and what does the suite add?
openDesk’s operations documentation lists ten components:
| Function | Component |
|---|---|
| Files | Nextcloud |
| Office editing | Collabora |
| Chat | Element, with Nordeck widgets |
| Video meetings | Jitsi |
| Projects | OpenProject |
| Mail, calendar and contacts | OX App Suite |
| Knowledge | XWiki |
| Portal and identity | Nubus, from Univention |
| Notes | Notes (also called Docs) |
| Diagrams | CryptPad with diagrams.net |
The suite adds integration: one portal and one identity layer in front of every component, with versions tested together and released monthly. The Enterprise Edition adds the vendors’ enterprise versions and support under service level agreements that can extend to round-the-clock cover (operating models). ZenDiS designs it “for large organisations with over 500 users”. The free Community Edition has the same functions with community support.
What does the openDesk partner programme require?
The September release named a BSI C5 attestation and SEAL level 3 as examples; the criteria catalogue in the model agreements (version 1.1) reads as a description of operating openDesk properly.
| Criterion | Sovereign Service Provider (SaaS) | System Integrator (on-premises, managed) |
|---|---|---|
| Security | ISO/IEC 27001 on BSI IT-Grundschutz, ISO/IEC 27017, NIS2 compliance, a BSI C5 Type 2 report (or comparable) under a year old | ISO/IEC 20000-1 or equivalent; NIS2 compliance where it applies |
| Sovereignty | SEAL-3 (EU Cloud Sovereignty Framework), self-assessed or third-party | No criterion |
| Platform | CNCF Certified Kubernetes (Hosted), ISO/IEC 20000-1, ISO 9001 or equivalent | Five Linux-certified and five Kubernetes-certified staff, three long-standing open-source contributors |
| Availability | At least 99.9% a month, maintenance at most four hours a month | No criterion |
| Support | In German on weekdays, round the clock for business-critical services such as mail | In German or the local language on weekdays, round the clock for critical services |
| Location | Servers, backups and disaster recovery in Germany or another EEA state; personal data in the EEA or Switzerland | Personal data in the EEA or Switzerland |
The agreement grants a label, not rights to the software: partners buy their licences from a distributor. ZenDiS may change the catalogue with at least 180 days’ notice. SEAL-3, in the European Commission’s words, means “immune from supply chain disruption from non-EU third parties”.
Can a Swiss organisation get openDesk today?
Yes, but the routes differ.
The SaaS label is tied to the EEA. A Sovereign Service Provider must host openDesk only in Germany or another member state of the European Economic Area, backup and disaster-recovery sites included. Switzerland is not in the EEA. On our reading, a provider hosting openDesk only in Switzerland cannot carry that label under version 1.1, although personal data may be processed in Switzerland.
The integrator route has no such clause. A System Integrator may deliver openDesk on premises or as a managed or SaaS service, and on our reading its criteria set no data centre location; ZenDiS says providers without a label will in future also be able to build offers on the Enterprise Edition. B1 Systems, which has been ZenDiS’s general contractor for operating openDesk, offers on-premises operation, and DACHS IT will.
The licence route is being built. The Zentrum SDS, a centre for digital sovereignty at the Bern University of Applied Sciences (BFH), started on 28 April 2026 with 31 contributors. It names obtaining openDesk licences from Germany as a hurdle for Swiss organisations, and its openDesk workstream lists among its prioritised activities “Contract negotiations with ZenDiS so that Swiss organisations can acquire the openDesk Enterprise Edition”, through a master licence for Switzerland bundled by the centre. As of 24 October 2026 no licence has been announced.
The federal and Zurich programmes are testing, not yet choosing. The Federal Chancellery’s pilot ran on openDesk, but its programme for about 3,000 staff from the end of 2027 names no product (our post on the federal workplace). The armed forces’ Cyber Command, by contrast, planned to equip all its staff with openDesk by October 2026, Netzwoche reported on 13 July 2026, citing Republik. On 21 May 2026 the City of Zurich reported a study finding that openDesk meets many simple office needs, such as mail, chat and file storage, but could not yet replace Microsoft 365 for the city, any more than a comparable sovereign solution could, because of dependencies on existing infrastructure and specialist applications.
What does running openDesk take?
openDesk runs on Kubernetes, and its documentation recommends the Enterprise Edition for production and says “basic knowledge of Kubernetes and DevOps processes is required”. The technical report of the Federal Office of Information Technology, Systems and Telecommunication (FOITT) records what that meant in the federal proof of concept:
- Platform. The FOITT runs OpenShift, not plain Kubernetes. openDesk is not optimised for it, according to its vendor, and about 100 container images had to be configured; the report notes the open code made that possible.
- Updates. Releases come monthly. Scanning and approving the images, which the FOITT requires for every update, took about 12 hours per update, and about three working days with preparation.
- Backups. The proof of concept had no established backup and restore processes, and an upgrade from version 1.4 to 1.8, made around the switch from the Community to the Enterprise Edition, lost data; the environment was rebuilt.
- Sign-in. The federal login worked in the browser, but Thunderbird and WebDAV clients needed app passwords because OAuth2 and OIDC were not integrated throughout.
Test users rated the browser version 5.4 out of 6. The backend ran on a best-effort basis, so some of this reflects a test, but the partner catalogue asks for much the same: a certified Kubernetes platform, documented change and operations processes, backup sites in Germany or the EEA and support hours.
Open source makes operators interchangeable, not optional
Proprietary vendors sell through partners too. The difference is what the label controls. With openDesk it governs who may market the Enterprise Edition as an approved partner, not who may run the software: the code is published, the Community Edition is free to deploy, and each component is an open-source project anyone can operate. A proprietary suite decides alone who may run it, where and on what terms, and even its on-premises edition depends on the vendor for licences and updates. With openDesk, the software stays the same when the operator changes: the property behind the operational autonomy the Swiss Government Cloud tender asks of its private cloud, and the direction the EMBAG set for federal code.
Open source does not run itself, though, and the suite is more than its parts. Run separately, the components need someone to do the integration the suite provides: single sign-on in front of each app, Collabora inside Nextcloud, meetings started from chat, a release routine per project. Mail is its own decision either way.
Separate components have advantages too. You can start with one service now, on your own premises, without waiting for a Swiss master licence or reaching the 500-user scale the Enterprise Edition is built for, and you can choose per function. Five of the ten components are the same projects when run alone, so a later move to the suite carries the data between installations of the same projects; sign-in and any mail move separately. Either way, what decides the outcome is what the FOITT’s report and the ZenDiS catalogue point to: who applies the monthly updates, who proves the backups restore, and who answers at night.
What to do, and by when
ZenDiS set the application deadline and announced STACKIT’s planned production start, and the event date is the organiser’s. The other dates are our suggestion.
- On 17 November 2026: hear the Swiss state of play. Attend the Zentrum SDS event on openDesk and sovereign workplace software (workstream page) and ask whether the master licence has been agreed.
- By 30 November 2026: decide between the suite and the parts. List the functions you need (and whether mail and calendar move at all), your user count against the 500-user design, and the specialist applications tied to Microsoft 365, where Zurich found the hard limits.
- By 31 December 2026: write operations into the tender, not the label. Start from the ZenDiS catalogue (platform, maintenance windows, support hours per service, data location including backups, references at your scale) and add what it leaves out: the update cadence, restore tests with dated records and an exit in open formats. Ask for the evidence behind each answer.
- Before choosing SaaS in Switzerland: check the hosting clause. A Sovereign Service Provider must host in Germany or the EEA. If your rule is Switzerland only, ask any other provider where every copy sits, backups included; if it is your own premises, plan for on-premises operation.
- Until 31 January 2027: watch who is approved. The window closes then unless ZenDiS extends it.
- From January 2027: run one component under production conditions. Files and editing, or chat, with single sign-on, one real update applied, one backup restored and one full export tested. Our post on Geneva’s pilot sets out how to make a pilot end in a decision.
How Pilae fits
Pilae does not sell openDesk and is not a partner of ZenDiS or Open Productivity. We operate open-source apps on your premises or on dedicated machines in Pilae Cloud, and five openDesk components are in our catalogue as separate apps: Nextcloud, Collabora Online, Element, Jitsi Meet and OpenProject. OX App Suite, XWiki, Nubus, CryptPad and Notes are not, and we do not operate mail.
- Start with the parts, now. The sovereign workplace runs files, editing, chat, meetings, a wiki and sign-in as one workplace, and you can start with one app while Microsoft 365 keeps running for the rest.
- On your premises, or Switzerland only. We install on bare metal, VMware, Proxmox, Hyper-V or a Kubernetes cluster you already run, from the Business plan, and the control plane never receives application data (on premises). For a public body, the contract names Switzerland as the only location for apps, backups and logs (public sector).
- Releases planned before they are applied. The Pilae Agent checks each upstream release against your configuration, writes a plan with a rollback and waits for your approval; the change runs only after a verified backup, and every step is recorded.
- Backups encrypted before they leave. Every app is backed up daily, encrypted on your machine and stored offsite in the country you choose (backups), with the keys staying with you (data location). On the Enterprise plan, an engineer restores them every month and records the result in the console.
- One login, and a way out. Keycloak or your Entra ID in front of every app that supports it, from the Business plan, with multi-factor authentication per group (identity); your data, configuration and runbooks come back in open formats (exit plan).
Our controls are built to ISO 27001 and the NIST Cybersecurity Framework, and your contract gives you the right to audit them (security evidence). Our plans and prices are on the pricing page. If you are weighing openDesk against separate components, talk to an engineer: we go through the functions you need, where your data must stay, and what operating each option would involve.
This post is general information, not legal or procurement advice. For the official terms, read the partner documents on openDesk’s partner page.