a run is a workflow run. The demo video i recorded for example would be 1 run.

This way of measuring things is kind of falling apart because people can nest automations and loop them to run many times on many values. One 'run' of a heavily nested automation could actually lead to hundreds of runs do to nesting.

My co-founder and I have debated this at length and the only way we see to solve this is to add a credit based system and stop caring about runs altogether. Each node would have a credit cost and each plan would have monthly credit alotment. If you can think of a better way we're very open to suggestions!