For Frame accounts that support multiple simultaneous users (all account types other than Frame Personal or the Frame Platform Trial), you will need to set up a pool of "production" instances and configure how you want that pool to scale up and down.  The "System capacity" setting in the admin dashboard controls the number of production instances that are in your pool, how many are actively running and ready to accept sessions and how many can be powered up on-demand.  

 

With our Instance management strategy, you can set the system up to dynamically scale your system based on user demand and three key parameters that you set:  the minimum, the buffer and the maximum.  This gives you complete control over how and when the system scales.  For example, you can configure up to twenty different intervals during a day and use minute-granularity.  For example, you might want to start up 15 instances as your minimum at 8:55 a.m. with a buffer of 5, drop to a minimum of 5 with a buffer or 2 at 10:32, raise the minimum to 20 at 11:55, etc. 


IMPORTANT:  Note that even if a user is not connected to an online instance (one of the "minimum" or "buffer" servers), the instance is still running and ready to accept a session - and so long as it is running, it is consuming hours.

 

Also, note that Frame uses hours in increments of one hour. Booting a Sandbox or Production instance will consume one hour of usage, even if you shut it down after just a few minutes. Also, anytime you publish - you will incur one hour of usage for each of the instances in your production "pool" -whose size is determined by your "maximum" capacity setting.  (Our instances currently run on Amazon Web Services, which bills in one-hour increments).