CLcl3misch·Aug 26, 2025Submission
Voilà: Turn Jupyter notebooks into standalone web applications
1 points · Open discussionvoila-dashboards
voila
Python2019–2025
voila-dashboards / voila
voila
Voilà turns Jupyter notebooks into standalone web applications
12Distinct people
13Mentions
0Explicit recommenders
6KGitHub stars
What to know before exploring
What it is
Voilà turns Jupyter notebooks into standalone web applications
GitHub
Where it is used
No documented product use was verified in the last source check.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year13 dated mentions
Observed mentions: 2019-10-06 05:39:26 UTC to 2025-08-26 09:53:14 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2019 | 2019-01-01 00:00:00 UTC | 2020-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 2 | 0 | 2 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 1 | 1 | 0 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 6 | 0 | 6 |
| 2024 | 2024-01-01 00:00:00 UTC | 2025-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2025 | 2025-01-01 00:00:00 UTC | 2026-01-01 00:00:00 UTC | 2 | 1 | 1 |
What Hacker News says
13 sourcesIn the browser only jupyter for now, you can use voila to make a server based application using jupyter: https://github.com/voila-dashboards/voila
As Caitlin pointed out below pyodide is a future goal.
In Fastplotlib: GPU-accelerated, fast, and interactive plotting library> I get an analysis that I like, but there isn't a good way to share it with others, so I end up just taking screenshots.
What would be your preferable way of sharing your analysis with others?
- You can turn jupyter notebooks into pdfs directly in the jupyter UI.
- You can upload them to Gitlab/Github and share the link to the rendered result.
- You can upload them to Colab/Binder/Kaggle and let people play with the code themselves.
- You can turn jupyter notebooks into beautiful websites/documents with:
https://quarto.org/docs/tools/jupyter-lab.html
- You can add jupyter notebooks to you docs using nbsphinx:
https://nbsphinx.readthedocs.io/en/0.9.1/
- You can turn jupyter notebooks into interactive web apps with voila:
https://github.com/voila-dashboards/voila
- You can turn jupyter notebooks into presentations with rise:
https://github
Read the rest
If you're interested in using React-style frontend programming in Python but want an experience / API closer to that of React, I recommend checkout out Reacton [1].
Similarly to this library, it gives you a `@component` decorator that allows you to create components out of functions. But it also:
1. Includes all existing React hooks (use_state, use_memo, etc) -- so you don't have to learn new patterns. I believe this results in a bit less magic (and so easier debugging) than just using raw variables.
2. Works with ipywidgets, so many existing data apps can be ported over very easily -- Jupyter users celebrate.
I'm not associated with the project, but I know the maintainers (creators of Volia [2]) and they are honestly excellent. I haven't use the project in production, but the getting starting guide is pretty compelling.
[1] https://githu
Read the rest
Quick link: https://github.com/voila-dashboards/voila
Humbly recommend when you share a product, you include a link to it ;)
https://voila.readthedocs.io/en/stable/
In Show HN: Mercury – Convert Jupyter notebooks to web appsOrienting the product to a different audience and therefore changing the defaults is fair enough.
> Jupyter is better suited to one off analysis.
> Works with CI/CD out of the box. Deploy to vercel, netlify, your own infra.
Jupyter is suited for whatever you want to do with it. Voila exists to enable the use case of re-generating notebooks on a CI/CD system: https://github.com/voila-dashboards/voila
Anyways, seems like the templating is more powerful than the one being offered by Jupyter Notebooks.
Good luck and much success with it :)
In Evidence.dev – Business Intelligence as CodeThere's Voilà for Jupyter Notebooks, that does exactly that: https://github.com/voila-dashboards/voila
In Evidence.dev – Business Intelligence as CodePerhaps https://github.com/voila-dashboards/voila?
Not sure about ease relative to other alternatives.
In Ask HN: Fastest way to turn a Jupyter notebook into a website these days?How is this better than Voila, which is developed by the Jupyter Notebook team?
https://github.com/voila-dashboards/voila
In Show HN: Mercury – Publish Jupyter Notebook as web app by adding YAML headerVoilà turns Jupyter notebooks into standalone web applications
2 points · Open discussionFor a visual output, voila can give you a dashboard look: https://github.com/voila-dashboards/voila/ see e.g. https://github.com/maartenbreddels/voila-demo for a mobile-ready responsive rendering of a notebook.
In A Visual Debugger for JupyterA mature implementation exists, called voilà, see https://github.com/voila-dashboards/voila, which is developed by members of the Quantstack.
In Jupyter Notebooks to Web AppCool!
requests_cache caches HTML requests into one SQLite database. [1] pandas-datareader can cache external data requests with requests-cache. [2]
dask.cache can do opportunistic caching (of 2GB of data). [3]
How does streamlit compare to jupyter voila dashboards (with widgets and callbacks)? They just launched a new separate github org for the project. [4] There's a gallery of voila dashboard examples. [5]
> Voila serves live Jupyter notebooks including Jupyter interactive widgets.
> Unlike the usual HTML-converted notebooks, each user connecting to the Voila tornado application gets a dedicated Jupyter kernel which can execute the callbacks to changes in Jupyter interactive widgets.
> - By default, voila disallows execute requests from the front-end, preventing execution of arbitrary code.
[1] https://github.com/reclosedev/requests-cac
Read the rest
he
[2] https://pandas-datareader.readthedocs.io/en/latest/cache.htm...
[3] https://docs.dask.org/en/latest/caching.html
[4] https://github.com/voila-dashboards/voila
[5] https://blog.jupyter.org/a-gallery-of-voil%C3%A0-examples-a2...
Acess control and resource exhaustion are challenges with building any {Flask, framework_x,} app [from Jupyter notebooks]. First it's "HTTP Digest authentication should be enough for now"; then it's "let's use SSO and LDAP" (and review every release); then it's "why is it so sloww?". JupyterHub has authentication backends, spawners, and per-user-container/vm resource limits.
> Each user on your JupyterHub gets a slice of memory and CPU to use. There are two ways to specify how much users get to use: resource guarantees and resource limits. [6]
[6] https://zero-to-jupyterhub.readthedocs.io/en/latest/user-res...
Some notes re: voila and JupyterHub:
> The reason for having a single instance running voila only is to allow non JupyterHub users to have access to the dashboards. So without going through the Hub auth flow.
> What are the requirements in your case? Voila can be installed in the single user Docker image, so that each user can also use it on their own server (as a server extension for example). [7]
[7] https://github.com/voila-dashboards/voila/issues/112