Hi Edward,

There may be technical ways to achieve this, but without Studio these would almost certainly violate the Terms of Service.
So I think that Studio actually must be installed. Furthermore I believe, that in order to be used on a server, you will at least need a Network license for Studio rather than a single-user license.

Anyone from RWS feel free to correct me on this. It is how I understand the license agreement. There may be exceptions when Studio is only used to generate TMs and not for project creation and handling.

Best,
Andreas

Hi Andreas, thanks. Will wait for someone from RWS to confirm license needed or if it's ok to use one or no license if it is only used to generate TMs.

Edward Carandang

I think Andreas Galambos has already provided the correct response this.  The EULA does have a section on "restriction on use" which specifically says this:

"The Software (or certain functionality) may be provided with an application programmable interface ("API"). This Agreement does not allow Licensee to make use of the API, except solely to automate manual steps in the normal functionality of the Software that otherwise would be performed through its user interface. Without limiting the foregoing, Licensee is prohibited from giving access to the Software (or to its functionality) to non-licensees (e.g. through terminal server technology or a web interface to the Software running on a server)"

Based on your description you would be breaking the licence agreement if you were to implement a solution along the lines you have outlined here. The only acceptable way to tackle this would be to do it through an integration with Language Cloud or GroupShare for example where the access via API is appropriately controlled.