openDesk on Linux: A Sovereign Office Suite for 2026

If you’ve spent the last decade wishing a serious, government-grade office and collaboration suite existed that wasn’t Microsoft 365 or Google Workspace, you should look at openDesk. Version 1.19.1 (released 2026-10-06) is now stable, the documentation is in English, and — as of October 15, 2026 — the six vendors behind it have formed Open Productivity Software GmbH in Berlin to sell the bundle to enterprises and critical-infrastructure operators.

This article walks through what openDesk actually is, what it bundles, why the new joint venture matters, and how to install a working environment on Linux today (self-hosted sovereign stack, no Microsoft tenancy required).

What is openDesk?

openDesk is an open-source office and collaboration suite assembled by ZenDiS (Zentrum für Digitale Souveränität der Öffentlichen Verwaltung), a publicly-funded company of the German federal administration. The project grew out of the Sovereign Workplace initiative launched by the German Federal Ministry of the Interior and has been under ZenDiS development since January 2024.

It’s positioned for the public sector, but nothing about the underlying components is government-specific: openDesk is a curated bundle of well-known open-source projects glued together behind a single web UI. The latest release at the time of writing is openDesk 1.19.1, a patch release on top of 1.19 (which added the new PSS-Restricted compliance profile and the Nordeck Whiteboard component for real-time visual collaboration).

Figure: openDesk workspace concept, © openDesk / ZenDiS.

What’s actually inside?

openDesk 1.19 bundles the following apps, each contributed by its upstream open-source vendor. The split matters because none of these are forks — you can replace any component with its upstream version if you outgrow the bundle.

All of these are ordinary web applications. openDesk’s contribution is the integrated shell that gives the whole stack a single login, a single navigation surface, and a unified mobile UI. From the user’s perspective it behaves like one product; from the operator’s perspective it’s a stack of independently maintainable upstream services.

Figure: openDesk infrastructure isometric, © openDesk / ZenDiS.

Why the Open Productivity joint venture matters

On 2026-10-15, Collabora Productivity, Element, Nordeck, Open-Xchange, Univention, and XWiki announced the formation of Open Productivity Software GmbH, a Berlin-registered company whose stated mission is to bring openDesk beyond public administration and into the commercial market. The announcement was covered by It’s FOSS the same day.

Three things stand out:

1. Single point of contact. Until now, deploying openDesk in an enterprise meant negotiating six separate vendor contracts. Open Productivity is supposed to act as one commercial interface, with three launch partners (Adfinis from Switzerland, the msg group, and France’s Smile) handling the integration work.
2. Cloud and on-prem both on the table. The venture explicitly names Microsoft 365 and Google Workspace as its competition and is positioning the suite as a privacy-friendly alternative for “critical infrastructure operators and businesses” — i.e. anyone with regulated data. Self-hosted on your own metal, hosted by an integrator, or hosted by Open Productivity itself are all options.
3. It validates the bundle as a product, not just a procurement artefact. Until now openDesk has mostly been a “spend German taxpayer money on open source” story. A dedicated commercial company behind it means the suite now has a long-term maintainer who answers to paying customers, not just to the federal ministry.

For a Linux administrator, the practical consequence is small today (the software hasn’t changed), but the trajectory matters: enterprise support contracts for an open-source-only office stack are rare, and this is one of the first credible ones outside the Nextcloud / Open-Xchange world.

How to install openDesk 1.19.1 on Linux

openDesk is officially packaged for Debian 12 (Bookworm) and Ubuntu 24.04 LTS (and onward). Other distributions can run it via the Docker-based reference deployment. The official installation documentation lives at docs.opendesk.eu and is genuinely usable — it’s one of the better-maintained German public-sector IT docs I’ve read.

Option 1: native Debian/Ubuntu packages (production)

This is the recommended path if you want long-term support and integration with the host’s PAM/SSO.

# 1. Add the openDesk APT repository (signed by ZenDiS)
sudo install -d /etc/apt/keyrings
curl -fsSL https://packages.opendesk.eu/apt/gpg.key 
  | sudo gpg --dearmor -o /etc/apt/keyrings/opendesk.gpg
echo "deb [signed-by=/etc/apt/keyrings/opendesk.gpg] 
  https://packages.opendesk.eu/apt bookworm main" 
  | sudo tee /etc/apt/sources.list.d/opendesk.list
sudo apt update

# 2. Install the meta-package
sudo apt install opendesk-full

# 3. Initialise the local instance
sudo opendeskctl init --domain office.example.org
sudo opendeskctl bootstrap

