Skip to main content
v2026.11,986 entries · CC-BY 4.0
CASRAICASRAI Working GroupsHelp write the standards you have to implement24 working groups propose, review and ratify the terms CASRAI publishes, one per dictionary domain. Community and observer seats start at about two hours a month; chairs and co-chairs give 6–8 hours a month. Applications are reviewed.Apply to join a group CASRAI · Volunteer seats
Dictionary termTrack BProposedv2026.2

EOSC Federation

The architectural model adopted by EOSC for federating heterogeneous national, thematic, and pan-European research-data infrastructures into a single user-facing layer, with shared identity and access management, monitoring, accounting, helpdesk, and service onboarding.

ByCASRAI Editorial Board
· Last updated 5 Sept 2026

Working group for this domain: Research-information systems and integration working group

Share this

Ask CASRAI · full access

Ask about EOSC Federation

Full access: large monthly usage, up to 10 source passages behind each answer, and MCP and API access for Claude Code, Codex and other CLIs. Cancel any time.

An AI assistant for research: funder rules, compliance, methods and publishing. It links the sources behind its answers and labels answers that come from a web search.

Answers draw on CASRAI's guides and dictionary plus the federal and funder documents we index: Federal Register, Grants.gov, Regulations.gov and UKRI.

Works on this site and inside Claude, Cursor and the AI tools you already use.

Everything CASRAI publishes — this page, the dictionary, the guides and the news — stays open to read, with no account and no card.

Editorial commentary

EOSC Federation in practice

The EOSC Federation is the operational architecture the European Open Science Cloud (EOSC) uses to bring together heterogeneous national, thematic and pan-European research infrastructures into one user-facing environment, without EOSC itself owning that underlying infrastructure. Rather than building a single central platform, EOSC federates existing infrastructure “nodes,” each of which commits to a baseline of shared interoperability requirements — common authentication and authorisation (AAI), integration with EOSC’s core services, and FAIR-aligned registration of the services it contributes.

Core services and who participates

EOSC’s own documentation groups its core, federation-enabling services around identity and access management (AAI), a service catalogue, monitoring, a helpdesk, and persistent-identifier infrastructure — the shared plumbing that lets a researcher move between federated services with one identity rather than separate logins per provider. The e-Infrastructure Assembly — EGI, EUDAT, GEANT, OpenAIRE and PRACE — has historically formed the backbone of pan-European digital service provision that the Federation builds on, and national and thematic infrastructures have been progressively onboarded as “EOSC Nodes” (a second wave of candidate national and thematic Nodes was invited to enrol in 2026), spanning both national general-purpose infrastructures and thematic ones tied to specific research infrastructures.

How it differs from the EOSC Marketplace

The Federation is the governance and technical-interoperability model — the rules and shared infrastructure that let independently-operated Nodes function as one system. The EOSC Marketplace is the user-facing service catalogue and discovery interface built on top of that federation — where a researcher actually browses and requests services. Put simply: the Federation is what makes a consistent, browsable Marketplace possible across dozens of independently-run providers; the Marketplace is not itself the federation model, just its most visible product.

Worked example / counter-example

A national research-data infrastructure that integrates its authentication with EOSC AAI, registers its services in the EOSC service catalogue, and commits to the Federation’s baseline interoperability requirements becomes an EOSC Node under the Federation model. A standalone institutional repository with no EOSC AAI integration and no catalogue registration is not part of the EOSC Federation, however open or well-run it is on its own terms — and a commercial cloud platform is not, by itself, an EOSC Node merely because researchers happen to use it.

References

  • EOSC Association, EOSC Federation handbook and architectural documentation (eosc.eu).
  • European Commission, European Open Science Cloud strategy documentation.

Examples

Worked examples

  • Is an instance

    A national research data infrastructure becoming an 'EOSC Node' under the Federation architecture.

  • Is an instance

    A thematic biomedical-data infrastructure federating into EOSC alongside its national hosts.

Counter-examples

Looks similar, but isn't

  • Not an instance

    A standalone repository with no EOSC interface is not part of the EOSC Federation.

  • Not an instance

    A vendor cloud is not, by itself, an EOSC Node.

Also known as

EOSC Federation model · EOSC Node architecture

Machine-readable encodings

Use in your systems

JATS XML <kwd> element
xml
<kwd vocab="CASRAI Dictionary"
     vocab-identifier="https://casrai.org/dictionary/"
     vocab-term="EOSC Federation"
     vocab-term-identifier="https://casrai.org/dictionary/term/eosc-federation">EOSC Federation</kwd>
Schema.org DefinedTerm (JSON-LD)
Schema.org DefinedTerm (JSON-LD)
json
{
  "@context": "https://schema.org",
  "@type": "DefinedTerm",
  "@id": "https://casrai.org/dictionary/term/eosc-federation",
  "name": "EOSC Federation",
  "identifier": "https://casrai.org/dictionary/term/eosc-federation",
  "description": "The architectural model adopted by EOSC for federating heterogeneous national, thematic, and pan-European research-data infrastructures into a single user-facing layer, with shared identity and access management, monitoring, accounting, helpdesk, and service onboarding.",
  "inDefinedTermSet": "https://casrai.org/dictionary/domain/research-info-systems#set",
  "url": "https://casrai.org/dictionary/term/eosc-federation",
  "alternateName": [
    "EOSC Federation model",
    "EOSC Node architecture"
  ],
  "license": "https://creativecommons.org/licenses/by/4.0/",
  "publisher": {
    "@id": "https://casrai.org/#organization"
  },
  "author": {
    "@id": "https://casrai.org/#editorial-team"
  },
  "datePublished": "2026-05-21T02:17:25Z",
  "dateModified": "2026-09-05T14:23:15Z",
  "inLanguage": "en",
  "isAccessibleForFree": true
}

Referenced across the research world

University of Cambridge logoColumbia University logoCrossref logoUniversity of Edinburgh logoHarvard University logoUniversity of Oxford logoPrinceton University logoStanford School of Medicine logoUniversity College London logoORCID logoUniversity of Cambridge logoColumbia University logoCrossref logoUniversity of Edinburgh logoHarvard University logoUniversity of Oxford logoPrinceton University logoStanford School of Medicine logoUniversity College London logoORCID logo
  • University of Cambridge logo
  • Columbia University logo
  • Crossref logo
  • University of Edinburgh logo
  • Harvard University logo
  • University of Oxford logo
  • Princeton University logo
  • Stanford School of Medicine logo
  • University College London logo
  • ORCID logo

View CASRAI adoption →