1. Which license applies
P2LRN's first-party code identified as covered is distributed under the P2LRN Non-Commercial Source License 1.0 (P2LRN-NCSL 1.0), unless a file states another license. It is not an OSI-approved open-source license.
Annex A, added on October 30, 2026, expands permissions for certain commercial uses. Its grants prevail for those specific uses; other obligations in the base license still apply.
The .p2lrn format may be implemented and authors may sell their own courses.
Annex A.1 and A.4Use, adaptation and redistribution of covered first-party code, with required notices and source.
Annex A.2Free for institutions, including academies with paid courses; it does not grant permission to resell the software.
Annex A.32. Permissions by component
This comparison summarizes Annex A. Before redistributing software, also review the full license and the obligations applicable to your specific version.
On smaller screens, scroll the table horizontally to view all columns.
| Component | Permitted use | Conditions and limits |
|---|---|---|
| The .p2lrn format and courses | Yes: create, implement compatible readers and writers, distribute and sell your own courses. | Annex A.1 and A.4. Third-party rights, trademarks and patents are not automatically granted. |
| Player + Toolkit | Yes: institutional, business and commercial use, integration, modification and redistribution. | Annex A.2. Retain LICENSE, notices, attribution, corresponding source and modification notices. |
| Native offline launcher | Yes: inclusion in executable courses or commercial distributions. | Annex A.2. Redistribution obligations and third-party notices still apply. |
| Studio + Analytics | Yes: internal institutional use of unmodified official versions, including paid training. | Annex A.3. Documented configuration and integrations are permitted; modifying, reselling or offering them as a commercial service to third parties requires express permission. |
| Third-party libraries and content | Depends on each applicable license, not Annex A. | Review the copyright, notices and terms for each dependency or resource. |
3. Before redistributing
If you distribute first-party components covered by the license, check the following under sections 8 and 9 and Annex A.2:
- Retain LICENSE, copyright and attribution notices, NOTICE.md, and applicable third-party licenses.
- Identify modifications and their date; do not represent a derivative as an official release.
- Provide corresponding source code when distributing modified versions or covered software in non-source form, such as binaries or executables.
- Keep source accessible, when offered by URL for a public distribution, throughout distribution and for at least three years after that version's last public distribution.
- Separate third-party rights: Annex A does not relicense H5P, images, libraries, other authors' courses or dependencies.
4. Common situations
Practical explanations to help you choose how to use each component.
Can I create and sell .p2lrn courses?
Yes. Annex A.1 permits creating, validating, distributing and selling .p2lrn documents; A.4 recognizes authors' rights in their original content. You must respect any third-party rights in materials you include.
Can a private training academy use Studio and Analytics for paid courses?
Yes, with unmodified official versions for the institution's own activities. Annex A.3 permits configuring public options and connecting documented integrations.
Can I integrate Player or Toolkit into a commercial platform?
Yes, for first-party code covered by Annex A.2. If you distribute covered software, you must retain the license and notices, identify changes and meet corresponding source code obligations.
Can I modify Studio or Analytics and offer them as SaaS?
Not under the institutional permission in Annex A.3. Modifying, creating derivatives or incorporating them into SaaS, an LMS or a commercial service offered to third parties requires prior express authorization from the rights holder.
When must I provide corresponding source code?
When redistributing covered software in non-source form, or distributing modified versions, under section 9. If corresponding source is offered by URL for a public distribution, it must remain accessible during distribution and for at least three years after the final public distribution of that version.
Is this an OSI-approved open-source license?
No. P2LRN-NCSL 1.0 is source-available and retains restrictions; Annex A grants specific exceptions. Third-party components keep their own licenses.
5. Full legal text and Annex A
The LICENSE file contains the 26 sections of the base license followed by Annex A with additional permissions. NOTICE.md identifies the scope of first-party code and third-party exclusions.
6. Corresponding source code
Source obligations apply to the exact version distributed. The link below provides the corresponding source manifest for the published Player; it does not replace your duty to supply source for a modified or redistributed version.
The following manifests identify and verify the corresponding source of each published component. They include the version, file list and SHA-256 checksums. Versioned URLs remain available independently of the current channel.
7. Official packages
The principal packages are @p2lrn/player, @p2lrn/toolkit, @p2lrn/studio and @p2lrn/analytics. Each package retains its applicable notices; use permissions are not identical for every package.
8. Third-party software and materials
Three.js (MIT), Rapier 3D compat (Apache-2.0) and h5p-standalone (MIT) are documented examples. H5P libraries, embedded content and other dependencies retain their own licenses. They are not covered by the P2LRN rights holder's additional grants.
9. Your courses remain yours
Creating, converting or playing content with P2LRN does not transfer ownership to the project. You can decide how to distribute or sell your original materials while respecting applicable third-party rights and any included software licenses.
10. Uses that require permission
To modify Studio or Analytics, offer them as SaaS, or include them in commercial products or services for third parties, you need prior express permission. Use the contact form on this website to request it. Enter “P2LRN commercial license request” as the subject and explain the components, versions, intended changes and whether you will offer them to third parties. Submitting the form does not grant a license; an express written agreement is required.