I am in the process of developing a SaaS application using Tenancy for Laravel (https://tenancyforlaravel.com/) and am considering utilizing one of your themes under the ThemeForest extended license. However, I have specific requirements for my application’s architecture, and I need to ensure that the license covers my intended use.
My application is a multi-tenant system built on Laravel. Here are the key characteristics:
Single Laravel Installation: The entire application will operate from a single Laravel installation.
Individual Client Databases: Each of my clients will have their own dedicated database. This means that while they will be using the same application, their data will be completely isolated in separate databases.
Sub-domain Usage: Every client will access the application through a unique sub-domain. From their perspective, it will appear as if they are using a standalone application.
Shared Codebase with Unique Configurations: All clients will be served by the same underlying code. However, the configuration and data for each client will be distinct and separate.
Given these parameters, my question is: Does the ThemeForest extended license permit the use of your theme in such a multi-tenant, SaaS application environment?
There seems to be a lot of ambiguity around the licenses and Saas applications. In my case, some clients could have 3 users but others could have hundreds, and I would charge them different amounts based on the number of users and the various features of the application they use.
Your clarification on this matter will be immensely helpful in ensuring compliance with the licensing terms and in making an informed decision for my project.
My question has nothing to do with selling the theme. I would be selling access to my application which is similar to a crm. It would use one of the admin themes to base its user interface on.
Yes i did but it still seems very ambiguous with regards to my use case. For example:
You can’t use the Item in any application allowing an end user to customise a digital or physical product to their specific needs, such as an “on demand”, “made to order” or “build it yourself” application. You can use the Item in this way only if you purchase a separate license for each final product incorporating the Item that is created using the application.
When they sign up for my application the clients will be able to go into the settings and customize parts of the application to suite themselves. Like changing colors, or switch on or off certain features. Switch to different layout configurations etc…
Technically it will all be a single application hosted on the same server. But each client will feel like its a seperate application. And access the site like client.myapplication.com, client2.myapplication.com etc
Also, the license is described as a “single application” license, not a “multi-use” license. This means you can’t use the Item to create more than one unique End Product (Clause 7). A multi-tenant architecture, where each tenant appears to have their own application, might be seen as creating multiple End Products. Even though technically it is all one product.
If your app requires a single installation but you want to manage it in multiple way for your each client (selling access) then for your purpose extended license will be fine.
If you like you can contact the theme author and envato support to get a clear answer.