I was thinking of having the following scenario:
have multiple versions of the same app in 1 billing account. each app for a company. Then Create user groups for each company that uses the app - The group (company) will then have access to their own version of the app.
I dont know if there is some best practice documentation on this type of stuff. The idea is simple; i have an app that I want to monetize - what is the best way of doing it under 1 umbrella billing company.
You cannot make updates in one app and have them "flow through" to another app; so maintaining multiple "duplicate" applications will be arduous and time consuming.
Since you will be paying for the subscription; my recommendation here would be to create 1 app, and setup Users associated to Companies and permission those users for only records associated to that Company. This is a very common usage case for QuickBase.
If they truly are different companies, you can sell them the app outright for whatever fee you set, but they should have their own account. They can then hire you to maintain it, or farm that work out to some developing company.
You agree not to copy, sell, rent or sublicense (including offering the Service to third parties on an applications service provider or time-sharing basis), lease, loan, redistribute, or create a derivative work of any portion of the Service (except solely to the extent necessary for you to create applications permitted under Section 7 (“Application Development and Distribution via QuickBase Exchange”) of these Terms of Service), use of the Service, or access to the Service. Such restrictions do not apply to the Content you place on the Service. You agree not to access the Service by any means other than through the interface that is provided by QuickBase for use in accessing the Service.
Trust me, I wish with all my heart I could do this. But they have to protect themselves, and their income stream somehow.
Correct me if I am wrong, but what you are suggesting is that the quickbase platform is soley for the use of customers in their "specific busines" use case.
My business is to have hundreds of Paid users access the app. I hope quickbase reads this because for what it is worth, i have no intention of breaking the rules, I just think there is something missing from my understanding of what you are saying. Another point is; how will any one ever know that I am charging a user to access the app?
Since you are building, managing and maintaining the Application/Account there is no conflict; since you own it and can control access to it. As long as the fees your clients pay you includes QuickBase and includes your management/maintenance services; then you should be free to charge as you see fit for their access to your system.
- Our Enterprise Governance team is currently looking at Application Lifecycle Management (ALM) utilities that could be considered a more robust sandbox. We are also thinking about the notion of master/child template deployments.
- I suggest reaching out to your account executive (connect with Care via support if you need to be routed) regarding pricing as we have a lot of options to facilitate these types of agreements.