This topic was automatically generated from Slack. You can find the original thread here.
Just noticed the new pricing on the website 
Iâm curious, what are âproduction workflowsâ and is there going to be a limit on âconnected accountsâ?
Also, will users on the existing pricing be grandfathered in?
Yes, existing users will keep their current pricing. Weâll communicate about that via email (with information specific to your plan) and here.
Yeah I think we can make âproduction workflowsâ more clear. Theyâre workflows set to an active state. If you disable, archive, or delete a workflow, that wonât count towards the total.
Oh interesting.
I know youâre running a business and need to generate profits.
My personal feedback after skimming through the new pricing is that itâs starting to look more like Zapier 
It should still be significantly less than Zapier for comparable features / volume but would love to hear more about that first reaction. Is it the number of distinct plans, the price, etc. thatâs the issue? Would love to hear all the initial thoughts.
A price increase is understandable (although itâs a 3x increase on the âProfessional Planâ which now becomes âBasicâ).
One of my favorite things about Pipedream is how easy it is to setup a quick workflow even if it will only run a few times a month (and maybe not for a few months).
Now I will need to prioritize which workflows and accounts I want to consider âproductionâ.
I understand to have a production workflow limit such as that on the free plan, definitely doesnât belong on a paid plan (the simple invocation credit system makes sense). Same thing with connected accounts. I also understand needing to drop the included invocation on the free plan.
Obviously having a bunch of plans is just confusing to the customer (previous flow of a free, pro and team plan was easier to understand).
Also when I say âlook like Zapierâ I mean mostly with the seemingly nickel-and-diming.
I stopped using Zapier when I found Pipedream because I realized itâs a far superior product and pricing.
Really appreciate the detailed feedback!
> I understand to have a production workflow limit such as that on the free plan, definitely doesnât belong on a paid plan (the simple invocation credit system makes sense). Same thing with connected accounts. I also understand needing to drop the included invocation on the free plan.
So is the limit on workflows and connected accounts on the Basic Plan (first paid plan) concerning?
> Also when I say âlook like Zapierâ I mean mostly with the seemingly nickel-and-diming.
Is it the number of different âgatesâ that trigger a plan upgrade, or something else? We would definitely consider simplifying the plans to make them easier to understand and avoid the ânickel-and-dimingâ.
Yes, all of the above 
I speak for myself (although Iâm sure a lot of customers agree)
I enjoy the simplicity of the previous pricing and itâs pretty clear if/why/when I would incur further charges (if I had lots of invocations).
Now itâs much more fluid and difficult to understand exactly how much I would need to pay based on my current plan and usage as well as forecast for the future.
Iâm curious what other customers have to say about the new changes, when were they released? Has there been any other feedback just yet?
yeah makes sense, thanks for sharing. We just released the pricing, so the feedback is appreciated.
Havenât studied the detail yes, but at first glance Iâm with Zalman on this, especially with respect to it âfeelingâ more like Zapier, and tending to make folks spend more time thinking about how to manage cost, rather than get stuff done ⌠either every minute âŚor just now and then.
for context, this is the old pricing (per invocation price is 4X on the basic plan)
Yes, I am only new to Pipedream and I was super excited to use this as alternative to Zapier. I hadnât started the switch over, I have an account and it shows the old pricing rather than the new pricing. I had some questions around how much longer will we have access to the âold pricingâ?
To make the switch with the new pricing it would mean I will now pay more for Pipedream than in Zapier. Yes for sure I dont get 10,000 credit per month. But I dont think I would ever need that much - so its a huge jump from 100 to 10,000 credits.
I understand the need to charge differently, but it seems like quite a fair jump in price.
If anyone could confirm how long with have access to the old pricing that would be amazing.
If you signed up before and have access to the old pricing, you can upgrade to one of the older plans. Appreciate the feedback, sharing with the team.
Had a little closer look at before and after and would say that itâs the small âpower usersâ that might hurt most. The Basic plan is a 50% increase (i.e. matching Zapier?) with quite tight limits on production workflows which will impact people doing lots of little, low-frequency stuff (such as showing random cat pictres on your 0.000002K desktop TV )
Next step up is a big one and conflates teams size (N>1) with overall volume/intricacy. Holding back features such as auto-retry seems a little niggardly too (as opposed to N>1 teams features which make sense
exactly! Keep in mind, itâs a 50% increase for half the invocationsâŚ
This is maybe my first time actually posting on this forum, but I really wanted to chime in on this.
When I looked at the pricing page today, I was really startled by how different it is from what I remembered. Like someone else said, my reaction was âwait, this is just the same as Zapierâ - and then, âin that case, why did I even bother signing up before?â
Iâm not exactly an active user right nowâI donât have any workflows running yet, just a handful of WIPsâso I donât frequently pay attention to whatâs going on here.
But when I found Pipedream a year or two ago, the entire reason I joined was to avoid the limitation on how many workflows and connections you can have. That limitation is the reason I never bothered using Zapier and all its no-code peers: I expect to need more than 5 workflows for what I want to do, so Iâm not going to put the energy into learning how to use a tool that Iâll outgrow right away.
Because free plans arenât a âtrialâ for me, theyâre my only option. Iâm not using automation for work, Iâm using it to manage my personal life and collect âquantified selfâ data. I live on disability benefits and thereâs no way for me to afford a monthly subscription for an automation service, period. Right now Iâm seriously considering, instead of learning how to finish making my WIP workflows on here, abandoning Pipedream and putting that energy into learning how to build a Raspberry Pi automation server with n8n or something instead.
(And sure, if I knew from the start that I can never pay a subscription, then maybe I should have known to just start by expecting to self-host my automations in the first place, maybe Pipedream never was meant for me to begin with.)
I fully expect and understand that free plans need to have limits in order for the site to survive, but the previous model where it was based just on the number of invocations felt much more fair. Limiting the number of workflows and connections feels more like a gimmick to annoy users into paying more, whereas limiting the invocations feels like a rational way of just asking people to pitch in for the âcost of materialsâ that they use.
Had a little closer look at before and after and would say that itâs the small âpower usersâ that might hurt most. The Basic plan is a 50% increase (i.e. matching Zapier?) with quite tight limits on production workflows which will impact people doing lots of little, low-frequency stuff (such as showing random cat pictres on your 0.000002K desktop TV )
Exactly. My intended use case is many different low-volume workflows: send my Fitbit data to Notion once a day, create a daily note, summarize some data once a week, etc. (My intention was lots of âpull info from all these scattered places into Notionâ, much of which could be run just once a day.)
I think part of why I felt put off by this change is that Pipedream used to give me a vibe of âhey we made this cool thing for our fellow devs, we hope it can help youâ and the monetization strategy just felt like âitâs here for everyone, but if you want to use a lot of resources then youâre gonna have to help us pay to make it happen.â Now it feels like a product youâre trying to market and upsell. (Did you recently update the landing page too? Because that also seemed to give me a more âmarketingâ vibe today than I had remembered.) It doesnât feel like itâs âhere for everyoneâ anymore. And I donât know, maybe you did mean this as a business venture from the start and itâs just me who didnât pick up on it, but I think that vibe is part of what drew me to Pipedream in the first place.
In short, if this were the pricing model when I first found Pipedream, I never would have even bothered trying it.
Also, unless Iâm mistaken, it doesnât seem like Pipedream sent out an email warning users that the pricing was about to change so much, which strikes me as pretty inconsiderate.
Hi @caesiumtea ,
Really appreciate the detailed feedback. Iâm sharing with the team and will respond to some specific points as we process. I wanted to clarify one thing:
Also, unless Iâm mistaken, it doesnât seem like Pipedream sent out an email warning users that the pricing was about to change so much, which strikes me as pretty inconsiderate.
Existing users will be able to keep their plan. The new pricing only affects new users. But since there are clearly a lot of users in your boat â free users who may later upgrade to a paid plan â weâre working on the communication for exactly how the pricing changes will affect you and what this means for your account. There is a lot involved in this â I wish I could invite you to be a fly-on-the-wall in the meetings we have discussing our comms / rollout plan 
. We put a lot of effort into this and think deeply about how our changes will impact our users, we just need to get that communication out.
1 Like