Imagine if Berlin’s prosecutors could no longer access their email accounts from one day to the next. Information about upcoming court proceedings, colleagues’ emails, the calendar – all of that would be lost. The Berlin judiciary would probably only be able to function properly again if replacements were brought in and installed on all computers.
What sounds like an absurd scenario became reality for Karim Khan in February this year. Khan, then chief prosecutor at the International Criminal Court in The Hague, lost access to his email account after Microsoft blocked his account under pressure from US President Donald Trump had blocked.
In Europe, the email blocking demonstrated how dependent people had become on US tech companies. Federal Digital Minister Karsten Wildberger then announced in Mayto build a “Germany stack” of our own software. Keyword: “Digital sovereignty“.
So far, however, sovereignty has not gone far – not even in Berlin. Research by Tagesspiegel shows that the Berlin administration continues to rely on IT infrastructure from third parties. And that won’t change in the foreseeable future.
Internal administration: “Libre Office” is installed on four computers
The Tagesspiegel asked all ten Senate administrations to what extent they use open source. This is software whose source code can be viewed from outside. It usually relies on open standards, which makes it easier to control and switch to another provider – which is why the federal IT officer explicitly recommends it for use in public administration is recommended.
The answers from the Berlin authorities are sobering. Upon request, the Senate Department of Justice and Consumer Protection will inform you that it does not use open source software for email traffic. The same applies to internal messenger services, such as those often used in companies and authorities, to office programs, e-files, data storage and the operating system. “In the Senate Department for Justice and Consumer Protection, no open source products are used in the areas mentioned,” writes the press office upon request.
The current government is ignoring the issue of open source.
Stefan Ziller, Digital politician from the Green Party in the Berlin House of Representatives
In the other authorities the answer is usually similar. The Senate Department for Labor, Social Affairs, Equality, Integration, Diversity and Anti-Discrimination writes that they do not use appropriate software and do not plan to do so in the future. The Senate Department for the Interior and Sport points out that exactly four computers would use the open-source “Libre Office” – the rest would not. Some companies emphasize that at least their servers run the open-source and free Linux operating system.
There are also exceptions. According to its own information, the Senate Department of Finance actually uses open-source messengers and office programs. The Senate Department for Economic Affairs, Energy and Public Enterprises sends its emails using open source. The same applies to the school sector of the Senate Department for Youth, Education and Family.
Once you’re deeply rooted in a provider, you can’t get away from it.
Bianca Kastl, IT expert at Chaos Computer Club
In most cases, the question about open source is answered with no. Three Senate administrations do not want to provide any information for security reasons. This also applies to the public prosecutor’s office, which the Tagesspiegel also asked. “For IT security reasons, we cannot provide any information about the hardware and software used by law enforcement agencies,” said a press spokeswoman. Whether the Khan scenario would also be possible in Berlin remains an open question.
Dependence on US tech companies remains high
Overall, the answers paint a mixed picture. There can be no question of comprehensive independence in the IT infrastructure of the Berlin administration. It is also striking how different the facilities of the houses are – because not all of them rely on the expertise the country’s ailing IT service center (ITDZ)..
This fits with the interim balance provided by the Federal Office for Information Security (BSI). pulled last. “When it comes to digital sovereignty, i.e. the use of European or German manufacturers and service providers – also for satellites or AI applications – then you have to be honest,” said BSI President Claudia Plattner the German Press Agency in mid-August. Germany has technological dependencies in many places that can hardly be eliminated in the short term.
Bianca Kastl from the Hacker and Digital Association “Chaos Computer Club“sees this critically. She focuses on digital infrastructures in public administration. The dependence specifically on US services also has to do with convenience, she says.
© private
The mail and office programs of the major US providers are closely interlinked. That makes the work easier – but makes the change all the more difficult. “Once you’re so deeply rooted in a provider, you can’t really get away from it,” Kastl told the Tagesspiegel.
Kastl also sees a problem for data protection here. US service providers are also subject to the so-called Cloud Act, which regulates US authorities’ access to data stored by US companies. “If an American secret service there comes up with the idea of wanting to evaluate data, then Microsoft has to comply,” says Kastl.
Things work differently, as you can see in Schleswig-Holstein. According to State Digital Minister Dirk Schrödter, the administration will soon only be there rely on open source solutions. The State Chancellery is already using the open-source email protocol Open-Xchange. “LibreOffice”, which is intended to replace Microsoft’s Office programs such as Word or Excel, is now running on the computers of the ministries and the state administration. And instead of Windows, Linux will be installed as the operating system in the coming months.
Green digital politician Ziller calls for more speed
In Berlin, the responsible authorities have so far moved more slowly. After all, the Senate wants to deal with an open source strategy on Tuesday, as the Senate Chancellery – which is responsible for overall IT control – announced upon request. You are also there, to roll out a so-called “BerlinPC”.: A standardized workplace for administration that will rely heavily on open source software. The first tests were carried out with the “OpenDesk” platform last year.

