Pipedream pricing explained: why the paid plan is built for shipping, not internal automation

Pipedream’s $99 Startup plan and Zapier’s $19.99 Professional plan look like they compete on price. They don’t, because each vendor bills a different unit. Pipedream’s Startup tier is $99 per month when billed annually, or $150 when billed monthly (Pipedream pricing). Zapier’s Professional tier is listed as “starting from” $19.99 per month, and the page does not state its billing basis (Zapier pricing). Neither headline tells you what your automations will cost. That depends on what each vendor meters and on who your automation serves. This post walks through those units, shows the arithmetic, and maps each plan to a buyer.

This analysis is based on the official pricing pages of Pipedream, Zapier, and Make (fetched 2026-10-23). We did not run these platforms hands-on for this post; all figures come from the vendors’ own published pricing pages, and the worked arithmetic is our own.

What Pipedream’s paid tier actually sells

Pipedream’s free plan costs $0 and needs no credit card, but it is labeled “Development only” (Pipedream pricing). The page says the free plan gives you full API, SDK, and MCP access to build and test. It does not include a production environment. External users and usage credits are also development-only on that plan.

The Startup row is headlined “Ship your integrations and agents to production.” It includes a production environment, 100 external users, 10,000 usage credits, and email support. After the included amounts, the page lists $2 per external user and $0.012 per credit (Pipedream pricing). The page makes the boundary explicit: “Serving real external users in production requires Startup.”

The pricing page defines an external user as “each distinct user of your app who connects at least one account through Connect, identified by the external user ID you pass” (Pipedream FAQ). That definition is the key to the whole tier. The $99 buys a production serving layer for people who connect accounts to an application you build. It does not buy a seat for one operator who wants to run their own inbox, CRM, and spreadsheet automations. If that describes you, you are paying for serving capacity you will not use.

The page’s customer logos point the same way. They include Alibaba, Apollo.io, Lindy, Perplexity, Relevance AI, Sana, Viktor, Wordware, and Workday (Pipedream pricing). These are product companies, and the page is written for people shipping software.

The credit math, worked out

The FAQ defines a credit as 1 credit per 30 seconds of compute for running an action, calling a tool through MCP, sending a request through the Connect proxy, or emitting an event from a deployed trigger. Listing apps and accounts and other management calls use no credits (Pipedream FAQ).

Here is the calculation from the page’s own numbers (Pipedream pricing). This is our calculation, not a figure Pipedream publishes:

Included credits: 10,000
Seconds per credit: 30
Compute-seconds: 10,000 × 30 = 300,000
Compute-hours: 300,000 ÷ 3,600 ≈ 83.3 hours per month

Treat 83.3 hours as an illustration, not a guarantee. It assumes every credit is a full 30-second unit. Actual usage depends on how your actions are sized.

Overage is the second half of the math. The page lists $0.012 per credit beyond the included 10,000 (Pipedream pricing). Our calculation, with page numbers as inputs: 15,000 credits in a month means 5,000 extra credits × $0.012 = $60 on top of the $99 annual price, for $159 per month.

External users add a separate meter. Our calculation: 250 external users means 150 beyond the 100 included × $2 = $300 extra per month, on top of the base price (Pipedream pricing). A product with a few hundred users can outgrow its credit allowance and its user allowance in different ways.

One gap matters for budgeting. The pricing page does not say whether an action that finishes in under 30 seconds rounds up to a full credit. We treat that as unverified. If it rounds up, your credit count will run higher than your compute time suggests, and the 83.3-hour figure will overstate what you can run. Confirm this with Pipedream before you budget.

Why the unit matters more than the price

Each vendor meters a different thing, and the cheap option depends on your workflow shape.

Pipedream charges per 30 seconds of compute and per external user. A 90-second action is 3 credits at the stated unit (our calculation from Pipedream pricing). Credits accrue for actions, MCP calls, proxy requests and deployed-trigger events alike (Pipedream FAQ).
Zapier states that “AI steps, code, and SDK now all follow the same task-based pricing model” (Zapier pricing). Task tiers run from 100 tasks per month up to 2M tasks per month on the pricing page’s selector. Per-task rates are listed separately at Zapier rates, so check that page before comparing a workflow’s step count to a tier. Yearly billing is labeled “Save 33%” on the pricing page (Zapier pricing).
Make bills in credits. Its FAQ says “most actions consume 1 credit, while some advanced features leveraging Make’s AI Provider may use more.” Router and error-handler modules consume no credits. The free plan includes 1,000 credits per month, and extra credits come in bundles of 1,000 or 10,000 (Make pricing).

