Verso

An interactive notebook platform and an embeddable .NET execution engine. Eight language kernels share one variable store, and every feature, including the built-in ones, is an extension.

LicenseMIT, developed in public
KernelsC#, F#, Python, SQL, HTTP, PowerShell, JavaScript, Markdown
SurfacesVS Code, browser, terminal, CI
Formats.verso, .ipynb, .md; imports .dib
Runtime.NET 8, .NET 10
Released1.0 on 2026-02-20

The problem it solves

Understanding data is iterative. You load something, look at it, reshape it, and look again, and the fastest loop wins. Python developers have had that loop in a notebook for a decade. .NET developers had a console app and a debugger, and the notebooks that existed were a place to run code, not an engine to build on.

Verso is that notebook, and the engine underneath it is an ordinary .NET library you can embed anywhere.

What Verso is

A C# cell hands a table to a Python cell or a SQL cell without serialization, because the kernels share one variable store. The same engine runs in VS Code, in the browser through verso serve, and in the terminal for CI. Notebooks are saved as .verso, .ipynb, or plain .md, and .dib files import directly.

The notebook surface itself is a layout, and layouts are extensions. The showcase ships a dashboard, a slide deck, a spreadsheet, a reactive graph, and an image compositor, each rebuilding the surface into something else on the same public interfaces.

If the extension surface is not good enough for our own features, it is not good enough to ship.

Compared with

Where Verso sits next to the notebooks .NET developers already know.

VersoPolyglot NotebooksJupyter
LanguagesC#, F#, Python, SQL, HTTP, PowerShell, JavaScript, MarkdownC#, F#, PowerShell, SQL, KQL, JavaScript, HTML, and moreAny language with a kernel, one kernel per notebook
Variable sharingOne store; every kernel reads and writes it directlyExplicit #!share, copying a value between kernelsNone across kernels
SurfacesVS Code, browser, terminal, CIVS Code; Jupyter front ends through .NET InteractiveJupyterLab, VS Code, and others
Embeddable engineYes, an ordinary NuGet libraryHostable, but built as a kernel processKernel process
Replaceable surfaceYes, layouts are extensionsNoNo
Formats.verso, .ipynb, .md; imports .dib.ipynb, .dib.ipynb
LicenseMITMITBSD

Where it fits

The Datafication SDK loads and shapes the data. Verso is where you look at it. Motus proves what the notebook produced in a real browser, and it is what we use to test Verso's own browser host.

Specifications

KernelsEight languages
C#, F#, Python, SQL, HTTP, PowerShell, JavaScript, Markdown. One shared variable store.
SurfacesOne engine
VS Code extension, browser host, command line for CI. All consume the same headless engine.
Layouts
Dashboards, slides, spreadsheets, reactive graphs, and an image compositor ship as showcase extensions.
Agents
Copilot participant and language-model tools in VS Code; an agent can run cells and read outputs.

Get Verso

VS CodeExtension
Command lineBrowser and CI
dotnet tool install -g Verso.Cli
EmbedEngine
dotnet add package Verso