HORIZON-INFRA-2026-01-EOSC: Enabling an Operational, Open and FAIR EOSC Ecosystem

HORIZON-INFRA-2026-01-EOSC: Enabling an Operational, Open and FAIR EOSC Ecosystem

The HORIZON-INFRA-2026-01-EOSC opportunity is a Horizon Europe destination under the Research Infrastructures part of the programme, focused on strengthening the European Open Science Cloud (EOSC). The official REA call page describes this as a two-topic destination aimed at enabling a trusted, interoperable ecosystem for FAIR research data and services that is usable across disciplines and European institutions. It is listed as a standard 2026 launch/submit flow in the REA page, with a deadline of 16 June 2026 (17:00 CEST) and an overall indicative budget of EUR 50 million.

As of the provided source snapshot, this is the core official launch page content to rely on. The page explicitly directs applicants to the EU Funding & Tenders Portal (FTP) for full call text and submission procedures and uses the call reference HORIZON-INFRA-2026-01-EOSC.

For your use, this is not a narrow biomedical grant, one-off travel program, or personal scholarship. It is a Research Infrastructures destination, meaning proposals are expected to have infrastructure-level design and reusable value beyond a single institution.

Key details

Because Horizon and REA call pages are policy-driven documents, always confirm whether this specific call remains open and unchanged at your application date. Dates on official pages can shift, and submission windows can be influenced by national/participating-state procedures.

What this call is designed to fund

This is not a standard curiosity-driven research project call in the usual sense. It is a systemic infrastructure opportunity. The REA summary frames the destination as delivering:

• a web-like environment of services and data for science,
• trusted, FAIR-aligned practices,
• easier uptake of EOSC across infrastructures and research communities.

The Work Programme material identifies this as part of Destination INFRAEOSC under the 2026-27 Research Infrastructures work programme and explicitly includes topics in this destination:

• HORIZON-INFRA-2026-01-EOSC-01: Uptake of FAIR data management and EOSC by research communities and infrastructures.
• HORIZON-INFRA-2026-01-EOSC-02: Trusted frameworks for secure and efficient data sharing in EOSC.

In practical terms, this call usually attracts projects and consortia that can do more than a simple software build. Strong candidates tend to address one or more of:

1. Data-management interoperability at scale (metadata, workflows, federation standards).
2. Cross-service integration (services from different domains and infrastructure operators working with a shared API/data contract model).
3. Community uptake strategy (how many communities and institutions will adopt the service model and why).
4. Security and trust posture (especially for sensitive or high-value research data services).
5. Sustainable service model (proof that the result can persist beyond grant closure).

Because this is an infrastructure and services route, proposals should not center only on method papers or pilot studies. Reviewers and policy teams evaluate what infrastructure effect you create, not only what you build in an isolated lab.

Who this is best for (and who it is not for)

Good fit

This call is usually most suitable for:

• Research infrastructure consortia that can coordinate data services across institutions.
• Organizations already connected to data-intensive domains (biology, social sciences, climate, materials, AI-enabled data analytics, etc.) where cross-project interoperability matters.
• National/international research entities, domain data platforms, large observatories, or federation-style initiatives that can scale.
• Teams that can show measurable community impact (adoption, integration points, service uptime/value).
• Applicants with policy and governance capability (not just technical coding capacity).

Likely weak fit

This is usually a weak match for:

• Single-lab projects that have no route to shared service operation.
• Early-stage prototypes without alignment to EOSC Federation models.
• Programs that rely only on theoretical outcomes without deployment/governance paths.
• Teams that cannot show consortium readiness or inter-organizational coordination.

The Work Programme framing emphasizes the EU-level function of these calls; therefore, a proposal that is technically good but institutionally isolated is often disadvantaged.

Eligibility and participation checks before you start

The public REA page gives high-level eligibility only through program-level channeling (“go to FTP”). That means your first checkpoint is usually not the same as in a traditional one-line NOFO: you must verify in the Funding & Tenders Portal and in the specific topic text exactly which legal, budget, and organizational rules apply.

Before writing, complete this minimum eligibility triad:

1. Organisation eligibility

   • Confirm your legal entities are eligible under Horizon participant rules.
   • Confirm partner composition is allowed for the specific topic type.

2. Geographic participation scope

   • Confirm your organization’s country status and any associated-country conditions.
   • Confirm if third-country participation requires specific clauses or exceptions.

3. Topic-type fit

   • Confirm which topic (EOSC-01 vs EOSC-02) aligns with your deliverable and impact model.

The 2026 page and Work Programme context make clear this is infrastructure-oriented. If your project does not require multi-party coordination and EOSC-level interoperability, it may be better to target a more domain-specific R&I call.

Application process and realistic timeline

Below is a practical sequence that reflects typical EU grant process expectations and the call timeline shown on official pages.

Phase 1: Foundation (immediately)

• Open the official REA destination page and capture the final version URL into your team notes.
• Open the Funding & Tenders Portal topic page for HORIZON-INFRA-2026-01-EOSC and save the exact topic text at your drafting timestamp.
• Determine whether your lead applicant is best positioned for ESA-like large-scale service architecture, EOSC interoperability, or secure data framework leadership.

Phase 2: Structure the consortium and governance model (weeks 1–3)

For infrastructure calls, the consortium model is often the core quality signal.

