Show HN: Pipedream. Develop any workflow, on any trigger, with auth and no infra

Post by tmikaeld » Wed, Oct 16, 2019, 5:54 PM UTC

haggy wrote: post #24

tmikaeld wrote: post #20

The usual question, how they monetize the service? It's answered here[1], along with limitations[2]: - 100kb max body-size. - Rate-limit at 10 requests per second - 10 seconds per execution for HTTP triggers, and 30 seconds for cron triggers - 192 MB of memory for your code and libraries during workflow execution - 512 MB of disk in the /tmp directory. [1] https://docs.pipedream.com/pricing/ [2] https://docs.pipedrea…

This isn't an answer to how they might monetize this service and quite frankly I've seen the OP/Co-Founder post their "answer" to this question on multiple other comments and it's extremely hand-wavy. I currently have little to no faith that this product isn't going to leave anyone that uses it stranded in a year or so when they have to shutdown due to lack of revenue.

Post by todsac » Wed, Oct 16, 2019, 5:59 PM UTC

tmikaeld wrote: post #31

haggy wrote: post #24

Earlier quoted context omitted.

This isn't an answer to how they might monetize this service and quite frankly I've seen the OP/Co-Founder post their "answer" to this question on multiple other comments and it's extremely hand-wavy. I currently have little to no faith that this product isn't going to leave anyone that uses it stranded in a year or so when they have to shutdown due to lack of revenue.

I really don't like it when new services leave out the pricing and hide it under "contact us". Testing and trying something new requires time and effort, which is limited, especially for companies that would be interested, if pricing/future isn't crystal clear, why make the effort?

Post by edoceo » Wed, Oct 16, 2019, 6:02 PM UTC

codezero wrote: post #28

cpursley wrote: post #21

Earlier quoted context omitted.

So basically, people are going to build on top of your service and if yall don't figure out a revenue model, you'll need to close down shop, leaving people scrambling to migrate somewhere else... No thanks, I've been there before. You'd be better off just charging from the get-go. Otherwise, this should be 100% open source.

From your past experience, do you have anything constructive to tell this new team on how they can attempt to build a business without knowing the future that would make you more comfortable using it? I ask because I see a lot of these dismissive comments on HN which end with "open source it" - and that doesn't seem like a super constructive piece of advice to a new startup team. FWIW, at my current company, an analy…

Post by codezero » Wed, Oct 16, 2019, 6:15 PM UTC

edoceo wrote: post #35

codezero wrote: post #28

Earlier quoted context omitted.

From your past experience, do you have anything constructive to tell this new team on how they can attempt to build a business without knowing the future that would make you more comfortable using it? I ask because I see a lot of these dismissive comments on HN which end with "open source it" - and that doesn't seem like a super constructive piece of advice to a new startup team. FWIW, at my current company, an analy…

I think the point is: monitize now to reduce risk

Post by pritambaral » Wed, Oct 16, 2019, 6:16 PM UTC

zimmund wrote: post #12

It looks like an interesting alternative to Zapier (or its open source counterpart n8n [1]). As a potential user, before even trying the tool I'd like to know how are you planning to monetize it. Free sounds awesome, but you'll get to a point where it costs you actual money to keep all this working. I don't want to waste my time creating pipelines in a tool that won't exist in a year or two -or that will become paid…