Dashboards in Python

Advanced dashboards
that compute and act

Fast, interactive dashboards over large data, with native charts for nearly every visualization, writeback where decisions happen, and an assistant that reads the same numbers. Built with agents, in Python your data team can read.
advanced-dashboard-demo.streamlit.appOpen app ↗
A Streamlit revenue dashboard with time range and filter controls, four KPI cards with sparklines, a stacked area chart of recurring revenue by plan, and a revenue bridge chart.
The dashboard demo, built with Streamlit and running on Community Cloud. It may take a moment to wake up.

Made for data

Your dataframes, straight to the screen

It's the most basic reason to pick Streamlit. It starts from the data, so most dashboards need no glue code between the query and the chart. No serializing for an API, and no wiring a data grid to a charting library by hand.
  • Your dataframes, as they are

    Hand a pandas, Polars, PyArrow, Snowpark, PySpark, DuckDB, Dask, or Modin dataframe straight to a table or a chart. NumPy arrays, database cursors, and plain lists and dicts work too.
  • Edits come back as data

    Editable tables return the edited data, ready to validate and write back.
  • The whole Python data stack

    Query, model, and forecast with any library, in the same code that draws the screen.
app.py
import polars as pl
import streamlit as st

orders = pl.read_parquet("orders.parquet")

# Any dataframe goes straight in: pandas, Polars,
# Snowpark, PySpark, DuckDB, and more
st.dataframe(orders)
st.bar_chart(orders, x="month", y="revenue")

# Edits come back as data, ready to write back
edited = st.data_editor(orders.head(20))

Built for advanced dashboards

Dashboards people trust, built on logic your team can read

Every release makes Streamlit faster and more capable for demanding dashboards. These features are hard to rebuild correctly in each app, so Streamlit solves them once in the framework, and every dashboard gets them for free, including access for agents.

Agent access

Ask your dashboard why the numbers moved

Every dashboard is also a tool for agents, with no code changes. An agent sets the dashboard's own filters and reads the KPIs, tables, and charts back as data. It runs through the same caches and partial reruns, so it gets the same numbers people see, often without a new query.
Your AI assistantrevenue dashboard · MCP
  • YouWhy did net revenue in EMEA drop last week?
  • Set Region to “EMEA” and read 4 metrics and the revenue table as data
  • Set Week to the week before and read them again
  • Two delayed renewals. Net revenue fell 4.1%, and two enterprise renewals that slipped into this week explain 3 points of that. New bookings held steady. These figures come from the revenue dashboard, so they match what your team sees.

Coming from a BI tool?

Move your dashboards to Streamlit, and modernize them on the way

For the dashboards your teams rely on, a move is a modernization, not a one-to-one copy. On Snowflake they keep the governed data, metrics, access controls, and live data your teams rely on. They also gain what BI tools weren't built for: your own Python models and logic, AI, writeback through that logic, and access for agents.
At Open Insurance, two engineers moved 30 dashboards to Streamlit in one month, remodeling the data to consistent definitions on the way. The team now spends half as much time creating dashboards as in its previous custom environment.
  1. Rebuild the dashboards that matter

    Have your coding agent rebuild them on the same governed data and metrics, such as Snowflake semantic views where you use them.
  2. Check the numbers against the original

    Compare every figure with the original before anyone switches, and keep those checks as tests.
  3. Add what BI couldn't hold

    Your Python models and logic, AI, writeback through that logic, and access for agents, in the same app as the numbers.
  4. Retire the reports nobody opens

    Switch people over once they've signed off, and leave one-off questions to chat.

Compared to BI tools

Dashboards that compute and act, built with agents, in Python your team can read

