About

Why Metagrid exists

Spreadsheets flatten the world into one rectangle. Real work is nested. Metagrid treats nesting as the primitive.

Problem

A project has a budget table; each line has its own schedule; totals roll up. Flat sheets force that structure into many tabs, named ranges, and fragile lookups. The hierarchy lives in the user’s head, not in the document.

Approach

Nested structures — grid, table, list, dictionary (and live pivot summaries) — that can contain each other. A dictionary is a one-record table with named fields; a field is numbered values only. Formulas walk the tree with paths instead of only A1 on a single plane. The UI is keyboard-first so navigation depth doesn’t require a mouse tree widget.

Implementation stays deliberately small: static files, optional Supabase for private cloud blobs, no collaboration layer until the document model is boringly solid.

Status

Numbers that matter

ThingValue
Structure typesgrid · table · list · dictionary · pivot
Documents1 tree per workbook
Export formatmetagrid-v2
App modulesmodel · formula · format · ui (ribbon, keytips, paint, …)

Open the app

Sample workbook is preloaded. F1 for shortcuts.

Open Metagrid →