3 ms·
(Nango co-founder here) We use the Elastic license precisely for the reason you mention: to prevent companies from rebranding Nango and selling it as it is. For
by bastienbeurier 3y ago
(Nango co-founder here) We use the Elastic license precisely for the reason you mention: to prevent companies from rebranding Nango and selling it as it is. For all other use cases, it should be accessible.
- buremba 3y agoSo let's say I want to build a service that lets people access all their libraries from multiple streaming services. Can't I automate all the backend with Nango and just build a front-end around it? If yes, wouldn't it be just rebranding Nango? If not, it would be nice to clarify in the docs. My point is that if there is no clear boundary, it's too risky for me to try this product even if it's open-core. For Elastic, their boundary is "database as a service" but I don't see anything similar in your license.
- bastienbeurier 3y agoOk I see. Indeed, it would be worth specifying what the boundary is in our case. Thank you for the feedback!