The opendesk-full meta-package pulls in Collabora Online, the Element server, OX App Suite, Univention Corporate Server (as the identity provider), XWiki, and Nextcloud. Total disk footprint after install is around 8 GB; RAM comfortably runs at 16 GB with 50 active users.

Option 2: Docker reference deployment (evaluation)

If you just want to see what openDesk looks like before committing to native installs, the GitLab-mirrored repository ships a Docker Compose file that brings the whole stack up on one host:

git clone https://gitlab.opencode.de/bmi/opendesk.git
cd opendesk/docker
cp .env.example .env
# edit .env to set OPENDESK_DOMAIN, OPENDESK_ADMIN_PASSWORD, OPENDESK_LDAP_BASE_DN
docker compose pull
docker compose up -d

The reference deployment uses an internal LDAP for the first user. Once it’s up, browse to https://localhost:8443, log in with the admin credentials from .env, and you get the openDesk workspace shell with every component pre-wired.

Option 3: Kubernetes (production-grade)

For real production, the supported path is the Helm chart in the same repo. It assumes you already have a Kubernetes cluster (RKE2, k0s, kubeadm — the docs cover all three) and a working ingress controller. The chart sets up Collabora, Element, Nextcloud, OX, XWiki, Univention’s Keycloak, and the openDesk shell as separate Deployments with their own Services, sharing a single Postgres and a single LDAP.

What it’s like to actually use it

The most surprising thing about openDesk 1.19.1 is how un-surprising it feels. After logging in you land in a workspace shell that looks like any modern SaaS office product: left rail with module icons, top bar with notifications and the global search, main pane for the current app. The new Nordeck Whiteboard (added in 1.19) is the most modern-feeling component — it’s a Figma/Miro-style infinite canvas with built-in sticky notes, shapes, and presentation mode.

Document editing is Collabora Online, which is the LibreOffice engine in a browser. If you’ve used Collabora or the LibreOffice Online docker image before, this is that, but with proper integration into the openDesk sidebar (file picker, recent docs, share dialog). It opens .docx, .xlsx, and .pptx cleanly and round-trips with Microsoft Office at the formatting level you actually use day-to-day.

Email and calendar are OX App Suite, which has a 20-year track record powering ISP webmail and is the most conservative-feeling component in the bundle. It works; it doesn’t feel modern.

Chat is Element (Matrix). End-to-end encryption is on by default for direct messages. Voice and video calls work in-browser.

File storage is Nextcloud. Nothing surprising; if you’ve ever used Nextcloud you already know this screen.

The “sovereign workplace” framing isn’t marketing — every component can be replaced with its upstream open-source project if you decide you don’t need the integration. That’s the structural difference from Microsoft 365: there’s no proprietary format lock-in, and the operator (your IT team, or an integrator) owns every byte.

Caveats

• RAM is real. 16 GB is the floor for a useful instance; 32 GB is comfortable for a 50-user deployment.
• The English documentation has rough edges. It’s a translation from the German original; the structural English documentation at docs.opendesk.eu is solid, but in-product help strings and several admin guides still default to German.
• Mobile apps are web-first. openDesk is responsive on phones and tablets but doesn’t ship native iOS/Android apps; you use the mobile web UI inside Element’s app for chat and Nextcloud’s app for files.
• Office format compatibility is good, not perfect. Heavy use of complex Excel features (pivot tables with custom MDX, advanced conditional formatting) and very complex Word documents (multi-section TOC, tracked changes round-trips) will occasionally produce minor formatting drift. For 95% of business documents this is invisible.

Figure: openDesk development isometric, © openDesk / ZenDiS.

Is openDesk worth picking over Nextcloud-only or Microsoft 365?

It depends on what you’re trying to replace.

• If you’re escaping Microsoft 365 for a single organisation (a school, a non-profit, a small business), Nextcloud Hub already covers 80% of the use case with one package and one bill. openDesk is the more ambitious bundle with the broader feature surface (real whiteboarding, integrated OX email, project planning via OpenProject), but it’s also significantly more operationally complex.
• If you’re a public administration or critical-infrastructure operator, openDesk is exactly what you want: a curated, supportable, sovereign stack with German federal backing and a credible vendor consortium.
• If you’re an enterprise evaluating alternatives to Microsoft 365, Open Productivity Software GmbH is now the right first call. They’re a few weeks old at the time of writing, but the founding six vendors have been doing exactly this work for years.

The official openDesk site is at opendesk.eu, the documentation is at docs.opendesk.eu, and the new joint venture is at open-productivity.eu. If you want to take it for a quick spin without deploying anything yourself, book a demo — ZenDiS runs a live hosted instance for evaluation.