Master Plan
Advance European digital autonomy by making European infrastructure easier to discover, compare, and choose.
The purpose is to reduce exposure to external leverage, sustain European jobs and innovation, and give Europe greater control over its technological future in line with its values.
i12e.eu is being developed as an independent, nonprofit reference and comparison platform. Its intended organizational home is a foundation. Its central resource will be a public, freely reusable dataset covering European digital infrastructure.
1. Make infrastructure choices more informed
Choosing infrastructure means assessing capabilities, compliance, continuity, ownership, and dependencies. Different people need different evidence to make that decision.
i12e.eu will organize hosted platforms and open-source projects by category and geography, with comparisons shaped by the visitor’s role. Developers should find useful options for experiments and production systems. Executives and compliance officers should be able to assess organizational requirements and provider viability. Policymakers should see the broader state of European infrastructure.
These decisions can reinforce one another. Familiarity gained through development work can inform organizational recommendations; organizational demand can support further product development. Transparent comparisons should also give providers an incentive to improve.
The ambition is for the dataset to become a reference for both people and AI assistants, reducing repeated research while making its supporting evidence available for inspection.
2. Build a reference that can stay current
Broad coverage requires repeatable collection and maintenance.
AI agents will periodically examine approved websites, documentation, and company records. Humans will approve sources, establish country-specific checks, and direct engineering, research, communication, and funding.
When information is incomplete, the platform will display that uncertainty. Clarification should lead providers to improve their published information, which agents can then rescan. Provider-data corrections will enter through that process, without manual record overrides.
The same maintained reference will support comparisons across sectors and applications tailored to particular industries. Research with users will determine which information makes each comparison immediately useful.
3. Start in the Netherlands and make each stage reusable
Establish Dutch cloud coverage. Research, prototyping and technology experimentation began on 1 June 2026. Main implementation began on 1 September, informed by that preparatory work. The target is a first public version containing Dutch cloud infrastructure data by the end of September. This establishes the initial collection, maintenance, and comparison system.
Apply the data to Dutch journalism. During the remaining SVDJ incubator period, through November 2026, use the reference to map news organizations’ dependencies, identify alternatives, and provide guidance informed by their peers. This connects the general dataset to practical decisions in a specific sector.
Broaden Dutch infrastructure coverage. Following the journalism work, extend coverage to additional categories, including email, content management, payments, tax, billing, and other core infrastructure. Exact completion dates for individual categories remain open. The shared dataset remains sector agnostic.
Expand internationally after the incubator. Reuse the framework and automation while onboarding each country’s sources and company-register checks. Expansion depends on appropriate funding and will require supervision and refinement.
The funded incubator work must remain within the Dutch context.
4. Keep evidence, access, and independence public
Make the data reusable. Published datasets will be freely downloadable and reusable in other tools, services, and products, wherever their users are located. The formal licence, formats, and access interfaces remain to be selected.
Make comparison accountable. Ranking inputs and the method of combining them should be public. Comparisons should reflect practical usefulness, capabilities, compliance, and evidence of continuity, with emphasis appropriate to the visitor’s role.
Distinguish location from sovereignty. Headquarters and incorporation provide initial geographic anchors. Ownership, control, operating entities, and dependencies require separate evidence. A provider can remain in the general comparison with foreign relationships disclosed; strict sovereignty views apply tighter requirements within a selected geographic boundary. Missing evidence produces a notice in the general view; its precise effect in strict mode remains open. Open-source projects require their own assessment of funding, maintenance, and continuity.
Protect independence. Financial support must not determine comparison results. Proposed sponsorship and advertising safeguards include public contracts, dates, amounts, and accounts; predefined advertising locations; and contractual restrictions on influence.
5. Fund the work and expand within its means
The preferred next step is EU funding, sought in late 2026 or early 2027, to support approximately one year of development work alongside compute and AI model usage.
EU funding would support EU member-state coverage and potentially the wider EEA where the funding permits. Otherwise, limited national contributions would be sought for Iceland, Norway, and Liechtenstein. UK and Swiss coverage would have separate funding routes.
Visitor requests could prompt investigation of other European countries where demand, funding, and assessed EU alignment support inclusion. This provisional scope remains conditional. The underlying eligibility principle for additional countries remains open; Monaco’s inclusion route is also unresolved.
Future grants have not been secured. Continuing operation will require funding after the initial build, potentially through public support and sponsorship, with advertising a possible supplement.
Over roughly one year, the ambition is a mature platform with an effectively complete overview across its intended coverage, a working journalism application, and a basis for further sector applications. Geographic pace depends on funding; adoption by external AI tools remains an outcome to pursue.
6. The plan in actions
- Publish the Dutch cloud infrastructure reference.
- Apply it to Dutch journalism and broaden Dutch categories.
- Secure appropriate funding and expand country by country.
- Keep the shared evidence current, reusable, and independent throughout.
The Five W One H document provides the detailed project definition and records the decisions that remain open.