I’m new to streamlit and want to know more about the definition of workspace users. Currently I am using a free tier to test out deployment which is working fine.
My questions are as follows:
I have deployed 1 app, and the app is open source (GitHub and free tier). what is the maximum number of users that can view/ interact with the app at one time?
let say a new viewer is viewing this public app. Under the hood, does the app gets deployed once more? Or is it only deployed once (the one time which I deployed it from streamlit cloud)
Hi @darkknight, welcome to the Streamlit community!
When people ask this, the answer is always “it depends”. The free tier isn’t limited by the number of public users per se, just by the amount of resources the deployment container has. So for an app that did nothing but a single st.markdown("hello, world!"), I’d expect it to easily scale into the thousands of users simultaneously.
In the free tier, unless Streamlit employees go in under-the-hood, you’ll generally have a single container instance running your app. So multiple people hit the same container, and the Tornado server we use at the core of Python will make new threads.
For the paid tiers, we have the option of both scaling horizontally and vertically. So if your app needs a lot of CPU and RAM resources for a few users, the containers can be made bigger. Or if you expect massive traffic but each container doesn’t need a ton of resources, we can make several replicas. And of course, the third choice of lots of resources and lots of users is why the Enterprise tier is ‘call for pricing’.
Thanks for stopping by! We use cookies to help us understand how you interact with our website.
By clicking “Accept all”, you consent to our use of cookies. For more information, please see our privacy policy.
Cookie settings
Strictly necessary cookies
These cookies are necessary for the website to function and cannot be switched off. They are usually only set in response to actions made by you which amount to a request for services, such as setting your privacy preferences, logging in or filling in forms.
Performance cookies
These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site. They help us understand how visitors move around the site and which pages are most frequently visited.
Functional cookies
These cookies are used to record your choices and settings, maintain your preferences over time and recognize you when you return to our website. These cookies help us to personalize our content for you and remember your preferences.
Targeting cookies
These cookies may be deployed to our site by our advertising partners to build a profile of your interest and provide you with content that is relevant to you, including showing you relevant ads on other websites.