Suppose we need to build two or three completely independent applications in OutSystems (not as part of a single portal), where each application has:
Different business purposes
Different user groups
Different release schedules and lifecycles
What would be the recommended approach?
1.Build all applications within the same OutSystems environment (sharing the same Dev, Test, and Production environments), or
2.Use separate OutSystems environments/licenses for each application (with dedicated Dev, Test, and Production environments)?
If the first option (single OutSystems environment) is recommended:
Is the end-user count shared across all applications within the environment?
then how this end user count will work, will it automatically increases with upgrading of increasing AO's to the environment format this question
Inside a license, if the users are the same, you don't have to pay twice.
So if you have 2 apps with the same 9000 users, you pay 9000 users. If you have two apps with 9000 unique users each, you pay 18000.
If you purchase another license, it will not have 10000 external users, only the 100 internal. External users are paid on the side.
So you would have a license with less AOs, but very similar in price with the original.
Another point to consider is that a new app that you see as 150 AO in a new server, on the same server can be 80 ou 100. Many modules can be reused in both.
The point is, are they the same users? You expect them to register twice and have two passwords? Or one login works on both apps?
It would be extremely expensive to have an OutSystems infrastructure per app.
The platform is great for building multiple applications (that potentially share data and components where applicable).
for O11 , on cloud
suppose we have taken an outsystems environment with 300 application objects, with 100 internal users and 10000 external users. we have built an app which already consumed 250 application objects and having 90 internal and 9000 external users. its already working great in prod.
now we want to build another application for the same customer, it might take another 150/300 application objects ,
1.now my question is if we upgrade our existing license with another 1 AO package 150, but not sure whether we need pay extra for another hundred interal users and 10000 external users?
2. or we can purchase new license with 150/300 ao's bydefaullt we will get100 internal users and 10000 extenal users with this license, (i can understand that we will reuse reusability of previous project concepts here, increase time by rebuild new things, but curious)
which of the above 2 is cost effective comparetively
OutSystems is supposed to be used for multiple apps. They can be connected or fully independent.
Users are an independent entry of the license. They are sold in packs of 1000, but Sales is the best place to discuss that.
In terms of cost you will save in the license for having a single license:-you save in Application Objects on any shared component;-and you also save in users as they only count once, no matter how many apps they use. Unless you need them to act as different accounts (different password for each account).
It will also depend if is on-premises or cloud, O11 or ODC...
The more details you give, the more we can help.
suppose we have taken an outsystems environment with 300 application objects, with 100 internal users and 10000 external users. we have built an app which already consumed 250 application objects and having 90 internal and 9000 external users. its already working great in prod.now we want to build another application for the same customer, it might take another 150/300 application objects ,1.now my question is if we upgrade our existing license with another 1 AO package 150, but not sure whether we need pay extra for another hundred interal users and 10000 external users?2. or we can purchase new license with 150/300 ao's bydefaullt we will get100 internal users and 10000 extenal users with this license, (i can understand that we will reuse reusability of previous project concepts here, increase time by rebuild new things, but curious)
Hi @Priya Naveen
As already mentioned that OutSystems designed for multiple applications easily. In addition to above wanted to add that you just need to follow correct architecture so each application have different life cycle and no dependencies on each other, rest platform can handle.
regards.