In that company we used Streamlit for demoing our solutions to our business clients. We used CNNs to make a list of visually similar products to end users. Bef

In that company we used Streamlit for demoing our solutions to our business clients. We used CNNs to make a list of visually similar products to end users. Before deploying that, we used Streamlit to demo the client. The backend was run on AWS, and we used GPU for inference. If the client said that our results were satisfactory, then we would simply store the data in a DB (using PostgreSQL), and that will be used to show similar products to end users (consumers), and here no GPU or Streamlit was involved. This Streamlit demo was a core part of our (B2B) business. I have also used Streamlit for a public frontend receiving thousands of hits per hour with multiple GPUs for inference. It could tackle that. > my conclusion is that you can do a few simple things super easily, but you hit a wall when you want to have anything beyond basic navigation and layout That's the reason Streamlit was used. We did not need a very customisable frontend. When we needed that, we passed that to our webdev team who used Js +// Vue/React +// Django/Flask. You use Streamlit when you don't need a very custom interface. You use it so that you can very quickly prototype something.