Should Public Grant Data Be Open by Default?

The relationship between the German public funding database, Förderdatenbank, and the digital infrastructure for accessing it presents a fundamental paradox. In the era of data-driven governance, the very information regarding taxpayer-funded investment remains locked behind manual, archaic gateways.

As of May 2026, despite the implementation of the EU Data Act in September 2025 and the Open Data Directive, the German Förderdatenbank continues to resist open data standards. While EU-level portals like the Funding & Tenders Portal have begun integrating API-based access and stricter data management protocols, the national landscape remains largely stagnant. 

This creates a controversial system where automated compliance is encouraged at the European level, yet national authorities continue to cite restrictive data formats.

A Digital Disconnect

The technical accessibility of funding data is in a state of friction. The EU Data Act has mandated that public administrations move toward automated compliance, interoperability, and the deployment of secure data management systems. Newer mandates task innovation actions with developing systems that improve the availability, and interoperability of data across the Union.

However, in Germany, this has not yet translated into specific actions. The Förderdatenbank continues to operate in the old ways due to format, licensing constraints, a concession by the firm Wolters Kluwer who does not want to provide any additional access options. This reliance on manual navigation persists, forcing stakeholders into a "workaround" ecosystem.

Because legitimate API access is unavailable, the market has turned to web scraping. While there is no specific court ruling from 2026 explicitly outlawing the scraping of "publicly available" government data, the regulatory environment has tightened. Under the current EU framework, any systematic data gathering is scrutinized under the requirements for high-quality data curation and privacy protection. 

The Case for Open Grant Data

The arguments for making public funding data "open by default" go beyond mere convenience for tech startups. They touch on the principles of democratic oversight, economic efficiency, and equitable access.

1. Public Funding as Public Data

At its core, funding programs are not commercial products. They are public services funded by the taxpayer. The current opacity creates an information asymmetry. It harms those who need help the most, e.g., small and medium-sized enterprises (SMEs) and first-time applicants who lack the budget to outsource everything to consultants to navigate these systems.

2. Efficiency and the Additional Tax 

Closed access results in a massive, ecosystem-wide waste of resources. Currently, consultant firms, platforms, and regional development agencies manually maintain thei own shadow database of funding opportunities. 

This is a redundant, inefficient use of administrative bandwidth. If the data were centralized and accessible, that energy could be redirected toward making the data useful, such as interpreting requirements, verifying eligibility, and supporting applicants, rather than simply trying to locate the information.

3. Alignment with EU Policy 

The legal scaffolding for a shift already exists. The EU Data Act, the Open Data Directive, and the Digital Single Market strategy all emphasize "open data as infrastructure." Current mandates for Horizon Europe projects explicitly require systems that automate metadata tagging, ontology management, and discovery. 

Continuing to isolate national grant data is not just an inconvenience. It is a deviation from the trajectory of EU digital policy, which seeks to enable data-driven feedback loops for better policy implementation.

The Case for Caution: Addressing the Objections

While the call for open data is strong, the concerns regarding its implementation are not without merit. A responsible transition must acknowledge the technical and ethical risks.

1. The Cost of Infrastructure 

Building, documenting, and maintaining a robust open data standard is not a trivial expense. It requires server capacity, security monitoring, and ongoing support for developers. Public budgets are often stretched, and agencies are right to ask who bears the financial burden of managing an infrastructure that facilitates high-volume, automated queries.

2. Data Security and Fraud 

There is a legitimate fear that bulk, automated access to grant data could be weaponized by bad actors. Sophisticated grant fraud, e.g., systematically exploiting program requirements, seems like a risk although there is a grant decision process in the end, too. 

Furthermore, public databases often contain contact information of officials, which must be handled with GDPR-compliant care. The regulatory environment in 2026 demands that any data sharing include advanced cryptographic protections and privacy-enhancing technologies, which adds another layer of complexity to simply "opening the floodgates". This one can be easily solved by changing the type of contact information provided.

3. Legal Liability and Quality Control 

Funding authorities might fear that if they release data in an API, third parties will redistribute it, causing confusion if the data is misunderstood or if it becomes stale. If a third-party platform provides an incorrect deadline, who is liable? This legal ambiguity regarding "official" versus "third-party" data is a significant hurdle. 

A Path Forward

The choice is not binary. it is not "keep it closed" versus "abandon all control." There are several governance models that would allow for open access while mitigating the risks of cost, security, and quality.

Tiered Access Models (Freemium APIs) 

Government agencies could implement a tiered API system, just like the European Funding & Tenders Portal. Basic program metadata (names, deadlines, eligibility criteria) could be open to the public without authentication. Access to more granular or sensitive details, or high-volume query capability, could be restricted to verified organizations or commercial entities, perhaps under a licensing framework that funds the infrastructure.

Federated Open Data Standards 

Rather than forcing a single, monolithic database, the EU could mandate a common schema across all member states and agencies. Each agency publishes its own "Open Data Feed" in a standardized format. This distributes the technical burden and ensures that third-party platforms are aggregating from authoritative sources rather than scraping fragmented, non-standardized websites.

Public-Private Partnerships (PPP) 

If public sector IT teams are too stretched to maintain a modern open data format, they could form partnerships with authorized third-party platforms. In this model, the government provides the raw data under an open license, and the private sector builds and maintains the access layer. This has the potential to turn a cost center into a managed public utility, provided there are strict SLAs regarding data quality, neutrality, and accessibility.

Conclusion

The current state of German grant data is a relic of an era where information was managed through manual gatekeeping. 

As of mid-2026, the regulatory and technological environment, driven by the EU data policies and advancements in AI-supported compliance, has already shifted in favor of open, interoperable data ecosystems.

The transition to open data is not merely a technical upgrade but rather an economic and democratic necessity. By moving toward a standardized, open data model, Germany can transform its funding ecosystem from a fragmented collection of manual portals into an efficient digital infrastructure. 

The concerns regarding cost, security, and liability are real, but they are challenges to be engineered around, not reasons to remain static. The future of public funding should be accessible, and the tools to make that happen are already within our reach.