How Kyso Evolved From a Jupyter Notebook Platform

Updated

Kyso began in 2018 as a Jupyter Notebook-focused platform and later widened into a universal aggregator for research formats, before shutting down on September 31, 2023 and releasing its code as open source. The evolution matters if you are tracing the history of notebook collaboration tools, evaluating the open-source project, or deciding whether any surviving piece fits your workflow.

The starting point: Jupyter Notebooks as the new Excel

The founding team's original premise was that Jupyter Notebooks were becoming the default working format for data science, much as spreadsheets had been for earlier analysts. Kyso's first product reflected that assumption directly:

  • Cloud-based compute environments so users did not have to run notebooks locally.
  • A simple reporting frontend to turn notebook output into something shareable.

The goal was to remove friction from collaborating on technical results when team members used different local workflows and tools.

The public notebook blog

One early experiment was a public, Jupyter-based blog. According to the team's note, it reached over 60,000 monthly readers at one point. That experiment is a useful signal of demand: there was an audience for notebook-native publishing, not just private team collaboration.

Why the scope expanded beyond notebooks

Conversations with more organizations surfaced a recurring problem. Data science work was spreading across many roles and many tools, and even within a single company the tooling ecosystem was fragmented. The team's own description of the shift:

  • Data science came to encompass a wide range of positions that use code and data to produce results and drive business actions.
  • Technical teams were embedded in a wide variety of tools, so there was no central hub to document and share everything regardless of source or format.
  • Results ended up scattered across applications, and collaboration happened in smaller private channels, which hurt wider and long-term discovery.

The stated consequence: companies investing heavily in data science and analytics would fail to fully leverage the value created if knowledge was not documented and searchable. Kyso's team noted this problem was well known enough that Stripe and Airbnb built internal solutions, Spotify was working on something similar, and Netflix was building an in-house aggregator.

That reframing is the core of the evolution: from "a place to run and publish notebooks" to "a universal aggregator for all research formats."

Timeline at a glance

Phase Focus What it produced
2018 founding Jupyter Notebooks Cloud compute environments, simple reporting frontend
Early experiment Public notebook publishing Jupyter-based blog with 60k+ monthly readers
Later iterations Broader data workflows and formats Universal aggregator for research formats
September 31, 2023 Shutdown Platform closed
After shutdown Open source Code published on GitHub

What this means if you are evaluating it today

The platform itself is no longer available, so the practical question is what remains usable:

  • The open-source project is the surviving artifact. The site points to a GitHub repository and a Gitbook, so that is where to look for code and documentation.
  • No pricing or access terms are stated in the available material, so do not assume the open-source release is a drop-in replacement for the hosted service.
  • If you need the original hosted features — cloud compute plus a reporting frontend — you would be evaluating the open-source code on your own infrastructure rather than signing up for a service.

For anyone studying the category, Kyso's arc is a compact case study in why notebook-only tools tend to expand: the collaboration problem is rarely confined to one file format.