What problem did Kyso aim to solve for data science teams?

Updated

Kyso set out to solve the fragmentation of data science results across tools. According to Kyso's own team note, the platform was built because technical teams often use different workflows and tools, and without a central hub to document and share results "whatever the source or format," findings end up scattered across many applications. Kyso shut down on September 31, 2023, and its project is now open-source on GitHub, so the problem it described is still relevant even though the hosted platform is gone.

The core problem: scattered results, siloed collaboration

Kyso's team described a specific chain of failure inside organizations:

  • Data science work spans many roles that use code and data to produce results and drive business actions.
  • Those teams are embedded in a wide variety of tools, "even within a single organisation."
  • Because there is no central hub to document and share everything, results are scattered across many different applications.
  • Collaboration then happens in "smaller, private channels," which limits wider and long-term discovery.

The net effect: knowledge is not documented or searchable, so the value created by data teams is not fully leveraged.

Why this happens even in well-funded teams

Kyso's note points out that the problem is common enough that large companies built their own internal solutions. Stripe and Airbnb built internal tools, Spotify was working on something similar, and Netflix was building an in-house aggregator. The team also noted that companies pouring money into data science and analytics capabilities "will fail to truly leverage all of the value created by these teams if knowledge is not documented & searchable."

How Kyso's focus evolved

Kyso started in 2018 focused specifically on Jupyter Notebooks, which the team described as "already fast becoming the new Excel," offering cloud-based compute environments and a simple reporting frontend. It also ran a public Jupyter-based blog that at one point had over 60k monthly readers. Over time, conversations with organizations revealed that the tooling ecosystem extended far beyond Jupyter, which led Kyso to reposition as a "universal aggregator for all research formats."

What this means if you are evaluating the problem today

Kyso is no longer available as a hosted service, so you cannot use it to solve this problem directly. What remains useful is the problem definition:

  • If your team's results live in notebooks, dashboards, documents, and chat threads with no shared index, you have the fragmentation Kyso described.
  • The test is whether results are documented and searchable across tools, not whether any single tool is good.
  • The open-source project on GitHub is the remaining artifact if you want to inspect how Kyso approached aggregation.

For current alternatives, evaluate them against the same criteria Kyso named: can they aggregate multiple formats and sources, and do they make results discoverable beyond private channels?