Skip to main content

What’s the ELISA Project’s mission?

ELISA stands for Enabling Linux in Safety Applications.

The mission of the Project is to define and maintain a common set of elements, processes and tools that can be incorporated into Linux-based, safety-critical systems amenable to safety certification. Please review the Project Charter for additional details.

Is the ELISA Project producing a safe Linux distribution?

No, the Project is not producing a safe Linux distribution. Instead, the Project provides a neutral space for open source and safety communities to collaborate so that common tools, methods, processes and documentation can be defined and maintained to help companies more easily demonstrate that a specific Linux-based system meets the necessary requirements for safety certification. Please note that the output from the Project:

  • Cannot engineer your system to be safe
  • Cannot ensure that you know how to apply the described process and methods
  • Cannot create an out-of-tree Linux kernel for safety-critical applications.
  • Cannot relieve you from your responsibilities, legal obligations and liabilities.

How is the ELISA Project collaborating with safety standards organizations and safety certification authorities?

Although the ELISA Project doesn’t directly work with safety standards and safety certification authorities, many of its members and contributors do. So there is a wealth of knowledge and expertise in safety standards and certification among the Project’s participants.

How does the ELISA Project compliment other communities that are also working towards enabling safety in open source projects?

The Project participants are in close collaboration with other open source projects with a safety-critical analysis focus such as the Xen Project and the Zephyr Project.

In addition, the ELISA community members also interact with open source projects with safety-critical relevance and comparable system architecture consideration such as Automotive Grade Linux, SOAFEE, and SDV Working Group at the Eclipse Foundation.

Beyond those, there have been outreach and interactions with those in the Yocto Project, SPDX, Real-Time Linux and the Linaro communities. If there are other potential collaboration opportunities that you would like to see please reach out to us at

How is the ELISA Project community organized?

The Project is made up of horizontal Working Groups such as Safety Architecture, Linux Features, Tool Investigation, Open Source Engineering Process, and Systems as well as vertical use case based Working Groups in Aerospace, Automotive, and Medical Devices domains.

These Working Groups collaborate to produce an exemplary reference system. Linux Features, Architecture and Code Improvements should be integrated into the reference system directly. Tools and Engineering Process should serve the reproducible product creation. Medical, Automotive, Aerospace and additional future WG use cases should be able to strip down the reference system to their use case demands.

The Project’s Technical Steering Committee (TSC) oversees the Working Group activities and coordinates cross Working Group collaboration to drive the technical direction of the Project. You can interact with the TSC by subscribing to its public forum and attend its biweekly meeting that’s open to the public by default.

What’s the IP policy for contributions to ELISA?

Generally speaking, new inbound code contributions to the Project shall be made under the GNU General Public License, version 2.0 only (GPL-2.0-only), available at, which aligns with the Linux kernel’s license. Exceptions need to be approved by the governing board.

Generally speaking, documentation and specifications will be received by the Project under the Creative Commons Attribution 4.0 International License, available at

Please review the complete Intellectual Property Policy section in the Project Charter for additional details including contributing to upstream projects and alternative license approval.

Can I use ELISA Working Group’s output within my product? What are the license requirements?

Yes, you can use output such as tools and documentations produced by the ELISA Project’s Working Groups.

Generally speaking, all outbound software code are made available under the GNU General Public License, version 2.0 only License.

Generally speaking, documentation and specifications are also made available by the Project under the Creative Commons Attribution 4.0 International License, available at

Please review the complete Intellectual Property Policy section in the Project Charter for additional details.

What are some of the main ways to participate in ELISA?

Are there opportunities to connect with the key participants of the ELISA Project?

There are many ways to connect with the key participants of the Project. For example, you can join the regularly scheduled meetings, such as the bi-weekly Technical Forum meeting, aka the public Technical Steering Committee meeting or the public meetings of any Working Group meetings led by key participants of the Project.

Another way to connect with other participants of the Project is to simply subscribe to our mailing list and introduce yourself on the mailing list forum.

To facilitate closer interaction, we recommend that you attend one of our upcoming events, such as the bi-annual in-person ELISA Workshop when we gather the members and contributors to collaborate and accelerate progress and plan for future goals.

Do I need to be a member to participate in the ELISA Project?

As with all open source collaborative projects hosted here at The Linux Foundation, you have the ability to participate as an individual, an employee of a company that is a non-member, or as an associate or corporate member of the ELISA Project.

The advantage of open source collaborative projects is that it’s open to anyone – so with the ELISA Project, you have access to public meetings, mailing lists, events, GitHub and many other public resources. Please do note that these resources would not be available without the support of the Project’s members.

Since ELISA is an open source project, why should a company consider supporting it by joining as a member?

Companies join the ELISA Project to:

  • Demonstrate thought leadership in, strategic alliance with, and investment in the mission of ELISA that’s important to their business goals
  • Network with other members to help define, establish, and maintain industry-wide processes, norms, and best practices in enabling Linux in safety applications
  • Support the project by helping fund services such as neutral governance, project management, infrastructure and tooling, events and marketing that the community relies on to effectively collaborate.

If you’re interested in membership, please visit ​​the Join ELISA page and contact if you have further questions.

What are the criteria for being approved as an ELISA Project Associate Member?

Non-profit organizations, open source projects and government entities are welcome to join the Project as Associate members.

Unlike for private sector General and Premier Members, for Associate members, no membership fee structure is imposed on qualified public sector members; however, all members will be expected and required to participate in applicable ways through the contribution of human capital, intellectual property, and/or goodwill.

The ELISA Project expects Associate Members to contribute in the form of research, code development, documentation, and collaboration with Working Groups etc. A prospective Associate member will be asked to provide evidence or plans for how they will contribute before being approved as an Associate member by the Project’s Governing Board.

I have a question and am not sure who and where to ask.

Please reach out to if it’s a general question. Please reach out to if the question is about how to join ELISA as a member or about membership benefits.

I am interested in learning more about the ELISA Project, do you have any resources to recommend?

Here is a list of additional resources you can check out to learn more about the Project.