Project Jupyter
nonprofit organization that developed and supported the interactive computing products Jupyter Notebook, JupyterHub, and JupyterLab
Project Jupyter (pronounced "Jupiter") is a project to develop open-source software, open standards, and services for interactive computing across multiple programming languages.
It was spun off from IPython in 2014 by its Seven Founding Members: Fernando Pérez, Brian Granger, Damian Avila, Kyle Kelley, Matthias Bussonnier, Min Ragan-Kelley, and Thomas Kluyver. Project Jupyter's name is a reference to the three core programming languages supported by Jupyter, which are Julia, Python and R. Its name and logo are an homage to Galileo's discovery of the moons of Jupiter, as documented in notebooks attributed to Galileo.
Jupyter is financially sponsored by the Jupyter Foundation.
History
The first version of Notebooks for IPython was released in 2011 by a team including Fernando Pérez, Brian Granger, and Min Ragan-Kelley. In 2014, Pérez announced a spin-off project from IPython called Project Jupyter. IPython continues to exist as a Python shell and a kernel for Jupyter, while the notebook and other language-agnostic parts of IPython moved under the Jupyter name. Jupyter supports execution environments (called "kernels") in several dozen languages, including Julia, R, Haskell, Ruby, and Python (via the IPython kernel).
In 2015, about 200,000 Jupyter notebooks were available on GitHub. By 2018, about 2.5 million were available.
The public source identifies “Project Jupyter” as nonprofit organization that developed and supported the interactive computing products Jupyter Notebook, JupyterHub, and JupyterLab. This brief keeps that definition visible, then builds a research path around Project, Jupyter and nonprofit.
Why this record matters
A short description can identify a subject without explaining its stakes. For “Project Jupyter”, the useful work is to connect “nonprofit organization that developed and supported the interactive computing products Jupyter Notebook, JupyterHub, and JupyterLab” to the records capable of establishing context and consequence.
Datasets, specimens, observations and peer-reviewed methods provide the appropriate test for the technical claims summarized here. The source revision retrieved here is dated Sep 20, 2026. The linked authority identifier is Q55630549. 1 of 2 selected statements include explicit references; 1 carry qualifiers and 0 use preferred rank. The first chronological checks are 2014, 2011, 2015 and 2018.
Current terminology should not be projected backward without checking the classification used when the underlying evidence was created. The lead is largely declarative, so disagreement and counter-evidence require a deliberate search beyond the opening account. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Check terminology, classification and the date of the cited evidence. Scientific names and technical consensus can change while older records retain historical value.
- Current terminology
- Classification context
- Finding cited technical literature
Primary datasets, specimen catalogues, standards bodies and the most recent peer-reviewed literature.
Three-step research path
- Establish the record: confirm the title “Project Jupyter”, its source revision and the description used here.
- Expand the search: follow Project Jupyter primary sources, Project Jupyter archive and Project research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “Project Jupyter”?
- Is the terminology current, historical or disputed?
- Has classification or technical consensus changed since the cited source?
Search terms from this dossier
This entry incorporates text from “Project Jupyter” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.