100 Tasks Or 1,000 Operations? That Isn’t A Comparison
The card is clean and the promise is clear: twenty AI workflow automation tools, enterprise platforms on the red side, what you can start on for free on the green side. Two of the free entries carry a number. One says a free plan of 100 tasks a month. The next says a free plan of 1,000 operations. Almost everybody reads those two lines in sequence and concludes that the second one is ten times more generous.
It might be. It might also be less. The two numbers are not in the same unit, and the units do not convert.
That is the interesting thing about this particular card, and it is not a criticism of it — the card is more honest than most, because it prints the actual meter next to each free entry instead of just writing “free”. Read down the green column and you find five genuinely different arrangements hiding under one word. A task cap. An operation cap. A monthly credit allowance. A developer tier. And two tools that have no cap at all because you are expected to run them on your own server.
Work out which of those five you are signing up for and the choice gets much simpler. Skip that step and you will build something that works beautifully for three weeks and then stops on the eleventh of the month.
The five meters, and what runs each one down
| 1 · TASKS | 2 · OPERATIONS | 3 · CREDITS | 4 · DEVELOPER TIER | 5 · SELF-HOST |
|---|---|---|---|---|
| One successful run of one automation | Each individual step inside a run | A pooled allowance spent at different rates | A generous allowance aimed at people testing | No allowance at all |
| A busy trigger empties it fastest | A long workflow empties it fastest | An expensive action empties it fastest | Production traffic empties it fastest | Nothing empties it |
| Keep workflows few, let them be long | Keep workflows short, let there be many | Find out what each action costs first | Fine until the thing stops being a test | You pay in a server and in upkeep |
Why the same job costs wildly different amounts
Picture one small automation, the sort anyone running a channel actually builds. Somebody fills in a form. The automation checks whether the address is already in your list, looks up which video they came from, writes a row in a spreadsheet, and sends you a notification.
That is one job. On a plan that counts runs of an automation, it is one unit. On a plan that counts every step inside the run, the same job is four or five. On a plan that counts credits, the price depends on which of those steps you used — a lookup and a spreadsheet write rarely cost the same.
So a hundred of one unit and a thousand of another can easily land in the same place. The only honest way to compare two free plans is to write your workflow down as a list of steps, count them, and then read each vendor’s own definition of its unit. It takes ten minutes and it is the only part of this decision that is actually a decision.
The second thing that follows from this: the shape of your work decides the plan, not the size of the number. A few automations that each do a lot of steps are punished by an operation meter and suit a task meter. Many small automations that each fire constantly are punished by a task meter and suit an operation meter. Neither is generous or stingy. They are billing different behaviour.
All twenty, with the meter attached
Here is the card in full. The first two columns are its own words. The third is ours, and it is the column that actually decides anything.
| Column | Tool | What the card says | Which meter you are on |
|---|---|---|---|
| Free | Zapier | Free plan: 100 tasks a month | Task meter |
| Free | Make | Free plan: 1,000 operations | Operation meter |
| Free | Activepieces | Open-source, self-host it | Self-host (truly open-source) |
| Free | n8n Community | Open-source, run it yourself | Self-host (truly open-source) |
| Free | Gumloop | Free credits each month | Credit meter |
| Free | Pipedream | Free tier for developers | Developer tier |
| Free | Bardeen | Browser automation, 100 credits | Credit meter |
| Free | Dify | Self-host AI workflows | Self-host (source-available) |
| Free | Flowise | Visual AI flows, open-source | Self-host (source-available) |
| Free | Relevance AI | Free tier for agent teams | Free tier, unstated unit |
| Paid | Power Automate | Microsoft 365 workflows | Bundled with an ecosystem |
| Paid | Tray.ai | Enterprise integrations | Sales-led pricing |
| Paid | UiPath | Robotic process automation | Sales-led pricing |
| Paid | MuleSoft | Salesforce integration layer | Bundled with an ecosystem |
| Paid | Pega | Big-company process engine | Sales-led pricing |
| Paid | Nintex | Forms, docs & approvals | Sales-led pricing |
| Paid | Kissflow | Custom internal apps | Sales-led pricing |
| Paid | ServiceNow | IT and service workflows | Bundled with an ecosystem |
| Paid | Workato | Enterprise-grade automation | Sales-led pricing |
| Paid | Celigo | iPaaS for operations teams | Sales-led pricing |
WATCH THE ORIGINAL — 45 SECONDS
The full card with all twenty tools, the free plan limits printed next to each one, and the footnote at the bottom.
The footnote at the bottom of the card
In small text along the bottom edge, the card says something that most lists of this kind would never admit: only n8n and Activepieces are truly open-source. Eight words, and they reorganise the whole green column.
Here is why it matters. A free tier is a decision somebody at a company made, and they can make a different one next quarter. Every tool in that column with a meter on it — tasks, operations, credits, developer allowance — is free at the vendor’s discretion. That is not a warning, it is just what a free tier is. But two of the ten are a different kind of object. If you run the software yourself, nobody can change your allowance, because there is no allowance. Your cost is a small server and the hours you spend keeping it alive.
That trade is real in both directions, and most people underestimate the second half of it. Self-hosting an automation tool means you are now the person who notices when it stops. There is no status page and no support queue. If the automation that files your sponsorship emails dies quietly on a Sunday, you find out on Tuesday.
The useful rule is about consequence, not preference. Anything where a silent failure costs you money belongs on a hosted plan that will email you when it breaks. Anything where a silent failure costs you an afternoon is a perfectly good reason to self-host and stop worrying about meters.
| The shape of your work | The meter that suits it | What will bite you |
|---|---|---|
| A handful of automations, each with many steps | A task meter — you are billed once per run | An operation meter, which charges you per step |
| Many small automations firing all day | An operation meter or a self-host | A task meter, emptied by volume alone |
| Anything touching AI models or paid lookups | A credit meter, once you know the per-action price | Assuming all actions cost the same |
| Something you will still be running in a year | A self-host you control, or a paid plan | A free tier the vendor can reprice |
| Something where silent failure costs money | A hosted plan that alerts you | A self-host with nobody watching it |
Four honest caveats
The paid column is not a shopping list. Most of the red side — the RPA platforms, the integration layers, the enterprise process engines — is sold to organisations by a salesperson, deployed by a team, and priced on request. Putting them beside a consumer free plan makes them look like a purchase you could make this afternoon. They are not that, and for one person running a channel they are not the upgrade path either.
Open-source and self-hosted are not the same word. The card is right to separate them, and right that only two of the ten are truly open-source. Several of the others can be run on your own machine but sit under licences that restrict what you may do commercially. If that matters to you, read the licence rather than the marketing page.
One of these has already changed its mind once. When we re-checked a similar chart tool by tool, Bardeen had moved its focus toward sales data rather than general browser automation — one of four distinct ways a free entry quietly stops being the thing you saved. That whole post is The Paid Tools Are Fine. It Is the Free Column That Rots.
The numbers are dated, and the card says so. All twenty were marked as checked in September 2026. Free plan sizes and unit definitions are the single most volatile thing in this whole category — we found the failure rate on a sixty-tool chart in Sixty AI Tools, Thirteen Were Wrong.
What to actually do this week
Do not sign up for four of these to compare them. Write down the one automation you most want to stop doing by hand, as a numbered list of steps. Count the steps. Then open two pricing pages and read their definition of a task, an operation or a credit until you can say what your list costs on each. If the two answers are close, take whichever one you find easier to read.
And before you add a new subscription, check what you already pay for — half the automation people go shopping for is already sitting unused inside a tool they have. The method is in Stop Paying Twice: The Overlap Audit, and the habit of stacking free plans until they collapse is in The Zero-Budget Stack And The Free-Tier Treadmill.
One more, for anything that connects to accounts on your behalf: give it the narrowest permission that works, and widen it only when something fails for want of access. We argued that case in Read-Only First.
Questions people ask
Which free plan is biggest? Unanswerable as asked, and that is the point of this article. Biggest depends on whether your workflows are few and long or many and short. Count your steps first and the question answers itself.
Is self-hosting hard? Getting it running is an evening. Keeping it running is the real cost, and it is a cost you pay quietly and forever. Fine for a hobby workflow, risky for anything that touches money.
Can I split work across two free plans to stay under both caps? You can, and people do. It works until something breaks and you have to remember which half of the job lives where. One meter you understand beats two you are dodging.
Do I need any of this to run a channel? No. Automation pays off on the tasks you already do the same way every week — filing, notifying, logging. Automating something you have done twice is how a whole afternoon disappears into a tool instead of a video.
Count the steps, not the tools
Twenty logos is not a decision. The decision is one line long: what shape is the work, and which meter bills that shape kindly. The card does the unusually honest thing of printing the meters where you can see them, and then one small line at the bottom tells you that only two of the ten are outside anybody’s control. Both of those details are worth more than the other eighteen logos put together.
Learning a lot does not make anyone good. Doing a lot does.
If you want to be pushed into building one automation rather than reading about twenty, we run a free challenge — there is no barrier to entry, only a commitment fee that is refunded when you finish. It exists because a deadline ships things that a saved post never will.
Which meter are you actually on, and have you ever hit the wall mid-month? Tell us in the comments under the original reel.
More on building a channel for a global audience at mmoyoutube.com.




3 Comments