Correct licensing model for having multiple annotators each with a model in the loop

Getting Started
,
1

Hi,

Within a large org we wish to create a process where we spin up multiple annotation tasks where each annotator is focused on a single task with a model in the loop. Does your licensing model allow this?

Thanks for the help,
James

1 Like
2

Yes, that’s generally no problem. Prodigy is licensed per developer, which is the person who has access to the Prodigy package, back-end, CLI and library. Annotators who will only have access to the front-end don’t require a license. The only restriction is that the web app can’t be publicly accessible by everyone, and should be hosted on an internal network or behind a password-protected URL.

So if your company holds one pack of five seats, up to five developers can start Prodigy instances and tasks on your machines at the same time, run training experiments, develop custom recipes, export data etc. The company seats are floating, so if a team member leaves and someone else takes over, they can also take over the Prodigy developer license.

3

Hi Ines,

Following on from James question, we have a sentence annotator working well locally based on the sentiment trainer example (customer feedback sentiment). We would like to have multiple annotators working on the sentence annotations through a url front end.

I assume that we would alter the http output in the recipe from the local server, to the url where we would like our annotators to use?

Am I right in thinking that the developer would then re-send "job" to the url as required?

Many thanks

Simon

4

Hi, I have a related question. With the company pack (5 seats), can we deploy library in a network environment for developers (e.g. Databricks) if we have active directory security to restrict access to that particular cluster to the developer who is assigned the license? (So far we only install in local machines).

Thank you,

5

@scarter79 Sorry, no idea how I missed your question!

Yes – we typically do this by setting up a reverse proxy. (You can find more tips and examples via the forum search).

Sure, that's no problem! You just have to make sure that only developers that currently hold a license can access the Prodigy back-end etc. If you can set this up, you can absolutely use Prodigy this way :slightly_smiling_face: