Germany's OZG required 575 government services online by 2022. Only 33 were ready nationwide. The problem isn't political ambition — it's a procurement culture that guarantees delay. Here's how municipalities can build digital workflows in weeks, not years.
Markus wants to open a small café. His first step: registering the business. He navigates to his local government's website, finds a link to a PDF form, prints it out, fills it in by hand, drives to the municipal office, waits forty minutes, and hands over a piece of paper in exchange for a rubber stamp. A letter arrives two weeks later.
The year is 2026. The word for this process isn't "old-fashioned." It's "unchanged." Markus would have followed the same steps in 2008. That's the quiet failure of Germany's Online Access Act — not the political blame game over who fell short, but the simple fact that a citizen in 2026 still has to drive to a government office to submit a form that could just as easily be filed online, if anyone had ever built that.
The Gap Between Law and Reality
Germany's Online Access Act (OZG) passed in 2017. It required federal, state, and municipal governments to make 575 administrative services available online by the end of 2022. What sounded like an achievable mandate became a quiet embarrassment: by the deadline, only 33 of those services were available nationwide, according to Germany's Federal Court of Audit. Not 33 percent. Thirty-three services — out of 575.
Klingt interessant?
The federal government has made progress since. By the end of 2024, the Interior Ministry reported that all 115 prioritized federal-level services were online — things like applying for child benefit or requesting a student loan on bund.de. But day-to-day government happens at the municipal level, and there the picture is considerably bleaker. The Federal Court of Audit found that as of July 2024, just five percent of the centrally-funded "one-for-all" (EfA) online services were in nationwide use. The other 95 percent were running in a single municipality, barely anywhere, or had become stranded investments entirely.
The structural reason isn't hard to find. Germany has roughly 11,000 municipalities, each with its own IT infrastructure, its own legacy software, its own procurement rules. In Bavaria, the dominant provider is AKDB. In the north, it's Dataport. Elsewhere, other proprietary systems — often decades old, with APIs that sometimes speak SOAP and sometimes speak nothing at all. Every new digital service has to connect to these siloed systems. The OZG 2.0, in force since 2024, dropped the rigid national deadline. Citizens now technically have a right to digital government services — but how and when that right is enforced remains undefined.
Why Municipal IT Projects Keep Failing
Most municipalities don't have software developers. Building a digital application means going through public procurement: writing requirements, complying with procurement law, evaluating bids, awarding the contract. That step alone takes three to six months. Then comes the concept phase, then development, then acceptance testing. A simple online form for building permit applications takes the better part of twenty months to go live.
What emerges is usually expensive and inflexible. A single online form for vehicle registration runs up to €250,000. A citizen portal with login and status tracking easily reaches seven figures. And every time requirements change — which they always do — the change request costs extra and takes additional months. The waterfall model, with its rigid requirements specification and fixed acceptance process, was abandoned by the private sector fifteen years ago. In municipal IT procurement, it's still the standard. Projects arrive already outdated, and municipalities that have burned through a budget on one failed system are reluctant to try again.
The underlying problem isn't technical. Online application forms, document-upload portals, case-worker dashboards with deadline tracking — this is all solvable, off-the-shelf technology. What's missing isn't capability. It's a way to deploy that capability without a three-year procurement cycle.
What a Different Model Looks Like
nopex isn't another IT vendor offering the same outcomes with a different logo. The model is different: a municipality describes what its process needs to do, and gets a working application in weeks, not years.
Here's what that looks like in practice. A city of 40,000 residents wants to digitalize its building permit process. Currently: paper forms, in-person submission, eight to twelve weeks processing time. The brief is simple — applicants should be able to fill out forms online, upload drawings and plans, and track their application status. Case workers need a clear queue with deadlines and checklists. That's the starting point.
Four to six weeks later, a responsive application portal is live on the municipality's own infrastructure — on-premise or in a German sovereign cloud such as STACKIT or govdigital, not on U.S. servers subject to extraterritorial data requests. The software belongs to the municipality. No vendor lock-in, no proprietary interfaces, no licensing fees for routine changes. GDPR compliance, accessibility under Germany's BITV 2.0 standard (WCAG 2.1 Level AA), and eID integration for services requiring verified identity are built in by default, not charged as extras.
This changes the equation that has kept the OZG from landing. A mid-sized municipal administration without a dedicated IT department can digitalize processes that would otherwise take years and run significantly over budget. What the OZG mandated from above but couldn't deliver from above can instead be built from the bottom up — provided municipalities stop procuring software the way they did in 2006.
Markus could have registered his business online. He's still waiting.
