Eclipse Tractus-X Partners with the Eclipse Dataspace Working Group​

Madrid, Spain | Dataspace Symposium 2026 – We are thrilled to announce a significant milestone for Eclipse Tractus-X at the Dataspace Symposium 2026 (February 10-11, 2026, in Madrid, Spain): our project has officially partnered with the Eclipse Dataspace Working Group (EDWG)!

Following a successful vote among the committee and project leads, Eclipse Tractus-X has been included under the purview of the Eclipse Dataspace Working Group. This partnership marks a pivotal moment in our journey and sends a clear signal: Eclipse Tractus-X is more ready than ever to drive the adoption of future dataspace solutions and accelerate dataspace development.

Making this announcement at the Dataspace Symposium—bringing together industry leaders, innovators, and standardization experts from around the world—underscores the international significance of this partnership and our shared commitment to advancing the dataspace ecosystem.

Hi Everyone 👋,

Let's have the first international Open Source Hackathon of Eclipse Tractus-X ever! 🌍🚀 And in Spain! 🇪🇸

Hello, Eclipse Tractus-X Community!

Collaboration drives the success of Eclipse Tractus-X, and we are excited to invite you to the Release Planning sessions for R26.06! These sessions are your chance to shape the roadmap, align with the community, and ensure a well-structured release.

Rooms for Discussion and Planning:

• Release Management
• Test Management

Key Information:

• Dates and Times: Listed for each session below.
• Resources: Visit our open meetings page for all session links and additional documentation.
• Preparation Materials: Ensure readiness by reviewing the provided templates, guidelines, and your own features.
• Overall process description: Release Planning Process

We look forward to seeing you there and working together to make R26.06 a success!

Hello Tractus-X community,

We are excited to announce the launch of KIT 2.0 Architecture - a major redesign of how we visualize and organize our KIT ecosystem. This update brings a fresh perspective to understanding the layered architecture of Eclipse Tractus-X, making it easier than ever to explore and navigate our comprehensive collection of KITs.

What is a KIT?​

KIT, short for Keep It Together, is an open-source toolbox with comprehensive documentation that enables multiple stakeholders (Business, Solution Providers, Developers) to build interoperable applications compatible with the Eclipse Tractus-X dataspace technologies, and support the compliance with industrial standards from standarization organizations (Catena-X e.V., IDTA, ISO/DIN, EDWG, Manufacturing-X, etc.) and in some cases enable regulatory compliance.

A KIT provides everything needed to implement and deploy specific business scenarios within a dataspace environment - from architectural guidance and API specifications to reference implementations and operational procedures. Each KIT serves as a complete, self-contained package that enables developers, operators, and business stakeholders to understand, build, and run solutions that are interoperable across the dataspace network.

What's New in KIT 2.0 Architecture?​

The KIT framework has evolved significantly from version 1.0 to 2.0 to support the growing needs of multiple dataspaces and industries. This transition represents a fundamental shift in how we approach dataspace interoperability - moving from a single-industry focus to enabling multiple industries to leverage the same foundational technologies while maintaining the flexibility to address industry-specific requirements through modular extensions.

Multi-Industry Architecture​

The new architecture features a beautiful hexagonal layout that visually represents the four main layers of our KIT ecosystem, allowing now KITs to be industry specific:

Modular Reusable Architecture​

Here is a detailed explanation of the diagram above, and how this architecture improves reusability:

Standardized KIT Development Process​

With KIT 2.0, we've established a comprehensive framework and clear guidelines for creating and maintaining KITs. Our Tractus-X Release Guidelines (TRGs) provide a structured approach to KIT development, ensuring consistency, quality, and interoperability across all KITs.

TRG 10 - Keep it Together (KIT)​

The TRG 10 series defines the complete lifecycle and requirements for KIT development:

Active TRGs (Necessary for the new Webpage Structure)​

• TRG 10.01 - KIT Architecture: Defines the architectural categories and layered classification of KITs within the Eclipse Tractus-X ecosystem
• TRG 10.02 - KIT Structure: Specifies the required folder structure, documentation organization, and content requirements for each KIT
• TRG 10.03 - KIT Lifecycle: Outlines the maturity levels (Incubating, Stable, Deprecated) and the progression criteria for KITs

Draft TRGs (Coming Soon)​

• TRG 10.04 - KIT Graduation Process (Draft): Details the process for KITs to move from incubating to graduated status
• TRG 10.05 - KIT Deprecation Process (Draft): Describes the deprecation process for KITs that are no longer maintained or relevant

KIT Master Data - Single Source of Truth​

All KIT metadata is centralized in a single source of truth - the KIT Master Data Overview. This comprehensive registry contains:

