Your own tools. Your own data. Your own decision.
I support the move to open source across the whole stack, from inventory to operation. My advice is vendor-neutral, and partners deliver the technology.
Starting point
Moving to open source is organisational change, not a software swap. The visible tools are the smaller part: mail, files, chat, video and office. What carries the weight is data, permissions, routines, roles, contracts, specialist applications and what your staff know.
Dependency shows in three places. The first is the provider’s jurisdiction, for instance when a US law such as the CLOUD Act reaches your data. The second is licence and pricing decisions taken by someone else. The third is missing exit routes: data that only comes out in the provider’s own format.
Open source is free of licence fees, not free of cost. Operation, adaptation, support and training cost money.
Four layers of the stack
Each layer has a part I advise on and a part that partners deliver. The split is deliberate: whoever advises does not earn from the operation.
| Layer | What I advise on | What partners deliver |
|---|---|---|
| Collaboration and office | Requirements analysis; comparing openDesk with single components such as Nextcloud, Collabora or LibreOffice, Open-Xchange, Matrix with Element, Jitsi, OpenProject and CryptPad; format strategy (ODF); dealing with macros and legacy files; exchange with external partners | Installation, integration, migration of mail, files and calendars, hosting |
| Infrastructure and operation | Choice of operating model; identity and access management first, for instance with Keycloak; requirements for hosting providers (BSI C5, ISO 27001, IT-Grundschutz); strategy for the Linux workplace; backup and disaster recovery | Operation, monitoring, security updates, support, packaging for workplaces |
| Specialist applications and data | Inventory of specialist applications and interfaces; ties to Windows, Office and macros; open standards such as XÖV, ODF, ICS, VCF and IMAP; data storage and exit routes; connection to open data; exit strategy | Adapting interfaces, migrating databases, isolated operation of remaining Windows applications |
| Organisation and law | Governance with an open source policy and a coordination office; procurement and specifications; licence compliance; data processing agreements; involving the staff council; change management and training; a strategy for contributing back to the projects and their communities; costs over the whole period of use | Legal advice in individual cases, running training sessions |
Approach
The project runs in ten phases. Between two phases there is a gate, shown as a diamond in the bar. A named person decides there, and there are four possible decisions: go on, go on with conditions, go back, or stop.
| Phase | Content | Result |
|---|---|---|
| 0 · Clarifying the mandate | What is to be decided? Mandate from the leadership; involving the staff council, data protection, IT security and the departments | Mandate paper, named decision-maker |
| 1 · Inventory | Services, data, formats, permissions, contracts with terms and exit routes, specialist applications, interfaces, skills | Inventory register, dependency map |
| 2 · Sovereignty assessment | Assessment per service, see method | Prioritised fields of action, quick steps, tipping points |
| 3 · Target picture | Requirements by must, should and could; checking candidates against the assessment grid; choice of operating model | Target architecture |
| 4 · Cost-effectiveness | Costs over several years: operation, adaptation, support, training, parallel operation, leaving the old system | Cost-effectiveness review, budget proposal |
| 5 · Procurement | Specifications, contract templates (EVB-IT), open source clauses, data processing agreements, choice of partners | Tender documents or partner contract |
| 6 · Pilot | Pilot group, success and stop criteria set in advance | Gate decision |
| 7 · Migration in waves | Area by area; parallel operation with an end date; quality assurance per batch with a second pair of eyes; training and drop-in sessions | Migrated areas, incident register |
| 8 · Shutdown | Archive export before notice is given, deletion of old data, end of contract | Shutdown record |
| 9 · Operation | Handover, update rhythm, restore tests, review of permissions, annual review, contributions back to the projects | Operations manual, review cycle |
Ways in
You do not have to commission everything at once. Each format ends at a gate, and then you decide again.
Sovereignty check
A compact inventory of the most important services, an assessment of the dependencies and pointers to first steps.
- free of charge
- phases 0 to 2 in reduced depth
Analysis and roadmap
Phases 0 to 4 in full, with a workshop for the leadership and a prioritised roadmap.
- Target architecture, operating model, costs over several years
Implementation support
Phases 5 to 8: procurement, project steering and change management. Partners deliver the technology.
- Procurement, pilot, migration in waves
Review and operational support
Phase 9 as an annual review or as support for follow-up projects. This keeps the stack maintained.
- Handover, updates, annual review
Training
Workshops on the basics, on licences, on assessing alternatives and on how to run a migration.
Assessment grid
I check every candidate piece of software against the same eleven points. The grid is published so that you can follow the assessment.
- G1Licence
- G2Single sign-on
- G3Sovereignty
- G4Data protection
- G5Active maintenance
- G6Interface
- G7Operating effort
- G8Telemetry
- G9Accessibility
- G10Security evidence
- G11Support and liability
Sovereignty per service
I assess each service along the lines of the European Commission’s Cloud Sovereignty Framework. Two questions are added that decide a move: can you get your data back out, and can you commission changes from more than one provider?
- strategic
- legal and jurisdictional
- data and AI
- operational
- supply chain
- technological
- security and compliance
- sustainability
- ability to switch: export in open formats, a documented way out
- ability to shape: commissioning changes, several providers on the market
The weakest link decides. The result per service is a traffic light and a reasoned effort level: low, medium or high. This is not a certification.
Three paths by type of organisation
Public administration
The framework is set by procurement law, EVB-IT, IT security rules, co-determination and accessibility. Decisions go through mandate, budget and committees, and there are many specialist applications. Sources include openDesk via ZenDiS or partners, the IT service providers of the federal states and municipalities, and framework agreements.
- Typical way in: sovereignty check, procurement support, a pilot in one organisational unit
Civil society and research
Often there is no IT department, the tools have grown over time, and a lot depends on individual people. Budgets are tight. A minimal model with a few building blocks, managed by providers in the EU, is often more realistic here than running openDesk in full. The move goes step by step, by effect and effort.
- Typical way in: check, assessment grid, minimal model
Companies and SMEs
What counts is cost, risk, productivity and compatibility with customers’ formats. Sovereignty is part of risk management here. Since September 2026, openDesk has also been available through private partners.
- Typical way in: check with a cost comparison, hybrid model
Roles and partners
- I advise. Vendor-neutral, and with no income of my own from hosting, licences or operation.
- Partners run the systems and provide support. They are chosen per project, for instance hosting providers in the EU, cooperatives or openDesk partners.
- Liability lies with whoever delivers the service under contract.
I do not give legal advice. Where a case needs it, it comes from lawyers.
When this offer is not the right fit
- The leadership does not back the move. Then only the check first, to prepare the decision.
- Critical specialist applications are firmly tied to Microsoft, with no alternative. Then a partial migration instead of a full move.
- There is no budget, in-house or through partners, for operation, updates and support.
- The only aim is to cut costs in the short term. In the first year, costs usually rise because of parallel operation and training.
- Core processes depend on complex macros or on exact format fidelity in exchange with external partners.
- The team is fully occupied with other large projects.
- What is wanted is a “sovereign” label without an open-ended review.
- What is wanted is legal advice, hosting or support. These come from partners.
Fact sheet
- For whom
- Public administration, civil society and research, companies and SMEs
- Way in
- Sovereignty check, free of charge
- Formats
- Check, analysis and roadmap, implementation support, review and operational support, training
- Results
- Inventory register, dependency map, target architecture, cost-effectiveness review, tender documents, operations manual
- Role of partners
- Installation, migration, hosting, operation and support
- What it costs
- The check is free. Everything else I discuss in the first conversation.