A chronological content entry typically used for blog posts, news articles, or similar date-based content.

Posts

post

Projects

project

Videos

video

Podcasts

podcast

People

person

Events

event

Publications

publication

Solutions

solution

Services

service

A standalone content entry generally used for static, non-chronological content such as "About Us" or "Contact" pages.

Pages

page

Partners

partner

Case Studies

case-study


<h3 class="wp-block-heading">EOSC Core Services addressed in EOSC Beyond</h3>



<ul class="wp-block-list">
<li><strong>Authentication &amp; Authorisation Infrastructure (AAI): </strong>The AAI service enables federated authentication and secure access across EOSC services and resources. It provides a consistent user experience by integrating with users&#8217; home identities and supporting the harmonised release of identity and authorisation information.</li>



<li><strong>Service Catalogue:</strong> The EOSC Service Catalogue provides data and functionality to register, maintain, administer and share resources onboarded by various providers. It also serves as the point of reference for all EOSC Core components that add value to this information, making the data and services searchable and accessible through various tools for both researchers and end users.</li>



<li><strong>Interoperability Framework Registry:</strong> The EOSC Interoperability Framework (IF) Registry, as part of the EOSC Platform, is designed to provide tools for detailing the interoperability capabilities of resources, specifically through Interoperability Guidelines (IG). The registry allows for the annotation of EOSC resources across various research and e-infrastructure domains, indicating the interoperability guidelines they adhere to. It facilitates an interoperability-focused overlay of EOSC resources across diverse disciplines, enabling discovery based on their interoperability capabilities and characteristics.</li>



<li><strong>Service Providers Dashboard: </strong>The EOSC Providers Portal components offer front-end functionality to users representing a Provider organisation, who wish to onboard their organisation and onboard resources into the EOSC Resource Catalogue, allowing them to manage and customise the way offerings are presented to end users and finally to gain insights on a multitude of usage statistics, user-generated events and statistics collected.</li>



<li><strong>Knowledge Graph:</strong> The EOSC Knowledge Graph is a subset of the OpenAIRE Graph searchable via the Front Office. The data model has been extended to include the notion of “EOSC Pilot Nodes”, and the resources have been tagged for the EOSC Pilot Node they are associated with.</li>



<li><strong>Front Office: </strong>The EOSC Beyond Front Office is a platform enabling researchers to discover, request, and access the services, analytical tools, data management solutions, storage, and computing resources essential to their work. This integrated platform provides access to a range of services across multiple research domains, as well as data and integrated data analytics tools. Additionally, the Front Office offers a platform for local, national, and international providers, including European e-Infrastructures and Research Infrastructures, to showcase their services and resources, and facilitate access for a broader international user community.</li>



<li><strong>Discovery Hub: </strong>The Discovery Hub is a core service that enables researchers to search, organise, and execute an array of scientific resources, including publications, data, software, services, bundles, training materials and more. It provides an environment for configuring, ordering, and tracking resources within customisable projects tailored to specific research goals.</li>



<li><strong>Research Product Provider Dashboard as a Service for EOSC Nodes:</strong> The service offers to EOSC Pilot Nodes managers a dedicated Provider Dashboard where they can manage their data sources, monitor compliance with the EOSC IF Guidelines for research product onboarding.</li>



<li><strong>PID Service: </strong>The Persistent Identifiers (PID) Service provides a reliable infrastructure for managing and maintaining persistent identifiers using B2HANDLE technology.</li>



<li><strong>Monitoring:</strong> The EOSC Monitoring Service provides insights into the availability and reliability of EOSC services across both the Core and Exchange layers.</li>



<li><strong>Messaging:</strong> The EOSC Messaging Service (EMS) is a real-time messaging platform that facilitates communication between independent applications by allowing users to send and receive messages using a Publish/Subscribe model over HTTP.</li>



<li><strong>Accounting for Services: </strong>The Accounting Service is a robust and scalable platform designed to streamline the collection, aggregation, and exchange of usage metrics across heterogeneous infrastructures, service providers, and projects. It facilitates reliable tracking of resource consumption, promotes interoperability, and supports accurate reporting and accountability across the ecosystem.</li>



<li><strong>Helpdesk:</strong> The EOSC Helpdesk provides a centralised support service for users across multiple communities and e-infrastructures.</li>
</ul>



<div class="wp-block-buttons is-layout-flex wp-block-buttons-is-layout-flex">
<div class="wp-block-button"><a class="wp-block-button__link wp-element-button" href="https://sandbox.eosc-beyond.eu/" target="_blank" rel="noreferrer noopener">Back to Services</a></div>
</div>


Next Generation of EOSC Core Services


<h3 class="wp-block-heading">Key Features:</h3>



<ul class="wp-block-list">
<li><strong>Multi-Environment Hosting</strong>: The Innovation Sandbox hosts three distinct versions of the EOSC Core Services:
<ol class="wp-block-list">
<li><strong>Development</strong>: For individual Core providers to test their own developments.</li>



<li><strong>Integration</strong>: To test and validate the capabilities of the entire EOSC Platform.</li>



<li><strong>Pre-production</strong>: An environment that includes new capabilities delivered by the project, simulating the production environment.</li>
</ol>
</li>



<li><strong>Distributed Infrastructure</strong>: Each Core provider deploys instances of their services for the Sandbox on their premises, mirroring the setup of the production EOSC Core services.</li>



<li><strong>Governed Access</strong>: Processes and procedures are in place to manage service provider access to the Innovation Sandbox, ensuring a structured and secure environment.</li>



<li><strong>Automated Integration</strong>: The integration of EOSC Exchange services with the EOSC Core Infrastructure will be increasingly automated throughout the project, utilising EOSC Core adapters from the EOSC Integration Suite.</li>
</ul>



<h3 class="wp-block-heading">Who Should Apply?</h3>



<ul class="wp-block-list">
<li>Service Providers: Test publishing data, offering cloud resources, or deploying tools in EOSC.</li>



<li>Research Communities: Validate workflows (e.g., structural biology pipelines) and assess EOSC’s capabilities for your domain.</li>



<li>Infrastructure Operators: Trial new EOSC Node setups or interoperability strategies.</li>
</ul>



<p>Technical experts from the EOSC Beyond consortium will provide tailored support throughout your testing journey.</p>



<h2 class="wp-block-heading">How to Get Started</h2>



<p>Selected providers will receive access credentials and onboarding guidance.</p>



<ul class="wp-block-list">
<li>Watch our <a href="https://www.eosc-beyond.eu/event/webinar-eosc-core-innovation-sandbox">Innovation Sandbox webinar</a> if you wish to know more.</li>



<li>Visit the <a href="https://link/">EOSC Core Innovation Sandbox page</a>.</li>



<li>Submit a request via the contact form, briefly describing:
<ul class="wp-block-list">
<li>Your organisation/community.</li>



<li>Your use case (e.g., “Setting up a climate modeling node” or “Testing FAIR data publication workflows”).</li>



<li>Technical requirements or support needed.</li>
</ul>
</li>



<li>Selected providers will receive access credentials and onboarding guidance.</li>
</ul>



<div class="wp-block-buttons is-layout-flex wp-block-buttons-is-layout-flex">
<div class="wp-block-button"><a class="wp-block-button__link wp-element-button" href="https://sandbox.eosc-beyond.eu/" target="_blank" rel="noreferrer noopener">Visit the Sandbox</a></div>



<div class="wp-block-button is-style-outline is-style-outline--1"><a class="wp-block-button__link wp-element-button" href="https://www.eosc-beyond.eu/services/">Back to Services</a></div>
</div>


EOSC Core Innovation Sandbox


<p>EOSC Beyond&#8217;s deliverable D7.1, titled &#8220;Initial EOSC Core Gap Analysis and Requirements Report&#8221; and published in Q4 2024, marked a critical step in enhancing EOSC Core services, ensuring they evolve to meet the dynamic needs of stakeholders, including researchers, service providers, and EOSC Nodes.</p>



<p>Deliverable D7.1 outlines a systematic approach to identifying gaps and defining requirements for improving the EOSC Core services. By engaging stakeholders and building on insights from prior EOSC initiatives, the report proposes actionable enhancements to align with the long-term goals of the EOSC community. It also serves as a blueprint for Work Packages 8 and 9, focusing on developing the <a href="https://www.eosc-beyond.eu/services/">next generation of EOSC Core services</a> and their integration with <a href="https://www.eosc-beyond.eu/pilots/">Pilot Nodes</a>.</p>



<h2 class="wp-block-heading"><strong>Key Highlights</strong></h2>



<ul start="1" class="wp-block-list">
<li><strong>Comprehensive Stakeholder Engagement</strong>
<ul class="wp-block-list">
<li>Consultations with end-users, service providers, and pilot EOSC Nodes ensured the analysis reflected diverse needs and challenges.</li>



<li>Leveraged lessons from earlier EOSC projects to inform requirements for scalability, flexibility, and interoperability.</li>
</ul>
</li>



<li><strong>Federated Architecture for Interoperability</strong>
<ul class="wp-block-list">
<li>Identified the need for a federated architecture to enable seamless interoperability across diverse infrastructure services.</li>



<li>Emphasised harmonised service development to address current and future demands for resource sharing.</li>
</ul>
</li>



<li><strong>Methodology for Iterative Improvement</strong>
<ul class="wp-block-list">
<li>Introduced a systematic framework for iterative requirement gathering, focusing on Core services’ functionality and integration with EOSC Nodes.</li>



<li>Aligns user stories and requirements with the broader vision of an EOSC Nodes Federation.</li>
</ul>
</li>



<li><strong>Actionable Recommendations</strong>
<ul class="wp-block-list">
<li>Proposes advanced technological solutions to strengthen service integration within the EOSC ecosystem.</li>



<li>Highlights pathways to improve scalability, user experience, and cross-node collaboration.</li>
</ul>
</li>
</ul>



<h2 class="wp-block-heading"><strong>Contributing to the evolution of EOSC</strong></h2>



<p>The findings and recommendations in D7.1 lay the groundwork for transforming EOSC Core services into a more robust, user-centric, and interoperable ecosystem. By addressing gaps in federated architecture and service integration, the report paves the way for:</p>



<ul class="wp-block-list">
<li>Enhanced collaboration across research communities.</li>



<li>Streamlined access to and reuse of scientific resources.</li>



<li>Scalable solutions that adapt to evolving Open Science challenges.</li>
</ul>



<p>This analysis is directly informing the development of future EOSC Core services under Work Packages 8 and 9, ensuring alignment with stakeholder needs and long-term sustainability.</p>



<div class="wp-block-buttons is-layout-flex wp-block-buttons-is-layout-flex">
<div class="wp-block-button"><a class="wp-block-button__link wp-element-button" href="https://doi.org/10.5281/zenodo.14052195" target="_blank" rel="noreferrer noopener">Read the deliverable</a></div>
</div>


Initial EOSC Core Gap Analysis and Requirements Report v1.0

core/paragraph

<p>We are announcing the release of two key deliverables that mark a significant step forward in the technical evolution of the European Open Science Cloud. The initial release of the next-generation EOSC Core Services (D8.1) and the EOSC Core Architecture and Capabilities Report (D8.2) together provide both implemented services and an architectural framework for transitioning EOSC toward a federated model.</p>

<p>These documents represent the coordinated work of Work Package 8 (WP8), demonstrating how core services have evolved to support a more distributed and interoperable EOSC ecosystem.</p>

core/heading

<h2 class="wp-block-heading">Architectural Evolution: Toward a Federated Model</h2>

<p>The D8.2 report describes a strategic evolution from a centralised architecture toward a federated model, designed to enhance resilience and support long-term sustainability. This approach is enabled by the introduction of the Node Registry, developed by GRNET and ARC, which provides a mechanism for discovering and managing EOSC Nodes and their capabilities.</p>

<p>"<em>The work delivered by WP8 product teams establishes a concrete foundation for federated EOSC Nodes. The Node Registry service, combined with comprehensive upgrades across the Front Office, Resource Catalogue, AAI, Monitoring, Accounting, Helpdesk, and Messaging services, ensures robust cross-node observability, support, and effective collaboration across the entire EOSC ecosystem. By leveraging the Node Registry, we enable nodes to function as equal, autonomous peers rather than funnelling researchers through a single central portal</em>” – Kostas Koumantaros, GRNET, EOSC Beyond WP8 Leader.</p>

<h2 class="wp-block-heading">Key Technical Enhancements</h2>

<p>The deliverables document specific improvements across core services:</p>

core/list

<ul class="wp-block-list"><li>Security and Access: The Authentication and Authorization Infrastructure now supports Multi-Factor Authentication and OpenID Connect Federation.</li><li>Resource Discovery: Enhanced registries and an expanded Knowledge Graph improve resource discovery and integration with EOSC <a href="https://www.eosc-beyond.eu/pilots">Pilot Nodes</a>.</li><li>Operations: Upgrades to Monitoring, Accounting, Helpdesk, and Messaging services improve cross-node observability and support.</li><li>Deployment Flexibility: Core components are designed as interoperable services that can be deployed as centralised offerings or white-label installations.</li></ul>

<h2 class="wp-block-heading">Supporting the Future Development of EOSC</h2>

