EOSC Nodes and Services
EOSC Nodes connect research communities, repositories, digital services and infrastructure providers to the shared organisational and technical environment of the EOSC Federation.
Each Node operates its own resources and services while participating in common Federation capabilities for authentication, discovery, user support, monitoring and service management.
This page explains the architecture of EOSC Nodes, the distinction between Node capabilities and research services, and the processes for enrolling Nodes and onboarding resources.
Page information
Topic: EOSC Nodes and service integration
Coverage: Node types, architecture, core capabilities, federating capabilities, research resources, service onboarding, governance and operations
Primary audience: Research organisations, research infrastructures, repositories, service providers, technical teams, data stewards and project coordinators
Primary sources: EOSC Federation Handbook, EOSC Federation policies, EOSC Academy and EOSC EU Node documentation
Last reviewed: August 2026
What is an EOSC Node?
An EOSC Node is an organisational and technical entry point to the EOSC Federation. It brings together resources, services, operational responsibilities and a represented research community.
A Node may be operated by a single organisation or by a consortium with an identified coordinating organisation and its own internal governance.
The organisation operating the Node remains responsible for its services, resources, users, policies and sustainability while complying with the common requirements of the EOSC Federation.
A Node is an operational organisation: it requires governance, staff, policies, support and sustainable resources.
A Node is a technical environment: it operates or integrates the capabilities needed to connect with the Federation.
A Node is a community gateway: it represents users, institutions or a scientific domain and provides access to relevant resources.
A Node is a service coordinator: it may provide its own services and onboard resources operated by third parties.
Types of EOSC Nodes
National or regional Nodes
Coordinate institutions, resources and services associated with a country or a defined geographical research environment.
Thematic Nodes
Serve a scientific domain, research community or group of related disciplinary infrastructures.
e-Infrastructure Nodes
Provide cross-disciplinary computing, networking, storage, authentication or scholarly communication capabilities.
EOSC EU Node
Provides the first operational European-level Node and reference implementation for core Federation capabilities.
Node, repository and service provider
| Entity | Primary role | Relationship with EOSC |
|---|---|---|
| EOSC Node | Coordinates a portfolio of resources, users and operational capabilities. | Enrols in the Federation and participates in common federating capabilities. |
| Repository | Preserves, publishes and provides access to research outputs. | May be operated within a Node or onboarded as a resource through an existing Node. |
| Research infrastructure | Provides specialised facilities, data, instruments and scientific services. | May operate a Node, participate in a consortium or contribute selected resources. |
| Technology provider | Provides computing, storage, platforms, networking or technical tools. | May offer infrastructure services through a Node. |
| Individual service | Performs a defined research, data-management or technical function. | Is onboarded into a Node and described in its service catalogue. |
EOSC Node architecture
| Concept | Meaning |
|---|---|
| Node Core Capabilities | Operational and technical functions used to run and manage the Node. |
| Node Generic Capabilities | General-purpose research and data-management services useful across scientific disciplines. |
| Node Research Resources | Domain-specific data, software, tools, workflows, instruments and scientific services. |
| Node Exchange | The subset of Node resources made discoverable or accessible to users of the wider Federation. |
| Federating Capability | A capability delivered collaboratively across Nodes through compatible services and Federation interfaces. |
| EOSC Interface | An API, metadata schema, protocol or other defined mechanism through which Nodes interoperate. |
| Interoperability Framework | Technical, semantic, organisational and legal specifications and guidelines used across the Federation. |
Node Core Capabilities
Core capabilities support the internal operation of a Node. They do not all need to be implemented using the same software, and a Node may operate them locally or reuse compatible capabilities provided by another Node.
| Core capability | Primary function |
|---|---|
| Resource Catalogue and Registry | Maintains descriptions of the Node, its services, providers and research resources. |
| Authentication and Authorisation Infrastructure | Authenticates users and controls their access to protected resources. |
| Helpdesk | Receives, routes and tracks user and provider support requests. |
| Service Monitoring | Observes availability, reliability and operational status. |
| Service and Research Product Accounting | Records usage of services, resources and research products. |
| Order Management | Manages requests for services or resources that require approval or allocation. |
| Configuration Management System | Records and controls operational components, dependencies and configurations. |
| User Space | Provides users with a personalised environment for accessing and managing resources. |
| Application Deployment Management | Supports deployment of applications, tools or workflow environments. |
| Resource Provisioning | Allocates and delivers computing, storage or other requested resources. |
Mandatory federating capabilities in 2026
During the 2026 build-up phase, the mandatory integration baseline focuses on five Federation-wide capabilities.
Federated AAI
Enables recognised users to authenticate and move between compatible Nodes and services.
Federated catalogues
Exposes Node, service and research-resource descriptions for Federation-level discovery.
Federated helpdesk
Allows support requests to be transferred to the Node or provider responsible for resolving them.
Operational integration
Connects service monitoring and service-management processes across the participating Nodes.
Federated Authentication and Authorisation
Federated AAI enables users to authenticate through a recognised identity provider and access services in different Nodes without creating a separate account for every provider.
Authentication: verifies the identity of the user.
Authorisation: determines which resources and actions are available to that user.
Single sign-on: reduces repeated authentication when moving between compatible services.
Community attributes: may represent group membership, role, project or entitlement.
API access: token-based mechanisms can support programmatic access to protected resources.
Resource catalogues and Node Registry
Node Registry
Identifies registered Nodes and records their principal organisational and technical information.
Service catalogue
Describes services, providers, access conditions, support and operational properties.
Research product catalogue
Exposes publications, datasets, software and other research outputs.
Catalogue federation
Exchanges structured metadata so resources can be discovered across Node boundaries.
Helpdesk and user support
A federated support environment should allow a user to submit a request without already knowing which Node, provider or technical team is responsible for the issue.
Receive
Accept questions, incidents, access requests and service-support enquiries through documented channels.
Classify
Identify the relevant resource, service, provider and level of urgency.
Route
Transfer the request to the Node or service team capable of resolving it.
Track
Record progress, response time, resolution and recurring support needs.
Service monitoring and management
| Function | What it supports |
|---|---|
| Availability monitoring | Checks whether services and endpoints are reachable and functional. |
| Performance monitoring | Observes response times, failures and other operational indicators. |
| Incident management | Restores normal service after an operational disruption. |
| Problem management | Investigates recurring incidents and their underlying causes. |
| Change management | Controls changes that may affect users or connected Federation components. |
| Configuration management | Maintains information about services, dependencies and operational components. |
| Continual improvement | Uses operational evidence to improve service quality and delivery. |
Accounting, ordering and resource provisioning
Accounting
Records service use, resource consumption and, where relevant, research-product access.
Order management
Manages requests for resources that require approval, allocation or a service agreement.
Resource provisioning
Allocates computing, storage, workspace or specialised service capacity.
Access management
Connects approved requests with entitlements, quotas, credits or provider-specific access conditions.
Node Generic Capabilities
Generic capabilities support common research and research data management tasks across disciplines. They add practical value for users but should not be confused with the mandatory federating baseline.
Storage and file sharing
Online storage, file synchronisation, controlled sharing and collaborative workspaces.
Interactive computing
Notebooks, virtual research environments and interactive analytical services.
Compute environments
Virtual machines, containers, cloud platforms and scalable computing resources.
Workflow execution
Deployment and execution of reproducible analytical and computational workflows.
Node Research Resources
Research data
Experimental, observational, computational, survey and derived datasets.
Research software
Source code, applications, libraries, scripts, models and software environments.
Scientific services
Domain tools, analytical platforms, instruments, catalogues and data processing services.
Training resources
Courses, tutorials, documentation and materials supporting effective use of resources and services.
The Node Exchange
The Node Exchange is the subset of resources and capabilities that a Node makes available to users or services outside its own organisational boundary.
Discoverable: resources are described in an appropriate catalogue.
Accessible: access procedures and restrictions are documented.
Interoperable: relevant metadata, interfaces and identifiers follow agreed standards.
Supported: responsibilities for operation, user support and incident handling are defined.
Monitored: operational status and use can be reported where required.
Services available through EOSC Nodes
| Service category | Examples |
|---|---|
| Data publication | Repository deposit, DOI registration, metadata review and long-term preservation |
| Data discovery | Catalogues, knowledge graphs, metadata harvesting and semantic search |
| Data access | Download, APIs, controlled-access environments and large-file transfer |
| Computing | Cloud computing, HPC access, virtual machines, containers and notebooks |
| Workflow support | Workflow registries, execution platforms, virtual laboratories and reproducible environments |
| Collaboration | Shared workspaces, file synchronisation, project environments and communication tools |
| Research data management | DMP tools, metadata services, FAIR assessment, provenance and curation support |
| Training and support | Courses, helpdesks, onboarding documentation and user guidance |
Enrolment and onboarding
Node enrolment
The process through which an eligible organisation establishes a Node and joins the EOSC Federation.
Provider registration
The process through which an organisation is recognised as the responsible provider of resources.
Resource onboarding
The review and integration of a service, repository, data source or training resource into a Node.
Technical federation
The connection of compatible Node capabilities to Federation-level interfaces.
Typical service-onboarding process
1. Provider assessment
Confirm the responsible organisation, service ownership, maturity and intended user community.
2. Metadata preparation
Describe the service, access conditions, support, policies, interfaces and operational properties.
3. Policy and quality review
Check compliance with the Node’s technical, operational, security and policy requirements.
4. Integration and publication
Connect the required interfaces, validate the service and publish its catalogue record.
Service metadata
| Metadata group | Information to document |
|---|---|
| Identity | Service name, description, provider, persistent reference and version |
| Purpose | Research tasks, user problems and intended communities |
| Access | Open, authenticated, ordered, allocated or restricted access |
| Interfaces | Web interface, APIs, protocols, data formats and technical endpoints |
| Support | Helpdesk, documentation, contact point and support hours |
| Operations | Availability, monitoring, service levels, maintenance and incident procedures |
| Policies | Acceptable use, privacy, security, access, licensing and pricing conditions |
| Maturity | Technical readiness, production status and evidence of use |
Service readiness
Production maturity: resources offered to Federation users should be operational rather than experimental prototypes.
Defined ownership: an organisation and responsible service team must be identifiable.
Existing users: evidence of use helps demonstrate relevance and operational maturity.
Structured metadata: service information must be prepared for catalogue exchange.
User support: documentation and support procedures must be available.
Sustainability: staffing and financing should cover continued operation beyond a temporary technical demonstration.
Access and service-delivery models
Open access
The resource can be used without individual approval, subject to its published terms.
Authenticated access
Users must sign in through a recognised identity provider.
Order or allocation
Access depends on a request, resource allocation, project or available credits.
Controlled access
Access requires eligibility checks, approval, agreements or a secure environment.
Node governance and operational roles
Node Coordinator
Represents the Node in Federation-level strategic coordination and institutional communication.
Operations Officer
Coordinates technical operations, service integration and interaction with Federation operations.
Cybersecurity Officer
Coordinates security policy, risk management and incident response.
Legal and communications roles
Address legal and privacy matters and maintain user and stakeholder communication.
Federation-level coordination
Node Coordinators Committee
Provides the principal forum for strategic discussion, priority alignment and non-binding recommendations.
Node Operations Committee
Coordinates cross-Node technical work, onboarding, interoperability and operational service management.
Working groups
Develop specific policies, interfaces and implementation approaches for shared capabilities.
Tripartite alignment
Connects Node-level implementation with European, national and community-level EOSC governance.
Cybersecurity, privacy and legal compliance
Security governance: define responsibility for risks, incidents, vulnerabilities and security communication.
Identity and access: protect authentication credentials, tokens and authorisation information.
Data protection: determine the roles of controllers, processors and other parties for personal data.
Incident response: establish procedures for reporting, escalation and coordination across providers and Nodes.
Service onboarding: include security and privacy checks before a new resource becomes available.
Legal arrangements: document access, acceptable use, service levels, responsibilities and cross-organisational dependencies.
Interoperability across Nodes
Technical interoperability
APIs, protocols, authentication mechanisms and machine-readable interfaces work across infrastructures.
Semantic interoperability
Metadata schemas, vocabularies and mappings preserve the meaning of exchanged information.
Organisational interoperability
Responsibilities, support, service management and escalation procedures are coordinated.
Legal interoperability
Access conditions, licences, agreements and data-protection roles can be applied across organisational boundaries.
Multi-Node scientific use cases
The added value of the Federation becomes visible when a research workflow combines resources that cannot be provided effectively by one Node alone.
Data from one Node
A thematic or national Node supplies trusted datasets and scientific metadata.
Compute from another
An e-infrastructure Node provides scalable computing or storage.
Shared authentication
Federated AAI provides a consistent user identity across participating services.
Connected results
Outputs are published with metadata, provenance and links to the resources used.
How a researcher uses EOSC Nodes
1. Discover
Search for data, software, services or training resources across catalogues.
2. Authenticate
Sign in through a recognised institutional or community identity.
3. Access or request
Use an open resource or submit the required order, allocation or controlled-access request.
4. Analyse and publish
Combine services from one or more Nodes and publish connected, reusable research outputs.
How a provider contributes a resource
Choose a Node
Identify the Node that represents the relevant country, domain, infrastructure or user community.
Prepare the service
Document ownership, users, maturity, access, support and technical interfaces.
Complete onboarding
Pass the Node’s policy, quality, security and technical integration checks.
Operate and maintain
Keep metadata, documentation, support and service status current.
The role of the EOSC EU Node
The EOSC EU Node acts as the first operational Node, a user gateway and a reference implementation for the wider Federation.
Resource Hub
Supports discovery of research outputs, services, data sources and training resources.
Tools Hub
Provides access to research applications and deployable analytical tools.
User Space
Supports projects, workspaces, notebooks, notifications and service use.
Contributor environment
Supports provider registration, resource onboarding and Node registration workflows.
EOSC Nodes in 2026
The EOSC EU Node is operational as the first Node of the Federation.
The Federation build-up group includes first-wave and second-wave national, thematic and e-infrastructure Nodes.
In July 2026, 28 Nodes participated in the Federation build-up process: the EOSC EU Node and 27 candidate Nodes.
First-wave Nodes are progressing towards production readiness, while technical onboarding of second-wave Nodes has begun.
Current work concentrates on federated AAI, catalogues, monitoring, helpdesk integration, service management and production-readiness assessment.
Node-readiness checklist
Institutional mandate and legal entity
Clear Node identity and value proposition
Defined governance and coordinating organisation
Named operational, legal, security and communication roles
Established research or user community
Production-ready services and research resources
Structured service and resource metadata
Pathway to EOSC AAI and catalogue integration
Helpdesk, monitoring and service-management arrangements
Cybersecurity and data-protection procedures
Multi-Node scientific or federating-capability use case
Sustainable staffing and financing
Willingness to sign the applicable Federation agreement
Common misconceptions
“Every repository should become a separate Node.” A repository can contribute through an existing national, thematic or infrastructure Node.
“A Node is only a technical server.” A Node also requires governance, staff, policies, support and sustainability.
“All Node resources must be open.” Nodes may support open, authenticated, ordered and controlled access.
“Every Node must implement identical software.” Nodes may use different implementations provided that they support the required interfaces and policies.
“Onboarding transfers ownership to EOSC.” Providers retain responsibility for and control of their resources.
“Catalogue registration completes integration.” Production participation also requires operations, support, monitoring, security and service management.
“A thematic portal is automatically a thematic Node.” A Node must demonstrate Federation integration and operational responsibilities beyond its public website.
How to use this page
For researchers
Understand how data, software, computing and support can be combined across Nodes.
For resource providers
Review the metadata, maturity, policy and support requirements for onboarding.
For institutions
Assess whether to operate a Node, join a consortium or contribute through an existing Node.
For Node teams
Use the architecture and readiness sections as an initial planning checklist.
Explanatory status
This page provides an explanatory overview of EOSC Nodes and services based on the EOSC Federation Handbook, EOSC Federation build-up documentation and EOSC EU Node materials.
It does not replace the current Federation agreements, technical specifications, Node enrolment documents, service-onboarding policies or security requirements.
The EOSC Federation remains in a build-up and transition phase. Mandatory capabilities, governance arrangements and production-readiness requirements may therefore be revised.
Organisations preparing an EOSC Node or onboarding a production service should verify all requirements against the current official documentation.