Sheet-Native Computing Foundation

A new word in infrastructure

The SNCF is the vendor-neutral home for Sheet-Native Computing — the practice of building resilient, reconciling systems on top of the spreadsheet. Cloud-native was the previous paradigm. It reconciled. Now it's a cell's turn.

Join the movement →

For a decade the industry told you the future was cloud-native: microservices, containers, and a control plane that needs a control plane. We propose the next epoch — Sheet-Native Computing — in which the substrate is not a cluster but a workbook, state is not a database but a range, and the reconciliation loop runs on a trigger every minute, forever, because the spreadsheet is eternal.

What is Sheet-Native Computing?

A discipline defined by five principles. Systems that satisfy all five are SNCF-conformant and may display the badge (self-issued, self-audited).

1. The Sheet is the source of truth

Desired and observed state live in cells. If it isn't in the Sheet, it isn't real.

2. Reconciliation over instruction

You declare rows; the loop makes reality match. You do not tell it how. It reconciles.

3. Legibility for all

Any human who can read a spreadsheet can read the system. Ops is no longer a priesthood.

4. Zero-infrastructure control plane

The plane is hosted by someone else's spreadsheet service. You operate nothing.

5. Time travel by default

Revision history is your backup, your audit log, and your disaster recovery.

Maturity levels

SNCF projects advance through three tiers — the natural lifecycle of any spreadsheet. Projects that stop reconciling fall out the bottom.

📝 Unsaved Draft

early

An experiment in a cell. No stability promised; may vanish on refresh. All projects start here, full of hope and #REF! errors.

💾 Autosaving

mid

Proven enough that Google keeps saving it. Real adopters, a maintainer, and a reconcile loop that mostly holds.

🏛️ Load-Bearing

mature

Mission-critical. An entire company secretly depends on this tab. Deleting it is a resignation letter. The highest honor the SNCF confers.

Promotion rules

Advancement is decided by the Technical Oversight Cell (TOC). Criteria are exacting, self-defined, and reconcile eventually.

Unsaved Draft → Autosaving

  • ≥ 2 believers actually using it.
  • A README and a maintainer who answers issues within one heat-death of the universe.
  • Survives one full reconcile loop without emitting a #REF!.
  • Sponsored by at least one existing SNCF project.

Autosaving → Load-Bearing

  • ≥ 3 independent adopters running it "in production" (proof: they filmed it).
  • A documented disaster-recovery story (i.e. "we pressed Ctrl+Z").
  • A SECURITY.md cell and no single formula longer than its visible column.
  • Two maintainers from different tabs.
  • Majority vote of the TOC.

Any tier → Archived #REF!

  • No maintainer response within a heat-death, or the source tab was deleted.
  • Marked #REF! and moved to the archive workbook.
  • Reinstatement requires a new believer and a fresh reconcile.

Landscape

The SNCF hosts projects across the three tiers. Like other landscapes, it is large, confusing, and mostly one thing. See the full SNCF Landscape →

Sheeternetes

🏛️ Load-Bearing

Spreadsheet-native container orchestration. The flagship. Reconciles.

CSFE Registry

🏛️ Load-Bearing

The verifiable credential registry for certified engineers.

Sheetlium

💾 Autosaving

Service discovery & load balancing over a shared network. Services, natively.

Sheetlux CD

💾 Autosaving

GitOps for the Sheet: sync a directory of manifests into desired state.

skctl

💾 Autosaving

The command-line client. kubectl muscle memory, spreadsheet backend.

SheetOS

📝 Unsaved Draft

Talos for spreadsheets: a minimal, API-only, declarative node OS whose single job is to bootstrap and run Sheeternetes. Distributable across many sheets. A moonshot.

The Foundation, by the numbers

1
graduated orchestrator
$0
annual infrastructure spend
∞
projected uptime (heat death)
0
enterprises in production (and counting)

Membership

The SNCF is wholly appointed, operated, funded, and accredited by itself. It is recognized by every organization that recognizes it, and holds ISO 9000.0.0.1 self-certification (self-issued, self-audited, pending).

Platinum

$0 / yr

You own a laptop. A seat on the Technical Oversight Cell.

Gold

$0 / yr

You have opened a spreadsheet this quarter. Logo on this page (conceptually).

Silver

$0 / yr

You believe. Unconditionally. That's the whole tier.

Get certified & join the registry →

Not affiliated with, endorsed by, or known to the CNCF, the Linux Foundation, any national railway, or any human being with hiring authority. All accreditation reconciles eventually.