You can programmatically remove the watermark, either via a flag or by changing the source code.
> [1] No, you can do whatever you want with it since it’s MIT
But if you use it in a commercial project, they'll likely shame you if you don't pay - like what happened to OpenAI with Agent Builder:
> [2] Hey @OpenAI :) We just saw that you are using our open source library React Flow We offer startup discount codes :) Let us know if you are interested
Personally, I’d prefer them to use a dual license, but I understand that it would likely create unnecessary hurdles for devs who just want to try out the library.
You can programmatically remove the watermark, either via a flag or by changing the source code.
> [1] No, you can do whatever you want with it since it’s MIT
But if you use it in a commercial project, they'll likely shame you if you don't pay - like what happened to OpenAI with Agent Builder:
> [2] Hey @OpenAI :) We just saw that you are using our open source library React Flow We offer startup discount codes :) Let us know if you are interested
Personally, I’d prefer them to use a dual license, but I understand that it would likely create unnecessary hurdles for devs who just want to try out the library.
They explained their reasoning here: https://xyflow.com/blog/asking-for-money-for-open-source
[1] https://x.com/xyflowdev/status/1975660206441820585
[2] https://x.com/xyflowdev/status/1975505810768777360
Agree, if they're going to guilt shame companies publicly and be defensive in replies, just dual license it. Not a great look.