<p>These releases provide a technical foundation for the continued development of EOSC's federated infrastructure. The work enables broader service adoption while supporting the scalability required for Europe's Open Science ecosystem.</p>

core/button

<div class="wp-block-button"><a class="wp-block-button__link wp-element-button" href="https://doi.org/10.5281/zenodo.17061478" target="_blank" rel="noreferrer noopener">D8.1 Initial release of the next generation of the EOSC Core Services</a></div>

core/buttons

<div class="wp-block-button"><a class="wp-block-button__link wp-element-button" href="https://doi.org/10.5281/zenodo.17357992" target="_blank" rel="noreferrer noopener">D8.2 Initial EOSC Core Architecture and Capabilities Report</a></div>


<p>We are announcing the release of two key deliverables that mark a significant step forward in the technical evolution of the European Open Science Cloud. The initial release of the next-generation EOSC Core Services (D8.1) and the EOSC Core Architecture and Capabilities Report (D8.2) together provide both implemented services and an architectural framework for transitioning EOSC toward a federated model.</p>



<p>These documents represent the coordinated work of Work Package 8 (WP8), demonstrating how core services have evolved to support a more distributed and interoperable EOSC ecosystem.</p>



<p>These documents represent the coordinated work of Work Package 8 (WP8), demonstrating how core services have evolved to support a more distributed and interoperable EOSC ecosystem.</p>



<h2 class="wp-block-heading">Architectural Evolution: Toward a Federated Model</h2>



<p>The D8.2 report describes a strategic evolution from a centralised architecture toward a federated model, designed to enhance resilience and support long-term sustainability. This approach is enabled by the introduction of the Node Registry, developed by GRNET and ARC, which provides a mechanism for discovering and managing EOSC Nodes and their capabilities.</p>



<p>&#8220;<em>The work delivered by WP8 product teams establishes a concrete foundation for federated EOSC Nodes. The Node Registry service, combined with comprehensive upgrades across the Front Office, Resource Catalogue, AAI, Monitoring, Accounting, Helpdesk, and Messaging services, ensures robust cross-node observability, support, and effective collaboration across the entire EOSC ecosystem. By leveraging the Node Registry, we enable nodes to function as equal, autonomous peers rather than funnelling researchers through a single central portal</em>” – Kostas Koumantaros, GRNET, EOSC Beyond WP8 Leader.</p>



<h2 class="wp-block-heading">Key Technical Enhancements</h2>



<p>The deliverables document specific improvements across core services:</p>



<ul class="wp-block-list">
<li>Security and Access: The Authentication and Authorization Infrastructure now supports Multi-Factor Authentication and OpenID Connect Federation.</li>



<li>Resource Discovery: Enhanced registries and an expanded Knowledge Graph improve resource discovery and integration with EOSC <a href="https://www.eosc-beyond.eu/pilots">Pilot Nodes</a>.</li>



<li>Operations: Upgrades to Monitoring, Accounting, Helpdesk, and Messaging services improve cross-node observability and support.</li>



<li>Deployment Flexibility: Core components are designed as interoperable services that can be deployed as centralised offerings or white-label installations.</li>
</ul>



<h2 class="wp-block-heading">Supporting the Future Development of EOSC</h2>



<p>These releases provide a technical foundation for the continued development of EOSC&#8217;s federated infrastructure. The work enables broader service adoption while supporting the scalability required for Europe&#8217;s Open Science ecosystem.</p>



<p>Access the deliverables:</p>



<div class="wp-block-buttons is-layout-flex wp-block-buttons-is-layout-flex">
<div class="wp-block-button"><a class="wp-block-button__link wp-element-button" href="https://doi.org/10.5281/zenodo.17061478" target="_blank" rel="noreferrer noopener">D8.1 Initial release of the next generation of the EOSC Core Services</a></div>
</div>



<div class="wp-block-buttons is-layout-flex wp-block-buttons-is-layout-flex">
<div class="wp-block-button"><a class="wp-block-button__link wp-element-button" href="https://doi.org/10.5281/zenodo.17357992" target="_blank" rel="noreferrer noopener">D8.2 Initial EOSC Core Architecture and Capabilities Report</a></div>
</div>


Release of Next-Generation EOSC Core Services and Updated Federation Architecture

<p><a href="/terms-of-use">Terms of use</a>  |  <a href="/privacy-notice">Privacy Notice</a></p>


Release of Next-Generation EOSC Core Services and Updated Federation Architecture

Architectural Evolution: Toward a Federated Model

Key Technical Enhancements

Supporting the Future Development of EOSC

Related Content