|
123
|
1 .. _licensing:
|
|
|
2
|
|
|
3 .. role:: green
|
|
|
4 .. role:: orange
|
|
|
5
|
|
|
6 Can I use Orthanc in my commercial product?
|
|
|
7 ===========================================
|
|
|
8
|
|
|
9 **Short answer:** yes, under certain conditions.
|
|
|
10
|
|
|
11 Orthanc's core has been released under the `GPL v.3 license <https://en.wikipedia.org/wiki/GNU_General_Public_License>`_ which means that, if anyone modifies Orthanc, integrates it in its product and **distributes** her product, she must make publicly available the source code of all Orthanc or derived work under a GPLv3 or more restrictive license (i.e AGPLv3).
|
|
|
12
|
|
|
13 However, if the product is a SaaS application, the product is not **delivered** to the user and, in this case, she must not make the source publicly available.
|
|
|
14
|
|
|
15 Orthanc's plugins have been released under the `AGPL license <https://en.wikipedia.org/wiki/Affero_General_Public_License>`_ which is usually considered as **contaminating** license even when the product is not **delivered** (i.e a SaaS application). As soon as Orthanc is used together with one of its AGPL plugin, Orthanc is contaminated by the AGPL and is considered AGPL herself. If anyone writes a software that is part of the same process as an AGPL plugin, her software is contaminated by the AGPL license and she must make publicly available the source code of her software under an AGPLv3 or more restrictive license.
|
|
|
16
|
|
|
17
|
|
|
18 My commercial product interacts with Orthanc only through its Rest API or through DICOM
|
|
|
19 ---------------------------------------------------------------------------------------
|
|
|
20
|
|
|
21 In this case, your product is not contaminated by Orthanc `GPL v.3 license <https://en.wikipedia.org/wiki/GNU_General_Public_License>`_ nor by any of the Orthanc's plugins `AGPL license <https://en.wikipedia.org/wiki/Affero_General_Public_License>`_.
|
|
|
22
|
|
|
23 I have written a plugin shall I make the code publicly available ?
|
|
|
24 ----------------------------------------------------------------
|
|
|
25
|
|
|
26 If your plugin is the only one loaded by Orthanc, then, your plugin is only *contaminated* by Orthanc's GPL license. Therefore, you'll need to make your plugin source code publicly available only if you **distribute** your software.
|
|
|
27
|
|
|
28 If another AGPL plugin is also loaded by Orthanc, then, your plugin is *contaminated* by the AGPL license and you must make the source code of your plugin publicly available.
|
|
|
29
|
|
|
30
|
|
|
31 Summary
|
|
|
32 -------
|
|
|
33
|
|
|
34 In all cases, you'll never be forced to make publicly available the parts of your product that is interacting with Orthanc only through the Rest API or through DICOM (Orthanc and it's AGPL plugins are not contaminating the *client* code).
|
|
|
35
|
|
|
36 If, part of your product runs in the same process as Orthanc:
|
|
|
37
|
|
|
38 * I'm using only Orthanc and I don't modify it: :green:`no restrictions`
|
|
|
39
|
|
|
40 * I have modified Orthanc or written my own plugin and I'm not using any AGPL plugins:
|
|
|
41
|
|
|
42 * My product is accessible only as a SaaS (it is not distributed): :green:`no restricitons`
|
|
|
43 * My product is distributed to my users (as a standalone application or as a server application my users can manage themselves): :orange:`You must make your Orthanc modifications and plugin publicly available`
|
|
|
44
|
|
|
45 * I'm using Orthanc and at least one AGPL plugin: :orange:`You must make your Orthanc modifications and plugins publicly available`
|
|
|
46
|
|
|
47
|
|
|
48 Note that, if you're not willing to make your code publicly available, there's an option to buy a licence exception. As for all open source projects, the intellectual propertly of Orthanc is still owned by multiple parties. In this case: CHU Liège University Hospital and Osimis S.A. The latter party, have the faculty to sell licence exceptions.
|
|
|
49
|
