11,000 municipalities, one deadline — and barely any progress. Why traditional IT projects in public administration fail and how AI-powered development can break the deadlock.
The OZG: Political Dream, Municipal Nightmare
575 government services were supposed to be available online by the end of 2022. That was the promise of Germany's Online Access Act (OZG). The reality: Even in early 2026, not even half are digitalized nationwide.
The problem isn't political will. It's implementation. 11,000 municipalities in Germany, each with its own IT infrastructure, its own specialized software, its own processes. And nearly all with the same problem: too little budget, too few staff, too little time.
The OZG 2.0 (effective since January 2024) adjusted the deadlines and increased the pressure — citizens now have a right to digital government services. But the fundamental problem remains: Who's going to build all of this?
Klingt nach deinem Problem?
Why Traditional IT Projects Fail in Government
The Procurement Marathon
Before a municipality gets a single line of code, it must go through procurement. Write requirements, comply with procurement law, evaluate proposals, award the contract. This process alone takes 3–6 months.
Then comes the concept phase. Then development. Then acceptance testing. In total, 12–24 months pass before a simple application portal goes live. For a building permit.
The Service Provider Oligopolies
The municipal IT market is dominated by a few large providers: Dataport in the north, AKDB in Bavaria, Kommunale Informationsverarbeitung in Baden-Württemberg. Add consulting firms that charge six-figure sums just for requirements analysis.
The result: Little competition, high prices, long timelines. A simple online form for vehicle registration? €250,000. A citizen service portal? Easily seven figures.
Waterfall Instead of Agility
Government IT projects almost always follow the waterfall model: Requirements specification, detailed design, implementation, testing, acceptance. Changes mid-project? Change request. Costs extra, takes months.
The private sector buried this model 15 years ago. In government, it's still the standard.
Lock-in Through Legacy Systems
Municipal specialized software (the core applications for civil registry, finance, building administration) is often proprietary and decades-old monoliths. APIs? Sometimes SOAP, sometimes none at all. Every new application must connect to these systems — a technical nightmare.
What a Municipality Really Needs
The digitalization backlog doesn't exist because municipalities need complex enterprise systems. It exists because even simple things are disproportionately expensive.
What most municipalities need immediately:
Online application forms — Citizens fill out forms on their computer or smartphone instead of waiting at the office. Document upload, digital signature, status tracking.
Citizen portal with login — A central place where citizens can view their applications, receive decisions, and communicate with the agency. Like online banking, but for government.
Case worker dashboard — A clear overview for case workers: open applications, deadlines, documents. Instead of file folders and paper chaos.
Appointment booking — For services that still require in-person visits: ID cards, marriage registration, consultations. Bookable online, without a queue number.
Automated decisions — Automatically generate and digitally deliver standardized administrative acts. Saves case workers hours per week.
None of these requirements are technically complex. A good development team builds this in a few weeks. The problem is: municipalities don't havedon't have a development team.
The Cost Comparison
| Service | Traditional Provider | With Nopex |
|---|---|---|
| Online application form | €50,000–100,000 | From €500/month |
| Citizen portal | €200,000–500,000 | From €500/month |
| Appointment booking system | €30,000–80,000 | From €500/month |
| Case worker dashboard | €100,000–250,000 | From €500/month |
| Timeline | 12–24 months | 4–8 weeks |
The numbers speak for themselves. And they explain why the OZG is failing: Not because digitalization is impossible, but because in its current form it's unaffordable and endlessly slow.
Practical Example: Digitalizing a Building Permit
A concrete scenario. A mid-sized municipality (40,000 residents) wants to digitalize the building permit process. Current state: Paper forms, in-person submission, processing time 8–12 weeks.
What nopex Builds From This
Step 1: Describe the requirements
"We need an online portal for building permit applications. Citizens should be able to fill out forms, upload building plans, and track status. Case workers need an overview of all applications with deadlines and checklists."
Step 2: Nopex generates
- Responsive application form with step-by-step wizard
- Document upload (site plan, building drawings, energy certificate)
- Automatic completeness checks
- Case worker dashboard with Kanban view
- Automatic deadline calculation
- Email notifications on status changes
- Citizen portal with login and status tracking
Step 3: Live in 6 weeks
The portal is deployed on the municipal infrastructure. Case worker training: 2 hours. Citizens need no training — the portal works like any modern web app.
Result: Processing time cut in half, follow-up inquiry rate reduced by 60% (because incomplete applications are automatically caught), zero wait time at the office.
GDPR, BSI Standards, BITV: Compliance for the Public Sector
Software for government agencies must meet higher standards than for the private sector. That's justified — it's about citizen data.
GDPR & Data Sovereignty
All applications generated by nopex run on infrastructure you control. No data processing in the US, no vendor lock-in, no dependency on cloud services outside Europe.
BSI IT Baseline Protection
The standard defined by Germany's Federal Office for Information Security (BSI) applies to government IT. nopex generates code that follows security best practices: input validation, SQL injection protection, secure authentication, encrypted communication.
BITV 2.0 & Accessibility
Germany's Accessible Information Technology Regulation requires public entities to provide accessible web applications. WCAG 2.1 Level AA is the minimum. Generated frontend code meets these requirements: semantic HTML, keyboard navigation, screen reader compatibility, sufficient contrast.
eID Integration
The OZG 2.0 requires digital identification via the online ID function (eID) for many services. nopex can generate integrations with the eID service, allowing citizens to identify themselves digitally with their national ID card.
Sovereign Infrastructure: Why This Is Non-Negotiable for Government
US cloud services (AWS, Azure, Google Cloud) may be technically superior — for government agencies, they're often not an option. The US CLOUD Act theoretically gives US authorities access to data even when servers are located in Europe. For German municipalities handling citizen data, that's a non-starter.
The alternative: Sovereign German cloud infrastructure (such as govdigital, STACKIT, plusserver) or classic on-premise hosting in the municipal data center.
nopex generates standard web applications that run anywhere: Docker containers that can be deployed on any Linux machine. No vendor lock-in, no proprietary cloud services.
Conclusion: Digitalization Doesn't Have to Take a Decade
The OZG isn't failing because of technology. It's failing because in 2026, we still procure software the way we did in 2006: Write a requirements spec, wait 18 months, pay €500,000.
AI-powered software development fundamentally changes this equation. What used to be a year-long project with a six-figure budget is now built in weeks. Not at lower quality — but with the same technology that tech companies use.
11,000 municipalities are waiting for digitalization. Citizens have a right to it. The technology is here. All that's missing is the courage to take new paths.
