Hub for implementing a complete self-hosted workplace (files, office, mail, chat, video, wiki and projects under one identity layer) with openDesk or a Nextcloud-centred stack, and how sector and sovereignty needs change it.
Sovereign workplaces for ministries, states and municipalities: what openDesk bundles, Community versus Enterprise support from ZenDiS, hosting in government data centers, procurement and the order agencies roll out components.
A complete self-hosted workplace for universities and school authorities: files, office, chat and video for staff and students, campus identity federation, BigBlueButton or Jitsi for teaching, and sizing for term-time load.
A workplace suite for hospitals and health authorities: keeping ePHI in files, mail and chat inside the HIPAA or national health data boundary, TI-Messenger considerations in Germany, and integrating with clinical identity.
Replacing US-controlled productivity clouds with an EU-hosted suite: what openDesk or a Nextcloud-centred stack covers, gaps to plan for, data residency of every component and the operating model that keeps it sovereign.
Running the full suite on disconnected networks: mirroring signed Helm charts and pinned images, internal TURN, SMTP and antivirus services, and upgrade rehearsal given openDesk's monthly minor releases.
How a self-hosted workplace suite supports NIS2 risk-management measures: supply chain security with signed charts and pinned images, access control through one identity provider, incident handling and the evidence each component produces.
Connecting openDesk or a Nextcloud stack to the identity you already run: OIDC federation to Keycloak, the Nubus Directory Importer for LDAP and Active Directory, why Entra ID needs Azure AD Domain Services, and attribute matching.
What it takes to host openDesk in production: Kubernetes version and tooling, evaluation versus production hardware, the external databases, caches, object storage, SMTP, antivirus and TURN services, and who operates each.
For organizations moving gradually: which user groups or workloads move first, shared identity, mail coexistence, file exchange between the two, and how to keep users from falling back to the old tools.
Requirements to settle before implementing a self-hosted workplace suite: components in scope, identity and directory, Kubernetes platform, external services, edition and support, data migration, security hardening and rollout order.
Questions for a partner implementing openDesk or a Nextcloud-centred suite: Kubernetes experience, Enterprise Edition handling, identity federation, upgrade cadence, migration of mail and files, and support across all components.
What a self-hosted workplace suite costs: Kubernetes infrastructure and external services, Enterprise subscriptions per component or for openDesk EE, implementation and migration, operations staffing, and comparison with per-user productivity cloud licenses.
Tell us what you're working on, whether it's a deployment, an audit, a security test or a cyber range. You'll speak with an engineer who can help you scope it.