HORIZON-INFRA-2026-01-TECH-01: R&D for next-generation scientific instrumentation, tools, methods, digitalisation and research infrastructure upgrades (INFRATECH)
A 2026 Horizon Europe destination under the Research Infrastructures programme supporting R&D to modernise European research infrastructures through next-generation instruments, digital methods, and industry collaboration.
HORIZON-INFRA-2026-01-TECH-01: R&D for next-generation scientific instrumentation, tools, methods, digitalisation and research infrastructure upgrades (INFRATECH)
Key details
| Field | Detail |
|---|---|
| Funding source | European Commission, Horizon Europe (Research Infrastructures) |
| Programme | INFRATECH 2026 destination (Destination 4: INFRA-TECH) |
| Topic | HORIZON-INFRA-2026-01-TECH-01 |
| Submission deadline | 16 June 2026 |
| Type | RIA (Research and Innovation Action), Horizon Europe |
| Indicative budget | EUR 110,000,000 for 2026-TECH-01 topic (combined 2026 INFRA-TECH destination: EUR 125,000,000) |
| Geographic scope | EU and associated countries |
| Official portal entry | .../topic-details/HORIZON-INFRA-2026-TECH-01-01 |
| Current cycle status in sources | 2026 call; launch reported as 10 March 2026 and deadline 16 June 2026 |
What this call is and why it is still relevant
This is a Horizon Europe 2026 work-programme call in the research infrastructures cluster, managed by the European Research Executive Agency. The call sits in the “INFRA-TECH” destination and is specifically about building and modernising research infrastructure capabilities across Europe. Its core premise is that future scientific competitiveness increasingly depends on infrastructure-level innovation, not only on project science alone.
The official REA page states this destination has two topics and lists a 16 June 2026 proposal deadline for the 2026 call cycle. The same family of calls appears in the 2026 EU work-programme material for Horizon Europe with an explicit budget split: EUR 110 million under 2026-TECH-01 and an additional related EUR 15 million under 2026-TECH-02, for EUR 125 million total in the 2026 INFRA-TECH destination.
In practical terms, this means the programme is explicitly trying to move from “nice ideas” to deployable upgrades of the research ecosystem: better tools, better methods, better digital backbones, and stronger commercial transfer pathways. If your institution already runs or uses large or specialised facilities, or if you are an organisation that can co-develop technologies with infrastructure teams, the call is usually a strategic fit.
The call is important because the call language links scientific infrastructure development to policy priorities in Europe-wide competitiveness and innovation ecosystems. That means proposals that only describe instrument upgrades without a clear route to user impact, operational resilience, or uptake beyond a single facility are usually weaker. Conversely, proposals that explain how the outputs scale, reduce burdens on multiple research infrastructures, and support ecosystem-level outcomes tend to be stronger.
What the 2026 topics usually fund
The source material identifies HORIZON-INFRA-2026-TECH-01 as part of “next generation scientific instrumentation, tools, methods, digitalisation and solutions for research infrastructure upgrades”. The work-programme framing in the accompanying PDF summary broadens this into practical outputs the EU wants to see:
- R&D and validation of new instrumentation concepts and methods.
- Digital solutions that improve how research infrastructure is used.
- Upgrades that improve efficiency and operational performance.
- Prototypes and demonstrators where relevant.
- Co-creation pathways that connect research infrastructure teams with industry and innovation actors.
- Contributions that expand research and user communities, including industrial or wider innovation contexts.
The same official summary states that the consortium model is expected to include at least two qualifying research infrastructures and relevant industry participation; this is critical for topic interpretation, because the call is intended for consortium-level change in the infrastructure ecosystem, not isolated single-lab procurement.
A useful way to decide fit is to map your proposal against three buckets:
- Infrastructure readiness: Is there a clear infrastructure-side baseline and measurable technical challenge (throughput, precision, data workflow, or operational performance)?
- Digitalisation quality: Are there concrete software, data or automation components that materially improve how the infrastructure works or is shared?
- Impact pathway: Does the project show who will use the new capability, what outcomes are expected, and what happens after funding ends?
If you only have a compelling scientific question without this infrastructure-wide framing, this call may be a poor fit.
Applicant profile and eligibility lens
The official REA listing is short on applicant-type detail because the definitive call rules live in the Funding & Tenders Portal and the work-programme annexes. From official linked references, this opportunity is designed for European collaboration around large-scale infrastructures and industry-relevant co-development. That usually means the following applicants are most likely to pass eligibility checks:
- Research organisations that can anchor work packages for infrastructure innovation.
- Public institutions and universities participating in EU-member or associated-country ecosystems.
- Research infrastructures and ERIC-style actors where there is demonstrated access need and implementation capability.
- SMEs, start-ups, and scale-ups that can contribute engineering, software, prototyping, or commercialization components.
The portal link is the authoritative source for current legal eligibility, with legal and capacity checks enforced through the submission flow. You should always validate this in the portal before investing in full proposal writing.
From the call materials in circulation, two points repeatedly appear in pre-award summaries:
- Eligibility and competitiveness are raised when the consortium has at least two different research infrastructures involved.
- Industry collaboration is expected in many topic formulations, especially where translational innovation and exploitation are relevant.
Another indicator is that the 2026 destination is Horizon Europe RIA, not a pilot micro-grant. So expected applicants are usually consortia that can deliver technical depth, coordination, testing, dissemination, and reporting at EU-project standards.
Practical eligibility checklist before you apply
- Confirm legal entity PIC numbers and legal representative readiness.
- Decide whether you need a full research infrastructure-led consortium.
- Confirm each partner’s role in implementation (e.g., instrument design, digital integration, deployment, data services, validation).
- Confirm cross-border cooperation feasibility (partner institutions in eligible countries with signing authority).
- Ensure you can demonstrate co-creation and exploitation strategy, not only scientific novelty.
Funding amount and award mechanics
The amount field in this page is intentionally split in two levels:
- Topic-specific budget: EUR 110 million is repeatedly linked to HORIZON-INFRA-2026-TECH-01 in the official work-programme materials.
- 2026 INFRA-TECH destination combined: EUR 125 million (including the related topic).
This is not the same as guaranteed per-project funding. The work-programme tables identify indicative project counts and contribution ranges, but exact financial envelopes vary by final topic rules, scoring, and budget distribution. In many 2026 Horizon RIA contexts, the award-size and funding-rate interpretation can change by action and evaluation outcome, so applicants should assume the portal documents and the specific topic annexes are decisive.
Because the call is in a research infrastructures context, budgets are frequently designed for collaborative technical packages (prototype development, software architecture, validation, and deployment support). That means applications that only request support for conceptual work with no demonstrable implementation track often rank weaker. A strong proposal usually demonstrates costed milestones and measurable progression to a deployed result.
Application process (how to prepare your filing path)
The only official submission entry point should be the EU Funding & Tenders Portal topic details page. The REA page explicitly directs applicants there, and this is where the submission process, proposal templates, admissibility checks, and submission deadlines are managed.
A practical flow for this call:
- Create and validate portal account access (EU Funding & Tenders profile requirements).
- Open topic HORIZON-INFRA-2026-TECH-01-01 and confirm you are seeing the exact open-call version.
- Assemble consortium documentation (project roles, legal IDs, institutional commitments, budgets).
- Prepare proposal sections with RIA-level depth, including work packages, milestones, risk control, and exploitation routes.
- Upload all required files through the portal before UTC deadline and avoid last-hour submission spikes.
The portal usually enforces one submission window; for Horizon-style calls the submission date is a hard gate. If your team is not fully onboarded one week before 16 June 2026, you risk missing technical validation checks that fail fast and are hard to fix in the final hour.
Preparation strategy for a competitive INFRATECH submission
This section is the one that usually determines success.
1) Lead with the infrastructure problem, not the technology brand
Reviewers evaluate whether the project addresses a real infrastructure gap and whether it is sufficiently specific to justify EU support. A good proposal opens with:
- Current bottleneck (e.g., throughput limitations, maintenance burden, data pipeline latency, insufficient interoperability).
- Root cause and why incremental fixes are not enough.
- Clear pathway from concept to demonstrated improvement.
2) Make consortium architecture visible in Week 1 draft
Because INFRATECH is built for cross-actor innovation, the consortium section should read like a technical operating plan:
- Who does baseline characterization?
- Who designs and integrates digital components?
- Who runs pilots in actual user settings?
- Who validates performance, security, and transferability?
If you cannot produce a credible coordination diagram in one page, the proposal reads as fragmented.
3) Write impact from the start, not only science
The call language repeatedly references strengthening and modernising the infrastructure ecosystem. Impact claims should be quantifiable:
- Reduction targets (energy, operational time, processing cost, reliability improvements).
- User expansion (new communities, external uptake, cross-domain reuse).
- Post-project continuation (integration into service offers, training plans, open interfaces).
4) Build technical depth in staged terms
A strong INFRATECH narrative moves from low-level technical tasks to ecosystem outcomes:
- TRL advancement with explicit milestones.
- Validation protocol across at least two infrastructure contexts where appropriate.
- Documentation for replicability and integration in different RI environments.
5) Manage the industry element as collaboration, not ornament
The call framing expects industrial co-development where relevant, so include concrete commercial partners and realistic transfer logic:
- Joint roadmap across RI and industry actors.
- IP and access terms that are clear for multi-institution setups.
- A post-funding roadmap for deployment and maintenance beyond grant life.
Common mistakes that weaken applications
- Applying as a near-single-actor team with no real infrastructure-level coordination.
- Overloading the budget narrative with vague cost categories not tied to demonstrable deliverables.
- Ignoring consortium depth and pretending that a single institution can carry all technical and deployment work.
- Treating the call as a generic RIA and omitting explicit RI impact pathways.
- Weakly mapped partner roles causing reviewer uncertainty on who is accountable for validation.
- Last-minute submission without final legal checks in the portal profile, partner metadata, and document format compliance.
A practical fix for #1 and #2 is to state a “before/after architecture” matrix in the proposal introduction. That alone makes reviewers see that the consortium has a coherent system design.
Timeline and what to do before submission
The REA listing and work-programme material indicate launch activity in March 2026 and the June 2026 closure date. Working backward from 16 June 2026, here is a realistic internal timetable:
- Mid-March to April: confirm partner commitment, register portal access, freeze consortium legal setup.
- Late April to early May: finalise technical work breakdown and cost logic.
- Late May to mid-June: draft all sections, internal reviews, data and annex consistency checks.
- Final week before deadline: run final compliance pass, submit with buffer time.
If your consortium is multi-country and includes ERIC/ESFRI-level entities, build an additional pre-submission week for legal and technical sign-offs. EU projects fail during submission mainly from governance and admin gaps, not from scientific content quality alone.
Frequently asked questions (2026 call-specific)
Q1: Is this open now?
As of the provided check timestamp (2026-05-31), available official sources report a 16 June 2026 close for the 2026 call and list 10 March 2026 as the launch. That makes it an open-window call at that snapshot date.
Q2: Can non-EU organisations apply?
The materials indicate EU and associated-country participation channels; however, partner eligibility and participation rights should always be confirmed in the official topic entry and eligibility rules at the portal level.
Q3: Is this a single-stage call?
Public summaries for this family mention single-stage-style submission windows in practice, but exact call rules should be read in the topic page and portal documentation before finalizing your submission format.
Q4: Are industry partners required?
Industry participation is heavily encouraged and repeatedly described in official summary material as part of co-development; it should be treated as a major strength rather than optional for many topic concepts.
Q5: Does it accept small pilot ideas?
This is a full Horizon RIA context. Concepts should usually be implementation-oriented with clear demonstrable outcomes, not only exploratory ideas.
Q6: Can the same team also apply to 2026-TECH-02?
The two topics sit in the same destination and are both listed in the 2026 INFRA-TECH package. Teams should avoid duplicative submissions and should treat each topic’s scope separately before deciding to pursue multiple topics.
Official links and evidence trail
Use only the links below for confirmation and current instructions:
- Official call hub (ERA/REA):
https://rea.ec.europa.eu/funding-and-grants/horizon-europe-research-infrastructures/next-generation-scientific-instrumentation-tools-and-methods-and-advanced-digital-solutions_en - Funding & Tenders topic entry:
https://ec.europa.eu/info/funding-tenders/opportunities/portal/screen/opportunities/topic-details/HORIZON-INFRA-2026-TECH-01-01 - Horizon Europe Work Programme material snapshot used for budget/topic context:
https://www.horizon-europe.gouv.fr/sites/default/files/2026-02/aap-infras-2026-27-infra-tech-2026-01-23-pdf-12292.pdf
Before you apply, revisit these pages to confirm any updates on submission status, scoring, and documentation requirements. Horizon calls often update procedural references in the portal as deadlines approach.