Make’s model shows how unit choice changes the answer. Our calculation, assuming a 20-action scenario that consumes 1 credit per action: 1,000 free credits ÷ 20 actions per run = 50 runs per month before any paid credits are needed (Make pricing). Router and error-handler modules consume no credits, so scenarios that include them fit more than 50 runs; AI-provider features that use more than 1 credit would fit fewer. The same 20-step, 50-run workload is 1,000 actions a month, which exceeds the 100 tasks included on Zapier’s Free plan (Zapier pricing). On Pipedream, that workload is metered by compute seconds, not action count.

Make’s credits also carry rules. Credits expire at the end of the term, and extra credits expire after one month on monthly plans or at year-end on annual Pro and Teams plans. The allowance includes 5 GB of data transfer and 10 MB of data storage per 10,000 credits (Make pricing). Read those terms before you rely on rollover.

This post does not quote Make’s tier prices; check the Make pricing page before comparing totals.

So, is Pipedream a cheaper Zapier? The honest answer

For a solo operator running their own automations, no. Pipedream’s free plan is development-only, and the paid tier prices production serving and external users, which you do not have. You would pay for a product-shipping layer to run internal workflows. For shared internal automation with several people, Zapier’s Team plan, starting at $69 per month with 25 users, is the closer no-code comparison (Zapier pricing).

The comparison inverts if you are shipping an integration or agent to other people’s users. Then the $99 Startup tier is the right category, and the decision turns on two meters: your external user count against the 100 included, and your credit volume against the 10,000 included (Pipedream pricing). The credit math above tells you where the overage starts.

Who should buy which row

Internal-automation operator (you run workflows for your own business): Zapier or Make paid tiers fit this profile, with Make’s Start-up Plan for organizations under 20 employees at 50% off Business (Make pricing). Pipedream’s free plan is for building and testing, not for production use (Pipedream pricing).
Builder shipping an integration or agent to external users: Pipedream Startup at $99 per month billed annually, or $150 billed monthly (Pipedream pricing). Model your cost against the $2 per external user and $0.012 per credit overages before you commit (Pipedream FAQ).
Enterprise or compliance needs: Pipedream Business is a custom annual contract that adds SSO, SCIM, HIPAA, dedicated static egress IPs, and SLAs (Pipedream pricing). Zapier’s Enterprise tier is “contact sales” (Zapier pricing).

FAQ

How many Pipedream credits do I get for $99 a month?

The Startup plan includes 10,000 usage credits (Pipedream pricing). Our calculation from the page’s 30-second credit definition is about 83.3 compute-hours per month (10,000 × 30 s ÷ 3,600), assuming every credit is a full unit (Pipedream FAQ). Beyond 10,000 credits, the page lists $0.012 per credit (Pipedream pricing).

Does Pipedream have a free plan for automations?

Yes, but it is labeled “Development only.” The free plan is $0 with no credit card, and it has no production environment. External users and usage credits are also development-only on that plan (Pipedream pricing). If your automation must run for real users in production, the page says that requires Startup.

Do Pipedream credits round up short actions?

Unknown. The Pipedream FAQ defines credits per 30 seconds of compute but does not say whether an action under 30 seconds rounds up to a full credit. Confirm this with Pipedream before you budget, especially if your workflows include many short steps.

Takeaway

Compare automation platforms by billing unit and by who your users are, not by headline price. Pipedream’s $99 Startup plan is a product-shipping tier: it prices production serving, external users, and compute seconds, so it suits a builder who ships to others and rarely suits an operator running internal workflows. Zapier prices tasks, and Make prices credits per action, so the cheapest choice depends on how your workflows are shaped (Zapier pricing; Make pricing). Before you commit, write down your run count, your step or compute profile, and your user count, then price each option against its own meter.

ToolBrain — tool reviews, LLM comparisons, and AI workflow guides

Cross-links automatically generated from NoCode Insider.