We want to build a shopping cart application where the end user can come and log in how we do in any shopping kart and make a purchase accordingly. So there are million of users for that client. So If I propose Outsystems for that use case do I need to pay the licensing fees for each of the end user who logged in to the application or it will be for the application wise.
Hi,
Yes, you need a license that covers the number of active users, or what OutSystems counts as external users.You only require users for pages with registered role or any application defined role. So for people just browsing your pages without login (anonymous users), you are not required to have a user registered in OutSystems.
But I guess with millions of users purchasing, there is some money to pay the license. The external users can be bought in packages so as your business grows to be more successful you can buy additional packages accordingly, and the more you buy, the cheaper the per-user price will be that OutSystems is asking.
Given you mention your client has millions of users of their website, you should figure out how many active recurring customers your client has every month that actually buy products. You can then limit the number of external users you need to buy in your license.
Regards,
Daniel
Outsystems has 3 different types of "users".
1) An internal user that belongs to the orgsanisation who creates/owns the application. These have the highest cost in the order of dollars per month per user depending on the number of users and any contract with Outsystems.
2) An External user that is outside the orgsanisation but has an active login. These will have a different email address domain than those of the internal users and are charged at a significantly reduced amount in the order of cents per month per user depending on the number of users and any contract with Outsystems.
3) Anonymous users who don't have an actual login. These are not charged for.
So depending on your use case will depend on the cost. For example if users make a purchase but never actually create a login then they are not counted as "users". You could give them a link with a code/token to view their order but if they never log in it's still ok.
However if they create an account to do things like save payment details and look at all their old orders etc then it would technically be an external user.
One thing to recommend is that if you have a lot of external users it may be worth having a timer that checks for and disables users who have not logged in for a long period of time and maybe give them a process that they can revive their accounts. This would reduce the number of active users and also improve security by disabling unused accounts.
what if the external users are mobile application users, they do need an account and have role, but usage is very less, viewing once a while and doing transactions also very less.
They will still count as an external user towards the license.
As Daniël explained, that still counts. This also means OutSystems is perhaps not the best tooling for webshops etc., where there may be 1000s of users, that login only once or twice a year, or mobile apps that are infrequently used, or do not generate any revenue.