Live data from Hacker News

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

pipedream.com

101–110 of 113 posts

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

#101

Earlier quoted context omitted.

Start charging immediately, and put up a real pricing page with SLAs. Find out as soon as possible if people will actually value this enough to pay for it. This provides a signaling of value, creates a real business relationship, and directly contributes to the lifespan of the vendor.

Not to diminish your point but that’s really hard to get right. Most early stage startups have absolutely no idea what their product is worth.

But that is my point. You won't know until you do it. It's a constant experiment, you just have to start somewhere.

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

#102

Earlier quoted context omitted.

Hi, Dylan, a co-founder here. Deploying workflows from source via CLI or your CI/CD pipeline is in the works! We want you to host workflows on Github / Gitlab and be able to deploy them using your standard process. Feel free to reach out to me directly if you'd like more information and I can let you know when we're testing this. dylan [at] pipedream [dot] com

Speaking of which, it's always overwhelming learning new tools. I know I can benefit from this, but at the same time I'm not sure I can risk trying it out given the time it will take to experiment and learn. I'd be using triggers based off Github commits and merges, but I don't see any specific examples for that and it's not exactly clear how the tutorial on the home page would translate to what I want to do so I cur…

I also think the name is fabulous - quite surprised the domain name was available!

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

#103

Earlier quoted context omitted.

Start charging immediately, and put up a real pricing page with SLAs. Find out as soon as possible if people will actually value this enough to pay for it. This provides a signaling of value, creates a real business relationship, and directly contributes to the lifespan of the vendor.

Not to diminish your point but that’s really hard to get right. Most early stage startups have absolutely no idea what their product is worth.

They could go the AWS route, start high and decrease prices.

Also they could combine this with discounts, such as if someone preallocates capacity for X month, they get f(X) % discount.

They should build a core customer base. Solicit feedback about what niche feature they would happily pay for.

For example here's a GitLab issue that I think people would (might?) use: https://gitlab.com/gitlab-org/gitlab/issues/15536 (provide a "lock service" or a queue with max concurrency gate and launch pipelines / jobs)

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

#104
post #46
post #32

Earlier quoted context omitted.

Haggy - we have no plans to charge individual developers for low volume workflows that fit within our defined constraints. Our revenue efforts will be focused on enterprise use cases. I have no desire to be hand-savvy so please ask whatever questions you have and I will do my best to clarify.

How would you envision supporting 10X the usage that you have today 1 year from now if all that usage is falling under your "free" plan constraints?

More throttling?

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

#105
post #25

Possible alternative for self-hosted applications: https://github.com/huginn/huginn/

Few others:

1. https://www.flogo.io/ (Go)

2. https://n8n.io/ (Recently featured in HN https://news.ycombinator.com/item?id=21192132 )

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

#107
post #30

What security measures are in place to deal with malicious code from other users?

Since you guys haven't answered, I'm going to assume there is no such security in place.

Hi, this is Dylan, a co-founder and engineer. I'm sorry we didn't get back to you sooner. It's tough to respond to every single comment on a Hacker News thread and we've been quite busy with launch. Hope you can sympathize.

Your code runs in its own Node execution environment and VM, completely isolated from other users' code.

Happy to answer any other specific questions you have! Feel free to reach me at dylan [at] pipedream [dot] com .

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

#108

Earlier quoted context omitted.

Thank you! I completely empathize with the time involved learning new tools. I'm happy to create a tutorial specific to your use case. We've built a few workflows to process Github events and I'd love to show you how this works end-to-end. Is there anything specific you'd like to do with the commit / merge events, just so I make sure the tutorial targets your use case? Feel free to reach out directly if you'd like to…

Thanks for the response and involvement in this thread, it really shows how committed you guys are to providing a great user experience. The specific use-case I have in mind is that when a commit made I'd want to run various checks on configuration files in the repo to make sure specific conventions are followed and that certain file references exist. Upon a merge I'd like run a build process and send the build files…

The easiest way to run code in response to Github events is using Github's built-in webhooks for a repo. I made a video showing you how to set that up to forward events from your repo (e.g. every time you merge a branch to master), then run code on Pipedream in response:

https://www.youtube.com/watch?v=9ZGNP1-1vyg&feature=youtu.be

You can load the workflow I created for the video here:

https://pipedream.com/@dylburger/template-workflow-to-proces...

and press the Fork button in the top right to create a copy of it in your own account. You can modify that copy and run it for free.

The video isn't perfectly polished and I made a few mistakes, but we've built Pipedream to make it easy to debug your workflows, too, so I hope the mistakes help you understand part of its power!

A couple of notes on your specific use case:

* There's no webhook event for new commits. A PR (like I show in the video) or a push might be the best event to listen for. You can then run Node code to list commits associated with that push. See the API docs for commits here: https://developer.github.com/v3/repos/commits/ . * I wasn't sure specifically what build process you wanted to run, so I end the video reviewing how to add new steps to the workflow and walk through a few options: you can run any Node.js code or any of our pre-built actions. You have access to the /tmp dir on Pipedream and can use a package like child_process [1] to spawn some commands if you need to run anything on the shell. Unfortunately you don't have access to a full shell but let me know if what we provide works or doesn't — we'd love the feedback.

Let me know if that helps or if you have any questions!

[1] https://www.freecodecamp.org/news/node-js-child-processes-ev...

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

#109

Earlier quoted context omitted.

Start charging immediately, and put up a real pricing page with SLAs. Find out as soon as possible if people will actually value this enough to pay for it. This provides a signaling of value, creates a real business relationship, and directly contributes to the lifespan of the vendor.

Not to diminish your point but that’s really hard to get right. Most early stage startups have absolutely no idea what their product is worth.

If everyone avoided doing hard things, our world would be a lot worse off.

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

#110
post #16

Earlier quoted context omitted.

If I can run workflows for free, how are you making money?

We believe anyone should be able to run simple, low-volume workflows at no cost, sharing their workflows with the public so everyone benefits from the work of others. We also want to foster a positive community where people feel good about sharing their work and where everyone can learn from one another. In the future, we may offer features available on paid tiers which would be logical enterprise features such as si…

Thanks for the response! I wasn't trying to rain on your parade, but having a reasonable revenue model in place does help give some confidence that 1) you're going to be around a while and 2) you're not selling data I don't want you to sell.
Post reply on HN