Visivo capability

Ship dashboards as static files. They still filter.

visivo dist packages your last visivo run into a folder of HTML, JavaScript and data. Put it on S3, GitHub Pages, Netlify or an nginx directory. Inputs and interactions run in the visitor's browser in DuckDB-WASM, with no server of yours behind it.

dist/
$visivo run$visivo distCreated dist folder: …/dist$python -m http.server --directory dist
A template dashboard named EV Quarterly Brief: two KPI tiles above a bar chart and a pie chart, laid out in custom HTML and served from a visivo dist folder.
The dist folder above, served as plain static files. Captured from visivo 2.3.2.
How it works

What you get with Static sites

  1. One command

    Run, then dist

    visivo run materializes the data. visivo dist writes the viewer and that data to one folder.

  2. Still interactive

    Not a screenshot

    Inputs, filters, splits and sorts run in DuckDB-WASM against the data in the bundle. Your database is never queried at view time.

  3. Know what ships

    A snapshot, readable by its audience

    The data is frozen at the last run, and anyone who can fetch the files can read it. Aggregate in your models and put access control in front when you need it.

From the CLI

Build the folder, host it anywhere.

Re-run both commands to refresh the numbers, for example from a CI job.

terminal
visivo run # materialize the data
visivo dist # viewer + data in ./dist
# host under a sub-path, e.g. example.com/reports
visivo dist --deployment-root /reports
# preview it locally
python -m http.server --directory dist
See it live

Click around a real dist build.

The live demo is the NYC Taxi project built with visivo dist and served as static files. Every filter runs in your browser.

Install command copied