Sovereign Workspace·

openDesk Leaves the Federal Bureaucracy – ZenDIS Opens the Sovereign Workspace to SMEs

Since May 2026, distributors are allowed to sell openDesk to SMEs. What the ZenDIS suite delivers, how it replaces Microsoft 365, and how to pilot it.

openDesk Leaves the Federal Bureaucracy – ZenDIS Opens the Sovereign Workspace to SMEs

In May 2026, the Zentrum für Digitale Souveränität (ZenDIS) – Germany's federally owned "Centre for Digital Sovereignty" – moved its reseller partner program for the openDesk Enterprise Edition into regular operation. That ends a phase in which the state-curated open-source office suite was, in practice, only available to federal agencies, the German armed forces and a handful of pilot ministries. From the second quarter of 2026 onwards, authorised distributors may deliver the package across Europe to SMEs, school authorities and state administrations – with SLA, migration services and training.

For German IT leaders who have been waiting for years for a federally funded, realistic alternative to Microsoft 365, this is the most important structural decision since the European Commission moved to Matrix. We unpack what openDesk technically is, why the distribution model makes the difference, and how a low-risk pilot looks.

What openDesk is – and what it deliberately is not

openDesk is an office suite that ZenDIS integrates, security-hardens, packages and supports from existing open-source components developed in Europe. It is not a from-scratch rewrite, but a curated distribution with defined versions, a patch pipeline and a support SLA. As of May 2026 the Enterprise Edition contains:

  • File storage and sync: Nextcloud (Files, Hub, Talk)
  • Document editing: Collabora Online (LibreOffice-based)
  • Email and calendar: Open-Xchange App Suite
  • Project management: OpenProject
  • Real-time communication: Element on Matrix – the same stack used by the European Commission
  • Knowledge management: XWiki
  • Identity and single sign-on: Keycloak
  • Directory service: integrated LDAP and Univention connectivity

Deliberately not included: AI inference, a search engine, ERP, CRM. ZenDIS positions openDesk explicitly as an office replacement, not as an all-in-one platform. Anyone who needs generative AI integrates it themselves – for example via locally hosted models in Nextcloud Assistant – and thereby avoids problems such as Copilot Flex Routing, through which Microsoft has been re-routing prompts to the US under load since April 2026.

Why "reseller" – and why that is a turning point

Until early 2026, any organisation that wanted openDesk in production had to contract directly with ZenDIS. That worked for the Bundeswehr (confirmed as anchor customer in February 2026), for the Federal Ministry of the Interior, the Robert Koch Institute and the Federal Ministry of Health. 8,756 licences had been issued across the federal administration by April 2026, 8,475 of them productive; the remainder runs in active pilots.

For SMEs, district authorities, municipal utilities and individual school authorities, that direct path was impractical: order volumes were too small, on-site consulting was missing, and EVB-IT contracting (Germany's standard public-sector IT contract framework) is unfamiliar territory for mid-market IT houses. The two-tier distribution model fixes that. ZenDIS remains the manufacturer and contracting partner for the distributors; authorised reseller partners deliver to end customers – including installation, migration, training and first- and second-level support.

Market consequence: For the first time there is a Microsoft-365 alternative that (1) is funded and maintained by a national government, (2) ships with a binding sub-processor model – every component in Europe, no hyperscaler dependency – and (3) can be procured locally through familiar IT vendors.

openDesk vs. Microsoft 365 – the honest comparison

AreaMicrosoft 365openDesk
Data residencyEU Data Boundary, perforated (Flex Routing)EU operator of your choice, BSI-IT-Grundschutz certifiable
CLOUD Act exposureFull (see analysis)None
Sub-processor changesUnilaterally by MicrosoftContractually controlled, notifiable
Real-time officeWord, Excel, PowerPoint OnlineCollabora Online
Email / calendarExchange OnlineOpen-Xchange
MessagingTeamsElement / Matrix
AICopilot (US routing possible)Optional, self-hosted
Licence modelPer user per month, vendor lockPer user, tiered, no vendor lock
Offline editionOffice AppsLibreOffice

Where openDesk still trails: very complex Excel workbooks with Power Query, deeply integrated Outlook add-ins, and Teams-specific bot workflows. For roughly 80 percent of typical administrative and SME work openDesk is functionally equivalent or better. Power users in controlling and reporting should test their workbooks before migration, not afterwards.

How to pilot openDesk – HowTo

The five steps below are encoded in this post's structured HowTo schema (for Google Rich Results). For human reading:

Step 1: Cluster your use cases {#step-1}

Lay out employee count times office function on a matrix. What is actually used today, not what is licensed? Mark power-user artifacts (Excel with Power Query, Outlook add-ins, Teams bots) separately.

Step 2: Select a reseller partner {#step-2}

Review the ZenDIS partner list (fully published from autumn 2026). Criteria: experience migrating Nextcloud and Open-Xchange out of the Microsoft stack, EU base, EVB-IT contracting capability, documented sub-processor chain.

Step 3: Buy a pilot tenant {#step-3}

10–25 licences over three months, mixed team of IT, business unit and management. Parallel operation alongside Microsoft 365 is mandatory – no big bang. Define success criteria in writing beforehand.

Step 4: Lock the migration path in the contract {#step-4}

Mailbox via IMAP/EWS, SharePoint via rclone into Nextcloud, Teams rooms via a Matrix bridge or rebuilt. Hold-back clause and rollback right for the first six months in the contract.

Step 5: Maintain NIS2 and GDPR documentation in parallel {#step-5}

Record of processing, risk register, TIA and DPIA maintained twice during the pilot – background in the NIS2 / GDPR paradox.

Defined terms

  • openDesk: open-source office suite, integrated and published by ZenDIS, productive in the German federal administration since 2025, available to SMEs via authorised distributors from May 2026.
  • ZenDIS: Zentrum für Digitale Souveränität GmbH, founded late 2022, headquartered in Bochum, owned by the German federal government. Mandate: provide and maintain open-source software for the public sector.
  • Sovereign Workspace ("Souveräner Arbeitsplatz"): German public-sector terminology for an office environment that runs without US hyperscalers. openDesk is the official implementation of that concept.
  • Reseller Partner Program: two-tier distribution model. ZenDIS supplies distributors, distributors supply end customers. Distributor operations from May 2026, end-customer operations via partners officially from autumn 2026.
  • EVB-IT: Ergänzende Vertragsbedingungen IT – the standard public-sector contract framework for IT procurement in Germany. Anyone doing business with public authorities must be EVB-IT capable.

Where europioneer fits in

europioneer has been operating an openDesk-compatible variant of the same stack since 2024 – Nextcloud, Collabora Online, Open-Xchange, Element/Matrix, Keycloak – as a managed hosted service, including migration from Microsoft 365 and a contractually fixed SLA. If you want to wait for the official openDesk partner program, that's fine. If you want to pilot today and become productive without EVB-IT bureaucracy, you'll find the same architecture, the same open-source components and the same data-sovereignty stance with us. Component overview at /en/alternativen, packages and pricing at /en/pricing.

Bottom line

May 2026 is a turning point. The years-old claim that "there is no real Microsoft 365 alternative" no longer holds since the launch of the ZenDIS reseller partner program. Anyone renewing Microsoft 365 licences in 2026 without an exit plan is not just renewing a contract – they are extending CLOUD Act exposure, the NIS2 supply-chain risk and the dependency on unilaterally changeable sub-processor lists.

Request a pilot consultation →


Related posts: