Supported stacks

Streamlit hosting
on Shipped.

Move your Streamlit tool off your laptop and onto a shareable URL. Give users access to the interface while your Python code runs on the server.

Host the running Python application

A Streamlit app needs its Python server as well as the interface visitors see in the browser. Deploy the project with its dependencies and production start command. Shipped hosts the service and its public address so users can interact with the app without installing Python themselves.

Keep datasets and results outside a session

Session state is useful for the current interaction, but it is not a durable database. Save records to PostgreSQL and files to object storage when people need to return to them later. Keep private data-source credentials in secrets, and apply access controls in the application where required.

Give resource-heavy tools room to run

Dataframes, transformations, and model calls can have very different resource needs from a small web page. Choose app capacity for the workload and test realistic inputs in staging. Move lengthy processing to a separate worker when users should be able to submit work and retrieve the result later.

A little more detail

Questions about Streamlit?

Can I deploy Streamlit as a static site?

No. A standard Streamlit app needs a running Python server and communication with the browser. Deploy it as a web service.

Will Streamlit session state preserve customer records?

Session state belongs to an active user session. Store records that must survive a session or restart in a database or persistent storage.

From your workspace to the web

Ready to ship your app?

Start shipping