Sakai
Learning platform for courses, teaching and collaboration at universities.
ECL-2.0Permissive
Building on it: what may you do?
Short answers based on the licence, for the version in the catalog.
- B1 Change the code for internal use in your company Yes Yes. Keep the licence notices.
- B2 Build your own product or service on top and offer it to customers as SaaS Yes Yes. You don't have to share your code.
- B3 Make a closed-source derivative and sell or distribute it Yes Yes, even closed. The licence and copyright notices must ship with it.
- B4 Use the project's name and trademark No No, not without permission. The licence covers the code, not the name or logo.
Keep in mind
- Contributing back to the project requires signing a Contributor License Agreement (CLA).
This is guidance, not legal advice. Check with a lawyer before deciding.
The licence in brief
Educational Community License 2.0 (ECL-2.0)
Permissive licence based on Apache-2.0. You may use, modify and redistribute freely, including commercially. The patent grant is narrower than Apache-2.0's for contributions by employees of institutions.
This is guidance, not legal advice (inte juridisk rådgivning). Check with a lawyer before deciding.
Facts
- Licence
- ECL-2.0
- Licence type
- Permissive
- Open core
- No
- GitHub stars
- 1.2k
- Latest activity
- Deployment
- Server
- Login/SSO
- SAML, LDAP
- API
- Unknown
- Multi-tenant
- Unknown
- EU vendor
- Unknown
- Source code
- github.com/sakaiproject/sakai
- Source
- GitHub API, fetched 2026-10-03
Licence analysis per use case
Sign in to see what the licence means for eight use cases – from internal self-hosting to offering the tool as a service.
Sign in