• Assign a lead institution with strong project-management and EU submission capability.
• Create a publication and data-policy owner, not just a technical lead.
• Define a sustainability steward role for post-award continuation planning.

Phase 3: Draft a coherent proposal narrative (weeks 4–6)

A strong proposal maps around three questions:

1. What bottleneck in EOSC adoption does this project remove?
2. How does the solution connect to existing EOSC services and standards?
3. How will your outputs survive as useful community assets after funding?

Each section should be tightly linked to one of the two EOSC topics and avoid generic infrastructure claims.

Phase 4: Internal technical review (weeks 7–8)

• Validate technical architecture assumptions against the real policy environment (data sovereignty, access control, interoperability requirements).
• Validate budget model against Horizon-compatible cost realism.
• Validate impact statements to avoid vague “we will enable open science” language without measurable indicators.

Phase 5: Finalization and submission (final weeks before deadline)

• Run a pre-submission compliance pass through the FTP toolchain and any portal-required fields.
• Resolve all uncertain links or required attachments early.
• Submit with margin to allow corrections.

Because the call is single-stage and deadline-driven, the strongest teams submit early and still leave time for technical QA.

What your application should include (beyond the obvious)

Everyone submits concept + budget + team. This call rewards applicants that also define implementation ecology clearly.

Core content blocks that matter

• EOSC alignment: Show clearly that your design integrates with existing EOSC architecture or clearly justifies transitional integration.
• Community pathway: Explain how teams/institutions adopt and operate the outcome.
• Security and trust model: Include practical assumptions around access control, auditability, and responsible sharing.
• Sustainability argument: Show who maintains, updates, and scales beyond grant close.
• Measurable milestones: Include explicit adoption, interoperability, and service reliability indicators.

Typical pitfalls that cost scores and credibility

1. Overpromising architecture without governance

   • A lot of technical excellence gets downgraded if governance and coordination are thin.

2. Treating this as a technology-only procurement bid

   • This call expects shared infrastructure impact and ecosystem outcomes, not just code.

3. Under-specifying standards and interfaces

   • If you claim FAIR alignment, explain your metadata, interoperability, and reuse strategy concretely.

4. Ignoring publication schedule and role clarity

   • For multi-organization consortia, undefined responsibilities are usually a hidden review risk.

5. Late portal compliance checks

   • Portal failures and format errors are preventable with early checks.

Review logic and what evaluators usually look for

The Horizon process combines strategic and technical review criteria, but for infrastructure/mission-like topics, two practical filters are usually decisive:

• Added value across the ERA/EOSC landscape: can this project actually improve shared infrastructure behavior for multiple actors?
• Feasibility with real governance: are responsibilities, governance, and sustainability credible, not rhetorical?

Because the call is in a destination context, it is evaluated less on narrow novelty and more on whether it strengthens an ecosystem.

Reviewers frequently reward:

• clear integration roadmap,
• realistic pilot/test deployment plans,
• evidence-based uptake plans,
• mature coordination between technical, legal, and operations roles.

FAQ for applicants (practical)

Is this for non-EU institutions?

Possibly, if they are eligible under the participation conditions for the specific topic on the FTP topic page. Eligibility is topic-dependent and must be confirmed there.

Is there an open-date window?

The destination page describes a 2026 call with a 16 June 2026 deadline. The same call also includes detailed key dates in the REA narrative and associated Work Programme references.

What funding level can I assume?

The REA page gives a EUR 50 million total indicative budget. Use this as the global amount and avoid fabricating per-topic sub-budgets unless confirmed in official portal text.

What are the two topics?

The Work Programme table links this destination to two topics: EOSC-01 (FAIR uptake) and EOSC-02 (trusted frameworks for secure and efficient EOSC data sharing).

What should I read first?

Read in this order:

1. REA call destination page.
2. Horizon Europe 2026-27 Work Programme for the Research Infrastructures destination line references.
3. The FTP topic page for HORIZON-INFRA-2026-01-EOSC (official text, forms, and required attachments).

Recommended strategy for a first-rate submission

Treat this as a policy-technical proposal, not a technical showcase. A strong submission usually combines:

• a clear scientific user problem,
• a real integration architecture,
• a well-governed consortium model,
• and a credible adoption and sustainability model.

If your concept ends with only “our software improves data sharing,” you are probably missing the policy layer. In this call, the policy layer is the substance: shared European openness, interoperability, and durable service operation.

Use the same logic for your written section hierarchy:

1. Problem and policy gap
2. Technical contribution
3. Community and user ecosystem plan
4. Governance and sustainability
5. Risk controls
6. Measurable results by date

Official links

• Official REA call page (main source): https://rea.ec.europa.eu/funding-and-grants/horizon-europe-research-infrastructures/enabling-operational-open-and-fair-eosc-ecosystem-infraeosc_en
• Funding & Tenders Portal call reference (official): https://ec.europa.eu/info/funding-tenders/opportunities/portal/screen/opportunities/topic-details/HORIZON-INFRA-2026-01-EOSC
• Horizon Europe Work Programme context (Research Infrastructures): https://eosc.eu/wp-content/uploads/2025/09/HORIZON-INFRA-2026-2027_09_30_2025.pdf

If your project is infrastructure-oriented and your timeline supports a 16 June 2026 submit deadline, this is one of the strongest EOSC pathway windows currently visible in the 2026/2027 cycle.