There’s a couple of questions, so let me split them out…
The important thing to recognize here is that you can already do something like this in Streamlit. For example, if we ignore password authentication right now, you could have a text input where the user types in their name, and you look up some information about them. For example, if you wanted everyone to have a separate user directory, you could check to see if their directory exists, and if not, create it.
But this is done with base Python, the only part of Streamlit you need is to take the text_input from the user.
Yes, Streamlit for Teams has a slightly different roadmap than Streamlit the open-source project and Streamlit sharing (which has already launched). If you implement the logic as mentioned above, you could do that today without needing Streamlit for Teams. So your question boils down to whether Streamlit for Teams will be providing enough hard drive space for you to reasonably support this workflow.
The pricing and instance sizes for Streamlit for Teams is still being worked through, but I would expect that the storage space would be reasonably large enough to support your use case. If you would like to talk specifics, @Corey_Bradford manages our commercial partnerships and would be happy to talk specifics with you.