Back openDesk Edu for a sovereign, open-source education — every vote counts.
Vote nowSave products you love by clicking the heart icon.
The EU Cyber Resilience Act makes cybersecurity mandatory for almost every product with digital elements sold in Europe — from IoT devices to software. Timeline, scope, conformity assessment, reporting duties, penalties, and what it means for developers, startups and open-source projects.
Own your stack — and stay compliant. A sovereign digital workplace keeps your data, tooling and collaboration under your own control: self-hosted, open source, independent of hyperscalers. The talks explain why; the workshops turn it into practice for your team.
Dr. Tobias Weiss — computer scientist, researcher (VR/XR, AI) and conference speaker (incl. DELFI 2023). Trusted by teams that need compliance and sovereignty, not vendor lock-in.
All formats run on-site or remote, from a half-day session to a multi-day program, tailored to your stack and your risk profile.
The EU AI Act makes AI literacy a legal duty for everyone who uses AI tools (Art. 4, Reg. (EU) 2024/1689) — applicable since August 2026. A one-size-fits-all online course does not satisfy it: you must be able to prove competence. Breaches of the AI Act can trigger fines of up to €35 M or 7 % of global annual turnover.
Our KI-Kompetenz-Training delivers audit-ready, role-based AI literacy:
→ Explore KI-Kompetenz-Training
Product security is now law. The Cyber Resilience Act (CRA) makes security obligations mandatory for products with digital elements — conformity assessment, SBOM, vulnerability handling and coordinated disclosure. CRA duties phase in now and through 2027; breaches can mean fines of up to €15 M or 2.5 % of turnover (set nationally) and exclusion from public tenders.
This workshop maps CRA duties to your product reality:
→ Read the Cyber Resilience Act guide
A sovereign workplace that does not trade sovereignty for convenience: self-hosted collaboration built from openDesk Edu (office suite), mailcow (mail) and the sovereign-cloud-stack pattern.
Before: locked into a SaaS, data leaving your perimeter. After: a workplace you run yourself, on your own hardware.
Self-hosted office + mail you control end to end
Sovereign-cloud-stack blueprint, documented and repeatable
Hands-on labs: from "we depend on a SaaS" to "we run it ourselves"
Combine any of the three tracks into a single program. Typical shapes (price on request, fixed packages):
Beyond client work I publish and speak — recent highlights: