I wish the workflow engine itself was open source too as it would be a better alternative to n8n.
1. We plan to publish an execution environment (as a container) that simulates the core Pipedream runtime. You could run this locally or as a container on whatever container service you'd like. 2. We get a lot of requests for a fully-self-hosted / open-source version, and we're considering how to approach that as well.
Please follow the issues below, and let us know if you have any more feedback!
[1] https://github.com/PipedreamHQ/pipedream/issues/1635 [2] https://github.com/PipedreamHQ/pipedream/issues/954
My other pipedream in addition to this would be multi tenancy (including integrations).
A perfect world scenario is a drop in multi tenant zapier alternative that enables SaaS providers to either create workflows for their users so all they need to do is authenticate integrations for the most part or allow for them to build their own workflows from scratch.
I realize this is probably out of scope of the services aim but it doesn't hurt to throw it out there since all of the alternatives that exist are sorely lacking in various ways.
If you're interested, join our community and you'll get early updates on stuff we're working on (GitHub integration, TypeScript / other new language runtimes, etc.): https://pipedream.com/support
Still in the idea phase, but let me know if that resonates.
Pipedream v1 ran on Lambda, but this post is touted as "AWS Lambda alternative", have you moved off the AWS Lambda platform?
I was curious how you added support for other languages, was it in the same way that you built-in support for Node.js? Where all the code gets effectively built into a single Lambda function and proxied?
For people who want to call OpenFaaS workloads from Pipedream, that's possible over HTTP and Pipedream makes that relatively simple. One thing I think they've really nailed is the OAuth integration, it just makes that whole painful flow a lot more convenient. I also like the editor and the way it infers what kind of input will go into the next step in a workflow.
Alex
We build our own containers and still run them on Lambda. The container base image contains the necessary language runtimes so that we can execute both Node.js and e.g. Python in the same workflow.
Do you think it would make sense to add an OpenFAAS integration to Pipedream? Then it would show up when users searched for it in workflows, and have a dedicated page at https://pipedream.com/apps . Even if we just end up wrapping HTTP requests to kick off a function, we've found it's helpful because users are often searching for FaaS platforms by name when they want to integrate with them in a workflow.