Introduction#
The Eclipse S-CORE project is evolving rapidly. With the launch of our first release, “Eclipse S-CORE 0.5”, we are providing this tutorial to explain how the project works from a technical perspective. Because S-CORE follows an iterative, code-centric development model, this description is updated continuously and may not always reflect the latest state. Contributions from the community are therefore welcome.
Get started with S-CORE#
Overview
Explore the S-CORE platform structure, technology stack and software architecture. Understand the core concepts before you start building.
Contribute own module
Follow a step-by-step guide to build and integrate your first S-CORE module — from source code to CI/CD and doc
What’s next?
Check how you can start being productive immediately
Software artifacts#
Requirements
Analyze Stakeholder requirements for the work with and implementation inside S-CORE. Or get the complete picture on the Requirements page.
Releases
Check out our latest release or explore our release roadmap.
Project structure and processes#
Process
Understand how we work, by reading our Process description. And receive tips & tricks for our used tool stack by reading the Contribute.
Platform Management Plan (PMP)
Read about our project and organization structure in the Project Handbook. And learn how we deal with Platform Safety Plan or care about Software Verification Plan.
Background of Eclipse S-CORE#
Eclipse S-CORE was founded in September 2024 by automotive industry members with a shared goal: a code-first, open-source software platform for onboard ECUs that the whole industry can build on.
Rather than each company independently developing and maintaining a software platform — at high cost and without direct customer value — S-CORE provides a common foundation with:
A reference implementation that catches integration issues early and prevents known bugs from reappearing across projects.
A Functional-Safety-compliant process (ISO 26262) applied to all modules, making S-CORE unique among open-source automotive projects.
Full transparency: process, tooling, and CI checks are open source — any stakeholder can verify the results.
Note: S-CORE is not a ready-to-integrate series product. It is a generic foundation for commercial distributions. Responsibility for ASPICE, ISO 21434 (cybersecurity), and ISO 26262 (functional safety) compliance of the final system always remains with the series project.