i want to ask a quick question. many open-source projects put a significant difference between the product they sell as a cloud service in production and the open-source version they offer, encouraging people to use the paid one. i appreciate and understand this, as everyone needs such an approach to keep their business going. how does this work with you guys? have you actually spent time developing an open-source product that's easy to deploy and has the exact same features? or do we really need to use the cloud services to get the full benefits? i'd be really grateful if you could provide some information on this. i want to use the product in production, but we have a use case where we can't let our data leave our environment. so, i have to go with the self-hosted option. i just wanted to ask for an honest perspective before i get my hands dirty, in case anyone's willing to share.
#open source feature limitation?
midnight dome
neon patrolBOT
Hi there, This repo (https://github.com/composiohq/composio) consists our Js/Ts & Py SDK, along with our docs. The authentication & tool execution infra is only available via our cloud version (https://app.composio.dev/). We do offer self-hosting as a add-on for limited customers on our Enterprise plan. Let me know if you want to more info, happy to do a quick call (https://calendly.com/composiohq/enterprise)!
midnight dome
thanks so much for the clarification, I really appreciate it.
could you tell me exactly what kind of limitations there are? like, which specific features didn't you fully include in the open-source version? or are you talking about offering more of a managed service with the cloud version?
so, just to be absolutely sure: if I use the open-source version, I definitely won't be able to use the "Authentication and Execution Infra" components, is that correct?