> For the complete documentation index, see [llms.txt](https://edehr.gitbook.io/edehr-compass/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://edehr.gitbook.io/edehr-compass/legal-and-compliance/licensing/understanding-the-open-source-licensing-agpl-3.0.md).

# Understanding the open source licensing (AGPL-3.0)

## GNU Affero General Public License v3.0 (AGPL-3.0)

### Overview

This page is a reference for institutions evaluating or adopting EdEHR's open-source edition. It explains the AGPL-3.0 license that governs the public EdEHR source code, what it requires, and what it means in practice.

Note that EdEHR is dual-licensed: the public open-source edition on GitHub is available under AGPL-3.0, while EdEHR Technologies also delivers the platform as a proprietary commercial SaaS offering. These are distinct products. The public AGPL-3.0 source is not the live commercial platform. Institutions using the hosted service do not need to concern themselves with AGPL-3.0 compliance -- that applies to those who deploy or modify the open-source codebase directly.

The **GNU Affero General Public License v3.0 (AGPL-3.0)** is a copyleft open-source license designed to ensure that users who interact with the software over a network can access its source code. It is an extension of the GNU General Public License (GPL-3.0) with additional provisions to cover software that is run as a service.

### Key Terms and Conditions

* **Copyleft License**: Any modified versions of the software must be distributed under the same AGPL-3.0 license.
* **Network Use Disclosure**: If the software is modified and made available over a network (e.g., as a web service or SaaS platform), the modified source code must be provided to users upon request.
* **No Proprietary Forks**: Organizations cannot take the software, modify it, and keep those modifications private if they provide it as a service.
* **Compatibility with Other Licenses**: The AGPL-3.0 is compatible with the GPL-3.0 but not with non-copyleft licenses.

### Implications for Use

#### 1. Deployment and Usage

For institutions deploying the open-source edition:

* Post-secondary institutions can freely deploy and use the AGPL-3.0 source code without paying for a license.
* If hosting the software internally without external access, there are no additional obligations beyond the standard GPL-3.0 terms.
* If the software is modified and provided as a service (e.g., a student-facing application), the source code of those modifications must be made available.

#### 2. Intellectual Property (IP) Considerations

* The EdEHR platform is owned by **EdEHR Technologies**. Institutions do not own exclusive rights to any modifications they make to the open-source software.
* Any customizations or improvements made to the open-source edition must be shared under the same license and cannot be commercialized as proprietary software.
* Institutions can charge for hosting, support, and implementation services around the open-source software.
* For platform IP, trademarks, and terms of service, refer to [edehr.org](https://edehr.org).

#### 3. Compliance Requirements

* If modifications are made, the institution must make the full modified source code available upon request.
* It is recommended to maintain a repository of changes (e.g., GitHub, GitLab) to track modifications and ensure compliance.
* Any external vendor or IT team providing services must also comply with AGPL-3.0, meaning they cannot develop and keep changes private.

### Relation to Open Source Standards

The AGPL-3.0 license aligns with the [Open Source Definition (OSD)](https://opensource.org/osd), as defined by the Open Source Initiative (OSI). This ensures:

* Freedom to use, modify, and distribute the software.
* No discrimination against any user group, institution, or purpose.
* Source code availability and transparency are enforced.

| OSD Principle                                | How AGPL-3.0 Complies                                                                                   |
| -------------------------------------------- | ------------------------------------------------------------------------------------------------------- |
| Free Redistribution                          | AGPL-3.0 allows unlimited redistribution of the software.                                               |
| Source Code Availability                     | AGPL-3.0 requires that the source code is always made available.                                        |
| Derived Works Allowed                        | Institutions can modify the software and distribute their versions, provided they use the same license. |
| Integrity of the Author's Source Code        | Modifications must be marked as such, but original licenses cannot be altered.                          |
| No Discrimination Against Persons or Groups  | Anyone can use and modify the software, including post-secondary institutions.                          |
| No Discrimination Against Fields of Endeavor | The software can be used for educational, commercial, or research purposes without restrictions.        |
| Distribution of License                      | The rights attached to the software apply to all users without additional conditions.                   |
| License Must Not Be Specific to a Product    | AGPL-3.0 is not tied to any specific software product.                                                  |
| License Must Not Restrict Other Software     | AGPL-3.0 does not impose restrictions on other software that is used alongside it.                      |
| License Must Be Technology-Neutral           | The license applies regardless of platform, programming language, or technology stack.                  |

### Frequently Asked Questions

<details>

<summary>Can institutions modify the software for internal use only?</summary>

Yes, institutions can modify the software for internal use without any obligation to share the modifications, as long as the software is not made accessible to users outside the institution.

</details>

<details>

<summary>What happens if the institution provides the software as a hosted service?</summary>

If students, faculty, or external users interact with the software over a network, then the institution is legally required to provide the modified source code.

</details>

<details>

<summary>Can institutions sell services around the EdEHR open-source software?</summary>

Yes, institutions can charge for hosting, support, and implementation services built around the EdEHR open-source edition. However, they cannot sell the EdEHR open-source software itself as proprietary software.

</details>

<details>

<summary>How can institutions ensure compliance?</summary>

* Always document and maintain a repository of any modifications.
* Make source code changes accessible via a public repository when required.
* Ensure that third-party vendors working with the software understand and adhere to the AGPL-3.0 terms.

</details>

### Additional Resources

* [Full AGPL-3.0 License Text](https://www.gnu.org/licenses/agpl-3.0.en.html)
* [EdEHR open-source edition on GitHub](https://github.com/edehr/edehr)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://edehr.gitbook.io/edehr-compass/legal-and-compliance/licensing/understanding-the-open-source-licensing-agpl-3.0.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.