OrcaSheets, local first analytics engine to process billions of rows
Runs billions of rows locally on your machine, bypassing cloud warehouse costs entirely.

Billion-row spreadsheets with live warehouse connections beat Excel's 1M row ceiling.
Data analysts and enterprise teams working with large datasets
Causal · Airtable · Excel
Under the hood, the spreadsheet engine is a columnar key-value store written in Rust. We built it from scratch because SQL engines like DuckDB only work well for structured tables. The unstructured nature of spreadsheets make them a bad fit for SQL. The engine also needs to be 100% Excel compatible so you can import existing xlsx files.
The front-end is a big React app with hand-rolled canvas rendering. We virtualize scrolling to handle 2 billion+ row data sets. All workbook state runs in the cloud (located in a data center close to you to keep things snappy).
We launched on HN 2 years ago and got lots of great feedback. Since then, customers have pulled us towards the enterprise. Today we're launching Row Zero 2.0 with support for all the enterprise bells and whistles: OAuth database connections, SSO, SCIM, workspaces, private link on AWS and Azure, bring your own AI key, and private storage. Excited to hear what you think.
Runs billions of rows locally on your machine, bypassing cloud warehouse costs entirely.
WASM engine handles millions of rows when Excel chokes on large files.
Sheetz literally reduces Apache POI boilerplate to Sheetz.read(...) / Sheetz.write(...), and it pairs that convenience with annotation-based mapping, a fluent multi-sheet builder, built-in streaming for million-row files, and row-level validation. It doesn't invent a new category—EasyExcel and POI already exist—but the one-line API, examples, and Maven releases make it an attractive, pragmatic choice when you need spreadsheet import/export without wrestling with workbook plumbing.
Yet another React data table, but Shadcn integration is timely.
Schema conformance checks beat generic text evals for JSON-heavy LLM pipelines.
Outbox + external worker architecture solves a real production pain: LLM calls in Postgres triggers without blocking transactions.