Start with our flexible plans and scale as you grow
| Core Features | Starter | Professional | Enterprise |
|---|---|---|---|
| All integrations | |||
| Text to automation creation | |||
| Leading AI Code Generation | |||
| Bulk operations | |||
| Database creation and reading | |||
| Email triggers | |||
| Workflow History | |||
| Code Steps with AI code generation | |||
| Custom API Requests | |||
| Trigger from webhook | |||
| External storage in S3 | |||
| Execution logging | |||
| Error workflows | |||
| Debug editor | |||
| Concurrent executions | 5 | 20 | 200+ |
| Support | Discord | Dedicated with SLA | |
| Custom contract & invoice billing |
Executions are much more powerful than the 'operations' or 'tasks' that you're billed on in other products. An execution is a single run of your entire workflow. It doesn't matter how many steps are in the workflow or how much data it processes — it's still a single execution. This makes your usage more predictable than other tools where you pay individually for every step or task. Plus Agent UI workflows you can do things in a single execution that would take 10,000 operations in other tools.
Active workflows are ones that are turned on and running automatically (e.g. listening for events or polling a service). They're usually ones you've finished building and just want to let run. Test workflows aren't running automatically yet, perhaps because they're still being built or they were an experiment. They are triggered by clicking a button in Agent UI, rather than running automatically. Only active workflows count towards your plan limits.
Of course. Just log in to your admin panel and click 'Cancel subscription'.