The world runs on data. Datafication builds the tools .NET teams use to load, shape, explore, and verify it, and the tools their AI agents use beside them.
Three problems we kept running into while building data products for other people. Each one became a product.
| The problem | What we built | Status | |
|---|---|---|---|
| 01 | Working with data in .NET has meant leaving .NET.Python has pandas and polars. .NET teams had LINQ and a shrug. Analytical work ended up in a sidecar language, a spreadsheet, or a database nobody wanted to own. |
 Datafication SDKDataBlock in memory, VelocityDataBlock on disk with SIMD-accelerated queries, connectors for CSV, Parquet, Excel, JSON, SQL, S3, and the web. About the SDK |
Commercial |
| 02 | Exploration had no home.Understanding data is iterative: load, look, reshape, look again. The fastest loop wins, and for .NET teams the fastest loop was in another language. |
 VersoInteractive notebooks and an embeddable engine. Eight kernels share one variable store. VS Code, browser, terminal, CI. About Verso |
MIT |
| 03 | Verifying what you shipped was bolted on.Browser testing from .NET meant a Node.js sidecar, a driver binary, and a process boundary between your test and the page. |
 MotusCDP and WebDriver BiDi spoken directly. Recorder, code generation, accessibility and performance audits, an MCP server for agents. About Motus |
MIT |
Each began as a tool we needed for our own work. Verso and Motus have their own sites; the SDK lives on NuGet.
Analytical data processing for .NET. DataBlock in memory, VelocityDataBlock on disk, connectors, and REST server components. Free for small teams and open-source projects.
Interactive notebooks and an embeddable .NET execution engine. C#, F#, Python, SQL, and more sharing one variable store. Every feature is an extension.
Browser automation and testing that talks straight to Chromium and Firefox. No Node.js sidecar, no driver binaries, and an MCP server so AI agents can drive a real browser.
Four rules that every product has to pass. They are why the products look and behave the way they do.
No Node.js sidecars, no Python bridges, no bundled driver binaries. A tool built for .NET should behave like .NET.
Every built-in feature is implemented on the same public interfaces available to any third party. No private APIs for first-party code.
Verso and Motus are MIT licensed and developed in public. The license will not change under you. The commercial products say so up front.
Every product began as something we needed. Documentation is written alongside the code, not after it.
Release notes with context, design decisions, and the occasional argument about how .NET should treat data.
A layout decides how a notebook is arranged and rendered, and it is an extension like any other: five samples on NuGet turn one file into a graph, a deck, a spreadsheet, a dashboard, and an image editor.
I parse the Palmer Penguins CSV once in C#, group it in Python, aggregate it in SQL, and render it as a typed DataFrame table in PowerShell, all in one notebook with no export step anywhere in it.
I built a full Motus suite against two public pages, gated it on accessibility and Core Web Vitals, recorded a trace, a HAR and a video, then split it across four agents and merged the results back into one report.
No forms, no ticket queues, no chatbots. Email lands with someone who works on the products. More about the company and the team.