Template Subheading
Subheading
Template Text
xxxxxx
xxxxxx
Open Source
Events
Tendering
Newsletter
Contact UsTo start contributing, create an Eclipse account and sign the Eclipse Contributor Agreement (ECA). Explore the XFSC GitHub repositories, fork the one relevant to your interests, and begin coding. More details, tools, and onboarding guidance are available in the Developer Hub.
All contributions must follow the Eclipse Foundation’s standard process:
Sign the Eclipse Contributor Agreement (ECA)
Submit changes via pull requests on GitHub
Ensure code is well-documented, tested, and aligned with project goals
Follow repository-specific rules.
Full details can be found in the Developer Hub.
If you have any technical questions, feel free to reach out to our Technical Lead, Lauresha Toska.
This FAP covers a key function for giving people access rights using verifiable credentials in a federated ecosystem. It lets organizations define and deliver secure digital IDs to their employees in a simple, standardized way. Discover full details of this FAP ›
This FAP offers a clear, end-to-end way to define, set up, and issue credentials across different organizations.
It brings administrators, data systems, and digital wallets together through a secure and standardized process – built on SSI and federation principles.
This FAP tackles a core challenge in federated data ecosystems – fragmented and siloed service catalogues:
- It allows organizations to discover, compare, and integrate digital and cloud services across different providers without creating a central dependency through connecting multiple catalogues.
- The result is greater visibility of available services, reduced vendor lock-in, and a more trusted, scalable foundation for cross-sector and cross-border collaboration. Discover full details of this FAP ›
This FAP showcases how organizations can create a secure, end-to-end data pipeline — from IoT data collection to AI-driven insights.
The FAP demonstrates a federated data pipeline with IoT sensing and data collection, data transfer via data space connectors, data aggregation with a data lake and AI-based data analysis for dashboard vizualisation.
- By enabling seamless data transfer, aggregation, and analysis across domains, it helps organizations unlock real-time insights while maintaining data sovereignty and trust. This approach lays the groundwork for scalable, federated data ecosystems that power smarter, more connected operations. Discover full details of this FAP ›
No Risk
Explore federated data ecosystem concepts without risk and pressure
Test Environment
Test interoperability in a neutral environment
Community
Contribute to the community by sharing insights with the public
Early Access
Benefit from early access to prototypes and architectures
The FACIS SLA Governance Framework
The SLA Governance Framework, which was unveiled for the first time in Berlin, is a practical toolkit that organizations in federated ecosystems can implement immediately. Consisting of two components, the SLA Taxonomy and the SLA Governance Playbook, it provides a shared vocabulary to standardize terminology across providers and a practical guide for creating actionable SLAs, respectively. Together, these tools promote transparency, accountability, and scalability among service providers.
Tender | Digital Contracting Service (DCS)
After refining the specifications and tender documents from the previous tender procedure, we have officially restarted the tender for the Digital Contracting Service (DCS). The DCS will be a Free and Open Source Software solution enabling automated, secure, and legally compliant digital contracting across sovereign IT environments. It is designed for multi-party and multilateral contracting, supporting dynamic service orchestration in federated cloud and edge infrastructures.
Submissions will be accepted until 09 December 2025 (tender already closed) >>
What do companies need to set up a federation?
Hossein Rafieekhah: To build a federation, companies need the following elements: First, legal and governance agreements between the members. Second, a shared trust framework along with common security policies. Third, a digital identity infrastructure – such as decentralized identifiers (DIDs) and verifiable credentials (VCs). They also need technical components for identity management, credential issuance, and verification. These can often be selected or adapted from reference components developed under the Eclipse XFSC project, such as OCM, PCM, TSA, and TRAIN. And finally, secure and standardized communication tools are required to enable the exchange of data and services.
