You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently it is not directly clear that this product is not "open" to use in a production environment. A user would need to go to https://www.crunchydata.com/developers/terms-of-use to see that production usage is not allowed for companies with 50+ employees until they buy a license.
Could be especially annoying for people that have already invested some time and then see that there is a license-fee based model.
It would be nice if this image or similar is included in the Readme:
The text was updated successfully, but these errors were encountered:
zadjadr
changed the title
Make terms of production more clear
Make terms of usage for production more clear
Feb 5, 2024
We are currently working on some updates to the README in this repository for better clarity, and will definitely consider your feedback as part of those updates.
Hello @andrewlecuyer,
I read the Terms of Use too. The terms seem to say production is allowed without any subscription for companies with less than 50 employees, and is allowed for bigger companies with an active subscription.
Is that right?
Should we consider that is something else?
What will be the update?
The operator is under license Apache 2.0 so it shouldn't be affected by that terms. It looks like the terms apply to softwares behind PGO. Is PGO impacted then?
Thanks! :)
Overview
Currently it is not directly clear that this product is not "open" to use in a production environment. A user would need to go to https://www.crunchydata.com/developers/terms-of-use to see that production usage is not allowed for companies with 50+ employees until they buy a license.
Could be especially annoying for people that have already invested some time and then see that there is a license-fee based model.
It would be nice if this image or similar is included in the Readme:
The text was updated successfully, but these errors were encountered: