Live example: a budget spreadsheet

Below is the same spreadsheet component you get in the delivery, with an ordinary budget: line items, quantities, prices, formulas, and shares. When the demo environment is up, you can use it right here: change a quantity or a price, and the row sums, “Total”, and “Due” recalculate on their own. The workbook opens in your own sandbox: only you see your edits, they’re never saved anywhere, and the next visitor gets the original budget.

The demo environment is down right now — the spreadsheet itself still works. Check back later, or write to us: we'll show it live, on your own workbooks.

Full screenopen in a new tab ↗A real workbook, not a snapshot: the core computes the formulas in the “Amount” and “Share” columns, not the page markup

What exactly is running here

The frame above isn’t a browser build. It’s set up the same way as shown in Runtime environments: the shell runs in the browser, and a separate core process on our side holds the workbook; a persistent connection sits between them. Every visitor gets their own process and their own copy of the workbook, so other people’s edits never reach you, and yours never reach anyone else.

That’s also where a visible trait comes from: recalculation isn’t instant, like a spreadsheet embedded in the page, but comes with network latency. That’s the cost of the scheme, not a trait of the core — in the desktop app and in the browser build, the same recalculation happens locally.

What’s worth trying

• Change a quantity in the “Qty” column — the row sum, the share, and both totals recalculate.
• Change the discount in B13 — only the “Due” row changes.
• Select cell D11 and look at the formula bar: it shows SUM, not a hardcoded number.

How this example differs from a production embedding

What	In this example	In your application
Who the user is	A guest: one identity for every visitor	Your signed-in user
Where the workbook comes from	The same demo file every time	Your file by ID
Where the edits go	Nowhere: the sandbox lives until it idles out, then it’s wiped	Into your storage, through your own API
Permissions	Not checked	You check them, including again while the session runs

Next

• Individual capabilities one at a time, each its own small project — SumSheet examples.
• Where the core computes in each environment — Runtime environments.
• What your side needs for embedding — Integrating into an application.