• Metadata: Version numbers, last updated dates, maturity levels, and graduation dates
• Architecture Classification: Which layer each KIT belongs to (Dataspace Foundation, Industry Core, etc.)
• Dataspace Assignments: Which dataspaces each KIT supports (Catena-X, Manufacturing-X, etc.)
• Links & Resources: Routes to documentation, repositories, and related materials
• Lifecycle Status: Current state (Incubating, Graduated, Deprecated) and progression history

File Location is at the /data folder:

/data/kitsData.js

In this way, the development, creation and usage of KITs is streamlined, transparent and easier to maintain.

KIT Datamodel​

There is a metadata datamodel for every KIT defined as follows:

{
  id: '<unique-kit-id>',                    // Unique identifier for the KIT
  name: '<KIT NAME IN UPPERCASE>',          // Display name
  logo: <KitLogoComponent>,                 // React SVG component
  logoHeight: <number>,                     // Logo height in pixels
  logoWidth: <number>,                      // Logo width in pixels
  route: '<route-to-kit-adoption-view>',    // Path to KIT documentation
  colors: {
    primary: '<hex-color>',                 // Primary brand color
    gradient: 'linear-gradient(...)'        // CSS gradient definition
  },
  maturity: {
    currentLevel: '<level>',                // 'Sandbox' | 'Incubating' | 'Graduated'
    graduationStatus: '<status>',           // 'draft' | 'in progress' | 'in review' (for Incubating only)
    graduatedAt: '<YYYY-MM-DD>',           // Date when graduated (only if Graduated)
    deprecatedAt: '<YYYY-MM-DD>'           // Date when deprecated (only if deprecated)
  },
  deprecated: <boolean>,                    // true | false
  domain: '<domain-category>',              // e.g., 'Sustainability', 'Engineering', 'Supply Chain'
  industries: ['<industry-id>', ...],       // Array of industry IDs (optional for foundation KITs)
  description: '<kit-description>',         // Short description of the KIT
  metadata: {
    created: '<YYYY-MM-DD>',               // Creation date
    lastUpdated: '<YYYY-MM-DD>',           // Last update date
    latestVersion: '<version>',            // Current version (semantic versioning)
    new: <boolean>                         // true if recently added
  }
}

Additionally, there is a Datamodel for Industries and for Dataspaces defined in a similar manner, more information can be found clicking on the button below!

KIT Statistics - Insights into the KIT Ecosystem​

Thanks to the master data, now we can also provide detailed KIT Statistics that give insights into the current state of the KIT ecosystem:

Key Statistics Preview​

Architecture Distribution & Growth Trends​

Thanks to this we can now monitor the growth and evolution of the KIT ecosystem over time, providing valuable insights into adoption trends and areas of focus. And knowing how is the state of life from the KITs evolving during each release.

KIT 2.0 Content Structure and Artifacts​

Now it is defined a clear structure for the content and the views

And depending from what is available a KIT will position itself in one or another lifecycle level:

KIT Lifecycle​

Understanding the KIT lifecycle is crucial for contributors and users alike. Each KIT in the Tractus-X ecosystem follows a structured maturity progression that ensures quality, completeness, and real-world validation before reaching production readiness.

The Three Maturity Levels​

KITs progress through three distinct lifecycle stages, each with specific requirements and validation criteria:

Lifecycle Management​

All lifecycle transitions are tracked in the KIT Master Data and validated according to the TRG 10.03 - KIT Lifecycle guidelines. This ensures transparency and consistency across the entire KIT ecosystem.

Artifact Requirements by Maturity Level​

Each maturity level has specific artifact requirements that must be fulfilled for a KIT to progress. The table below shows the comprehensive list of required artifacts for each lifecycle stage:

KIT Template​

Follow the KIT template to have an example of folder structure that can be followed following the KIT Framework Guide and the needed content for each view in order to achieve all requirements from the KIT Lifecycle.

KIT Office Hours - Get Expert Support​

Need help developing your KIT or have questions about the KIT framework? Join our KIT Office Hours - a dedicated time for the community to get direct support from the KIT development team.

What are KIT Office Hours?​

KIT Office Hours are regular community sessions where you can:

• Get guidance on KIT development and lifecycle progression
• Ask questions about TRG compliance and best practices
• Discuss your KIT architecture and implementation approach
• Receive feedback on your KIT graduation readiness
• Connect with other KIT developers and maintainers

How to Participate​

Office hours are held regularly and open to all community members. Whether you're just starting with KIT development or preparing for graduation review, the team is here to help.

Learn More​

Want to dive deeper into the KIT framework? Explore our comprehensive documentation to understand the complete structure, artifacts, and requirements for building your own KITs.

All KITs are licensed under the non-code CC-BY-4.0 License.

All industry logos and trademarks are property of their respective organizations.

Hello Eclipse Tractus‑X community,

We are about to start the test phase (03.11.2025 - 21.11.2025) for Release 25.12. Below you'll find the key meetings and quick facts — visit the Open Meetings page for session links, agendas, and additional resources.

Key meetings​

