How does this differ from Amazon Lambda?
Only read the landing page so far but it looks like Lambda with just Node support. Can someone correct me if I’m off?
Show HN: Pipedream. Develop any workflow, on any trigger, with auth and no infra
91–100 of 113 posts
Re: Show HN: Pipedream. Develop any workflow, on any trigger, with auth and no infra
#92Earlier quoted context omitted.
> or its open source counterpart n8n Unfortunately, n8n is not[1] Open Source, despite claiming to be "Open Source and so free" on their website[2]. 1: https://github.com/n8n-io/n8n/blob/master/LICENSE.md 2: https://n8n.io/
That's a shame, seems like a great product... What about the license makes this not open-source?
The “Commons Clause” License Condition they stuck on top of the Apache license: "Without limiting other conditions in the License, the grant of rights under the License will not include, and the License does not grant to you, the right to Sell the Software."
Q: Is this “Open Source”?
A: No.
Re: Show HN: Pipedream. Develop any workflow, on any trigger, with auth and no infra
#93How does this differ from Amazon Lambda? Only read the landing page so far but it looks like Lambda with just Node support. Can someone correct me if I’m off?
Hi, this is Dylan, a co-founder. It's a great question. Having built many applications on Lambda this is something I think about a lot :) .
We've found that for integrations or common automations, building on a cloud platform is too low-level. Frequently you're working with more than just a Lambda. You've got to manage a number of services that aren't core to your use case (e.g. API Gateway, IAM, Cloudwatch Logs, etc.). There's a lot of boilerplate config, and many of these services are tangential to the core logic of your app.
We operate at a higher level and just give you an execution environment to run Node.js code or stitch together pre-built actions, similar to integration platforms like Zapier. We manage the HTTP endpoint, function config, and give you built-in observability. We also provide higher-level services, like built-in app integrations and OAuth / API key-based authorization. Building this yourself on AWS can take time.
This kind of abstraction isn't great for every application, but we think it shines when you're building integrations between services.
I'd love if you had time to sign up and see how this works! It's free to use and we'd love the feedback.
Let me know if that answers your questions, or if you have any more!
Re: Show HN: Pipedream. Develop any workflow, on any trigger, with auth and no infra
#94How does this differ from Amazon Lambda? Only read the landing page so far but it looks like Lambda with just Node support. Can someone correct me if I’m off?
Your comment has me imagine a more visual, GUI-based editor on top of AWS Lambda (i.e. hooking up all sorts or internal/external events, tying workflows or multiple Lambdas together, still including a small editor for writing JavaScript, etc.)
I mean, you can write code in-line with AWS Lambda but to have an application help setup multiple Lambdas and/or integrate outside APIs would be pretty neat.
Re: Show HN: Pipedream. Develop any workflow, on any trigger, with auth and no infra
#95How does this differ from Amazon Lambda? Only read the landing page so far but it looks like Lambda with just Node support. Can someone correct me if I’m off?
Your comment has me imagine a more visual, GUI-based editor on top of AWS Lambda (i.e. hooking up all sorts or internal/external events, tying workflows or multiple Lambdas together, still including a small editor for writing JavaScript, etc.) I mean, you can write code in-line with AWS Lambda but to have an application help setup multiple Lambdas and/or integrate outside APIs would be pretty neat.
That's spot on! Take a look at our intro video for an end-to-end overview of how to use the tool: https://www.youtube.com/watch?v=ivkE26ZsyUo&feature=youtu.be .
I'd love if you had the chance to sign up. It's free to use and we'd love the feedback.
Re: Show HN: Pipedream. Develop any workflow, on any trigger, with auth and no infra
#96Possible alternative for self-hosted applications: https://github.com/huginn/huginn/
One quick glance on this: this is amazing!
If you want something that works really well with nodejs there is also Node-RED [0].
Re: Show HN: Pipedream. Develop any workflow, on any trigger, with auth and no infra
#97Earlier 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…
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.
Re: Show HN: Pipedream. Develop any workflow, on any trigger, with auth and no infra
#98Earlier 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.
It doesn't have to be right from the get go. Hard is why it should get done.
A free model doesn't really tell their business if there's actually demand and if people actually value it when supply is "infinite" when in reality it isn't.
Guess a high price with some research for similar things and lower it iteratively. Def. see what sticks.
Re: Show HN: Pipedream. Develop any workflow, on any trigger, with auth and no infra
#99It 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…
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 your reply! But it doesn't answer my question: I'm worried about how you will sustain your platform in the long run for all those free tier users.
Learning a new tool -even if it's friendly and has a community around it- takes time and effort. We want to know it will be there in the future. That's why I'm interested to know: how are you planning to keep Pipedream alive for, let's say, the next 5 years?
Re: Show HN: Pipedream. Develop any workflow, on any trigger, with auth and no infra
#100Earlier quoted context omitted.
> or its open source counterpart n8n Unfortunately, n8n is not[1] Open Source, despite claiming to be "Open Source and so free" on their website[2]. 1: https://github.com/n8n-io/n8n/blob/master/LICENSE.md 2: https://n8n.io/
That's a shame, seems like a great product... What about the license makes this not open-source?
> Without limiting other conditions in the License, the grant of rights under the License will not include, and the License does not grant to you, the right to Sell the Software.
>For purposes of the foregoing, “Sell” means practicing any or all of the rights granted to you under the License to provide to third parties, for a fee or other consideration (including without limitation fees for hosting or consulting/ support services related to the Software), a product or service whose value derives, entirely or substantially, from the functionality of the Software.
IANAL but sounds like that means if you're building apps for people on the platform, consulting, using it for clients/freelancing, or a hosted platform built on the technology then you're not licensed to do that and will need to get approval.