Prysm
// Module — Spreadsheets

A real formula engine, not a toy grid.

The spreadsheet inside PrysmOS runs on a genuine calculation engine: Excel-parity formulas across multi-tab workbooks, recalculated on the server and pushed to everyone watching, live. Fork a what-if scenario, trace any number back to the cell that made it, and never get paged for a stale sheet again.

Excel-parity
formula library
Realtime
recalc for every viewer
Sandboxed
what-if scenarios
CSV · XLSX
in & out, no lock-in
// How it works

From blank grid to answer in four moves

No import ritual, no connector spaghetti. In PrysmOS the grid is the engine.

01

Type a formula

Excel-parity syntax with autocomplete — VLOOKUP with approximate match, the STDEV family, SUMIFS. The semantics you already know, so the muscle memory transfers.

02

Recalc cascades

Change one cell and the engine recomputes every dependent — across every tab in the workbook — then pushes the result to your collaborators in realtime.

03

Fork a scenario

Spin up a sandboxed what-if copy of the grid, flip your assumptions, and compare outcomes side by side. The real numbers never move.

04

Decide together

Threaded cell comments with @mentions and per-cell blame mean the argument happens next to the numbers — and the audit trail writes itself.

// Feature grid

Everything a spreadsheet should do, plus the parts they skip

The familiar surface is the point. The engine underneath is the difference.

Excel-parity formulas

A real calculation engine, not a lookalike — lookups, stats, financial, engineering, and text functions that behave the way your models expect.

Multi-tab workbooks, live recalc

Edit an input on Sheet1 and watch totals update on Sheet4 — recomputed server-side and pushed to every collaborator in realtime, even with the tab closed.

What-if scenarios

Sandboxed forks of the whole grid. Change assumptions freely, compare against base, merge the winner — or discard it and forget it happened.

Pivots & 16 chart types

Pivot a range in place, or chart it — sixteen chart types with recommendations that pick the right shape for the data, so the first pass takes seconds.

Formatting that signals

Conditional formatting flags the outliers before anyone asks; full cell styles, fonts, borders, and number formats keep the board readable.

Validation, named ranges, autofilters

Dropdowns and input rules keep data clean at the source, named ranges make formulas readable, and autofilters let anyone slice the table without breaking it.

Freeze panes, merges, outline groups

Lock headers in place, merge the cells that need merging, and collapse detail rows into outline groups — the structural stuff big sheets need.

Sheet protection

Lock a finished model so the next person can't fat-finger the assumptions. Protect whole sheets when the numbers are final.

Threaded cell comments

Conversations stay attached to the exact cell they're about — threaded, with @mentions that pull the right person in.

Version history & per-cell blame

Every change is recorded down to the cell. See who changed what and when, diff versions, and roll anything back in one click.

Multiplayer by default

Live presence shows who's in which cell while you work — no refresh, no conflicts, no version_final_v3.xlsx in the shared drive.

CSV · XLSX, in and out

Drag files in, export them back out. Your data stays portable — import from anywhere, leave whenever you want.

// See it work

Edit a cell. Watch the cascade ripple.

This is a live sketch of the real thing in PrysmOS: change an input and every dependent formula recalculates on the server — while two teammates watch from inside the same grid.

Q3-forecast.grid
MODR 2 online
fx=SUM(D1:D4)
A
B
C
D
E
1
Q1
120
×1.2
144
units
2
Q2
140
×1.2
168
units
3
Q3
98
×1.2
117.6
units
4
Q4
176
×1.2
211.2
units
5
Total
534
—
640.8
avg 160.2
Sheet1 · Sheet2 · Scenarioslive recalc on
Scenario fork
base-planD5 = 5,316
fork
what-if: churn +20%D5 = 4,652
what-if: price +8%D5 = 5,741

Scenarios are sandboxed forks of the whole grid. Compare, merge the winner, or throw it away — the base plan is untouched either way.

  • Presence: see who's in which cell, live
  • Threaded cell comments with @mentions
  • Per-cell blame plus full version history
  • Pivots, autofilters & named ranges on demand
an excel-parity librarymath · stats · text · logical · lookup · dates · financial · engineering · units · web
=SUM(=PRODUCT(=AVERAGE(=MEDIAN(=MODE.SNGL(=STDEV.P(=STDEV.S(=VAR.P(=VAR.S(=VLOOKUP(=HLOOKUP(=INDEX(=MATCH(=SUMIFS(=COUNTIFS(=AVERAGEIFS(=IF(=IFS(=AND(=OR(=SUM(=PRODUCT(=AVERAGE(=MEDIAN(=MODE.SNGL(=STDEV.P(=STDEV.S(=VAR.P(=VAR.S(=VLOOKUP(=HLOOKUP(=INDEX(=MATCH(=SUMIFS(=COUNTIFS(=AVERAGEIFS(=IF(=IFS(=AND(=OR(
=CONCAT(=TEXTJOIN(=LEFT(=RIGHT(=MID(=TRIM(=LEN(=DATE(=EDATE(=DATEDIF(=TODAY(=NOW(=NPV(=IRR(=PMT(=FV(=CONVERT(=HYPERLINK(=NOT(=ROUND(=CONCAT(=TEXTJOIN(=LEFT(=RIGHT(=MID(=TRIM(=LEN(=DATE(=EDATE(=DATEDIF(=TODAY(=NOW(=NPV(=IRR(=PMT(=FV(=CONVERT(=HYPERLINK(=NOT(=ROUND(
// In the wild

Where the grid earns its keep

Finance

Revenue forecast, with scenarios

Model next quarter in the grid, then fork three scenarios — conservative, expected, aggressive — and put all three on screen in the same meeting. Merge the one reality picks.

Ops

Inventory reconciliation

Pull the warehouse export next to the ERP extract, VLOOKUP the SKU lists, let conditional formatting flag the mismatches, dedupe, done. Twenty minutes, not a weekend.

Teams

The ops tracker

A shared grid the whole team updates live: owners, statuses, validation dropdowns, comments for context — and a cell-level audit trail when someone asks who changed what.

// Questions

Fine print, answered

Yes — it's Excel-parity, not a lookalike: SUM, VLOOKUP with approximate match, the STDEV and VAR families, INDEX/MATCH, and the financial, engineering, text, and date functions your models already rely on — across multi-tab workbooks.

// One workspace

Stop fighting toy grids.

Excel-parity formulas, recalc pushed to everyone in realtime, and what-if scenarios that can't break the base plan. Free to start — bring your ugliest CSV.