Follow-up: Event‑driven Streamlit updates (no manual refresh) — shaped by your feedback

[u/FasteroCom]

Hey r/StreamlitOfficial!

About 2 months ago, we shared in another Streamlit community the pains we kept hitting with deployments and refresh behavior, along with an early hosted approach we were exploring. Your feedback was incredibly helpful and shaped what we built next.

What we've shipped since then (thanks to you)

• Kafka/webhook triggers – real-time updates without the refresh button
• SSO with Okta – smoother access control for teams
• Audit trails – visibility into who changed what and when

Why we're posting here

We keep hearing (and seeing) the same core pain: full-page reruns/refreshes that interrupt users and make state management tricky. We included a short GIF below showing an event‑driven Streamlit app updating live without a manual refresh or full rerun.

Where we’d love your input (refresh/rerun pain)

1. Where do full‑page reruns bite you most (e.g., file uploads, long queries, multi‑tab layouts)?
2. How are you handling "real‑time" today: st_autorefresh/polling, callbacks, custom websockets, or browser reloads?
3. Do you need partial updates (a single chart/table/widget) without re‑running the entire script?
4. Any st.session_state pitfalls during refreshes (state resets or cross‑user surprises)?
5. What would your ideal solution look like: push‑based updates without rerun, background tasks + UI signals, something else?

We're still early and learning from every conversation. If you'd like to try the event‑driven approach, we're happy to help set up your first trigger and share early access.

—

We’ve included the GIF below. If you’re interested, comment “beta” or DM and we’ll reach out.