Pipedream pricing: how it worked and what it is now

Pipedream pricing changed meaning in 2026. Until recently, "Pipedream pricing" meant Workflows plans billed in credits. After Pipedream announced that Workflows and String shut down on March 31, 2027, it stopped selling Workflows subscriptions, and the pricing page now lists only Connect plans. This page explains both: how Workflows billing worked (useful for comparing costs before you migrate), what is on sale today, what happens to existing subscriptions, and how the numbers compare with n8n.

All figures are from Pipedream's and n8n's official pages, checked on October 21, 2026.

What the pricing page shows now

As of October 21, 2026, pipedream.com/pricing lists three plans, all for Connect (the API, MCP servers and API proxy for adding integrations to your own app or AI agent):

Plan	Price	Includes
Free	$0	Every feature, in development; credits for development only
Startup	$99/month billed annually, or $150 billed monthly	10,000 credits, then $0.012 per credit; 100 end users, then $2 each
Business	Custom	Annual contract, volume pricing, SSO/SCIM, SLAs and more

The page doesn't mention Workflows. If you're searching for Workflows pricing because you want to start a new workflow project on Pipedream: that's no longer possible. The shutdown notice says Pipedream is "no longer accepting signups or subscriptions" for Workflows.

How Workflows billing worked

Pipedream billed Workflows in credits, not tasks or steps (Pipedream pricing docs):

• 1 credit = 30 seconds of compute at 256 MB of memory.
• Counted per workflow segment. A segment is a linear run of steps between control-flow operators (control flow), so a branch or a delay starts a new segment.
• More memory costs more, in 256 MB steps: 1 GB is 4× the credits for the same time.
• Testing in the builder was free. Idle workflows cost nothing.
• Event sources from the public registry that trigger a workflow ran free; private custom sources were billed.
• Unused included credits didn't roll over.

Examples from the docs (256 MB):

Run	Credits
Linear workflow, 1 s of compute	1
Linear workflow, 15 s	1
Linear workflow, 35 s	2
15 s, delay, 15 s	2
3 s before a branch, 15 s inside it	2
3 s before, 15 s in the branch, 3 s after	3

The same runs at 1 GB cost 4, 4, 8, 8, 8 and 24 credits respectively, according to the same table (the last row isn't simply 4× the 256 MB figure).

The docs still refer to older plan names (Free, Basic, Advanced, Business), for example "Advanced plan or higher" for File Stores and automatic retries. Those plans are no longer listed on the pricing page, and we don't quote their old prices here because the official page no longer shows them.

What happens to your subscription

From the shutdown notice:

Situation	What happens
Any active subscription	Stays active until March 31, 2027, then cancelled automatically with a prorated refund
Monthly plan, want to stop earlier	Cancel yourself in account settings
Annual plan, want to stop earlier	Contact support for early cancellation and a prorated refund
Data	All Workflows data deleted by April 30, 2027
Connect	Not affected; settings and credentials stay

Plan the end date: the auto-cancellation happens on the same day your workflows stop. If you migrate earlier, cancelling early saves the remaining months.

Pipedream vs n8n: pricing models

	Pipedream Workflows (until 2027)	n8n Cloud	n8n self-hosted
Billing unit	Credits: 30 s compute per segment	Workflow executions, regardless of steps	None for Community edition; Business license priced by executions
Long-running steps	Cost more	Same price per execution (within plan's max duration)	Your server
Many steps	No extra cost	No extra cost	No extra cost
Branches	Each segment billed separately	One execution	–
Sub-workflows	–	Don't count toward execution limits	–

n8n's pricing page (annual billing, October 21, 2026) lists Starter at €20/month with 2,500 executions and Pro at €50/month with 10,000 executions on Cloud, and Business at €667/month with 40,000 executions, self-hosted only. n8n's docs state that sub-workflow executions don't count toward plan execution limits (sub-workflows).

What this means in practice:

• Short, frequent workflows (webhook in, two API calls, done): Pipedream charged about 1 credit each; n8n Cloud charges 1 execution each. Compare your monthly run count with the n8n plan's execution allowance.
• Long or memory-heavy workflows (file processing, slow APIs): Pipedream charged more per run; n8n Cloud charges the same per execution but caps run time per plan (5 minutes on Starter, 40 on Pro, per the pricing table).
• High volume with npm-heavy code: self-hosted n8n usually wins, and it is the only n8n option where Code nodes can use arbitrary npm packages.

Our n8n Cloud vs self-hosted guide covers the other differences.

Estimating your n8n cost from Pipedream

1. In Pipedream's usage dashboard, note monthly executions per workflow (not credits).
2. Add them up across workflows you'll migrate. Workflows you'd split into sub-workflows count once.
3. Compare with the n8n Cloud plan allowances, or size a self-hosted server.
4. Check run time: any workflow that runs longer than the Cloud plan's maximum duration needs Pro or self-hosting.
5. Check code: steps that import npm packages beyond crypto and moment need self-hosted n8n.

Migration cost

Moving the workflows themselves is the other cost. Rebuilding by hand takes roughly as long as building them did. Our converter turns the Pipedream export into n8n workflow JSON and tells you up front what converts, what needs review and what stays manual. The report and 1 workflow are free. Full export: $3 per workflow, $19 minimum — coming soon. Upload the export to the converter, check single steps with the code step checker, and follow migrate Pipedream to n8n for the full process. If you only use Connect, see Pipedream Connect after the shutdown; nothing changes for you.

Not affiliated with Pipedream or n8n.