5 ms·

Given the name, and premise of creating flows of python scripts ... is this intended to make people think of Airflow? A lot of what we see in the demo video (on

by abeppu 5y ago

Given the name, and premise of creating flows of python scripts ... is this intended to make people think of Airflow? A lot of what we see in the demo video (on a scheduled basis run a sequence of steps which gather data, produce some summary statistics, share it to slack, parameters which can be defined when a run is triggered or from prior steps, etc etc) is very familiar to users of existing workflow systems. The UI to create/author flows seems slick, but I also think that for important flows, teams will want to be able to review changes to flows, make cross-cutting updates to several flows when a popular script or connector is updated, etc, in which case being able to view/edit/diff flows as code is quite valuable.

rubenfiszel 5y ago
Demo is a bit old (2 months ago), I need to reshoot it. It has some resemblances with Airflow but one aim is to make it accessible to less technical users that can treat modules like blackbox. Similar to Zapier but the code is inspectable and editable at any point. At the core, it is a scheduler/orchestrator of script execution, so it's similar to Airflow in that sense, but the product is really not meant for the same usage. I picked the name a bit randomly because it is retro and one of the first automation humans have created. I did not think too much about it but now I love it :)