pricing and executions
Can someone please explain/clarify the pricing model?
7000 executions in the starter tier , is that for the month or per hour? #pricing
7000 executions in the starter tier , is that for the month or per hour? #pricing
GHi @tmez , you can check this FAQ to learn more about how execution works per hour - https://buildship.com/pricing#faq1-workflow-executions.
Pthe pricing page is delusional... you don't get 7000 executions but 10h hours of processing time per month. you can buy additional hours per month ($1 = 1h). The thing with the "7000" is based on an assumed execution time of 4 seconds per workflow execution. My workflows currently range between 20 and 90 seconds. far away from 4 seconds and far away from 7000 executions (~654 executions = (20+90)/2).
you could actually create a script with buildship to log your executions, calculate the average, and show your milage (similar as in speedometers: 8.7L/100km)...
you could actually create a script with buildship to log your executions, calculate the average, and show your milage (similar as in speedometers: 8.7L/100km)...
Pyou can review how much gas is still in the tank here:
https://buildship.app/p/<your instance>/settings/plan
or you just manually navigate there via the web interface.
https://buildship.app/p/<your instance>/settings/plan
or you just manually navigate there via the web interface.
Visually build workflows and powerful backend logic for your apps. Powered by AI, connect to anything with or without code.
Pbtw: can someone tell me what "overused hours" means?
Phere is where the speedometer idea could be shown to the user if implemented by the buildship team
BThe "overused hours" is only displayed if you've overused your subscription and addon packs. It's an issue on our end, will fix it.
PThanks! But I still don't understand it. In my case, I used 2.6 hours, have 7.4 left and 1.83 overused...? Do I have 0 overused in reality?