Hello, we are looking at the Flyte V2 UI codebase. We noticed the license is different from the flyte project. There is a segment about limitations

You may not provide the software to third parties as a hosted or managed
service, where the service provides users with access to any substantial set of
the features or functionality of the software.

You may not move, change, disable, or circumvent the license key functionality
in the software, and you may not remove or obscure any functionality in the
software that is protected by the license key.

You may not alter, remove, or obscure any licensing, copyright, or other notices
of the licensor in the software. Any use of the licensor's trademarks is subject
to applicable law.

We are trying to understand if open source users are allowed to fork the UI and implement/modify subsets of the features only available in the licensed edition (ie. run metrics).

I think it’s more like Hasicorp license- BSL or BUSL github.com/hashicorp/terraform?tab=License-1-ov-file So what i think : You can use the software for commerical use , but cannot provide it as a service to your customers. You cannot run flyte2 in your company and use the UI for paying customers to use, for that they can use Union

I think that makes sense for the third party sentence but I'm more worried about

You may not move, change, disable, or circumvent the license key functionality
in the software, and you may not remove or obscure any functionality in the
software that is protected by the license key.

So what it means that, you cannot take part of the code(not the entire UI, but only say dashboard) and use it to monitize/provide as a service to 3rd party. So basically, if you are not using it as a service for paid customer, then you are fine. You can use it for cumorcial internal usage. Someone from flyte can clarify that, but that’s my take

Reading along here. We have been looking forward to v2 for some time now but not being able to patch in functionality to suit our needs would put a bit of a damper on adoption / force us to build a separate UI 🙁 From our reading, it appears the license-key circumvention restriction is separate from the commercial redistribution clause, ie. if anything is put behind a license key gate, it’s not allowed to fork/modify. Can anyone from UnionAI comment/confirm that reading? And if so, could you specify what is planned to be put behind a license key gate - RBAC again (this was very cumbersome to get merged in Flyte v1)?

Sorry for the delayed reponse. The UI was created by us and we wanted to stop a lot of blatant re-hosting and commercialization of the product with no contributions back to the community. So the license provides, 1. you cannot create derivatitve oss or commerical products 2. you can fork and use it internally (fork has to be private)

You don’t want vibe coders to get the vibes…How brutal

Haha, We are a small company and want to survive 😀❤️

I think you are on the right track, even if LLM’s fade your’s is related to ML task , which will survive

Haha, actually flyte 2 is awesome to vibe code on though

It’s even better with the

flyte-agent-plugins

skills union.ai/docs/…/agent-plugins

I have no qualms with using LLMS for coding. I do it all the time. But the problem is with complete vibe coded apps. Most of my time now is spent on reading/reviewing code, the least i think people should do is read their own vibe code and understand what it does. At least back in the days when we used stackoverflow and copy pasted the code in it, we put in some effort to understand it as it was only a snippet and not end to end module.

This is a great discussion @acceptable-knife-37130! moving thread over to #C06CR7K94KB https://flyte-org.slack.com/archives/C06CR7K94KB/p1786022036413749, very curious what folks and in the community think