White Telekom Logo

Menu

Digital public services need a shared platform.

Platform strategy

From portals to a shared platform.

Germany needs binding standards, reusable platform services and a controlled migration architecture to make digital public services work end to end.

Download german whitepaper
Summary
Skills shortages, federal fragmentation and legacy systems continue to slow Germany’s digital public administration. The whitepaper proposes a shared platform with one access point, an API platform, open standards, controlled AI assistance and mandatory reuse. Three phases, clear responsibilities and measurable targets lead from the platform core to gradual migration.
Whitepaper Authors
Page content
    Man in business attire sitting in a lounge chair looking at his smartphone
    Test123
    Rethinking administration

    Platform instead of portal.

     
    How a shared platform can drive digital government forward.

    You are currently viewing a placeholder content from HubSpot. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.

    More Information
    Platform services for end-to-end public services

    Public services as platform products.

    One access point for people and businesses

    A citizen app or unified web frontend guides people through life events and needs. Dialogue, forms, evidence, payments, status and a mailbox are connected in one traceable flow.

    A shared backend for public administration

    The public administration platform orchestrates services, data, evidence and processes. It connects legacy systems, supports case workers and provides reusable services.

    API platform as transition architecture

    Standardised, versioned and documented interfaces make legacy systems connectable. This allows the new platform to be integrated gradually without replacing every existing system at once.

    AI agents with human final decisions

    Agents support needs, forms, evidence, process routing and quality assurance. Roles, permissions, tool use, logging and escalation paths limit automated actions.

    Open standards for interoperability

    FIM, XÖV, OpenAPI, AsyncAPI, OAuth 2.0, OpenID Connect, eIDAS, EUDI Wallet and NOOTS provide the functional, technical and trust foundation.

    Mandatory reuse through a marketplace

    A repository provides services, interfaces, agents, process models, adapters, test cases and documentation. Reuse becomes a technical and funding rule.

    KeyVisual Verwaltungsdigitalisierung 2560x1242
    Architecture and migration

    Implementation combines platform build and gradual migration.

    The eGov hub brings together access, services, processes, data, evidence, AI functions and integrations. An API gateway, authentication, authorisation, logging and protection mechanisms form the technical base.
    An API platform encapsulates existing systems behind standardised interfaces. Modern APIs are used directly, while older systems connect through adapters. Versioning, documentation and event capability make integrations verifiable.
    A controlled agent layer supports intent recognition, forms, documents, evidence, process routing and case work. The legal final decision remains with the responsible authority.

    FIM, XÖV, OpenAPI, AsyncAPI, OAuth 2.0, OpenID Connect, eIDAS, EUDI Wallet and NOOTS connect functional models, data exchange, identity and evidence.

    Legacy systems are assessed by strategic relevance, technical replaceability and operational risk, then connected, renewed, consolidated or retired.
    A permanent product team, clear service levels, incident and problem management, and central documentation should make operations and support reliable across system boundaries.

    Platform strategy

    From OZG mode to platform strategy.
    Measurable platform operations

    Public metrics steer progress.

    Four measures for governance.
    Usage, connectivity, reuse and cost show whether the platform works in operation. Values should be updated and published regularly, then linked to prioritisation, funding and course correction.

    40%

    Usage: By the end of Phase 2, the platform should reach 40 percent of the population.

    80%

    Connectivity: By the end of Phase 2, 80 percent of the 100 most important systems should be reachable through the integration layer.

    60%

    Reuse: From Phase 3, at least 60 percent of new services should be based on existing marketplace components.

    -40%

    Cost: By the end of Phase 3, digital transaction costs are targeted to be at least 40 percent lower than analogue costs.
    Our experts

    Get to know us.

    Our consulting areas​

    Discover the areas where we provide tailored solutions designed to enhance value for our clients.

    Select your location

    Contact

    You are currently viewing a placeholder content from HubSpot. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.

    More Information

    On this page

    On this page

    Get in touch

    Contact

    You are currently viewing a placeholder content from HubSpot. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.

    More Information