Title slide "ISCN Global Mixer – Measuring and Implementing Digital Sovereignty in the City of Munich", speaker Dr.-Ing. Dirk Gernhardt, 1 October 2026.
Foto: Álvaro de la Paz Franco (CC0), via Wikimedia Commons Álvaro de la Paz Franco, 2025

ISCN Global Mixer: Measuring and Implementing Digital Sovereignty in the City of Munich

How dependent is a city administration on individual IT vendors – and how can that be changed? Munich has developed a simple digital sovereignty score and is anchoring sovereignty in its core IT processes.

Paragraphs

How can a city keep its data safe and remain truly independent? Munich, with around 43,000 employees in its administration and an IT department of about 1,500 staff serving all city departments, received a clear mandate from its city council: measure how dependent the city is on individual vendors – and reduce these dependencies.

The city chose a deliberately simple, agile approach: a digital sovereignty score based on German school grades, from 1 (fully sovereign) to 5 (not sovereign). For each IT service, a first question asks whether a real alternative exists – if not, the service is rated 5. Further questions raise the score, for example whether the provider is headquartered in the EU, whether the software is open source, whether security updates are guaranteed and whether only standardised interfaces and file formats are used. Instead of assessing all its roughly 2,500 IT services, Munich focused on about 200 business-critical services. The result: around three quarters are rated sovereign to sufficiently sovereign, while about 20 percent are not sovereign – typically products of large US vendors, but also specialised administrative software for which only one provider exists.

To improve the score year by year, digital sovereignty is now being built into four processes: IT strategy, IT architecture management, IT solution management – where sovereignty becomes an evaluation criterion alongside functionality, cost and security, and open-source options must always be considered – and procurement. Practical examples include architecture guidelines that confine proprietary platforms to specific domains, a Windows workplace without Teams and SharePoint, AI models hidden behind a gateway so they can be exchanged easily, an open-source sabbatical and feature funding for tools the city uses, and the principle "public money, public code": code developed by the city is published on GitHub and OpenCoDE.

Key Takeaways for Municipal Decision-Makers
  • Start simple: a transparent score with a handful of yes/no questions already provides a robust snapshot of vendor dependencies.
  • Focus first on business-critical IT services instead of the entire IT portfolio.
  • Dependencies cannot be eliminated completely – the aim is to identify risks and keep them under control.
  • Anchor digital sovereignty in strategy, architecture, solution selection, and procurement, so that it becomes part of everyday decisions.
  • Good architecture (e.g. gateways, open interfaces) keeps systems exchangeable and reduces lock-in over time.
Further links

This event is part of the ISCN Global Mixer, a series of events organized by the International Smart Cities Network. The presentations cover a wide range of topics related to international smart city approaches and provide exciting insights into urban digitalization worldwide - in just 30 minutes.

Contacts