compile_events · live
awaiting first compile…
Comparison · Flatland vs.

Flatland vs.
Excel.

Excel is an untyped grid that computes whatever formulas it's given. Flatland is a typed compiler that refuses to compile invalid models.

Excel · 1985-present · the world's most-deployed numerical surface. · Flatland · 2026 · typed reasoning layer, API-first, metered.

Specimen · the same logic, two substrates
Excelcell B9 · selected
Formula bar:
=B7-B8
B7
71,040
gross profit?
B8
62,400
opex?
B9
8,640
?

Cell B9 holds a number. The number was computed by subtracting B8 from B7. Whether B7 is revenue or gross profit, whether the subtraction is even semantically valid, is up to the human looking at the sheet.

Flatland · IRdriver · ebitda
driver ebitda {
  category: "computed",
  type:     Currency(USD),
  formula:  gross_profit - opex,
  depends_on: [gross_profit, opex]
}

 dimensional check: Currency − Currency → Currency
 dependencies resolved at compile time
 assertion: ebitda > -cash_reserves · passes

The driver has a name, a type, a formula, declared dependencies, and an assertion that constrains the valid output range. The compiler reads all of this before producing a number. If the types don't line up, no number comes out.

Both substrates produce the same number. Only one of them can tell you why, and only one of them refuses to produce it when the math is wrong.

Diagnostic · 12 dimensions, honestly✓ = wins ·: = neither · × = loses
Dimension
Excel
Flatland
Why it matters
Typed values
×
Excel cells hold strings or numbers; type is implicit. Flatland drivers carry Currency, Percentage, Count, Duration types: checked at compile time.
Named dependencies
×
Excel formulas reference cell coordinates (B7). Flatland references named drivers (gross_profit). Refactor without breaking refs.
Assertions / guardrails
×
Excel has no built-in concept of "this number should always be ≥ 0." Flatland has a first-class assertion engine.
Audit trail of changes
Excel has Track Changes; nobody uses it. Flatland's IR is versionable in git and diffable line-by-line.
Determinism on re-open
Excel recalculation order has produced reproducible spreadsheet bugs (Reinhart-Rogoff). Flatland compilation is topologically sorted; same IR → same output, bit-identical.
AI agent surface
×
Excel exposes COM/Apps Script. Flatland exposes a typed MCP tool surface; agents call it with structured contracts.
Multi-author concurrent edit
Excel Online + Office 365 do real-time collab. Flatland models are git-flow today; concurrent edit is on roadmap.
Familiarity / hiring pool
×
Everyone in finance can read an Excel sheet. Flatland's reader pool is smaller; the export is a real Excel.
Charts & visual formatting
Excel has a 35-year head start on chart libraries. Flatland exports to Excel for charts.
Cell-level formula editing UX
Excel's formula bar is unmatched for direct cell-level math. Flatland models edit at the driver level, not the cell level.
Scenario / sensitivity built-in
×
Excel has Data Tables; they break on non-trivial models. Flatland has a typed sensitivity engine that traverses the DAG.
Investor / regulator acceptance
Excel is the lingua franca; Flatland exports rubric-scored Excel. The artifact your auditor receives is identical.
When you should pick Excel instead

You're building a one-off model with five drivers and three months of life. You need a chart in the next twenty minutes for a board meeting. Your collaborator doesn't use AI and you're working in Office 365 alongside them. You're producing a deliverable that needs Pivot Tables, Power Query, or VBA macros. In all of those cases, Excel is the right tool. We'll still export an Excel you can hand to the auditor; the model lives in Excel, not in our IR.

When you should pick Flatland

The model has to outlive the modeler. The model has to be auditable by someone who didn't build it. The model has to be touchable by an AI agent without producing an answer no one can defend. The model has to compile, fail loudly, and tell you exactly which assumption broke.

The model decays.
The compiler doesn't.

Try it · sixty seconds

Compile your Excel model
into typed IR.

Tell our agent what you'd build in Excel. It produces a typed model with named drivers, assertions, sensitivity analysis, and an Excel export your auditor already recognizes. No replatform. Excel stays the deliverable.

Flatland · index of everything
© 2026 Flatland · made for systems of record · live pulse · awaiting first compile