How does the enterprise license work if I wanted to extend Twenty to build a distributable product?
Hi again! I am building a product that could naturally integrate with Twenty CRM. In short, I'd be adding an extra tab that's an iframe to a specialized service that runs from CRM data and my own database. Think medical recommendations for each person in the CRM. This would be something I would host (due to medical data being present) and/or would distribute to customers for their own use (e.g. a hospital pays for my CRM-service hybrid, which they host). I saw in the license that this would require an enterprise license for specific features but how does that work? How would that multi-layer billing work?
8 Replies
I see that it's largely billing, SSO, and webhooks when I search in the code: if I want SSO, I then have to pay for enterprise? How would you know that I'm using SSO if this is self-hosted? I'm trying to get my facts straight when designing this tool and what relationships I'd have with Twenty PBC if enterprise features (SSO, in-app billing, webhooks) were needed.
@Stephanie could you please answer this question?
thanks @bob and Hi @dolan
happy to hop on a call to discuss this live if you want.
Basically, you can use the free version self-hosting and resell it. As soon as you update the code - which you plan on doing, you will be required (per our open-source licence AGPLv3) to publish your code as open-source as well, under the same licence.
If you do not want to make your code open-source but still want to host (and resell) your solution, you can buy the Organization licences (while self-hosting). It gives you access to the SSO login, to support from our core team and waves the condition that forced you to publish your code.
From a technical perspective, we are actively developing a framework that will allow users to build applications directly within Twenty. This will enable you to create custom tools integrated into your workspace without needing to fork the repository.
The licensing model for these applications hasn’t been finalized yet. at this stage, I’m strictly speaking from a technical point of view
All very good to know. Some of the code I'd be happy to be in public domain (e.g. configurable iframe component) but a plugin/application system would be very welcome.
Good to know that the Organization license waives the need to publish code. On the note of distribution, one other option is multitenant. I know that's hard and doesn't seem to be what twenty is designed for, but is that a roadmap item?
If by multitenant you mean multiple workspaces, Twenty offers it by changing a value of IS_MULTIWORKSPACE_ENABLED to true in .env file
I mean ensuring that one workspace can't access anything from the other, so presumably that's enforced?
Each workspace is stored/scoped under a postgres schema
So yeah basically, lets say a user auth token of another workspace got leaked
It will only compromise his workspace schema