MIT
Use MIT by default. Apache-2.0 may be selected when an explicit patent grant is materially useful.
Alternative: Apache-2.0Public policy / verified 2026-10-16
One organization.
Different grants.
Elixpo publishes code, papers, hardware, datasets, models, services, and brand material. Each artifact keeps the license stated by its owning repository or release record.
Defaults for new work
A default is a starting point, not a retroactive grant.
These choices guide new Elixpo-owned artifacts. Existing work changes only after authority, contributor, provenance, and compatibility review.
CC-BY-4.0
Use CC BY 4.0 for papers and general documentation unless upstream material requires compatible additional terms.
CERN-OHL-S-2.0
Use CERN-OHL-S-2.0 for new hardware design sources after confirming the artifact is within its intended scope.
Review per artifact
Select per dataset after provenance, consent, privacy, and upstream-license review.
Review per artifact
Select per model, weight, or checkpoint after training-data, upstream-model, and distribution-term review.
Review per artifact
Colour tokens, typography guidance, and general usage guidance remain publicly available. Official sticker artwork is preview-only: no print or distribution permission is granted from the preview, and print-ready material is released only under an approved written event partnership. Copyright permission and trademark or endorsement rules remain separate.
Member projects
The existing license stays.
Joining Elixpo or transferring a repository does not silently relicense a Member Project or its contributor work. Repository custody, maintainer authority, authorship, and copyright are recorded as separate facts.
Unclear terms
No permission is invented.
Existing custom, missing, or mixed licenses remain in force until project authority and contributor permissions are established. A missing or custom license is disclosed rather than presented as open source.
Open-source claims
Describe the artifact that is actually licensed.
An artifact with field-of-use, competitor, royalty, or similar restrictions must not be described as open source merely because another artifact in the repository uses an open-source license.
Official domains, package publisher identities, deployment credentials, signing keys, production data, and service operations are not transferred merely because related source code is public.
Names and marks
Copyright permission is not endorsement.
Copyright licenses do not grant a right to impersonate Elixpo, claim endorsement, or control official names, domains, registry identities, or distribution accounts.
The Elixpo name and an unmodified public logo may be used only to identify a genuine Elixpo project, contribution, compatibility, event relationship, or source link accurately and without implying endorsement.
Written permission is required for official sticker production, merchandise, event co-branding, modified marks, naming a product or organization with an Elixpo mark, or any use likely to imply sponsorship, certification, or governance authority.
Read the public brand guidanceInspect the evidence
Use the license attached to the work—not an assumption about Elixpo.
The public registry preserves current repository-level evidence. The actual license file or artifact record remains controlling. This page explains Elixpo’s publishing practice and is not legal advice.