Pricing
Simple, flat pricing
No per-seat charges and no credit metering. Pick a plan by how long your jobs run and how many of them there are.
Free
Enough to build something real and find out if it fits.
- Runs
- 500 / month
- Max runtime
- 60 seconds
- Memory
- 512 MB
- Run history
- 7 days
Free stops at 500 runs a month. Upgrade to keep running past it.
- JavaScript and Python
- Any npm or pip package
- Editors and admins dry-run against real records; members get a synthetic preview
- 1 connected portal
- Community support
Pro
For teams running production automation.
- Runs
- 25,000 / month
- Max runtime
- 5 minutes
- Memory
- 1 GB
- Run history
- 30 days
Runs keep executing past 25,000 and are metered as overage. Set a spend cap to stop instead.
- Everything in Free
- 3 connected portals
- Secrets vault
- Bulk replay and failure alerts
- Version history and rollback
- Email support
Scale
Higher volume and longer jobs.
- Runs
- 150,000 / month
- Max runtime
- 12 minutes
- Memory
- 2 GB
- Run history
- 90 days
Runs keep executing past 150,000 and are metered as overage. Set a spend cap to stop instead.
- Everything in Pro
- Unlimited connected portals
- Priority execution queue
- Audit log
- Priority support
Need higher limits, a private deployment, or an invoice instead of a card? Get in touch.
FAQ
Pricing questions
What counts as a run?
One execution of one action. A workflow that enrolls 200 records and runs your action on each one uses 200 runs. Test runs from the editor are not counted against your quota.
What happens if I go over my run limit?
On a paid plan, actions keep executing and you get an email — we will not fail a workflow step mid-month over a quota. A broken automation is a much bigger problem for you than an overage is for us. Runs past your allowance are metered at $0.005 each, and you can set a spend cap if you would rather we stop. The free plan is the exception: it stops at 500 runs a month, because there is no card on file to meter against. Upgrade to keep running past it.
Can anything stop my workflows for billing reasons?
On a paid plan, only a spend cap you asked for. Set one and runs stop at it until you raise it or the month rolls over; nothing else about your plan stops a run. The free plan stops at its 500-run allowance instead, since there is nothing to meter against. We also run automatic protection limits against abuse and runaway loops, but those sit far above every plan allowance, they are not billing, and if one ever trips we tell you it is a protection limit and not a plan limit.
Why are runtime and memory part of the plan?
Because they are what actually costs money to provide. A 15-second action costs roughly fifteen times what a 1-second action does. Pricing on run count alone would leave that unpriced and push the price up for everyone. Tying the ceiling to the plan keeps the cheap plans cheap.
Is pricing per seat?
No. Plans are per workspace and cover your whole team. Invite as many people as you like.
Do you charge credits per action, like HubSpot does?
No. Pricing is flat and the limits are published. You should be able to predict next month's bill from this page without modelling your volume against a credit table.
Can I change plans later?
Yes, in either direction, at any time. Changes are prorated.
Ready when you are
Start on the free tier
No card required. Move up only when your run volume or runtime needs it.