Would need more information on what you are trying to do.. Are you saying that each user need to be on their own server, why?

If users are ‘logging-in’ then control that by sessions. 10 users is fairly small, even 100 should be fine on a single droplet. If you want to scale you can use app platform or setup multiple droplets and place a LB in front of it or roll your own container cluster.

What I’m trying to accomplish is the following.

The app monitors and gathers data from exchanges. Each user of the app might have their own settings of what needs to be monitored and gathered, therefore I think it would be the easiest that at least there is a separate context for the backend of each user.

Moreover the backend needs to be kept running even if the user logged out.

As you can tell I’m new to this and would appreciate a few nudges in right direction of what would be a good architecture for this problem.