Overview
Jupyter Day brings together data scientists, developers, researchers, educators, and open source contributors to shape the future of interactive computing. This year's event explores how Jupyter enables new workflows across data science, scientific computing, visualization, education, and AI, while advancing open, reproducible, and accessible computing. Attendees will hear from Project Jupyter contributors and the broader community, exchanging ideas about the future of interactive computing.
Speakers
25Schedule
Jupyter Day
Learn more and help shape the future of AI in Jupyter through hands-on collaboration, demos, roadmap planning, and community sessions.
Registration + Badge Pickup
Registration + Badge Pickup
Welcome + Opening Remarks
Welcome + Opening Remarks
Keynote: Jupyter at Twenty-Five: Curiosity, Community, and the Work Ahead
<p>In December 2001, a graduate student shared a few hundred lines of Python designed to make interactive computing a little less tedious. There was no grand plan for the future of interactive computing. It was simply someone building a better place for people to do their work.</p><p>That prompt grew into a rich shell, then an interactive notebook, then a global ecosystem. Twenty-five years later, Jupyter is how millions of people explore and share ideas, in classrooms, research labs, and quiet
Keynote: Jupyter at Twenty-Five: Curiosity, Community, and the Work Ahead
Children of Jupyter: What Core Should Steal Back
<p>Jupyter's 2011 kernel design has aged well: Colab, VS Code, Deepnote, and even ChatGPT's Python tool all run Jupyter kernels today. The notebook itself, though, still runs on the same linear REPL as in 2011, and hidden state remains its most famous complaint. A generation of descendants (Observable, Pluto, marimo, Hex, Livebook, Deepnote) has spent a decade shipping fixes for these problems. It is past time for Jupyter core to steal from its children, but first it needs a survey of
Children of Jupyter: What Core Should Steal Back
Max Klein talks about what the core of Jupyter should steal back from its children.
Notebooks Behind the Firewall: AI Agents and Real Patient Data in Jupyter
<p>Biomedical researchers have the same AI agents as everyone else, but can't point them at their actual data. Patient records can't leave the medical center, so the agent never sees them. Institutions already host compliant model inference. The gap sits at the agent layer.</p><p>This talk covers how we use Biorouter to close that gap at UCSF and connect it to Jupyter. Biorouter is an open-source research agent that routes work across institutionally hosted, local, and commercial model
Notebooks Behind the Firewall: AI Agents and Real Patient Data in Jupyter
Wanjun Gu discusses AI agents and real patient data in Jupyter notebooks behind firewalls.
Your AI-Generated GPU Kernel Passed the Notebook. It Is Still Wrong.
<p>Attendees will leave able to turn a persuasive notebook demo into a reproducible correctness gate for AI-generated CUDA and Triton kernels.</p><p>An AI-generated kernel can compile, run quickly, and match a reference on a few friendly tensors while still failing on boundary shapes, strides, aliasing, dtype extremes, special values, or reduction order. This talk builds the verification workflow as a Jupyter notebook: an independent CPU oracle, operator-aware input generation, explicit toleranc
Your AI-Generated GPU Kernel Passed the Notebook. It Is Still Wrong.
Dipankar Sarkar explains why AI-generated GPU kernels can be wrong despite passing notebook tests.
Break
<p>Assorted Bagels + Cream Cheese<br>- Gluten-free bagel available<br>- Vegan options available</p><p>Assorted Low Fat Yogurt (V/GF/NF)<br>- Vegan option available</p>
Break
Upstream Is Everyone’s Business: How Can Industry Contribute to Jupyter?
<p>This session is intended to be a facilitated discussion about the opportunities and obstacles people encounter when trying to contribute to the Jupyter ecosystem from within a company.</p><p>SESSION FORMAT<br>We will begin with a brief framing of the question and a few common models for organizational participation in open source.</p><p>Most of the session will then be dedicated to experience-sharing among participants.</p><p>The final portion of the session will synthesize the discussions in
Upstream Is Everyone’s Business: How Can Industry Contribute to Jupyter?
Inessa Pawson explores how industry can contribute to Jupyter.
When LLMs Get Infrastructure Wrong: Building Reliable AI Workflows in Jupyter
<p>LLMs can summarize logs, explain failures, analyze configurations, and suggest fixes in seconds. But infrastructure engineering has an uncomfortable requirement: an answer that merely sounds correct isn't good enough.</p><p>In this session, I’ll use Jupyter to build and evaluate an AI-assisted infrastructure analysis workflow where LLM-generated conclusions are treated as hypotheses rather than facts. We’ll examine common failure modes including hallucinated root causes, missing context,
When LLMs Get Infrastructure Wrong: Building Reliable AI Workflows in Jupyter
Sowmya Varakala discusses building reliable AI workflows in Jupyter when LLMs get infrastructure wrong.
How Does Jupyter Display a Plot? Making Passagemath Plots Work in Any Notebook
<p>When plotting in passagemath, I noticed that plots sometimes displayed text instead of an image. passagemath is a modular version of the math software SageMath. SageMath has its own display system, but the system is not in many notebook environments. I learned that IPython's DisplayFormatter collects the available representations and the notebook frontend chooses which one to display. In contrast, SageMath asks the frontend what it supports and renders just one thing. By adding repr<em>s
How Does Jupyter Display a Plot? Making Passagemath Plots Work in Any Notebook
Samuel Chen and Matthias Köppe explain how Passagemath plots work in any notebook.
Lightning Intros
<p>Ever wished you could meet everyone at a conference in one go? This is your chance!</p><p>During Lightning Intros, each participant gets 30 seconds to introduce themselves to the full group and share what topics they’re most excited to talk about. Then, during the reception that follows, you can seek each other out and dive into those conversations.</p><p>No slides, no prep—just you and a microphone.</p>
Lightning Intros
Lunch
<p>The Lunch Box</p><p>Sandwich:<br>- Chicken Caesar Roll Up | Grilled Chicken Breast, Romaine Lettuce, Gouda Cheese, Sun Dried Tomatoes, Caesar Dressing, Spinach Tortilla (NF)<br>- So California Sandwich | Smoked Turkey, Maple Bacon, Garlic Aioli, Arugula, Whole Wheat Multigrain Hero (DF/NF)<br>- Romaine Salad | Turnips, Lentils, Cranberries, Apple Cider Vinaigrette (Vegan/GF/NF)<br>- Chipotle Steak (GF/DF/NF)<br>- Soy Ginger Tofu (Vegan/GF)</p><p>Sides:<br>- Kettle Chips (V/NF/GF)<br>- Honey C
Lunch
The Future of Jupyter: Building the Next Core, Together
<p>Project Jupyter's future is being built in the open, but much of it lives outside the default install. This panel brings maintainers from multiple organizations to align on what's next.</p><p>We'll debate the foundational capabilities that would benefit everyone: disconnection-resilient execution (a reload never loses a running cell), robust real-time collaboration, native diffing, performance for large notebooks, and simpler, better-documented server APIs developers can build
The Future of Jupyter: Building the Next Core, Together
David Qiu, Kirstie Whitaker, Zach Sailer, Min RK, Chris Holdgraf, and Jason Grout discuss building the next core of Jupyter together.
Invisible Infrastructure at Scale: Operating 5,000 Daily Notebook Servers Across Multiple Kubernetes
<p>Starting a Jupyter notebook appears to be one simple action. At approximately 5,000 real notebook-server sessions on a typical day, that action becomes considerably more complex - especially because the workloads are not identical. Each notebook may require a different combination of CPU, memory, GPU capacity, container image, storage, and runtime configuration, with some resources available only in particular clusters.</p><p>This talk presents how we extended KubeSpawner to separate the Jupy
Invisible Infrastructure at Scale: Operating 5,000 Daily Notebook Servers Across Multiple Kubernetes
Karthik Ravi and Karthik Banala share insights on operating 5,000 daily notebook servers across multiple Kubernetes clusters.
Running GPU Jupyter Workspaces on Kubernetes: Scheduling, Autoscaling, and Policy Lessons
<p>Kubernetes autoscaling is built for workloads that can be killed and rescheduled at any moment. A notebook is the opposite: its state lives in a running kernel, an eviction interrupts a person mid-work, and its GPU cannot be shared. We added GPU workspaces to jupyter-k8s, an open-source Kubernetes operator for Jupyter, and most of the hard questions turned out to be one question: which layer should own this knob, cloud instances, autoscaler, operator, infrastructure-as-code, or UI.</p><p>The
Running GPU Jupyter Workspaces on Kubernetes: Scheduling, Autoscaling, and Policy Lessons
Andrii Ieroshenko and Gaurav Bhanderi discuss scheduling, autoscaling, and policy lessons for running GPU Jupyter workspaces on Kubernetes.
Cartographers on Your Hub
<p>JupyterGIS is an in-development ecosystem project to enable collaboration and reproducibility in Geospatial Science. Cartographers, designers who specialize in representing spatial data, are not the users it was most obviously built for, but I'd argue they may be a major component of its first serious userbase.</p><p>Professional cartographers do surprisingly little of their work in GIS. They use it for cleaning, filtering, and basic symbolization, then hand off to a design tool for the
Cartographers on Your Hub
Benjamin Szeghy talks about cartographers on your hub.
Break
Roadmapping to Improve Community Capacity, Alignment, and Team Productivity
<p>In The Voices of JupyterHub (<a href="https://voicesofjupyterhub.orgmycology.com" target="_blank" rel="noopener noreferrer">https://voicesofjupyterhub.orgmycology.com</a>) ethnographic report, the JupyterHub leadership team identified that our community "struggles with onboarding new contributors and delegating responsibility", and that "project management, prioritization, and triage processes are a source of stress for maintainers and confusion for newcomers". Building on
Fantastic Environments and Where to Find Them
<p>Frontier labs pay millions for a single RL environment representing one high-value task: software engineering, cybersecurity, project management. That closed industry is a big part of why frontier agents perform.</p><p>This talk is a field guide to cracking it in the open. I'll cover how the environment business works, from research and reporting; the open source counterparts, Prime Intellect, TRL, and OpenEnv; and an end-to-end walkthrough of training a cybersecurity agent for free. You
Beyond WER: Interactive Failure Analysis for Multilingual Audio Models in Jupyter
<p>Word Error Rate is often treated as the final answer when evaluating speech recognition models. But a single aggregate score can hide where a model actually fails.</p><p>In multilingual and conversational speech, two models with similar WER can behave very differently across dialects, code-switching, acoustic conditions, speaking styles, and data sources.</p><p>In this talk, I will show how Jupyter can turn model evaluation from a static benchmark into an interactive and reproducible investig
Jupyter Day
Learn more and help shape the future of AI in Jupyter through hands-on collaboration, demos, roadmap planning, and community sessions.