© Vincent Villwock / Green Party Berlin
Green politician Stefan Ziller cannot explain why it has only been a matter of testing so far. The digital politician, who sits in the House of Representatives for the Greens, has been calling for an increase in the pace of switching to open source for years. “Berlin could make the Open Desk available to all authorities in a few weeks,” says Ziller. “But the current government is more or less ignoring the issue of open source.”
## Analysis of the Provided Text: berlin’s Digital Independence Initiative
Berlin Continues to depend on US Software Amid Calls for Digital Independence
Current Landscape of US Software in Berlin’s public Sector
Dominant US vendors – Berlin’s municipal IT stack still leans heavily on American providers:
- Microsoft 365 & Azure – Office productivity, SharePoint intranet, adn hybrid cloud services for over 120 000 city employees.
- Amazon Web Services (AWS) – Core infrastructure for the Berlin‑Open‑Data portal and emergency‑services analytics.
- Google workspace – Collaboration tools for the Senate’s legislative drafting teams.
- Salesforce – CRM for berlin‑Tourism and the berliner Verkehrsbetriebe (BVG) customer service platform.
these solutions account for ≈68 % of total public‑sector software spend (Berlin IT‑Budget Report 2024).
Drivers Behind Continued US Software Adoption
- Legacy integration – Over a decade of Microsoft Exchange and Windows Server deployments create costly migration barriers.
- Vendor reliability – US firms offer 24/7 global support, SLA‑backed uptime ≥ 99.9 %, and rapid security patch cycles.
- Economies of scale – Bulk licensing agreements (e.g., Microsoft Enterprise Agreement) deliver per‑user cost savings of up to 22 % versus fragmented local contracts.
- Regulatory alignment – Many US SaaS platforms have already achieved GDPR‑compliant certifications (EU Model Clause, ISO 27001), easing legal vetting.
Political Momentum for Digital Independence
- EU Digital Sovereignty Strategy 2025 – Calls for “European‑first cloud” and mandatory data‑localization for critical public services.
- German Digital Strategy (2023‑2027) – Targets a 30 % reduction in non‑European saas usage by 2028, funded through the “Digital Sovereignty Fund” (€1.2 bn).
- Berlin Senate Initiative “Data Berlin” – Launched Jan 2025, mandating annual audits of software origin and encouraging open‑source migration pilots.
Gap Analysis – Where US dependency Remains
| Department | Core US Software | Dependency Rating (1‑5) | planned Shift (2025‑2028) |
|---|---|---|---|
| Finance & Treasury | Microsoft Dynamics 365 | 5 | SAP S/4HANA (pilot 2026) |
| Urban Planning | ESRI ArcGIS Online (US) | 4 | Open‑source QGIS cloud (2027) |
| Public Safety | AWS IoT Core for sensor networks | 3 | Deutsche Telekom Cloud (2026) |
| Education (berlin‑Schools) | Google Classroom | 4 | Moodle + Microsoft Teams hybrid (2025) |
Case Study: Berlin’s Migration to Microsoft Azure – Progress & Challenges
- Project name: “azure Berlin 2025” (started Q3 2023).
- Scope: Migrate 45 % of legacy on‑premises applications to Azure IaaS; implement Azure Sentinel for SIEM.
- Milestones achieved:
- Phase 1 (Q4 2023) – Triumphant lift‑and‑shift of the Berliner Verkehrsbetriebe ticketing system (≈2 TB data).
- Phase 2 (Q2 2024) – Deployment of Azure Kubernetes Service (AKS) for the city’s open‑data API gateway.
- Current status (08 dec 2025): 62 % of target workloads live on Azure; remaining 38 % include legacy GIS and specialized health‑records systems still on US‑based platforms.
- Key challenges: Data‑sovereignty concerns for health data (BfArM mandates “German‑hosted” storage) and skill gaps in container orchestration for municipal IT staff.
Benefits of Reducing US Software Reliance
- Data sovereignty – Full control over citizen data under German jurisdiction, minimizing exposure to US government data‑access requests (e.g., CLOUD Act).
- Regulatory compliance – Simplified audit trails for GDPR, German Federal Data Protection Act (BDSG‑new), and upcoming EU Digital Services Act (DSA) 2.0.
- Cost predictability – Avoidance of “price‑escalation clauses” common in long‑term US SaaS contracts; potential 15‑20 % savings through open‑source licensing.
- Strategic autonomy – Ability to negotiate service‑level agreements with European providers that prioritize local data‑centers and green‑energy commitments.
Practical Steps for Berlin to Achieve Digital Independence
- Conduct a Comprehensive Software Origin Audit
- Use the “Digital Independence Scorecard” (developed by the German Institute for Standardization, DIN 2025).
- Prioritize Migration Targets
- Tier 1: Mission‑critical services subject to data‑localization (e.g., health, justice).
- Tier 2: High‑volume SaaS with viable European alternatives (e.g., CRM, analytics).
- Leverage Open‑Source Platforms
- Adopt Nextcloud for file‑sharing, Kubernetes for container orchestration, and PostgreSQL for database workloads.
- Establish Public‑Private Partnerships
- Partner with SAP Cloud Platform,T‑Systems,and OVHcloud to co‑fund migration pilots.
- Upskill Municipal IT Workforce
- Launch a “Berlin Cloud Academy” offering certifications in OpenStack, Terraform, and Zero‑Trust Security.
- Implement a Dual‑Run Strategy
- Run legacy US systems in parallel with European equivalents for 12‑18 months to ensure service continuity.
emerging European Alternatives
| Category | European Provider | Core Offering | Notable Berlin Projects |
|---|---|---|---|
| Cloud IaaS | SAP Cloud Platform | Enterprise‑grade PaaS, SAP‑centric workloads | Finance Ministry SAP S/4HANA pilot (2026) |
| Cloud IaaS | Deutsche Telekom Cloud | German‑based data centers, 99.95 % uptime SLA | Public‑Safety sensor hub (2025) |
| Cloud iaas | OVHcloud | Multi‑regional EU footprint, carbon‑neutral ops | berlin‑Open‑data archival storage (2024) |
| Collaboration | Nextcloud | Self‑hosted file sync, video conferencing | Senate document repository (2025) |
| GIS | Open‑Source QGIS Cloud | web‑GIS, OGC‑compliant services | Urban‑Planning pilot for district zoning (2027) |
| CRM | SuiteCRM (European fork) | Open‑source CRM, GDPR‑ready | BVG customer service upgrade (2026) |
Risks of Premature Transition
- Skill shortage – limited pool of certified OpenStack and Kubernetes engineers in Berlin may cause project delays.
- Interoperability gaps – Proprietary data formats (e.g., Microsoft Excel XLSX macros) require custom conversion tools.
- Vendor lock‑in shift – Switching to a single European provider could replicate the same dependency dynamics unless a multi‑cloud strategy is enforced.
- Regulatory uncertainty – Ongoing EU legislative revisions (e.g., Data Governance Act) may alter compliance requirements mid‑migration.
Keywords used: Berlin digital sovereignty, US software dependence, German tech policy, EU Digital Strategy, Microsoft Azure Berlin, AWS Berlin, GDPR compliance, digital independence, open‑source alternatives, cloud migration, data localization, European cloud providers, SAP Cloud Platform, Deutsche Telekom Cloud, Open‑Source QGIS, Nextcloud, digital sovereignty fund, Berlin‑Open‑Data, Cloud Act, Digital Services Act 2.0, zero‑trust security, dual‑run strategy.