Pipedream's free tier is real, and its numbers are not in the page source

50 lands Pipedream in our Limited band and fifth in this category, and a meaningful part of that number is our uncertainty rather than Pipedream's stinginess. Generosity at 45 is scored conservatively on purpose, because we will not credit a free tier whose size we could not read at the source, and feature depth at 60 judges an unverified free scope rather than the platform, which for developers is deep.

Freedom at 45 is the pillar making a real criticism rather than an admission. The component registry is open source and inspectable, which is more than most hosted rivals offer, but the engine is proprietary with no self-hosting, and a free plan whose limits are not in the page source is a free plan you cannot budget around. That is the finding, and it is the reason the score sits where it does rather than higher.

The honest list here is short, and half of it is an admission (as of July 2026).

What we know:

• The free tier is metered in credits, and a credit maps to compute time (roughly 30 seconds at 256 MB) rather than to a step. Fast workflows cost less regardless of how many steps they contain, and slow ones cost more even if they are simple.
• The allowance is daily rather than monthly, so a heavy afternoon does not spend the month, and a permanently heavy workload cannot be smoothed across it either.
• Active workflows and connected accounts are both capped on free, at numbers we could not confirm.
• There is no self-hosting. The engine is proprietary, so your workflows run on Pipedream's infrastructure and nowhere else. Only the component registry is open source.

What we do not know, stated plainly rather than borrowed from a roundup: the credit figure, the workflow count, the connected account limit, what the paid tiers cost, and what happens when the daily allowance runs out. Open pipedream.com/pricing and read them there before you plan around any of it.

The credit model also carries a design consequence worth knowing: a workflow that waits on a slow third-party API spends more of your allowance than one that does real work quickly, which is the opposite of how per-step billing behaves.

The plan cards below carry no figures above the free tier, and that is deliberate. Our sourcing rule is that the vendor's own site wins for pricing and that we omit a number rather than repeat one from a third-party roundup. Pipedream's pricing page renders client-side, so there was nothing to record. We would rather leave a visible gap than publish a figure we cannot stand behind.

What we can describe is the shape of the ladder. Paid monthly tiers raise the credit allowance, the active workflow count and the number of connected accounts, and add operational headroom such as larger memory and longer execution limits. Those last two are the ones developers actually meet: a workflow that needs more memory or a longer run than the free tier allows is a hard stop rather than a slow month.

Set against the rest of this category, that opacity is the real cost of the free tier. Make tells you it is 1,000 operations. Zapier tells you it is 100 tasks. Activepieces tells you it is 10 flows. Pipedream tells you when you open a browser inspector, and for a tool aimed at developers, that is an odd place to hide the one number they would check first.

Yes, within limits, and that is one step above where a score of 50 would normally land. The departure is deliberate: the score is low largely because we could not verify the tier's size, not because we found it to be thin, and a free tier with a daily credit allowance and a handful of active workflows is a real free plan rather than a demonstration.

Who can live on it: a developer running a few small, fast workflows, someone who wants to write Node.js or Python inside an automation without standing up a server, anyone extending a connector in the open source component registry. Who cannot: anyone who needs to budget precisely, because the ceiling is not published anywhere you can read it; anyone running slow or long-polling workflows, because credits track compute time; and anyone who needs to own the infrastructure, because there is no self-hosting at any price.

If the code-first model appeals but the opacity does not, n8n's free plan gives you code steps on a server you own and Make's free plan publishes its numbers plainly. Free Pipedream alternatives covers the rest, and the best free automation tools ranks the category.