Thanks! We've put a ton of effort into the look and feel. Two of our biggest power users are founders building their apps on top of AgentHub. One is doing mass data extraction from documents for research institutions in Australia.
The other built a cascading prompt engineering pipeline that iteratively tries to improve on it's output in a series of nested steps. They're the ones hitting 5k runs per day because they've nested their automations so many layers deep.
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!
Each node in our backend has a cost associated with it that we defined on a 0-100 scale. Our plan is to aggregate those at the end of a run to determine it's cost. Tying that cost to some actual metric like CPU usage could be a great idea though.
Runs are basically dynamically generated scripts. Our backend parses the automation definition from the DAG on the frontend, fetches the definitions of each node and stitches it all together to run in a sandbox env. It started off quite simple in the early days but it's become quite an monstrous system with dynamic variables, nesting, looping, credential access and error handling.
That's how it goes! If you're not already doing it, you're going to want to eventually make sure every Run is done independently. Parallel runs between multiple clients isn't going to fly as your load picks up.
The other built a cascading prompt engineering pipeline that iteratively tries to improve on it's output in a series of nested steps. They're the ones hitting 5k runs per day because they've nested their automations so many layers deep.