Sabela: Reactive notebook for Haskell with pedagogical value for data work

What it does

Sabela is a notebook environment for writing and running Haskell code. Cells in a notebook automatically react to changes in other cells, updating their outputs in real time. The tool supports Python interoperability, allowing users to call Python code from Haskell and vice versa. It includes widgets and animation capabilities alongside traditional code execution.

Who it is for

The primary use case is exploratory data analysis and interactive data work in Haskell. The gallery shows notebooks covering linear regression, dataframe operations, and machine learning workflows. Beyond data work, Sabela has emerged as a teaching tool. The platform hosts ported versions of Haskell tutorials and can illustrate functional reactive programming concepts. It suits developers learning Haskell who benefit from immediate feedback loops.

Pricing

The site does not show prices.

How it stands out

Reactive notebooks are common in Python (Jupyter) and JavaScript (Observable), but few exist for Haskell. Sabela fills this gap by making the language more accessible for exploratory work without sacrificing Haskell's type system or functional paradigm. The gallery demonstrates this covers diverse domains: 3D graphics, effects systems, machine learning, and animations. The ability to interleave Python and Haskell in one notebook is a practical advantage for teams with mixed codebases. Sabela notebooks are published as downloadable files that others can fork and modify, creating a shareable artifact that runs directly in the browser or locally.

What a founder should check

First, understand the incumbent landscape. Jupyter dominates data notebooks across all languages, and it runs Haskell through kernels. Verify whether Sabela's reactivity and pedagogical framing address pain points Jupyter does not solve for Haskell users, or if the niche is too narrow to sustain a business.

Second, assess switching costs. Haskell developers investing time in Jupyter Haskell kernels, whether individually or in teams, would need strong reasons to migrate. Check whether the community network effects matter more than ease of setup.

Third, examine the free offering versus monetization strategy. A gallery and hosted notebooks exist at no visible cost, suggesting either ad-supported, donation, or enterprise-tier revenue models. Clarify whether keeping the core tool free while charging for hosting, computation, or collaboration features is viable with Haskell's small developer population.

Thinking of building something like this?

Every launch here is a competitor to somebody's idea. If yours is close, check it against the market before you build: the Full Check names the rivals, the prices and the gaps.