Version 3.0
The headless spreadsheet runtime.
Flow executes compiled workbooks as workflows and APIs on parallel workers, with validation before every run and provenance on every output cell. Deploy in GSH's cloud or inside your own tenancy.
What a workflow gets from Flow
Parallel execution
A workflow is steps of processes that run side by side; per-row and per-group directives fan a spreadsheet out across workers and stack the results.
Validation first
Fail, warn, unique, identical-columns and the rest run before a number is produced. Bad inputs are rejected with the directive that caught them.
Provenance
Every submitted input and every output of every spreadsheet is stored with the request. Trace any output cell back to the rows that produced it.
Connectors
HTTP, SQL, files, queues and email as directives, with credentials sealed on the server. Start with the Data Service and FRED, add your own systems.
Templating extraction
New in 3.0: pull data from human-oriented, non-rectangular worksheets by template, and pull report formats back into Zen.
Your tenancy or ours
Container app deployments, telemetry export to CSV, styling palettes stored on the server, and early worksheet downloads while a run is in progress.
From Zen to Flow in one step
A workbook that validates in Zen runs in Flow unchanged. Zen connects to your Flow server automatically once you have an account on it, so modelers submit from Excel and operators run from the workflow builder.
- Model and validate in Excel with Zen
- Assemble spreadsheets into a workflow in Flow's builder and test it
- Run on demand, on a schedule, or from your systems through the REST API
Ready to run your models in the cloud?
Flow is offered on the Modeler, Studio and Enterprise plans. Enterprise runs in your own tenancy.