Every plan includes the complete workflow platform. Pricing is based on monthly completed workflow executions, regardless of complexity.
For trying a real workflow
No card required. Build and run before you buy.
Trial includes:
For solo builders
Full platform, single seat. You build the workflows.
Less than one client engagement rebuild.
Everything in the trial, plus:
For teams building together
Everything in Starter, with seats for the whole team.
Everything in Starter, plus:
Platform plus hands-on help
Everything in Growth, plus four engineering hours directed by you each month.
Everything in Growth, plus:
Packaged solutions
Fixed-scope solutions have their own pricing and implementation details.
Plan comparison
Compare capacity, AI, developer tooling, observability, package delivery, and support. A run is one completed workflow, not every step inside it.
| Feature | Trial | Starter | Growth | Professional | Enterprise |
|---|---|---|---|---|---|
| CapacityMonthly allowances. QuickFlo counts completed workflows, not every node they run. | |||||
| 20 | 10k | 250k | 500k | Custom | |
| Workflows | 10 | 2,000 | 2,000 | 2,000 | Custom |
| Steps per workflow | 5 | 50 | 75 | 100 | Custom |
| Scheduled triggers | 1 | 10 | 25 | 50 | Custom |
| 100 | 25k | 150k | 500k | Custom | |
| Trial use | 1M+/mo | 5M+/mo | 20M+/mo | Custom | |
| 1 MB | 1 GB | 5 GB | 10 GB | Custom | |
| 5 | 50 | 100 | 200 | Custom | |
| Users | 1 | 1 | 10 | 25 | Custom |
| Workflow executionQueue-backed execution limits for each organization—not a shared-project limit. | |||||
| 5 | 10 | 15 | 15 | 15 | |
| 5/sec | 20/sec | 30/sec | 50/sec | 200/sec | |
| ✓ | ✓ | ✓ | ✓ | ✓ | |
| ✓ | ✓ | ✓ | ✓ | ✓ | |
| ✓ | ✓ | ✓ | ✓ | ✓ | |
| Build with Flo AIBuild workflows, dashboards, and analytics by describing the result you need. | |||||
| Flo AI workflow builder | ✓ | ✓ | ✓ | ✓ | ✓ |
| Flo AI dashboard builder | ✓ | ✓ | ✓ | ✓ | ✓ |
| ✓ | ✓ | ✓ | ✓ | ✓ | |
| 12 | 40 | 100 | 250 | 500 | |
| Workflow buildingThe same workflow engine is available on every plan; capacity changes as you grow. | |||||
| Visual workflow editor | ✓ | ✓ | ✓ | ✓ | ✓ |
| ✓ | ✓ | ✓ | ✓ | ✓ | |
| ✓ | ✓ | ✓ | ✓ | ✓ | |
| Speech-to-text and text-to-speech | ✓ | ✓ | ✓ | ✓ | ✓ |
| ✓ | ✓ | ✓ | ✓ | ✓ | |
| Data operationsShape large operational datasets inside the workflow instead of handing them off to another tool. | |||||
| Merge, join, diff, and enrich datasets | ✓ | ✓ | ✓ | ✓ | ✓ |
| Map, filter, sort, group, and reduce | ✓ | ✓ | ✓ | ✓ | ✓ |
| Scrub, deduplicate, classify, and reshape records | ✓ | ✓ | ✓ | ✓ | ✓ |
| CSV parsing, transforms, and streamed file output | ✓ | ✓ | ✓ | ✓ | ✓ |
| ✓ | ✓ | ✓ | ✓ | ✓ | |
| ✓ | ✓ | ✓ | ✓ | ✓ | |
| Data, connections, and environmentsKeep operational data and credentials beside the workflows that use them. | |||||
| Data stores and dashboards | ✓ | ✓ | ✓ | ✓ | ✓ |
| ✓ | ✓ | ✓ | ✓ | ✓ | |
| ✓ | ✓ | ✓ | ✓ | ✓ | |
| ✓ | ✓ | ✓ | ✓ | ✓ | |
| ✓ | ✓ | ✓ | ✓ | ✓ | |
| — | — | ✓ | ✓ | ✓ | |
| Developer toolsWork in the UI or control QuickFlo directly from your terminal and coding agent. | |||||
| ✓ | ✓ | ✓ | ✓ | ✓ | |
| ✓ | ✓ | ✓ | ✓ | ✓ | |
| API and webhook access | ✓ | ✓ | ✓ | ✓ | ✓ |
| ✓ | ✓ | ✓ | ✓ | ✓ | |
| InsightsBuild live operational views and see exactly what happened when a workflow ran. | |||||
| Live operational dashboards | ✓ | ✓ | ✓ | ✓ | ✓ |
| Flo AI analytics assistant | ✓ | ✓ | ✓ | ✓ | ✓ |
| Dashboard PDF export | ✓ | ✓ | ✓ | ✓ | ✓ |
| Dashboard and execution CSV export | ✓ | ✓ | ✓ | ✓ | ✓ |
| ✓ | ✓ | ✓ | ✓ | ✓ | |
| Inputs, outputs, duration, and failure details | ✓ | ✓ | ✓ | ✓ | ✓ |
| Execution search and filters | ✓ | ✓ | ✓ | ✓ | ✓ |
| ✓ | ✓ | ✓ | ✓ | ✓ | |
| ✓ | ✓ | ✓ | ✓ | ✓ | |
| SecurityCredentials and customer data stay scoped to the organization and environment that owns them. | |||||
| Encrypted connections and environment secrets | ✓ | ✓ | ✓ | ✓ | ✓ |
| Encryption in transit and at rest | ✓ | ✓ | ✓ | ✓ | ✓ |
| Separate credentials for each client install | ✓ | ✓ | ✓ | ✓ | ✓ |
| Permission-scoped access tokens | ✓ | ✓ | ✓ | ✓ | ✓ |
| Permission controls for secrets and sensitive logs | ✓ | ✓ | ✓ | ✓ | ✓ |
| ScalingChoose the worker pool that matches the memory and compute required by each workflow. | |||||
| Standard worker pool | ✓ | ✓ | ✓ | ✓ | ✓ |
| ✓ | ✓ | ✓ | ✓ | ✓ | |
| Concurrent medium executions | 1 | 1 | 3 | 5 | Custom |
| — | — | — | ✓ | ✓ | |
| Concurrent heavy executions | — | — | — | 1 | 3 |
| Workflows assigned to heavy workers | — | — | — | 3 | 10 |
| — | — | — | ✓ | ✓ | |
| Concurrent XL executions | — | — | — | 1 | 1 |
| Packages and client deliveryBundle workflows, triggers, data stores, connections, and environments into reusable solutions. | |||||
| Private packages for your organization | ✓ | ✓ | ✓ | ✓ | ✓ |
| Install public marketplace packages | ✓ | ✓ | ✓ | ✓ | ✓ |
| Publish public marketplace packages | — | ✓ | ✓ | ✓ | ✓ |
| — | — | ✓ | ✓ | ✓ | |
| Install shared and unlisted packages | — | — | ✓ | ✓ | ✓ |
| CollaborationBring in teammates, share the right resources, and operate QuickFlo across customer organizations. | |||||
| Shared workflows and dashboards | — | — | ✓ | ✓ | ✓ |
| Role-based access for builders and viewers | — | — | ✓ | ✓ | ✓ |
| Cross-organization data sharing | — | — | ✓ | ✓ | ✓ |
| Unlisted client package delivery | — | — | ✓ | ✓ | ✓ |
| — | — | On request | On request | On request | |
| BillingTrack what you use and what you owe without translating steps into tasks or operations. | |||||
| ✓ | ✓ | ✓ | ✓ | ✓ | |
| Live usage meters | ✓ | ✓ | ✓ | ✓ | ✓ |
| Self-serve plan changes | ✓ | ✓ | ✓ | ✓ | — |
| Downloadable invoices and receipts | — | ✓ | ✓ | ✓ | Direct invoice |
| — | ✓ | ✓ | ✓ | Custom | |
| SupportGet answers by email or work directly with the team on implementation. | |||||
| Email support | — | ✓ | ✓ | ✓ | ✓ |
| Direct Slack support | — | — | — | ✓ | ✓ |
| Customer-directed engineering | — | — | — | 4 hours/mo | Custom |
Scroll sideways to compare every plan →
For consultants & implementation firms
Join our partner network and grow your consulting business. Refer customers to QuickFlo, implement their workflows, and earn recurring commissions while focusing on high-value services.
For 12 months on every customer you refer
The no-card trial includes 20 completed executions per month, 10 workflows with up to 5 steps each, 1 scheduled trigger, and every step type—including code steps. It is meant to prove a real workflow before you choose a paid plan.
Each time a workflow runs from its trigger through completion, that is one execution. The number of steps, branches, loops, data operations, or records processed inside the workflow does not multiply the charge. A complex workflow is still one completed execution, not a bill for every node it touched.
Count how often each workflow starts. A daily schedule is roughly 30 executions a month. A schedule that runs every five minutes is roughly 8,640. For webhook and event workflows, estimate how many incoming events you handle. If you are migrating, use the run count from your current platform—not its task or operation count.
Paid plans keep production workflows running instead of stopping them at the allowance. QuickFlo records the additional usage and bills it at $5 per 1,000 standard-run equivalents. If the higher volume is consistent, moving to the next plan is usually simpler and more economical.
Your workspace has live usage meters for executions and the other plan allowances. You can also search executions and logs across the organization, so the number is backed by the actual runs and traces rather than a surprise at invoice time.
An AI builder message is one instruction or follow-up you send to Flo while building a workflow, dashboard, or analysis. The allowance resets monthly. These messages are separate from workflow executions and from AI model steps that run inside your workflows.
Data-store rows are your live operational working set: records workflows create, update, look up, and reuse. Dashboard analytics records are high-volume history such as call logs or activity events. With a ship-through dashboard source, you write them through the same data-store steps; they remain available to dashboards and analytics queries after they leave the live row allowance.
Every execution includes a step-by-step trace with inputs, outputs, timing, retries, and failure details. The current hosted retention window is 30 days, giving you searchable history for debugging and audit work instead of leaving you to guess why a run failed.
Starter and Growth include email support. Professional adds direct Slack and email access to the QuickFlo team plus four customer-directed engineering hours each month. Enterprise support and response requirements are scoped with the plan.
They are four hours each month for work directed by you: a new build, a fix, implementation help, or guidance. You choose the priority. They are not a generic onboarding call or a hidden setup fee.
Yes. You can upgrade, downgrade, or cancel without a long-term contract. Plan changes are handled through the billing portal; contact us when the change involves custom Enterprise capacity.
Book a quick call. We'll figure out the best fit for your business together.