Formulon

English

日本語

English

日本語

Appearance

Scenarios ​

These pages show how Formulon fits into concrete workflows. Each scenario uses a different runtime or product — pick the one closest to your deployment, then read the matching Runtime page for setup details.

Start with a real workbook

After the one-formula quick start, test one representative workbook as early as possible. Spreadsheet engines fail or succeed on workbook details, not only on isolated formulas.

Where the workbook arrivesShared engineBrowser uploadWASM, file stays on the deviceUpload API / serviceNative Node or WASMScheduled job / notebookPythonPull requestCLI snapshots in CIAI agentformulon-mcp toolsSpreadsheet UI in a web appformulon-cell (beta)One C++17 coreload → mutate → recalc → saveWhere the workbook arrivesShared engineBrowser uploadWASM, file stays on the deviceUpload API / serviceNative Node or WASMScheduled job / notebookPythonPull requestCLI snapshots in CIAI agentformulon-mcp toolsSpreadsheet UI in a web appformulon-cell (beta)One C++17 coreload → mutate → recalc → save
Each scenario differs in where the bytes come from and go; the calculation is the same core.
ScenarioRuntimeGoal
Browser workbook uploadWASMRecalculate a user-uploaded .xlsx without sending it to a server
Node service recalculationNative Node / WASMRecalculate uploaded or internally generated workbooks behind an API
Python batch recalculationPythonRecalculate reports or models in jobs and notebooks
CI workbook regressionCLIDetect formula and value drift in automated checks
Agent workbook editingMCPLet AI agents open, edit, recalculate, and save .xlsx or .xlsb through formulon-mcp
Spreadsheet UI in a web appformulon-cell (WASM)Show and edit a workbook inside your own page; beta, evaluate before shipping to end users

What the scenarios share ​

Every scenario follows the same load → mutate → recalc → save lifecycle described in Workbook lifecycle. What changes between them is:

  • where the bytes come from (File, file system, IO stream, MCP tool input),
  • where the bytes go (save() result, written file, returned bytes field),
  • which runtime owns memory and IO,
  • how errors cross the host boundary.

Compatibility gate ​

Before adopting any scenario, inspect the workbook's formulas and decide how to handle external-service functions. Formulon has 511 real implementations among 526 recognized names, including the environment-bound CELL and INFO; the remaining 15 are deliberate unavailable service stubs such as COPILOT, PY, IMAGE, WEBSERVICE, STOCKHISTORY, RTD, and CUBE connection functions. Treat those as product decisions: reject the workbook, show a compatibility warning, or route it to an Excel-backed workflow.

For runtime-specific setup, see Runtimes. For the engine-side flow, see Workbook lifecycle.