PlatformAnalyse
Calculations that run on their own, on time and on new data
A flow links functions in a graph, runs them when needed and writes the result to a managed table. You watch it run, recompute it over the past, and an administrator approves what it executes.
Scheduled · 0 6 * * 1 (Europe/Rome)
Source
Orders by area
Function
z_deviation
Table
Managed table
Illustrative example
From a calculation written to a calculation running
You decide when it runs
On a schedule, with a cron expression and a time zone; on every new piece of data; or only by hand with «Run now».
Replay: recompute the past
Replay redoes history from the data kept, one window at a time, when you change the logic and want the old data consistent.
Writes to managed tables
The platform writes the rows, only into the flow's own saved tables. Dashboards, notebooks and reports read them like any other data.
Approved and traced
A flow with project code starts only after an administrator approves it, and stops if you change it. Every run stays in the register.
From graph to run
- 01
Draw the graph
Start from the sources and add functions, from the catalogue or written by you. The graph shows which ones can connect.
- 02
Try it with the preview
The preview runs a sample and writes nothing. You see each node's rows before the flow starts.
- 03
Let it run
Pick the trigger and have the flow approved. Then follow the runs: status, duration, rows read and written.
In detail
- Triggers
- Schedule (cron and time zone), new data, manual.
- Preview
- Runs a sample of the inputs and writes no rows.
- Replay
- Redoes history one window at a time; needs the permission to edit queries.
- Output
- Tables managed by the platform, with declared keys and retention.
- Approval
- Needed for project code and for capabilities such as sending mail or using AI.
- Register
- Runs with status, duration, version, rows read and written.
Frequently asked questions
It stops again: the approval covers the flow as it is, and an administrator has to approve it again.
No. It writes only to its own managed tables. Sources stay read-only.
Yes, with Replay: pick the range and the flow redoes it one window at a time.
Bring us a question you can't answer today.
We start from a real question your business has and walk the path from source to dashboard with your systems, not a demo dataset.