Move your dashboards to Streamlit, and they come out better than the original. Together with Snowflake, Streamlit covers much of what teams use a BI tool for: governed data and metrics, including semantic views where you use them, Snowflake's access controls, interactive filtering and drill-down, live refresh, and sharing and embedding. On top of that, it adds what BI tools weren't built for.
Dashboards that compute and act, built with agents, in Python your team can read
What a dashboard isA BI toolA report in a tool-specific formatStreamlitPython code in your repository
LogicA BI toolA formula or modeling languageStreamlitYour existing Python models, libraries, and tests, plus SQL and the whole Python ecosystem for forecasts and AI
ChartsA BI toolThe vendor's chart catalog and custom visualsStreamlitNative charts, maps, and diagrams, plus any Python library
InteractivityA BI toolBuilt into the toolStreamlitLazy-loading tables, cross-filtering, drill-down, background refresh, and shareable views, from Python that agents write and change
Taking actionA BI toolBuilt mainly for reading, with writeback in some toolsStreamlitEditable tables, forms, approvals, and writeback, validated by the same Python code that produced the numbers
Who builds itA BI toolAnalysts in a visual editorStreamlitAnyone, through a coding agent, reviewed by the data team
Change managementA BI toolMostly published from a visual editorStreamlitPull requests, review, and tests, with agents making changes from a request in plain words
Questions from agentsA BI toolThrough the vendor's own assistant or connectorsStreamlitAn assistant sets the filters and reads the numbers through the dashboard's own logic, instead of guessing at the warehouse schema
CostA BI toolPer-seat licensesStreamlitOpen source; pay for the compute you use
Best forA BI toolDrag-and-drop self-service and paginated reportsStreamlitThe dashboards that matter most, with logic and actions

A BI tool still fits

  • Drag-and-drop self-service exploration by people who don't want code
  • Pixel-precise paginated reports

From BI concepts to Streamlit

What each part of a dashboard becomes

Use this as a checklist when you, or your coding agent, rebuild a dashboard. It maps concepts, not files: there's no automatic converter, and the point is to rebuild what matters, not to copy everything.
What each part of a dashboard becomes
Slicers and filtersIn StreamlitSelect boxes, multiselects, date inputs, and sliders, bound to the URL so filtered views can be shared (bind="query-params")
Measures and calculated fieldsIn StreamlitPlain Python or SQL functions, cached with @st.cache_data
Scheduled refreshIn StreamlitCached queries that expire after a set time and refresh in the background (ttl, refresh_mode="background")
KPI cardsIn StreamlitMetrics with deltas and sparklines (st.metric, chart_data)
VisualsIn StreamlitNative charts for nearly every visualization, from quick charts to ECharts, Altair, and Plotly, maps and 3D layers, and diagrams (st.echarts_chart, st.altair_chart, st.pydeck_chart)
Tables and matricesIn StreamlitTables with number formats, progress bars, and links that load rows as people scroll (st.dataframe, column_config)
Cross-filtering and drill-downIn StreamlitSelections on charts and tables drive the rest of the page (on_select="rerun")
Report pagesIn StreamlitMultipage apps with shareable page URLs (st.navigation)
Auto-refreshing visualsIn StreamlitSections that rerun on their own schedule (@st.fragment(run_every=...))
Data entry and approvalsIn StreamlitEditable tables and forms that write back to your database (st.data_editor, st.form)
Themes and templatesIn StreamlitOne brand theme for every app, with colors, fonts, and chart palettes ([theme] base)
Viewer accessIn StreamlitBuilt-in authentication (st.login) on top of your existing access controls; on Snowflake, queries can run with caller's rights, so each viewer sees only the data they may see
Natural-language questionsIn StreamlitEvery dashboard is also a tool that assistants call over MCP, with the dashboard's own logic and access rules
Version historyIn StreamlitGit, so every change is a reviewable diff

Compared to dashboards built in chat

A chat report is a snapshot. An app is what your team relies on.

Most dashboards generated in chat are one-off reports: a page that renders in the browser, with the data from one conversation baked in. You can share it, but it doesn't refresh, nobody answers for its logic, it isn't tested, and it can't take action. Ask the question in chat. When the answer needs to become something more, it becomes a Streamlit app.
  • It needs to stay live

    Fresh data every time someone opens it.
  • It takes new parameters

    Filters, levers, and drill-downs instead of a fixed answer.
  • It needs to be reviewed and tested

    Reviewed code in your repository, with tests that run in CI.
  • It writes decisions back

    Approvals, sign-offs, and corrections, saved where the data lives.

Frequently asked questions

Get started

Rebuild the dashboard that matters most

Set up your coding agent with Streamlit's skills, point it at your data, and describe the dashboard. Then check the numbers against the original.
Terminal
$ pip install streamlit
$ streamlit skills

> /developing-with-streamlit Rebuild our
> weekly revenue dashboard on the sales.revenue
> semantic view, with region and plan filters,
> and a check against last week's numbers.