What Are the Implications of a Major Pricing Change for Existing Users?

1

This topic was automatically generated from Slack. You can find the original thread here.

This is a very big pricing change.
What happens with users that joined before the change?

2

Hi , existing user will have their existing pricing unchanged. You will receive an email from Pipedream regarding this.

You can read more in this message by Dylan https://pipedream-users.slack.com/archives/CN1BUB92B/p1676171602132069?thread_ts=1676171432.308179&channel=CN1BUB92B&message_ts=1676171602.132069

3

Thanks.
I’m pretty sure that this big change surprises many users because it’s very big change not just in the pricing but in the limitations as well.

It was more sense to increase from 19 to 39 or even 49 but for my opinion the if I a new user want the same like before which is 19$ now need to pay 149$ and this is very big margin

4

I agree! We have a big thread discussing it.

5

Thanks for your note and we will be sending out more communications about the new pricing plans soon. Existing customers are not impacted yet as the plans are only available for new users.

Overall, our pricing philosophy is to price our products far below the current value we are providing and do everything possible to honor the pricing of existing customers who helped us get to where we are.

The pricing you are referencing was created when we had single user accounts only, less than 100 integrated applications, a few hundred triggers and actions, Node.js only code steps, and no data stores, concurrency controls, execution rate controls, and much more.

Today, we offer the ability to collaborate and add members to your workspace, provide 1000s of integrated apps, multiple thousands of triggers and actions, code steps in multiple languages including Python, and provide data stores, concurrency controls, execution rate controls, and automatic retry for failed executions. In addition we will be launching major features including a GitHub integration, extended event history, and looping & branching later this year.

Our goal is to build a product that our customers feel is wildly underpriced for the value we are providing, and we are working every day to make that happen. If there are areas in which our product isn’t delivering, please let us know.

Lastly, we love our free customers and support tens of thousands of active free customers today. These customers often are our best promoters and provide us the best feedback. We don’t anticipate that ever changing and intend to have a robust free tier at all times.

6

Thanks for the explanation.
I’m a paid user and I brought some other paid users to Pipedream.

I agree that you’re providing lots of value and possibilities but it’s still very big margin from 19$ to 149$

7

I want to explain my thought process here a bit. I’m a paying customer and have brought a couple others as well (and contributed to many components) because I really believe in the platform. The biggest concern I have now is how much more time/effort to invest into PD at this point.

> Existing customers are not impacted yet as the plans are only available for new users.
This tells me that eventually I should expect to adopt the new pricing structure. It also makes it hard for me to recommend Pipedream to others right now.

Because Pipedream makes it so easy, I currently use it to perform dozens of quick random integrations/automations and proof-of-concepts. Since many of your customers are developers I expect this to be fairly common. Under the new pricing structure I will need to 7x my monthly budget for PD.

Additionally, the new pricing is pretty complex - with many “gates” requiring an upgrade; as @U014FPNR7FA said, it will make us “spend more time thinking about how to manage cost, rather than get stuff done”

I think “production workflow” limits and application limits for paid customers is a bit excessive. This and all the plan upgrades needed are why I said it’s starting to feel more like Zapier et al.

8

How long do I have to upgrade to the $19 package before that’s no longer an option?

9
  • A few additional thoughts:
  1. We greatly appreciate your contributions to components, and those made by members of the developer community more broadly. Material contributors should not be expected to pay the same price as a non-contributing user, and we will find a way to formalize this going forward.
  2. We are adding annual plans in the next few weeks which will reduce the costs of all the plans by ~33%. This means we will have $19 and $99 plans again, which are the same pricing tiers that we had previously. We had hoped to get this in for our initial launch but it didn’t make the prioritization cut.
  3. Lastly, as we add additional features to the plans moving forward, our hope is that users will want to move to the new plans rather than being “expected to adopt the new plans.” Automatic retry for failed executions, workflow serialization, GitHub integration, extended event history, and looping & branching are material improvements to the product. We will be sharing more detail on the options for existing users will be shared shortly.
10
  • For users who are not on a paid plan, I would expect the transition to only offering the new plans to be in the next week or two.
11

The most important feature you should implement is the ability to debug things deeply and easily. Today is very hard to debug problems if you have many workflows.

You can take some ideas from this tool which is the only thing they do:

12

We are familiar with hookdeck. What debugging functionality do you feel is missing specifically?

13

The ability for debugging.
They have very nice UI to manage all the Webhooks and I can search even some specific data I need and go directly to this Webhook and see what’s going on.

Also, I like the visual of how I can see the source and where it goes.

I can have just one source and send to 10 different Webhook in Pipedream according the filter I put.
Also, they have the option to white label Webhooks. this gives my the power of selling automation to my customers under my own brand and charge them more.

They have some more features but basically the most important thing for me that I want to see in Pipedream is the option to debug things by specific data and see all the run so I can find the problem easily.

And the white label Webhooks.