• Briefing — Testing Phase for R25.12

  • Date: Monday, 20 October 2025
  • Time: 08:30 — 09:30 (local timezone shown on the Open Meetings page)
  • Purpose: Prepare for the test phase, clarify the test process, and review Release Check Issues.

• Kick‑Off — Testing Phase for R25.12

  • Date: Monday, 3 November 2025
  • Time: 08:30 — 09:00
  • Purpose: Provide updates on deployment status and answer questions about the test phase.

• Eclipse Tractus‑X — E2E Test Phase Daily (R25.12)

  • Occurs every weekday: 4 November 2025 — 21 November 2025
  • Time: 08:30 — 09:00
  • Purpose: Onboarding and deployment status on the INT environment, defect/blocker updates, and test status across participating products.

Where to find details​

All meeting links and resources are published on the Open Meetings page (look under "One-time meetings"):

• Briefing - Testing Phase for R25.12
• Kick-Off - Testing Phase for R25.12
• Eclipse Tractus‑X — E2E Test Phase Daily (R25.12)

Join the conversation​

• Test Management Matrix Chat: https://matrix.to/#/#tractusx-test-management:matrix.eclipse.org

Contact​

If you have questions about the test phase setup, test environments, or participation:

• Monika Jacobsen — Test Management — monika.jacobsen@catena-x.net

We look forward to your participation and support during the test phase.

— The Release & Test Management Team

Hello, Eclipse Tractus-X Community!

Collaboration drives the success of Eclipse Tractus-X, and we are excited to invite you to the Release Planning sessions for R26.03! These sessions are your chance to shape the roadmap, align with the community, and ensure a well-structured release.

Rooms for Discussion and Planning:

• Release Management
• Test Management

Key Information:

• Dates and Times: Listed for each session below.
• Resources: Visit our open meetings page for all session links and additional documentation.
• Preparation Materials: Ensure readiness by reviewing the provided templates, guidelines, and your own features.

We look forward to seeing you there and working together to make R26.03 a success!

Dear Eclipse Tractus-X- and Dataspace-Community,

The Eclipse Tractus-X Community Days serve as a platform for collaboration, innovation, and knowledge exchange within the Tractus-X ecosystem. Building on the success of previous events, this fifth edition brings together industry leaders, developers, and open source enthusiasts to help shape the future of digital transformation in the automotive industry.

If you'd like to be involved — whether through a presentation, workshop, or sharing a use case — we'd be glad to hear from you and welcome your contribution to this vibrant community gathering.

New Tutorial Available​

Based on the upstream Identity Hub, one of our brave proud committers Carlos Diez Rodriguez, has created an effective tutorial which will guide you from 0 to hero on how to start developing with the Eclipse Tractus-X Identity Hub!

You will find the tutorial here:

https://eclipse-tractusx.github.io/docs/tutorials/identity-hub

What are our objectives?​

We are restarting the development of the Identity Hub (Wallet) in Eclipse Tractus-X.

Our objectives are the following:

• Create a well documented identity hub using the Eclipse Dataspace Components framework.
• Implement a multi "-X" dataspace support wallet.
• Reduce complexity for applications that are willing to use the wallet.
• Make a reality in Eclipse Tractus-X aspect model credentials issuance, based on frameworks like the dpp-verification and the future Data Trust & Security KIT!
• Demonstrate the issuance, holding, request and management of membership credentials.

Our next features​

Feel free to look at our latest features sig-release identity hub

We are planning to develop a frontend, a backend, have an extensive documentation, and much more!

How can I contribute?​

We are looking for developers and brave contributors which want to innovate and collaborate for building this new open source wallet together!

If you are interested on joining the development, feel free to join our open meetings and build dataspaces with us!

Links of interest​

Our Matrix Chat

Our Repository

Our Planning Board

Hello, Eclipse Tractus-X Community!

Collaboration drives the success of Eclipse Tractus-X, and we are excited to invite you to the Release Planning sessions for R25.12! These sessions are your chance to shape the roadmap, align with the community, and ensure a well-structured release.

• New room in our matrix chat -> Release Management
• New room in our matrix chat -> Test Management

Key Information:

• 📅 Dates and Times: Listed for each session below.
• 📂 Resources: Visit our open meetings page for all session links and additional documentation.
• 🔗 Preparation Materials: Ensure readiness by reviewing the provided templates, guidelines, and your own features.

We look forward to seeing you there and working together to make R25.12 a success!

Hello Eclipse Tractus-X Community,

We’re happy to announce that the Eclipse Tractus-X website has been successfully updated. The underlying documentation framework, Docusaurus, is now running on version 3.7.0.

This upgrade was essential, as we were previously using an outdated version that limited our flexibility and security.

What's New?​

Visually, not much has changed — but you might notice that the News Blog is now grouped by year for improved clarity. While the visible updates are minimal, this upgrade clears the path for more improvements in the future.