Inquiry About Orthanc Licensing and Commercial License Quote

General
1

Dear Orthanc Team,

I hope this message finds you well. My name is Vinoth , and I am a solution architect at Zeiss. We are exploring the use of Orthanc for a specific project and would like to clarify the licensing requirements for our use case. Additionally, we are interested in understanding the terms and cost of a commercial license, if applicable.

Our Use Case

  • Deployment Environment: Orthanc will be deployed in a private network.
  • Functionality: Orthanc will act only as a DICOM forwarder, pulling data from local systems and pushing it to a cloud service.
  • Integration: We plan to use Orthanc’s REST API and Python scripts to interact with it. No modifications to Orthanc’s source code or custom plugins are planned.
  • Proprietary Product: Orthanc will be integrated into a proprietary workflow solution, but it will not be exposed directly to external users or offered as a service.

Questions

  1. Based on the above use case, does our deployment fall under the obligations of the AGPL license?
  2. Would our use case require us to obtain a commercial license to avoid AGPL obligations, given that Orthanc is part of a proprietary workflow?
  3. If a commercial license is recommended, could you provide an estimate of the cost and the terms associated with it?

We are committed to ensuring compliance with all licensing requirements and would appreciate your guidance on the best approach for our scenario. Please let me know if you need any additional information to assess our use case.

Thank you for your time and support. I look forward to your response.

Best regards,
Vinoth

1 Like
2

Hi Vinoth,

First of all, we appreciate that you are willing to comply with the licensing terms !

Given your explanation, I understand that you won’t modify anything in Orthanc source code and you will not have any proprietary code running inside the same process as Orthanc since you will only use the Rest API and DICOM protocol interfaces to interact with Orthanc.

Therefore, your proprietary product is not affected by the Orthanc license in any way.

Note that, we do not offer commercial licenses anymore since the IP is now spread over multiple entities (mainly UCLouvain, CHU Liège, Orthanc Team and Osimis (now bankrupt) + a few independent committers).

Note that, it is a good practice to mention “Orthanc inside” or “Powered by Orthanc” somewhere but this is not mandatory at all.

If your proprietary product relies on Orthanc, you might also consider supporting the project through Open Collective or by purchasing a support contract from Orthanc Team to make sure the project remains sustainable :wink: .

Best regards,

Alain.